Scenarios as States for State Machines

[bluespheal]

Describe the feature

I think the app would greatly benefit from being able to encompass several screen events/triggers into a single element and have them behave as modular states. Perhaps it would need its own category as a "State" in the scenario list.

They would work as follows:

• A state would have screen events and triggers, just as regular scenarios, but only scenarios labeled as states can be referenced by other scenarios.
• A state can referenced by other scenarios, for example, Scenario 1 and 2 can both reference state "A"
• States remain consistent between scenarios, if you edit state "A", it will be reflected in Scenario 1 and 2 (or whatever scenario references it)
• States can be deactivated or activated by other screen events/triggers or states, re-activating one will reset it to its default behavior.
• States just appear as a single item on a scenario's list, if you wish to edit or see what's in the state, you'd need to go to that state's scenario, however, if you'd choose to, you can unpack a state, this would not affect the original state.
• States and normal screen events/triggers can coexist in the same scenario.
• You can change/upgrade a current scenario into a state, in case you already have a behavior you'd want to fit into a state.
• Likewise, you can select a few elements in a scenario to turn them into a state.

In short, states would be like a reference to a different scenario, packed into a single item, which can in turn be referenced by other scenarios. Perhaps the "state" distinction is redundant or could be better labeled, in which case, would be similar to another existing request: #788 (comment)

Describe the usage

This feature would improve both modularity and navigation of the tool; making states function as a single item on a list, as well as making it easier to share similar behaviors between scenarios without copying or having redundant scenarios.

Use cases would include:

• You want to keep a very complex scenario cleaner and more modular, states would allow you to create a scenario that just delegates states, keeping the more complex actions packed separately.
• Some scenarios often share the same conditions and actions, requiring you to either; copying a bunch of scenarios manually, or copying an entire scenario and then trimming/changing it. States would allow a more modular and consistent set of smaller scenarios and a better flow.

A more concrete scenario and one which I'm using the app for is for Pokémon TCGP, in which I can automate some of the more sluggish actions.

Some of these include: Opening a pack of cards, retrieving the free daily items from the shop, retrieving gifts, checking if any of the wonder picks has any of my wanted cards, claiming the daily rewards, giving likes to my friends and sharing a card.

As you can see, there are several actions and I do use the app several times a day, each one of these being several smaller actions and conditions I label myself to keep track of. However, each time I need to do a specific set of actions, so one can look like:

Open pack > retrieve gifts from shop > check WP > give likes and share a card.

While later in the day I use:

Open pack > retrieve gifts > check WP > claim daily rewards

You can see some overlap in actions, which means I had to heavily edit a copy of my initial scenario, making each custom state a bit hard to keep track of even with my labels. Also, if I make any improvements to one of my actions, I have to manually edit or copy said improvements into my other scenarios.

I'm sure there are caveats and limitations to a system like this, if there's any obvious ones or things I haven't considered, do let me know or offer a solution/alternative, likewise, if there's anything like this already implemented also let me know, I'm sometimes oblivious to such features, but to my knowledge there is none other than copying screen events and scenarios directly.

Is it a duplicate?

• There is no duplicates