 |
Fizgar
Magician
Joined: 07 Feb 2002
Posts: 333
Location: Central Virginia
|
 Posted: Sat Sep 25, 2010 2:59 pm
[3.29a-3.29b] Setting trigger options.
|
As of 3.29a and in 3.29b too, the example in the help file
| Code: |
| #TRIG {^~[&hp/&{maxhp}hp &mana/&{maxmana}ma~]} {#IF (@hp < @maxhp/10) {cast 'heal'}} "" "prompt" |
no longer will set the prompt option I tested with nocr also and nothing. How do we set trigger options now?
I was toying with #temp in a script when I discovered this. Not being able to set the options of a temp trigger kind of limits it's usefulness. |
|
_________________
Windows Vista Home Premium SP2 32-bit
AMD Athlon Dual Core 4400+ 2.31 GHz
3 GB RAM
CMUD 3.34 |
 |
|
|
Fizgar
Magician
Joined: 07 Feb 2002
Posts: 333
Location: Central Virginia
|
Posted: Thu Sep 30, 2010 5:39 pm
|
*bump*
|
|
_________________
Windows Vista Home Premium SP2 32-bit
AMD Athlon Dual Core 4400+ 2.31 GHz
3 GB RAM
CMUD 3.34 |
|
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Thu Sep 30, 2010 6:33 pm
|
This bug is confirmed. The TRIGGER command does seem to be processing any of the options (prompt,nocr,regex,stop etc) any more.
|
|
_________________
Asati di tempari! |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Sep 30, 2010 7:01 pm
|
Confirmed and fixed for the next version. It was actually just the first option in the list that was being ignored. Left over from the transition to the json tables/arrays which are 0-based instead of 1-based internally.
|
|
|
|
|
|
|
|
