It seems that creating new triggers unintentionally overwrites existing ones. For example, adding a new GenericRegion with a miRegionIndex value of 9000 (or any other value not currently used in the trigger lists) ends up overwriting a LandMark trigger with miRegionIndex value 5613.
Notably, there are already 5612 GenericRegion triggers, so the new one appears to be incorrectly using the same slot as the LandMark trigger - even though LandMark triggers are stored in their own list and should be logically independent.
As a result, the LandMark that marks the finish point for Waterfront disappears completely and attempting to enter the new trigger with miRegionIndex 9000 causes the game to crash.
It seems that creating new triggers unintentionally overwrites existing ones. For example, adding a new
GenericRegionwith amiRegionIndexvalue of9000(or any other value not currently used in the trigger lists) ends up overwriting a LandMark trigger withmiRegionIndexvalue5613.Notably, there are already 5612
GenericRegiontriggers, so the new one appears to be incorrectly using the same slot as theLandMarktrigger - even though LandMark triggers are stored in their own list and should be logically independent.As a result, the
LandMarkthat marks the finish point for Waterfront disappears completely and attempting to enter the new trigger withmiRegionIndex9000causes the game to crash.