[Suggestion] Simplify item filter file with new block type ActionGroup

When creating an item filter files, I found that I often want to use the same set of actions (e.g. in-game ground item label styling) for different conditions. Right now, I have to repeat the same set of actions again and again, unnecessarily make the long file even longer.

Here is a simple example: we want to highlight uncut gems and the highlight will be based on the area level. When we're leveling, the low level gems will be highlighted and when we're mapping, only the high level gems will be highlighted. An example filter will be:


Notice that the same highlight actions are repeated 4 times in this simple example. Now imagine you want to use the same highlight for every equipment slots.


One solution is to first define a new block type ActionGroup. Where it predefines a set of actions that can later be used in other blocks. The format of ActionGroup can be as follows:

ActionGroup <name>
{one or more actions}

where <name> is a user defined string to reference the group in other blocks.


Then we will also define a new action type RunActionGroup to execute all actions in a given group.

Format: RunActionGroup <name>
Example: RunActionGroup "gem highlight"

The name must exists or the filter will fail to load.

With both, we can simplify the filter a lot:

The file is no only shorter, but also easier to read and edit.

Note:
1. If we want to keep the parser simple, we can disallow the RunActionGroup action to be used inside a ActionGroup block. This will prevent nested action groups and thus recursion is impossible.

On the other hand, if we want more flexibility, we can allow nesting. If there's recursion, the filter will fail to load.

2. The RunActionGroup can be mixed with other primitive actions as well.


3. When parsing the filter, all actions will be flattened to an ordered list based on their appearance order in the file. If a primitive action appears multiple times, only the last one (or first one depends on the implementation) is kept. For example,


The font size of skill gem will be 45 and support gem will be 40.

(Reserved)

actually would like that - usually I just copy paste blocks I use more commonly, the qustion is if you can implement defining variables into it

This would be cool.