Triggernometry is a plugin for Advanced Combat Tracker, intended to extend its built-in trigger system with a variety of different actions and configuration options.
Problem: When starting ACT, Triggernometry instantly checks triggers zone restrictions, but zone id is still equal to 0, because events are set after and a zone change has yet to happen.
A zone change event is fired after setting up events, but the trigger restrictions are not refreshed. This means that triggers using ZoneId will not work until an actual in-game zone change happens. Login does not count as a zone change if the zone is the same as when you logged out.
Note: I tried using GetCurrentTerritoryID to manually fetch the zone id before Triggernometry checks restrictions, but that just returns 0, probably because ACT is not ready fast enough.
Problem: When starting ACT, Triggernometry instantly checks triggers zone restrictions, but zone id is still equal to 0, because events are set after and a zone change has yet to happen. A zone change event is fired after setting up events, but the trigger restrictions are not refreshed. This means that triggers using ZoneId will not work until an actual in-game zone change happens. Login does not count as a zone change if the zone is the same as when you logged out.
Fix: This change is fixing all the aforementioned issues. However it is not ideal in the sense that both this and https://github.com/paissaheavyindustries/Triggernometry/blob/master/Source/Triggernometry/RealPlugin.cs#L3236 will call
ZoneChange. It is not that bad, as it only happens on zone change, but I am mentioning it, as you may have a better fix in mind.Note: I tried using
GetCurrentTerritoryIDto manually fetch the zone id before Triggernometry checks restrictions, but that just returns 0, probably because ACT is not ready fast enough.