New customizability setting for Actions: Additional Conditions

[vibhor1102]

The new option would be placed as shown in the image (The exact wording & order can be suggested to change). Image for demonstration generated by AI, not from real implementation/prototype.

• The aim is to allow certain actions within an event to run/not run on the basis of certain conditions.
• If the condition rule set is not true at the time of check, that action is skipped and the execution continues like normal.

Currently, I've thought of 2 conditions:

1. Counter-based condition: allows certain actions to run or be skipped on the basis of counter's values.

Examples:

• Create 2 actions, one for when a counter ≥ 10, another for when counter < 10. This allows only one to run at a time, but the action ran can be customized based on what the state of the counter is.

2. Triggerred condition-based condition: If a scenario has multiple image conditions and an OR logic set, The condition detected first could be used as an additional condition within actions, and there would be specific actions that'd run based on detected condition which triggerred the event.

• In case a scenario is set to AND mode, the ability of the user to create additional conditions on the basis of triggerred image condition isn't restricted, or warned him, but since every condition will HAVE to be satisfied, internally those actions are going to run 100% of the time. Users are expected to figure this out themselves as a consequence of running an event in AND mode.

(i hope the explanation was clear, as "condition" has been overused term at multiple places at this point. suggest a different name for this "Additional Condition" concept if there are any better ideas)

Thanks to @Mohamed-ayman-901 for the inspiration of this Condition type in #946.

Examples:

• Certain image conditions being detected might be similar in nature to fall into one event, but different enough to require a slightly different set of actions, or a different offset. This feature would allow creating multiple actions for each specific image condition according to the image condition triggerred. This would satisfy the requirement in Image OR conditional (idk but this is a problem imo) #946 perfectly.

Potential challenges

• Database edit would be required to hold this info, and backup robustness will be required to be verified.
• The info about actions' additional conditions satisfied/not satisfied would be required in the debug report so that users can figure out whether the actions are triggerring or not.
• It deals at a close enough level with the main Klick'r algorithm, plus the above 2 factors, that i hesitate in working on the development of this feature, and would want the maintainer, @Nain57, to take up this feature request instead. (ofc after bugfixes and tutorial rework for 4.0)

[vibhor1102]

Restored back after a month of invisibility as my account was false-positively flagged