State machine based Scenario

[g0tRoob]

Describe the feature

Ever thought about adding a state machine/FSM based Scenario definition?

Example: Only certain conditions can be triggered when having multiple views in a game/app. But all conditions are checked for all views. So there are many conditions that can never be triggered in a view.

I tried setting up a scenario where Events are disabled and enabled, when switching a view that it behaves like a state machine. But it was really tedious setting it up and toggling the events didn't really work. I didn't dig into it why toggling didn't work in my case for now and the in-app debug feature was not enough for finding the issue.

My suggestions to add a new scenario where you have states instead of events.

Using a state machine could have some benefits e.g.:

• Reducing number of checks for conditions, because only predefined conditions can occure in a state. And also reducing accidently triggering conditions. Probably even reduce performance requirements.
• Defining complex procedures gets easier with substates, Logical conditions for other states (AND, OR, XOR, NAND,...)
• Definition of Entry/Exit-Actions could also be possible.

An example for a possible state machine:

Describe the usage

New type of scenario definition.

Is it a duplicate?

• [X] There is no duplicates

[g0tRoob]

Forgot to add. The main difference would be that instead of a list of events there would be a transistion to the next state(s). I guess the big changes would be, if sub-states with logical operators are added. I guess 90% of the Smart Scenario code could be reused.