 |
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
 Posted: Sat Mar 15, 2008 3:01 pm
[2.20] Trigger firing when it shouldn't
|
I found this during testing of the pattern compilation error message box. This trigger pattern also has an error which can be verified with the trigger test tab, but it fires.
1. Launch CMud
2. Close Sessions Window (ESC)
3. Enter at the command line
4. Hit CTRL-Q
You will see the a inbetween each line
5. Open Package Editor (CTRL-G)
6. Go to the Test Pattern tab for the trigger in the PE and click the Test Trigger button
You will see it gives the 'nothing to repeat at position 0' error correctly. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Sat Mar 15, 2008 7:23 pm
|
Confirmed.
|
|
_________________
Asati di tempari! |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Mar 17, 2008 5:23 pm
|
Heh, this is a very interesting bug. From what I have found, if a CMUD Trigger pattern cannot be compiled into an expression, then CMUD just returns the raw string value as the pattern. The new error checking for Regular Expressions caused the error in compiling the pattern as you saw in the Test Trigger tab. So, because it got a compile error, the routine to create the trigger pattern was just returning "*" as the pattern. But this is a valid CMUD Trigger! CMUD was taking the bad result and then executing it as a normal CMUD Trigger.
Anyway, I've added this to the bug list. |
|
|
|
|
|
|
|
