Smart Scenario ‐ Engine
Here, you will find more information about how Klick'r handles your Smart scenarios, how they are structured and how to create the best scenario for your use cases. I will explain how a Smart scenario is structured and how Klick'r is executing it in order to use Klick'r for complex automation, as automation based on image detection is really different than timer based automation like any regular autoclicker.
The Smart Scenario structure is really different than the usual autoclicker scenario structure.
It is composed of two lists of Events. An Event is the center of your scenario, it's a combination of Conditions and Actions; when the conditions of an event are fulfilled, the actions of those events are executed. Those two lists of Events are:
- The Screen Event list: the events verifying what is happening on your device screen
- The Trigger Event list: the events verifying what is happening on your scenario (such as the time since begin, or the execution count of another event...)
Once the Smart Scenario is started, Klick'r will waiting for the next image generated by the device screen to start its processing:
-
First, it will verify if there is at least one enabled **Event ** in one of the Event lists. If not, the scenario will automatically stops, as there is nothing to execute.
-
Then, for each enabled Trigger Event in the list, it will verify its Trigger Conditions ; if they are fulfilled, the Actions of this Trigger Event will be executed.
-
Then, for each enabled Image Event in the list, it will verify its Screen Conditions ; if they are fulfilled, the Actions of this Screen Event will be executed. If the "keep detecting" setting of this Screen Event is disabled, the Screen Event list verification will stops here and ignore all next Screen Events in the list.
-
Finally, it loops back to the first step and wait for the next image generated by the device screen.
Here is a diagram of this logic, as it can be easier to understand with an image than an explaination:
