Trigger Matching.

Posted by Errigour on Sun 05 Apr 2026 11:14 AM — 4 posts, 2,584 views.

USA #0
I have this line of code to match.
Global Quest: The quest will start in 4 ticks and will last for 81 ticks.


The problem is I have to use this expression to match it and it only matches when more code is sent after the line I am trying to match when I use test trigger.
*Global Quest: The quest will start in * ticks and will last for * ticks.*


This line doesn't match it at all.
Global Quest: The quest will start in * ticks and will last for * ticks.


How can I get it to match that line without requiring more code sent after it or before it. Just match it if that line is sent anywhere in the output.

Like when I test trigger, It doesn't match until something is sent from the mud after it.
Amended on Sun 05 Apr 2026 04:22 PM by Errigour
USA #1
Also if you can explain why it isn't matching and why it doesn't match test triggers output that would be awesome.
USA Global Moderator #2
Quote:
Like when I test trigger, It doesn't match until something is sent from the mud after it.


It sounds like you're just testing it wrong. The "Test Trigger" dialogue in the Game menu does not automatically end the line you put into it, so the next line from the MUD gets attached to the line you entered, and then that finally ends the line. That obviously then won't match your trigger unless the trigger ends with the * wildcard, because of how MUSHclient patterns work. You need to end your test line with either
\0A
or Ctrl+Enter.

See:

https://github.com/fiendish/aardwolfclientpackage/wiki/Writing-Triggers#i-tried-making-a-trigger-but-it-isnt-firing-what-did-i-do-wrong

and

https://github.com/fiendish/aardwolfclientpackage/wiki/Writing-Triggers#i-did-that-and-its-still-not-firing-when-i-test
Amended on Mon 06 Apr 2026 04:00 PM by Fiendish
USA #3
Alright thanks.