Klick'r 4.1.2

[Nain57]

Bugfixes:

• Refresh playstore purchase more aggressively
• Fix possible crash when capturing a gesture above 1 minute
• Fix possible crash in dumb scenario when an invalid gesture has been recorded

---

This discussion was created from the release Klick'r 4.1.2.

[tiGOl1]

Hello! Thank you for the update!
Quick check - the feature to read coordinates of a detected condition only works for a single condition. Even in an event with an OR operator and multiple conditions, I'm only able to select one of the conditions to extract the coordinates. Is there a way to make it get coordinates for the first detected condition instead? Same as the click action effectively.

[yeohaowei]

Hi sorry for the asking here, have bought Klickr Premium version, may I seek guidance? For for this smart auto clicker, how do I set by clicking just once? Understand there is a condition and action when condition is triggered, and it spams the click until the next condition is triggered, may I know how do I control the number of clicks? For example if it see green colour, I just want to click 1 time only rather than rapidly spamming the green colour.

Appreciate everykne here for guidance, Thank you.

[tiGOl1]

I had this exact scenario when I started using this software. What's happening is the screen is being read multiple times, even immediately after your action is triggered. So, before the click is registered and the action reflects a change on the screen, it is being read again. What you need is to add a small delay before and after each click or set of actions.

Your current event is like this:
If (image) then (click 5 ms)

Try changing it to:
If (image) then (wait 200 ms) (click 5 ms) (wait 500 ms) end event

Always end each event with a small delay. It just helps the script run smooth and also helps you debug easier.

You can also add multiple actions inside each event. But, if there are actions that require interactions with the screen - clicks, gestures, panning, etc. add a small delay between each of those as well. Like this:
If (image) then (wait 200 ms) (click 5 ms) (wait 200 ms) (click 5 ms) (wait 200 ms) (click 5 ms) (wait 500 ms) end event

You could even change it to disable the event after it is triggered, but you will need something else to enable it again:
If (image) then (wait 200 ms) (click 5 ms) (wait 500 ms) (disable current event) end event

If the last action is disabling the current event, I have found you don't necessarily need to add a delay after it and it still works fine.

Hope this helps.

[yeohaowei]

Thank you, I will try it out! But hopefully and eventually they are able to add additional option to control the amount of clicks!

[Nain57]

An event will be evaluated for each frames generated by your screen, that is why the click is executed several times and that's the expected behaviour. That is because Klick'r is based in screen content detection and not timing like other auto clickers. In you case; it doesn't spam until something else is detected, it click once per frames displayed by your screen.

For your use case, you need to define what you want clearly:

• Click once and never again: you need to add a "Change Event State" at the end of your action list to disable the event. This way, it will never be evaluated again.
• Click on something once and wait for the content app to settle: Basically menu interactions, you know you will never have to spam the actions. In those cases, use the Event reloading feature, allowing you to define a "cooldown" to the event. Unlike the first case, this allows you to reuse it later

Using timing as proposed by tiGOl1 to separate several gestures in the same event is often a bad idea, as you go back to rely on time instead of screen content, which will cause problem as soon as a lag occurs. Regular autoclicker are like i wait, i do, i wait, i do..., but to use Klick'r correctly, you have to think like a human using an app: I see something, I do something.

Check the tutorials provided on the upper right of the Scenarios screen, as it will provide you more insight on Klick'r internals.