Home
When using Smart AutoClicker, you need to understand several concept before taking full advantage of the capabilities of the application. The first thing to understand is the structure of a Scenario.
Here is its general structure:
A Scenario defines what will happen when you start the detection. It contains:
- A ordered list of Events, defining what will happen and when it will happen.
- A list of End conditions, defining when to stop the detection automatically.
- The global detection settings, like the Anti Detection state or the detection quality/speed.
An Event defines which Actions to execute and under which Conditions those actions should be executed. It contains:
- A list of Conditions, defining what the device should display in order to execute the Actions.
- A ordered list of Actions, defining what is executed once the conditions are fulfilled.
- A state, defining if this event should be executed or not. It can be changed with a specific Action.
A condition defines what should be displayed on your device's screen in order to execute the list of Actions. It contains:
- A screenshot of the element to be detected on the screen.
- The area of detection (same spot or the whole screen).
- The tolerance for the detection. The algorithm create a confidence score every time it compares a screen frame with a Condition screenshot. The tolerance is the tolerated difference between a 100% and the current match. Ex: Detection of the condition have a confidence score of 94%, if the tolerance is at least 100 - 94 = 6, the condition will be detected as visible on the screen, if the tolerance is below 6, it will ignored.
- The visibility on screen. Useful to negate a condition (iow, execute an action once something is no longer displayed).
An Action defines what should be executed once the Conditions of an Event are fulfilled. There is multiple types of Actions, each of them allowing you to interact differently with your device. All the actions of an Event are contained in an ordered list, and the actions will be executed with the same order.
Simulate a click on your device. To select the coordinates, you can either:
- Manually select a position on the screen.
- Click on the detected Condition position.
Simulate a swipe gesture on your device. You have to manually select two positions, the start and the end of the swipe gesture.
Pause the processing for a given duration. This is useful for waiting between two actions, or to add at the end of the action list in order to avoid executing the Event twice to quickly.
Start another application, or simply interact with them. There is two configuration modes:
- Simple, allowing the user to select which application to start
- Advanced, offering access to the whole Android Intent API. Documentation is available https://developer.android.com/reference/android/content/Intent.
Change the enabled state of an Event during the processing. This allows the user to create progressive scenario, disabling events when not needed and enabling new ones while processing.
An End Conditions defines when the detection should stop automatically. They are not mandatory and running a scenario without any will just run it until you manually stops it, or all events are disabled. It contains an Event associated with a number of executions.
