Boy, that subject doesn't seem very clear! Examples are the best:
I have a variable:
<variables>
<variable name="customcommand">armorGG|blindTT</variable>
</variables>
I have a regex trigger:
^@leader tells you \'(@!customcommand)\'$
This works fine when:
LeaderMan tells you 'armorGG'
LeaderMan tells you 'blindTT'
But what If I want it to do both?
LeaderMan tells you 'armorGG blindTT'
I COULD (and currently do) split the string into individual pieces and individually analyzed, but my suggestion is that this could be simplified.
I have a variable:
<variables>
<variable name="customcommand">armorGG|blindTT</variable>
</variables>
I have a regex trigger:
^@leader tells you \'(@!customcommand)\'$
This works fine when:
LeaderMan tells you 'armorGG'
LeaderMan tells you 'blindTT'
But what If I want it to do both?
LeaderMan tells you 'armorGG blindTT'
I COULD (and currently do) split the string into individual pieces and individually analyzed, but my suggestion is that this could be simplified.