Multiple Custom Quest Not Starting

[portowulf]

I'm having trouble with getting custom quests to work:

 

TLDR: Either the stage never changes, or the stage does change, but the script fragment doesn't run. (full description to follow)

 

Attached, Quest Data tab

I have it set to Start Game Enabled

 

Attached, Quest Stages tab

I have stage 10 set to Run On Start

I have fragment as SetObjectiveDisplayed(10)

 

Attached, Quest Objectives tab

I have Display text, and the matching index of 10 (see papyrus fragment above)

 

Attached, Quest Aliases

I have aliases set to 'optional'

 

Note:

I'm using a fresh save with NO mods. Each time I load in, it mentions that achievements will be disabled, so I know there's no mods conflicting, and there's no old quest data on this save.

 

So I have a quest that starts when your game starts. It should start at stage 10, and display the objective; but it doesn't.

If I use console commands to get the stage, it says it's stage 10, but still nothing displays.

Any help would be appreciated.

[DieFeM]

I think the problem could be in the settings of the aliases, if you could post screenshots of the aliases it would help to determine the issue.

[werr92]

By the names for the aliases, it seems to me that you're using some vanilla characters. That's important. And... to the point.

 

When you guys do quests, you need to understand the underlying mechanics of it. I see on the regular basis, that for some reason many people omit this part and dive right into further quest building. This leads to the sutuation, when they try to hunt down issues in the wrong place.

 

LOGIC. When the Game loads, it initializes your quest and ALL OF THE ALIASES in it (because you have it Start Game Enabled). Then it tries to fill out the aliases stricktly in the order provided by you (top to bottom). If it fails to fill any alias, the quest won't fire and run. Thus, failure. Now, when can it fail to fill an alias? The most common reason (feels to me, this is exactly your case) is when the reference you're trying to fill this alias with, is already in use by some other quest or quests. When this happens, your quest is unable to have this reference for itself, because it is already reserved for another quest(s). Hence, it just leaves this alias unfilled and moves on to the next one. But, from the explanation above, you can get, this quest won't "just work" anymore.

 

REASON OF FAILURE. Alias not filled. Quest not really started. Moreover, when you mark an alias as 'Optional', it simply means, the Game can leave it unfilled if no condition match. But when you tell system to show the alias on Player's map, it simply doesn't know where to place marker at, as the alias itself is empty and doesn't contain reference it could appeal to.

 

SOLUTION. Since the reference you want to use seems vanilla (see the beginnig of this post), it most likely is already reserved by other quests. You must allow your quest to use such reserved refs. Toggle 'Allow Reserved'. Your quest is of Start Game Enabled type, this box should be grayed out. To tick it either temporary uncheck Start Game Enabled, reopen quest and tick the box, or press Shift+Ctrl+R.

 

Good luck.

[portowulf]

By the names for the aliases, it seems to me that you're using some vanilla characters. That's important. And... to the point.

 

When you guys do quests, you need to understand the underlying mechanics of it. I see on the regular basis, that for some reason many people omit this part and dive right into further quest building. This leads to the sutuation, when they try to hunt down issues in the wrong place.

 

LOGIC. When the Game loads, it initializes your quest and ALL OF THE ALIASES in it (because you have it Start Game Enabled). Then it tries to fill out the aliases stricktly in the order provided by you (top to bottom). If it fails to fill any alias, the quest won't fire and run. Thus, failure. Now, when can it fail to fill an alias? The most common reason (feels to me, this is exactly your case) is when the reference you're trying to fill this alias with, is already in use by some other quest or quests. When this happens, your quest is unable to have this reference for itself, because it is already reserved for another quest(s). Hence, it just leaves this alias unfilled and moves on to the next one. But, from the explanation above, you can get, this quest won't "just work" anymore.

 

REASON OF FAILURE. Alias not filled. Quest not really started. Moreover, when you mark an alias as 'Optional', it simply means, the Game can leave it unfilled if no condition match. But when you tell system to show the alias on Player's map, it simply doesn't know where to place marker at, as the alias itself is empty and doesn't contain reference it could appeal to.

 

SOLUTION. Since the reference you want to use seems vanilla (see the beginnig of this post), it most likely is already reserved by other quests. You must allow your quest to use such reserved refs. Toggle 'Allow Reserved'. Your quest is of Start Game Enabled type, this box should be grayed out. To tick it either temporary uncheck Start Game Enabled, reopen quest and tick the box, or press Shift+Ctrl+R.

 

Good luck.

 

The first Alias, (POI) was a location reference that went unused. I deleted it to no effect on the issue.

The second Alias (A2Opening) is a custom reference of a custom trigger I placed in the world. I did the 'Allow Reserved" and still no fix.

[portowulf]

I think the problem could be in the settings of the aliases, if you could post screenshots of the aliases it would help to determine the issue.

[DieFeM]

There's no reference selected, click on [select Forced Reference] to pick your trigger from the render window.

[portowulf]

There's no reference selected, click on [select Forced Reference] to pick your trigger from the render window.

 

I added the forced reference; quest still not starting

[DieFeM]

I don't see why it wouldn't start, so the only assumption I can do is that you are loading a saved game where this plugin was previously loaded and the quest is already started on a failure state, if this is the case then just load a previous save where you didn't had this mod loaded.

[portowulf]

I don't see why it wouldn't start, so the only assumption I can do is that you are loading a saved game where this plugin was previously loaded and the quest is already started on a failure state, if this is the case then just load a previous save where you didn't had this mod loaded.

 

I'm trying with a new save; it even gives the warning, upon loading, that achievements will be disabled since I had no mods before.

If I use console commands, it says the quest is stage 10, but nothing shows up.

 

It's driving me crazy, 'cuz everything looks like it's right, but it still doesn't work. :(

[DieFeM]

Try to set the quest type in the quest data tab to "side quests".