Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ MUSHclient
➜ General
➜ Trigger Matching.
You need to log onto the forum to reply or create new threads.
Refresh page
| Posted by
| Errigour
USA (42 posts) Bio
|
| Date
| Sun 05 Apr 2026 11:14 AM (UTC) Amended on Sun 05 Apr 2026 04:22 PM (UTC) by Errigour
|
| Message
| 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. | | Top |
|
| Posted by
| Errigour
USA (42 posts) Bio
|
| Date
| Reply #1 on Sun 05 Apr 2026 11:16 AM (UTC) |
| Message
| | Also if you can explain why it isn't matching and why it doesn't match test triggers output that would be awesome. | | Top |
|
| Posted by
| Fiendish
USA (2,555 posts) Bio
Global Moderator |
| Date
| Reply #2 on Mon 06 Apr 2026 03:59 PM (UTC) Amended on Mon 06 Apr 2026 04:00 PM (UTC) by Fiendish
|
| Message
|
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 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 |
https://github.com/fiendish/aardwolfclientpackage | | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
361 views.
You need to log onto the forum to reply or create new threads.
Refresh page
![[Go to top]](/images/gototop.gif)
top