 |
Seb
Wizard
Joined: 14 Aug 2004
Posts: 1269
|
 Posted: Tue Oct 09, 2007 12:02 am
[2.05] Display issues when several triggers fire on the same line
|
New in v2.05
There seem to be some issues when more than one trigger that affects the display fires on the same line of text from the MUD...
I have a trigger that adds send tags to the name of the person who sent me a tell (and #CAPTUREs it to another window) and I have a trigger that:
| Code: |
#ECHO {%1 wants a newbie kit!}
#VAR kitperson {%1}
whois @kitperson |
when someone sends me a tell with the word "kit" in it.
But they seem to be interfering. This is 100% reproducable when both triggers are enabled, but is not a problem with only one trigger. It can even be reproduced offline. e.g. with this (although this works even slightly worse than normal MUD output):
#show %cr""Xxx tells you 'kit'%cr
Actual mud output (names changed, and I changed yellow to green to make it more readable; Yellow is normally my commands, Cyan is the default #ECHO colour, red is ansi sent by the MUD, underline is my send tags):-
| Quote: |
Tttttt tells you 'newbie kit please ?'
Tttttt wants a newbie kit!
Tttttt tells you 'newbie kit please ?'
Tttttt wants a newbie kit!
(02:30:09) Tttttt tells you 'newbie kit please ?'!# 16[0:16]>Tttttt is a level one Man Apprentice.
(02:30:09) Tttttt wants a newbie kit!
whois (02:30:09) Tttttt
Is playing from *.anon.
(02:30:09) !# 16[0:16]>Tttttt is a level one Man Apprentice.
Is playing from *.anon.
(02:30:10) !# 16[0:16]>No-one by that name.
(02:30:10) !# 16[0:16]>
|
As you can see, the kit (#ECHO) trigger is firing three times and the usual tell (#SUB) trigger is firing twice, and not on the original tell line, which is the one that is should be #SUBbing.
WinXP SP2. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Oct 09, 2007 12:33 am
|
Please show me the *full* script and trigger pattern for both the "wants a newbie kit" and the #SUB trigger. I need the full triggers in order to test this with the #show command that you gave.
|
|
|
|
|
Seb
Wizard
Joined: 14 Aug 2004
Posts: 1269
|
Posted: Tue Oct 09, 2007 12:43 am
|
I was already on the case of creating a test scenario for you (but my router went crazy and cut my link)!
In a blank session I created the two triggers I spoke off, cut down as much as possible:
| Code: |
<window name="untitled" host="0" usesession="false">
<uid>{189D4896-7EAC-4B2B-A43D-3D30FD973F19}</uid>
<packages>untitled</packages>
<trigger priority="9350" id="1">
<pattern>(%w) tells you '*kit</pattern>
<value>#ECHO {%1 wants a newbie kit!}
</value>
</trigger>
<trigger priority="14280" id="2">
<pattern>(%w) tells you '(*)$</pattern>
<value>#SUB {AAAAAAA %1 tells you '%2 ZZZZZZZZ}</value>
</trigger>
</window> |
Test code:
| Code: |
| #show Xxx tells you 'kit' |
Result:
Xxx tells you 'kit'
AAAAAAA Xxx tells you 'kit' ZZZZZZZZkit!
Expected result:
AAAAAAA Xxx tells you 'kit' ZZZZZZZZ
Xxx wants a newbie kit!
Cyan is my #ECHO colour. |
|
|
|
|
Seb
Wizard
Joined: 14 Aug 2004
Posts: 1269
|
Posted: Tue Oct 09, 2007 1:20 am
|
Add:
| Code: |
#VAR kitperson {%1}
whois @kitperson |
to the end of the first trigger value for a slightly different result and somewhat more similar to the original. i.e. It will be the 3rd line that gets SUBbed instead of the 1st. |
|
|
|
|
Seb
Wizard
Joined: 14 Aug 2004
Posts: 1269
|
Posted: Thu Oct 11, 2007 8:12 pm
|
| Zugg wrote: |
| You might wait until 2.06 is released on Friday. It solves the serious trigger problems in 2.05. |
Is that this trigger problem? Cos I reckon this one might be quite serious and I've not heard anything specifically relating to this... |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Oct 11, 2007 10:25 pm
|
Well, 2.05 had *many* trigger problems (skipping triggers, etc). But yes, this specific bug is also fixed in 2.06 :)
|
|
|
|
|
Seb
Wizard
Joined: 14 Aug 2004
Posts: 1269
|
Posted: Thu Oct 11, 2007 11:32 pm
|
Cool! Can't see any others reported, but maybe you found them yourself when you were mudding? Or as a result of this report?
|
|
|
|
|
|
|
|
