Refactor and rename effect processing-related functions, make it so that message effects are processed even when encountering tags (? verify if that will work as expected).
For ex.{{m_pause}}{{m_rmmsg}} should cause the pause to be executed before removing message, but as it is now it won't unless there is at least non-tag character between these two tags. Since the effects can be specified as {{effect1, effect2}} I'd expect that putting them one after the other explicitly like this would cause them to execute one after the other and not simultaneously.
This may however interfere with certain other effects, as that would for example cause m_type to pause at each tag. This could be resolved by adding additional logic to effects - ignore_tag variab;e/function. This would allow the effect to specify whether it wants to be executed for tags as well as other characters or ignore them.
Refactor and rename effect processing-related functions, make it so that message effects are processed even when encountering tags (? verify if that will work as expected).
For ex.
{{m_pause}}{{m_rmmsg}}should cause the pause to be executed before removing message, but as it is now it won't unless there is at least non-tag character between these two tags. Since the effects can be specified as{{effect1, effect2}}I'd expect that putting them one after the other explicitly like this would cause them to execute one after the other and not simultaneously.This may however interfere with certain other effects, as that would for example cause
m_typeto pause at each tag. This could be resolved by adding additional logic to effects -ignore_tagvariab;e/function. This would allow the effect to specify whether it wants to be executed for tags as well as other characters or ignore them.