Part of the baseline setup for random encounters is that the script fragment stores the encounter's trigger alias as a property named Alias_TRIGGER, and uses that property in an attempt to re-arm the trigger when the encounter shuts down. While that shutdown fragment has its own problems that the Unofficial Patch has worked around, many random encounters aren't even attempting to rearm their own triggers, because they are instead storing the trigger alias for RESceneTEMPLATE. This appears to be an error propagated from when they first set up the system, and it most heavily impacts chokepoint encounters where the template is still misconfigured.
The following quests use the wrong trigger alias in their fragment properties:
- REObjectDL01
- REObjectKMK01
- REObjectKMK02
- REChokepointTEMPLATE
- REChokepointKMK_MS11
- REChokepointKMK_MS01
- REChokepointKMK_COMNick
- REChokepointCT01
- REChokepointCT02
- REChokepointCT03
- REChokepointRJ01
- REChokepointSC08_FactionInstDefenders
- REChokepointSC07_FactionBosDefenders
- REChokepointSC04_FactionInstRelayAmbush01
- REChokepointSC05_FactionInstRelayAmbush02
- REChokepointSC06_FactionMMDefenders
- DLC01REObjectKMK01
- DLC01REObjectSC02
- DLC04REChokepointCT01
- DLC04REChokepointCT02
- DLC04REChokepointCT03
While this is a low priority since the Unofficial Patch already has a means of cleaning up triggers that failed to re-arm, fixing the issue will allow these encounters to clean themselves up in a more timely manner when the shutdown fragment runs correctly. (Obviously, it does not always run soon enough for this to matter)
The template quest listed above is unused and only included for informational purposes, while the object quests do not rearm their triggers and were included because I do not know if that fragment property is used elsewhere in the random encounter scripts. On a related note, REObjectCC01 has the same misconfiguration, except the property is referring to the trigger alias for REObjectTEMPLATE rather than RESceneTEMPLATE.