 |
Fuego Ledrey
Wanderer
Joined: 09 May 2007
Posts: 64
Location: Dustin Acres, California
|
 Posted: Sun Jul 01, 2007 2:30 am
Multiline triggers firing only every other time.
|
I think I found another bug, but I hope not.
I have the following code in my system as a test:
| Code: |
#VAR testing_trigs {0}
#REGEX "ledrey_test" {^Oh my\, you look tired\.$} {#GAG}
#COND {^Maybe you should sleep or something\.$} {#GAG} {regex}
#COND {^That or pass out\.$} {testing_trigs = 1;#SUB {Wow you sure are tired!}} {regex} |
When I punch this into the command line:
| Code: |
#VAR testing_trigs {0}
#ECHO {Oh my, you look tired.}
#ECHO {Maybe you should sleep or something.}
#ECHO {That or pass out.}
#ECHO {Results: @testing_trigs}
#ECHO {---------} |
The results I expect are:
| Quote: |
Wow you sure are tired!
Results: 1
--------- |
The first time I execute the second set of code I get these expected results. The next time I execute the second set of code I get these results:
| Quote: |
Oh my, you look tired.
Maybe you should sleep or something.
Results: 0
--------- |
The third time:
| Quote: |
Oh my, you look tired.
Wow you sure are tired!
Results: 1
--------- |
The second and third quote repeat over and over upon further echoes. If the code fired, the variable would echo as 1. As you can see, sometimes it echoes as 0.
Is there something I'm missing? Is there something that I can execute in the last #COND to make the trigger work all the time? This is really messing up a lot of multiline afflictions/defs and it's just plain annoying, heh. |
|
_________________
EDIT: Image moved to Avatar FINALLY. |
 |
|
|
Fuego Ledrey
Wanderer
Joined: 09 May 2007
Posts: 64
Location: Dustin Acres, California
|
Posted: Sun Jul 01, 2007 5:52 pm
|
Since I've gotten no response, is it safe to assume that this is a known bug and I just missed it when reading this?
|
|
_________________
EDIT: Image moved to Avatar FINALLY. |
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Sun Jul 01, 2007 6:13 pm
|
It's probably not on the known issues page - known issues is more "features that aren't finished yet". The bug list is something else. I can confirm that I was getting this problem as well last night - it looked like CMUD wasn't updating the current state fast enough so that when the next line arrived, the wrong state was active and the trigger didn't carry on as it should.
|
|
|
|
|
Fuego Ledrey
Wanderer
Joined: 09 May 2007
Posts: 64
Location: Dustin Acres, California
|
Posted: Sun Jul 01, 2007 6:17 pm
|
I just wanted to make sure Zugg wasn't practicing:
| Zugg wrote: |
| If you report one of these known issues, I'll probably just ignore it. |
Hehe. |
|
_________________
EDIT: Image moved to Avatar FINALLY. |
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Sun Jul 01, 2007 6:23 pm
|
Well, bear in mind that it's the weekend and Zugg's never around (as much) then. He does need some time to relax :P
It really says something about the level of service though when people start going "Oh my god, has Zugg missed my post!?" when it's only been up for 16 hours though :P |
|
|
|
|
Fuego Ledrey
Wanderer
Joined: 09 May 2007
Posts: 64
Location: Dustin Acres, California
|
Posted: Sun Jul 01, 2007 6:25 pm
|
He is extremely thorough  , hence the patience being shorter than normal  . Apologies.
|
|
_________________
EDIT: Image moved to Avatar FINALLY. |
|
|
|
Fuego Ledrey
Wanderer
Joined: 09 May 2007
Posts: 64
Location: Dustin Acres, California
|
Posted: Mon Jul 02, 2007 6:08 pm
|
Yeah, it's not the weekend anymore -twiddle-
|
|
_________________
EDIT: Image moved to Avatar FINALLY. |
|
|
|
|
|
|
