Issue #22252: REActorAttach02 - attempting to start event scoped quest outside of story manager
[03/31/2017 - 07:28:48PM] error: REActorAttach02 (000392F8): attempting to start event scoped quest outside of story manager.
[REActorAttach02 (000392F8)].rescript.SetCurrentStageID() - "<native>" Line ?
[REActorAttach02 (000392F8)].rescript.setStage() - "g:\_F4\Art\Raw\ScriptsMilestone\Quest.psc" Line 174
[ (000392FB)].Fragments:Packages:PF_REAttachActor02ScavengePa_000392FB.Fragment_End() - "g:\_F4\Art\Raw\ScriptsMilestone\Fragments\Packages\PF_REAttachActor02ScavengePa_000392FB.psc" Line 16
EDIT: REActorAttach01 has the same problem.
It's unbelievable ...
REActorAttach01 spawns raider scavengers around dead corpses and REActorAttach02 spawns conventional scavengers around dead robots. The scavengers all have two packages: (1) a patrol package, and (2) a sandbox package that is supposed to run when the patrol package ends.
The patrol packages all have a package end fragment that calls the owning quest to set stage 100. This stage is empty and it is the second last quest stage; only the stop stage comes after it (and the stop stage can only be set by the quest script to shut the quest down). Thus, this fragment does absolutely nothing, at least not quest wise ...
So I had a closer look at the packages, and found that the sandbox packages have been conditioned to only run when the quest is at stage 100. Simply speaking, they use a script and an extra quest stage to make sure that the sandbox package runs after the patrol package. They could have done this much easier by moving the patrol package on the top of the stack. Because the actual pproblem here is that the sandbox packages are blocking the patrol packages on all quest aliases.
Solution: remove the scripts and correct the package stacks. This also eliminates the error (which occurs because the call from the package fragment occurs after the quest has alredy started to shut down).