Nah, you didn't need to convert it to a regexp, you could've left it as is, without converting, and without the checkbox.
The regulars here mostly just write their own triggers as regexps, they're more powerful, faster (non-regexps just convert to regexps internally, so you can either convert (manually, or via the button) at runtime, or compile time), and a lot more flexible, except they are more complicated to understand, so most of us revert to non-regexps (unless the trigger requires) when helping people who are still figuring the rest of MC out.
However (like I already said), you're not required to use them, simply having gos * and +chat %1 without the regexp check wouldve worked just as well (which is why we didn't mention it).
Edit:
Another thing to note is that your other trigger did infact work, but it matched: "gos" with any number of spaces after it ( *) the * meaning 0 or more of the previous character (a space) and you were sending a blank wildcard (because you didn't capture anything in your regexp).
Also, had you been TALKING about 'gos' (or had anything with gos in it) it would have matched. like: 'I like to gossip' would've matched, and other similar things.
That's why (when dealing with regexps, and aliases (and most triggers)) it's important to anchor it to the beginning of a line (and usually the end too), so you don't fire it when talking about an alias, or whatnot.
This also (coming from Gmud) is useful, because it keeps people from being able to spoof lines (via says, or whatnot) and fire your triggers because you can anchor them to the beginning (non-regexps default to matching whole lines).
I'm sure that last paragraph is a bit confusing (but once you read up on regexps a little, you'll understand). |