I was using "is overlapping at offset" followed by a trigger once event.
Collision wouldn't work because I needed the offset.
I put the event together thinking it would act like a collision and only run once, but actual results ran the events indefinitely.
I made a quick capx to try and duplicate the problem, but using the exact same events resulted in different results......
Going to assume it is because of animations or collision shapes. Of my actual project.
Regardless, it isn't behaving reliably for me, working in one project but not another would just add to my frustration using it.
I got around the issue by checking animation states instead, disregarding the trigger once condition.
I guess the purpose of my post was to say there are times where we(I) want events to run a single time. Once if true can run many times, if the last tick ever becomes false.
Having a condition that after the event triggers doesn't allow that event to ever run again might be useful.