 |
Gregorius Beginner
Joined: 12 Nov 2006 Posts: 16
|
Posted: Sun Dec 03, 2006 1:49 pm
[1.18] Case sensitive option in triggers |
Created 2 triggers firing on different patterns:
Pattern: * Slightly good$
Script: #echo test
and
Pattern: * Good$
Script: #echo test2
Checked 'case sensitive' box for both triggers.
What happens: Pattern 'Slightly good' fires both triggers and unchecks the case sensitive box. |
|
|
 |
Fang Xianfu GURU

Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Sun Dec 03, 2006 2:02 pm |
How bizarre. Confirmed, though.
|
|
|
 |
Zugg MASTER

Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon Dec 04, 2006 10:24 pm |
Maybe this is already fixed for 1.19, but I cannot reproduce it.
I don't see how 'Slightly good' would fire the first trigger since you have a '* ' in front of it, so you need some other text first.
Please try to give me the exact commands that you typed to see this. Here is what I tried:
#trigger {* Slightly good$} {#echo test} "" {case}
#trigger {* Good$} {#echo test2} "" {case}
#show test Slightly good
This fired the first trigger and showed "test" on the screen.
#show test Slightly Good
This fired the second trigger and showed "test2" on the screen.
I didn't have any problems with anything unchecking the case sensitive box. |
|
|
 |
Fang Xianfu GURU

Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Mon Dec 04, 2006 11:16 pm |
Definitely works. I created this trigger in the settings editor (not from the command line):
#trig {Slightly good} {#echo slightly good} "" {case}
and got a trigger loop error from the echo. When I go into the settings editor, there's no check in the case box. |
|
|
 |
Zugg MASTER

Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon Dec 04, 2006 11:31 pm |
OK, looks like this was related to one of the other bug fixes with the trigger options, because the above example doesn't cause a trigger loop in 1.19.
|
|
|
 |
|
|