 |
ZealousAnonymous
Wanderer
Joined: 06 Jan 2006
Posts: 70
|
 Posted: Mon Mar 20, 2006 6:49 pm
Condition vs \n
|
I was trying to convert all of my multiline triggers into condition triggers
using with within=1 parameter.
This seems to be giving me odd problems that I can't seem to figure out. Any words of wisdom? |
|
|
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Mon Mar 20, 2006 10:24 pm
|
| Quote: |
Any words of wisdom?
|
Yeah, tell us about the problem.  |
|
_________________
EDIT: I didn't like my old signature |
 |
|
|
ZealousAnonymous
Wanderer
Joined: 06 Jan 2006
Posts: 70
|
Posted: Wed Mar 22, 2006 1:28 pm
|
It just seems like the withinlines=1 quits working after awhile.
This works fine
You eat a blah\.\n\d+h, \d+m
but the cond starts off fine then just seems to quit working.
I also heard through the grape vine that #COND is a lot faster than \n. |
|
|
|
|
Larkin
Wizard
Joined: 25 Mar 2003
Posts: 1113
Location: USA
|
Posted: Wed Mar 22, 2006 3:37 pm
|
You may just have syntax problems with your triggers or the pattern might need a little tweaking to work better. I don't really recommend you use \n with prompts like that, though.
This is what works for me:
| Code: |
#REGEX {You eat a blah\.$} {}
#COND {^\d+h\, \d+m} {reset blah afflictions} {regex|nocr|prompt|within|param=1} |
|
|
|
|
|
|
|
|
