trigers with identical patterns

Why not let users to define more triggers with the same pattern, when they have keep evaluating on?

For example I use two prompt triggers - one active always to watch my current hp etc, the second one activated only sometimes from script to serve as triger to function that captures multi-line object identify and puts it into database (as a sign where the object id ends). I solved it by adding (.*) to the beginning of one of them, but I see no reason for this not to be allowed directly without such tricks.

I suppose I did that because it didn't seem logical to check for the same thing twice, and you might get confused if you had two triggers matching on the same thing, and changed the first one you saw to give a different result, but nothing happened.

You could achieve what you want with one trigger by calling a script, and in the script decide whether to do A or B depending on whether some flag is set.

I had in my mind for example to change the error dialog into warning with possibility to accept the risk of confusing these two triggers later - it "doen't seem logical" to me to disallow something that can be easily circumvented anyway.

I must admit though that is is not any major idea and I'll quit bugging about it after this post, after all this is the only thing I found little annoying in Mushclient and there is workaround for it, it just makes few regexp triggers more unreadable then necessary.

The error test was an early one, before you could do "keep evaluating", scripting, and regular expressions, so it was logical at the time.

Now, you are right, it makes less sense. I have added your idea as suggestion #445.