Object overlaps square = add 1 to counter help?

[King_Cool]

If you create your Event like this:
- Special -> Compair two general values -> FlagX of Puck is OFF + Overlap
^ There is going to be a problem

If you do it normally as this:
- Puck -> FlagX of Puck is OFF + Overlap
^ Itll be fine

[Emerson3]

I have it the second way, but I have Overlap and then FlagX of Puck is off. Does this order make the difference?

[King_Cool]

Nope, should be fine
In this case, the order does not make a big difference

Note that some Condtions are 'Green', and that these doesnt allways follow the systematic flow of the rest of the Events ( being checked from top to bottom ), like Loops which trigger as soon as they are called.
Green Events usually trigger as soon as the condition is met, but not allways.
You can force a Green Event to not become green, and thus forcing it to follow the systematic flow of the rest of the Event Editor, by making sure the Green Condition in the Event is NOT the 'topmost Condition' of the Event. If its not the top Condition, the Condition looses its Green color.
One could for example add the Condition 'Allways' above a green Condition to achieve this, all depending on what your trying to do of cource.

...
You can also rearrange Conditions in an Event to gain a, technical, speed/ processing advantage, although it is very limited how much effect this actually has.

Considder these two Events:

( #1 )
+ Flag0 is OFF
+ AltvValueA / 33 + GlobalValueB * 7 / 5 +77.7 mod 5 = 999

( #2 )
+ AltvValueA / 33 + GlobalValueB * 7 / 5 +77.7 mod 5 = 999
+ Flag0 is OFF

Event #1 first checks if 'Flag0 is OFF' which is a simple and quick task, and if its not OFF it skipps the rest of the Event and doesnt bother checking the next Condition, meaning you are saving the Application the troubble of checking/ processing the second complicated calculation.

Event #2 however, 'allways' checks this complicated calculation regardless.

[Emerson3]

Awesome info.

Thank you. And by the way, Cannon Ball Jack looks awesome.