 Issue Data
|
|
||||||||||||||||||||||||
Issue #34509: dunRannveigQST (0005160C): attempting to start event scoped quest outside of story manager
This should only be possible if dunRannveigQST didn't start, and I can't see any way that would happen, Sild is even Allow Reserved and 000A88C2 has DisableWhenDone defaulting to True.
The console (SQV) indicates that it's still running and is at stage 30. There are 10 aliases actively being held by the quest. This obviously, like other quests I've reported not shutting down, shouldn't be happening. It's probably engine related, specifically the notorious dialogue bug that's been causing problems for years now.
The SQS command shows the following:
Stage 0: 1
Stage 10: 0
Stage 20: 0
Stage 25: 1
Stage 27: 0
Stage 30: 1
That's really all of the information I know to give you. The dungeon quest played out like it always has. I don't think there was anything I did out of the ordinary.
The SQS command shows the following:
Stage 0: 1
Stage 10: 0
Stage 20: 0
Stage 25: 1
Stage 27: 0
Stage 30: 1
That's really all of the information I know to give you. The dungeon quest played out like it always has. I don't think there was anything I did out of the ordinary.
Comment #2 Jan 26, 2025 9:57 pm
Edited by BlackPete on Jan 26, 2025 10:00 pm
The quest should shut down once you kill Sild, USSEP has a script that does that.
Comment #3 Jan 27, 2025 12:38 am
Edited by DarthVitrial on Jan 27, 2025 12:39 am
Yeah. For whatever reason it didn't in my game. I went back to the dungeon and Sild is dead but his corpse is still there, which is obviously because the quest is still running.
The SV command shows the following output on Sild's RefID:
--- Papyrus - Alias Warlock on Quest dunRannveigQST (0005160C)
USKP_SildAliasDeathScript
Script state = " "
No variables
No papyrus scripts attached
It's entirely possible that this was a fluke and there's no possible explanation for it happening. If by some chance it would help to look at my game save, let me know. Otherwise, it sounds like everything that can be done has already been done to prevent it.
The SV command shows the following output on Sild's RefID:
Spoiler:
--- Papyrus - Alias Warlock on Quest dunRannveigQST (0005160C)
USKP_SildAliasDeathScript
Script state = " "
No variables
No papyrus scripts attached
It's entirely possible that this was a fluke and there's no possible explanation for it happening. If by some chance it would help to look at my game save, let me know. Otherwise, it sounds like everything that can be done has already been done to prevent it.
Comment #4 Jan 27, 2025 4:54 am
Edited by BlackPete on Jan 27, 2025 4:57 am
No papyrus errors from USKP_SildAliasDeathScript when you killed him?
No, there wasn't any mention of that script. It was only the error in the original post.
I went back to a previous save before going to the dungeon to test it again. Right after killing him the quest shut down immediately like it's supposed to with no errors in papyrus. Something weird must have happened originally that caused the USKP script to not do its job. The game engine has been known to do this kind of thing in rare cases when there is script lag. Anyway, I can't reproduce it again now.
I went back to a previous save before going to the dungeon to test it again. Right after killing him the quest shut down immediately like it's supposed to with no errors in papyrus. Something weird must have happened originally that caused the USKP script to not do its job. The game engine has been known to do this kind of thing in rare cases when there is script lag. Anyway, I can't reproduce it again now.
Showing Comments 1 - 6 of 6