Issue Data
|
|
||||||||||||||||||||||
I didn't notice right away, but this was reported a long time ago in a multi-issue ticket (13587). It's entirely possible something was already done to attempt to correct the problem. I didn't get any of the other errors in that ticket while doing Lost to the Ages, so this could be one of those that won't cooperate.
Comment #1 May 20, 2025 9:31 pm
Edited by BlackPete on May 20, 2025 9:32 pm
Could be script latency, maybe you entered the trigger before the location change event processed.
That definitely sounds like a possibility. I've never been able to narrow this type of error down to anything in particular. It seems more likely to happen with larger, complex quests like this one.
Showing Comments 1 - 3 of 3

Issue Data