 |
acaykath
Wanderer
Joined: 03 Aug 2005
Posts: 84
|
 Posted: Thu Sep 22, 2005 3:35 am
Classes Losing flags when ZMud Exits
|
I have ZMud 7.13b and I have some spamming classes that I want to disable when I connect to the mud. I have tried setting the disable on connection flag in the script (from the superclass and in the classes themselves), and with the GUI. I have tried with with the classes being enabled and with the classes being disabled. I have tried it without saving, with saving on the class menu, and with saving on the Settings window menu. I have tried refreshing. No matter what I do, the next time I open zMud, the disable flag is gone. How can I get it to stay?
|
|
|
|
|
billaben
Wanderer
Joined: 02 Sep 2005
Posts: 60
|
Posted: Thu Sep 22, 2005 3:55 am
|
This is how I do that. The #CLASS SomethingSomething 0 line only executes once, as soon as you load the script or login or whatever. It immediatelly disables the class before it does anything.
| Code: |
#CLASS {System|SomethingSomething}
#CLASS SomethingSomething 0
#NOOP Some stuff or something
#NOOP
#NOOP
#CLASS 0 |
|
|
|
|
|
acaykath
Wanderer
Joined: 03 Aug 2005
Posts: 84
|
Posted: Fri Sep 23, 2005 4:42 pm
|
Zmud does not allow "#CLASS SomethingSomething 0" it is automatically truncated to "#CLASS 0" if I modify the one at the end of the class. If i insert iy into the class as in your example it messes up the trigger and zMud freezes.
Putting it in my autolog trigger seems to work though, but i'd prefer if the actual "disable class when connecting to mud" checkbox worked instead of having to do a work-around like this. |
|
|
|
|
|
|
|
