I have a quest that is not 'StartGameEnabled', and it seems that I cannot get it running. I have a dialogue line ingame that should start it, but it does not. The papyrus fragment includes a 'SetStage' line to get it moving, a 'SetObjectiveDisplayed' line to direct the player, and a 'MyQuest.Start()' line to start it. The script is firing, as the other half is to end the current quest. Yet, the quest refuses to start. No alias's are filled, the stage is still 0, it's not Enabled, and it's state is 'Stopped'.

Am I missing something here? It should be as simple as setting the stage to kick it into motion, but I even have the 'Start' command and it wont start. I can also try to start it via console ingame, but nothing happens.

Thanks,
Alexander J. Velicky

From reading some of the threads here about the story manager, a quest won't start if its aliases aren't filled. You're not starting your quest through the story manager, but maybe it still applies. Can you try checking "Optional" for your aliases and seeing if that will start the quest?

I changed them to 'Specific Reference' which FORCED them to fill, and it now starts; which means that was the problem. Thanks!

Just bear in mind that using "Specific Reference" locks them in memory permenantly:

http://www.creationkit.com/Quest_Alias_Tab

A little bit related to this, it's a problem that had me pulling my hair out for ages.
If you try to point an alias to a Unique Actor which "starts dead", the alias fails and hence your quest won't start properly.
Here too the solution is using Specific Reference instead of Unique Actor.

Yeah, it's by no means a perminant solution but it prooved that alias's failing to fill was the problem.

Also, it seems that if you make an alias a 'specific ref' then save and play or something; then reopen the CK, THEN set it to Unique Actor that it will fill properly. I'm very slowly converting all my actor alias's to Unique Actor instead of Forced ref... How weird...

For the last bit, did you test it with a clean save? Because if you did, that really is weird.

Just to clarify, you're trying to start Quest B in a dialogue assigned in Quest A. You set the stage of Quest A to say 10, where in that stage papyrus script box you're trying to start quest B? As long as you have a quest property assigned to quest b, questbproperty.start() should be all you need. Is the objective display part of quest B?




Make sure your unique actor doesn't have the cleanup script attached.

You could mark it as optional, and then have your quest script register for update and check the NPC periodicallyi and when it's alive again, Force it into the alias.

if you are re-testing off of the save game and not coc'ing from the main menu, it probably means your save game is corrupting your test (re-introducing saved data from previous version), unless this is some really strange bug (and even if it is, i would not trust it).

also Unique actor will not fill an alias unless it has a Persistent Location set in its reference

What does this mean? Could you elaborate a bit please?

when you place your actor in the world as a reference, you can double click on it to edit. there is a tab called Persist Location. if you set this to a location specific to your actor, it can be filled as a Unique Actor alias. I believe what this does is it only loads your reference alias into memory for that specific location only.

a forced refernce loads the reference permanently into memory at all times, even long after the quest is finished.

Isn't that what the "Allow Dead" checkbox is for?

By the Nine this may be what I was missing! I'll try this to see if I can then just fill unique actor alias's!!!

Excellent, thanks for explaining that. Very interesting!

Good point. Quest aliases confuses me a bit so I dunno hehe