What have you tried?
Do you need to 'know' the modname (as in, be able to use it in a wildcard).
If not, then you can just do this:
^You slice (.*?) with your (.*?)\.$
However, the first wildcard would be either "mob name" or "mob name horribly" depending.
You can also do this:
^You slice (.*?)(?: horribly) with your (.*?)\.$
which will allow you to use %1 as "mob name" and %2 as "weapon" all of the time, regardless of horribly.
However, in the past we've had some problems with lookaheads having wierd results, so if that doesnt work, you have two options.
If you want to make sure you can use the wildcards, thn you'll need to do this:
^You slice (.*?)(| horribly) with your (.*?)\.$
which will allow you to use %1 and %3 as your mob, and weapon respectively (and 2 will be "" or " horribly", however, if you DONT care about using the wildcards (or at least the weapon), you can do this:
^You slive (.*?)( horribly)? with your (.*?)\.$
which will make it so you either have %1 %2 or %1 %2 %3, with the first being the mob name, the last being the weapon, and the middle (where applicable) being " horribly".
Other problems, make sure there isnt a space after the period, or at the beginning of the line (or a prompt at the beginning of a line), and make sure you have regexp checked (and either double check you have the correct case of everything, or tell mushclient to ignore it). Also, if you are testing it using CTRL-SHIFT-F12, make sure you put a carriage return before and after the line, to make sure you're sending a clean line, and ending with a newline (the trigger won't try to match until it recieves a newline). |