Thanks for your reply, that was helpful. Yes, breaking up all the triggers into smaller manageable zones definitely seems to be a much more efficient way to handle things in this case. Your presumption is correct - 99% of the time only any one of the triggers will be hit. I did start doing the zone sub-division some time back, but just due to the sheer number of triggers (that’s a lot of copy&paste work there) I didn’t follow through (lazy). On a side note, the docs only say how to use the trigger components, but not exactly how they “listen” at run-time. Are each and every trigger components called during every “Tick” event to inform them whether they have been activated or not, or is there a separate process through which they are managed - that’s what I am interested in (maybe I missed something).