I just noticed that my multi-line triggers are broken. I know for a fact that they use to work, and those I haven't changed. I tried creating new testing triggers (^a$^b$) and modifying the existing triggers. If I change the current ones to single line, and take out the other line it was supposed to match, it still works. Each line individually matches.

I didn't notice exactly when they stopped working, so unfortunately I don't know what I did that killed them. I did make a plugin that replaces the prompt with a prompt+timestamp+damage tracker. I don't think that broke them, but I tried disabling "Convert IAC EOR/GA" and it didn't make a difference, except I no longer get a prompt AND the plugin stops working.

I also tried turning off "Triggers match on empty strings" and it didn't make a difference.

Does anyone have the slightest idea what I can do? I've tried browsing Nick's forums and I didn't see anything pertinent. I've just found that often someone here knows how to fix it, after I've spent 4 hours trying to do something on my own.

Don't use ^$ for matching newlines. Use \\n in a regex pattern. You have to tell MUSHclient that the trigger is multi-line AND how many lines it matches, too.

I'll bet that's it. I'll try that and get back to you. (See? I knew it would be easier to ask here than spend another 2 hours on it)