Object overlaps square = add 1 to counter help?

Hey Clickteam,

I'm wracking my brain on this one and need help! I'm making a mini shuffle board type game where the player throws a puck that can slide on three different squares. The closest square to the player is worth 1 point, the second square 5, and the last square is worth 10. I created an event when the puck is overlapping the first square, which is worth 1 point, I add one to the Players score counter. But this like it should, continuously adds 1 to the counter since the puck stays on the square. I want it to only add once to the counter the value of which point square the puck lands on. How can I do this? Thanks Clickers and Merry 12 days of Christmas!

Unless I've misunderstood the problem, you could use flags to limit this. For example:

+ Puck is overlapping square
+ Square Flag 1 is off
- Add Score
- Turn Square Flag 1 On

Hey thanks Chrille. Haha. I hope it's not that simple cause my Clickteam street cred will go way down. I'll try it and post!

Sure - that should work. You could also "Run this event only once."

Hey Ziplock,

The player gets 4 throws. I was creating the same puck for every throw so when I tried "run this event only once," it would work on the first puck throw but not on the other three. Now that I'm typing this out, I might just create 4 different active pucks for each throw.

"Now that I'm typing this out, I might just create 4 different active pucks for each throw. "
This sounds overly unessesary.

Chrille suggestion should work
if your creating 4 different Active Pucks, your more or less quadrupeling any code for the Puck, but it does work though

Darn King_Cool,

I spent about an hour copying code for the four different pucks. Lol. It does seem unnecessary. It is fun to experiment and figure out the best way. I now know what I need to do. I wasn't resetting the flag back off after the first puck throw. So the second puck throw wouldn't add the score. That's why I ended up creating four different actives. It was late... Thank y'all for the help!

You shouldnt need to reset the Flag for any new Pucks, as the default value for Flags are OFF, so it is allready OFF when you created and ready to score another point.

you need to use the " one action when event loops" condition

unlike the run event only once it will allow run the event the next time the puck lands wherever

limit conditions > one action when event loops

Great.

Last night when I tried shooting another puck, it didn't add the score. I'm going to check it out tonight. Its probably something I missed. I'll update! Also, that was another question I wanted to ask. If flags are by default off. Thanks 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

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

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.

Awesome info.

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