![]()
|
|
The package has a script that's supposed to disable him, but he's enable parented. Removing the script from that package would fix the error, but that's probably not the reason he doesn't leave.
As a workaround, we could change the script to have Rhorlak MoveTo a holding cell upon quest completion.
Attached Files:
PF_TGTRQ1RhorlakLeavesHouse_000DA695.pex
PF_TGTRQ1RhorlakLeavesHouse_000DA695.psc
35374.esp




I think it would be better if the package simply disabled the marker he's using as a parent since that would effectively disable him along with it, which is obviously what they want to happen. Moving him to a holding cell isn't really a good solution to anything.
The only other consideration needs to be the leveled bandit that is set up to enable when Rhorlak disables. This may come as quite a shock with the bandit in its default location. We could either just untie him from the marker or move him deeper into the dungeon where it won't be noticeable that he wasn't there before.
The only other consideration needs to be the leveled bandit that is set up to enable when Rhorlak disables. This may come as quite a shock with the bandit in its default location. We could either just untie him from the marker or move him deeper into the dungeon where it won't be noticeable that he wasn't there before.
The reason I move him to a holding cell was because of that enable marker, swapping the enable state of the marker would make the bandit pop in prematurely, whereas script i did, assuming I did it right, will temporarily move him to the holding cell until the quest swaps the enable parent back in later. (Though I may have forgotten to do that second part to ensure he actually gets disabled)
Showing Comments 1 - 4 of 4