This forum is a read-only archive of the Gammon Software forum (2000–2026). No new posts can be made. Search the archive.

Triggering on my prompt line?

Posted by Kaimarae on Wed 11 May 2011 09:40 AM — 11 posts, 37,713 views.

Kaimarae #0
Hello all,

This is my first post here, but I've been lurking for a while.

The issue I am having is that I'm trying to trigger on my prompt and display the relevant data on the info bar. I'm having no trouble displaying what I want, however the trigger on the prompt just Refuses to fire.

This is my prompt:

869h, 230e, 657m xb A:50% -


This is my trigger (I have tried SO many variations on this):

*h, *e, *m x?b? A:* -


Any ideas on what I'm doing wrong?
I've turned on trace to make sure it wasn't just my script (Lua) failing to do anything. It doesn't trigger at all.

Any help would be greatly appreciated.

Regards,
Kaimarae
Twisol USA #1
Well, there are two possibilities here. The first is that your trigger is incorrect (and it is). Try this:
^(\d+)h, (\d+)m, x?b? A:(\d+)%$

The problem with the original is that you were mixing basic pattern syntax (where * represents a capture) with regular expression syntax (with the ? zero-or-one quantifier). I converted it to a full regular expression, since basic patterns don't support optional sections.

The second possibility is that your prompt doesn't end with a newline. Triggers are only processed and executed after a newline is received, so the prompt won't be scanned until the MUD sends a newline. This could still be the case even after the trigger is fixed, so if you notice that your trigger seems to "lag" (i.e. only fire after data comes in after the prompt), you should try enabling "Convert IAC EOR/GA to newline" in Game -> Configure -> Output, on the right.
Amended on Wed 11 May 2011 09:58 AM by Twisol
Kaimarae #2
That does help, but I substituted my trigger for yours and there is still no firing happening. I added in the dash at the end to be sure and still nothing.

This is what I'm using:

<triggers>
  <trigger
   enabled="y"
   expand_variables="y"
   group="Prompting"
   match="^(\d+)h, (\d+)m, x?b? A:(\d+)%$"
   send_to="12"
   sequence="100"
  >
  <send>SetVariable("CurrentHealth", "%1")
SetVariable("CurrentEndurance", "%2")
SetVariable("CurrentMagic", "%3")</send>
  </trigger>
</triggers>


I doubt it makes a difference, but I'm using MUSHclient 4.72?
Nick Gammon Australia Forum Administrator #3
You don't have "regular expression" checked.
Kaimarae #4
Good point. Checked it and still no dice. :/

My trigger:
<triggers>
  <trigger
   custom_colour="14"
   enabled="y"
   expand_variables="y"
   group="Prompting"
   match="^(\d+)h, (\d+)m, x?b? A:(\d+)% -$"
   regexp="y"
   send_to="12"
   sequence="100"
  >
  <send>SetVariable("CurrentHealth", "%1")
SetVariable("CurrentEndurance", "%2")
SetVariable("CurrentMagic", "%3")</send>
  </trigger>
</triggers>


Also this one:
<triggers>
  <trigger
   enabled="y"
   expand_variables="y"
   group="Prompting"
   match="*"
   send_to="12"
   sequence="100"
  >
  <send>InfoClear()
SetStatus("H:", GetVariable("CurrentHealth"), " E:", GetVariable("CurrentEndurance"), " M:", GetVariable("CurrentMagic"), "   Target: ", GetVariable("Target"))
</send>
  </trigger>
</triggers>


I suspect the one above is pretty rudimentary and could be done a fair bit better. Sadly, it's the only part that works. My infobar reads:

Quote:
H: E: M: Target: beaver


Again, any help would be greatly appreciated.
(In other news, amazing program Nick. Truly!)
Amended on Wed 11 May 2011 12:48 PM by Kaimarae
Kaimarae #5
As if the MUSHgods wanted to smite me in a fit of cruel irony, all of my triggers just stopped working. Even the simple do-nothing-but-highlight ones. I closed MUSHclient, nothing. Unchecked "Enable Triggers" then re-checked it... Nothing :/

Did a google search to see if anyone had encountered it before but couldn't find anything.

Help?
Nick Gammon Australia Forum Administrator #6
Quote:

This is my prompt:

869h, 230e, 657m xb A:50% -


I don't see an "e" in your trigger, so it won't fire. You have to look carefully at the line you are trying to match on, and your trigger.

Trigger, and regular expressions *do work*. Sometimes it can take a while, I have wasted quite a lot of time on them at times. But it always turns out that I haven't carefully looked at what I am trying to match on.
Nick Gammon Australia Forum Administrator #7
Kaimarae said:

As if the MUSHgods wanted to smite me in a fit of cruel irony, all of my triggers just stopped working. Even the simple do-nothing-but-highlight ones.


Well you just added this:


   match="*"


And without ticking "keep evaluating" it has probably fired before all the other ones, thus overriding them.
Kaimarae #8
GAH! You are correct! Sadly, I can't check to see if it works right now :|

Edit: Correction. You are legendary. I had it in there before (it was just disabled), but it didn't kill everything before I disabled it. Ah well, who cares now? xD

Sorry to bother you with something so silly. I appreciate the patience!

Edit 2: Is there a better way to accomplish what I did with my "*" trigger?
Amended on Wed 11 May 2011 01:04 PM by Kaimarae
Nick Gammon Australia Forum Administrator #9
What is the problem with just updating the info bar when you get the prompt? Why have the extra trigger?
Kaimarae #10
I found for me that all the lines in the script fire at the same time, and the prompt gets updated with the last ticks stats. I'll give it a shot, but that's what it was doing before.

EDIT: Strike that. It seems to be working now. Woohoo! Redundant trigger removal!