 |
complex
Apprentice
Joined: 12 Apr 2004
Posts: 134
Location: USA
|
 Posted: Fri Oct 15, 2010 12:33 am
Broken Trigger?
|
To resolve an earlier issues I added a carriage return after the last character in my prompt. However now the trigger that captures and stores my gauge variables no longer functions. To be clear the package editor says the pattern matches but the variables are not updated. The structure of my prompt has not changed in anyway, it is just followed by a carriage return.
This is how my mud displays my prompt with no leading or trailing spaces
| Code: |
| <1940/1940:hp 718/718:Mv 144/144:Cm 0:Wait 785:Tnl 3:Qt> |
This is what the debugger shows me (I am not sure what the 37m and <ESC> stuff is, but the only way I could get anything out of the debugger aside from the vanilla prompt was to turn everything on.
| Code: |
| 0.0013 | h Kingdoms |<ESC>[37m<1940/1940:hp 718/718:Mv 144/144:Cm 0:Wait 785:Tnl 3:Qt><ESC>[0m |
This is my trigger
| Code: |
| <&hp/&mhp:hp &mv/&mmv:Mv &cm/&mcm:Cm &wait:Wait &tnl:Tnl &qt:Qt> |
And these are the only settings I checked under more settings
Trigger on Trigger
Trigger on prompt
I have played with various combination's of the above settings, and leading and trailing wild cards, and even remade the trigger from scratch by highlighting the prompt on the screen right clicking it and selecting make trigger. But nothing I do updates the variables any more. |
|
_________________
<Clever text here> |
 |
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Fri Oct 15, 2010 3:19 am
|
Uncheck Trigger on Prompt and check Trigger on Newline.
|
|
_________________
EDIT: I didn't like my old signature |
|
|
|
complex
Apprentice
Joined: 12 Apr 2004
Posts: 134
Location: USA
|
Posted: Fri Oct 15, 2010 3:33 am
|
That worked... 
I swear I tried that.  |
|
_________________
<Clever text here> |
|
|
|
|
|
|
