 |
jed
Adept
Joined: 18 Dec 2005
Posts: 246
|
 Posted: Sun Mar 04, 2007 4:04 am
[1.25] #t- odd behavior
|
type #t- aaaaahahahahbhblelleeeeeha
in the command line.....
I get a new class created called aaaaahahahahbhblelleeeeeha when I do this. This also happens when I use #t- for a trigger that is disabled. Is this a feature.... or a bug? |
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4805
Location: Pensacola, FL, USA
|
Posted: Sun Mar 04, 2007 4:18 am
|
this behavior happened in zmud as well... if there is no active setting to go with the name used, it creates an empty class.... annoying really
|
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Sun Mar 04, 2007 3:34 pm
|
That is rather when you consider that the whole point of the #t- command in my eyes was that there was no possibility of it making a bunch of settings if you accidentally typoed. That's why I hate using #class, going through and deleting all the settings it creates can be a nightmare in some scripts.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Apr 11, 2007 8:54 pm
|
I agree that this behavior from zMUD is definitely a "wierdness" and I've changed it for v1.27 (and have added a help topic to the Changes for zMUD users section).
In CMUD 1.27 and later, #T+ and #T- will *never* create a new class. Whereas the #CLASS command will *always* create a new class if needed. If you used
to create a new class in zMUD, you will need to change this to
in CMUD. Specifying the "1" to enable the class forces it to create the class but does not change the currently active class.
Also, I've fixed #T+ and #T- so that the "Type" argument works properly and will pick the specified setting type rather than look for a class with the matching name.
Also, Events now have ID values that can be used with #T+ and #T- |
|
|
|
|
|
|
|
