Shared screen event between scenarios

[hatbrox]

Hi,

I would like to suggest a feature that could greatly improve scenario maintenance and reduce duplication in Klick’R.

My current use case

I currently use around 10 scenarios in a mobile game to manage in-game ads automatically.

Each scenario contains several screen events, including one called “Close Ad”.
This screen event detects the small “X” button shown after a video ad finishes, then taps it to close the ad.

The problem is that ad providers constantly change their ads:

• different X button colours
• different button positions
• different layouts

Because of this, I regularly need to add new detection conditions for new ad close buttons, sometimes every couple of weeks.

Current limitation

When I update the “Close Ad” screen event in one scenario, the update only applies to that specific scenario.

The other 9 scenarios still use the old version and do not benefit from the new conditions.

Currently, my workaround is:

1. Update the “Close Ad” screen event in Scenario A
2. Manually open every other scenario
3. Delete their old “Close Ad” screen event
4. Duplicate the updated one from Scenario A

This becomes repetitive and difficult to maintain.

Feature suggestion: Shared screen events

One possible solution would be to allow screen events to be shared between multiple scenarios.

For example:

• several scenarios could reference the same “Close Ad” screen event
• updating it once would automatically update it everywhere it is used

This would greatly simplify maintenance and avoid duplication.

I understand this could require a larger architecture change, such as:

• a global screen event library
• or a central catalogue of reusable screen events

Alternative idea: Sub-scenarios

Another approach could be to support sub-scenarios or callable scenarios.

For example:

• I create a scenario called “Close Ad”, which itself contain the "close Ad" screen event
• other scenarios can call or execute this scenario when needed

This would work similarly to reusable workflows or subroutines in enterprise automation software.

I think either approach would make complex automation setups much easier to maintain.

Thanks for your work on Klick’R!