See, my problem is that the first trigger should start when you (or any entity) walks into the box, then knows that you’re there. The second one shouldn’t trigger until you leave the box. But the second trigger fires simply if you stop. In my viewpoint right now, this is a bug. But the solution given is a more straightforward way of looking at it, and I like it. Going to have to test it when I get back to my project later and run the debug on it just to see how it performs. In my scrambled brain at the moment, it seems like it’ll be constantly running the Reverse the entire time unless you’re in the box which seems like a performance hit. But I could be wrong. Can’t think completely straight at the moment due to last night’s beverages. Lol