Quest Stage 255

[JanitorsLOL]

Is this some kind of error state for a quest?

 

Quest cr09 "striking the heart" bugged out for me in my game. No quest marker was given and the silverblood leader was not at the written location (the location described was in mainland skyrim and not in any dlc location). Im just going to assume there was a conflict with a mod and with the data needed to spawn the leader. Only mods which may conflict are the latest versions of the unofficial skyrim patch, high level enemies sse, and morrowloot ultimate, but with the patch which removes the encounter zones of MLU SSE

 

The quest is locked in stage 255 when looking at the stages in console, and 255 is not listed as a quest stage for this quest on any website, but does list for its stages within the console. and trying to run setstage or resetquest in the console does absolutely nothing. Yes im using proper syntax and including the proper quest id with the command. The quest is just stuck and wont move. However I can run completequest which does work but im wondering if this is ok or if it will cause any problems?

There is no information about this on the internet, about a quest which wont move at all through console and is also in stage 255

[JanitorsLOL]

Im just going to assume this is an error stage and running "completequest cr09" will be ok.

Im not sure what kind of error would return when the game runs this quest scripting since scripts are a mystery in skyrim. Might be a conflict with SKSE, who knows.

 

I dont think running completequest is going to change whats already been done, so its probably ok.

Would be nice if somebody could describe whats going on here

[JanitorsLOL]

Also just considered how stage 255 can be sort of a system designation for when the quest is operating, or waiting for something, or hasnt completed running the actual scripts for the quest, which would explain the inability to change anything, but again im unsure. Though given how the game is behaving, its probably possible.

[nt5raham]

Just in general, stage 255 is a valid stage for quests. Specific to CR09, stage 255 is where the quest rests once completed and stopped or no longer running (not shown in the Fandom Wiki). You can use sqv cr09 to see if it is stopped or running.

 

Completequest is provided as a development tool and not recommended for use in an ongoing game. It can have long-term ill effects because, while it may clear the quest from your journal, other NPCs (like Aela) may have no idea that the quest has been completed.

 

Just for general information, frequently when a quest is "stuck" it is waiting for something. One of the most common causes of a quest getting stuck is nothing more than the player not being patient enough to wait for it. An impatient player may start tinkering around under the hood and make matters worse. If the load order is script heavy, it may simply be waiting its turn to be serviced among the other scripts in the game; in this case attempting console commands will not help. Of course there are triggers, like reaching a specific location, speaking with an NPC, etc., but if it is not something simple like that then the best alternative may be to go back to a clean, unadulterated save before the quest was assigned.

[JanitorsLOL]

Just in general, stage 255 is a valid stage for quests. Specific to CR09, stage 255 is where the quest rests once completed and stopped or no longer running (not shown in the Fandom Wiki). You can use sqv cr09 to see if it is stopped or running.

 

Completequest is provided as a development tool and not recommended for use in an ongoing game. It can have long-term ill effects because, while it may clear the quest from your journal, other NPCs (like Aela) may have no idea that the quest has been completed.

 

Just for general information, frequently when a quest is "stuck" it is waiting for something. One of the most common causes of a quest getting stuck is nothing more than the player not being patient enough to wait for it. An impatient player may start tinkering around under the hood and make matters worse. If the load order is script heavy, it may simply be waiting its turn to be serviced among the other scripts in the game; in this case attempting console commands will not help. Of course there are triggers, like reaching a specific location, speaking with an NPC, etc., but if it is not something simple like that then the best alternative may be to go back to a clean, unadulterated save before the quest was assigned.

 

Yes I saw the quest had been stopped. But theres no obvious reason for it. Probably a mystery error since the game doesnt actually tell you whats going on with script. There was no rushing in regards to waiting for the quest to start working. It had been perpetually broken for well over 6 real life human hours of gameplay.

And running "completequest" on something which is in stage 255 is probably the only valid use for that command. Probably.

[nt5raham]

 

 

Yes I saw the quest had been stopped. But theres no obvious reason for it. Probably a mystery error since the game doesnt actually tell you whats going on with script. There was no rushing in regards to waiting for the quest to start working. It had been perpetually broken for well over 6 real life human hours of gameplay.

And running "completequest" on something which is in stage 255 is probably the only valid use for that command. Probably.

 

Did Aela acknowledge successful completion of the quest? If so, you're home free.