Zugg Software :: View topic - Hideous lag linked to my triggers it seems

Newbie Joined: 15 Sep 2004 Posts: 4

I'm not sure if there's a certain scripting that zmud just doesn't support or what. If I turn all my triggers, aliases, macros and EVERYTHING off, it runs smoothly. If I turn them on I can hardly do anything within the game. Help!

Wanderer Joined: 17 Aug 2004 Posts: 98 Location: OK, USA

What does "I can hardly do anything within the game" entail? Pleae be more specific. Generically, you probably have a settings conflict which you can resolve by reviewing your settings.

Newbie Joined: 15 Sep 2004 Posts: 4

Sorry. What I mean is that the lag is horrible. If anything happens where the spam is too much, zmud freezes up until said spam fights. This includes any spam related to combat or anything else. I can review my settings, however I'm afraid I don't know what I'm looking for.

Wizard Joined: 14 Oct 2000 Posts: 1368

The only way for people to see what is wrong is to check your triggers. Some general optimization hints though:

1. Try to avoid making triggers too general. Instead of doing #TRIGGER {Some message} {} try doing: #TRIGGER {^Some message$} {}. This way zMUD can decide if the text matches the pattern or not faster.
2. If you use #wait you can get lag. You should try to avoid using the #wait command and use #alarm instead. #wait is bad, #alarm is good.
3. Place similar/related triggers in their own classes, and turn off those classes when they aren't needed. For example some trigger sets might only be needed when you are in a group/party.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

The lag is almost certainly from your triggers (including any aliases or other subscripts used by the triggers). The other settings don't react to MUD input and therefore aren't likely to cause lag by themselves.

To identify the problem triggers, disable all the triggers individually (double-click the green circle in the Settings Editor) or by class (disable the class). Then, enable one trigger class, or a small number of individual triggers, at a time until the lag shows up. When you find a problem trigger or group of triggers, disable them again so you can continue testing. Don't assume there's only one problem trigger.

Once you've identified your problem triggers, post them here if you need help finding the actual problems. Remember to include the scripts of any aliases or other subscripts they use.

Newbie Joined: 15 Sep 2004 Posts: 4

Well, alright. I'm not exactly sure what's going on but here's what someone told me who had a look at my system. All throughout my triggers (this system, by the way was not made by me. It was given to me by someone else) the "=" command is used. Apparently, for some reason because of this command the system is creating new variables instead of adding to already existing ones. So, for example I had NINETEEN of the same variable. *die* That is what my friend told me to tell you guys, hopefully she can fix it because I'm a complete moron when it comes to stuff like this. Thanks for your advice and suggestions. Embarassed

SubAdmin Joined: 18 Nov 2001 Posts: 5182

This is most likely cause by having the "Set as default when executing" option checked on your classes. Open your character in offline mode, or disconnect from the mud. Open the Settings Editor (CTRL-G). Click on "none" in the Class Panel (left pane), if you do not see a Class Panel select the menu option within the Settings Editor "View|Show Class Panel". Next in the Settings panel select the first of your class folders. Then check for the option in the Editor window (usually docked at the bottom). Repeat this for all class folders shown in the Settings panel. Next work you way down the Class Panel selecting any that have a + in front of them. Again check all classes, in the Settings panel. Lather, rinse, and repeat until you have checked every class. Finally delete all duplicate variables leaving only one in whatever class you actually want it in.

If you have further speed problems Lightbulb has posted the only method there is for actually tracking down the cause of them. Rorso has already provided all the pointers there generally are, I wish to further stress do not use #WAIT within a portion of script executed by a trigger.

Since you didn't write the script I can assume you won't be familiar with it, if possible you might wish to ask the author about this. Otherwise I would suggest exporting the script to text then using find in notepad to check for #WAIT. If you find any you should post that portion of the script for more help.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

While you do have a variable problem if you have 19 of the same variable, it's probably not what your friend thinks. In many computer languages, = is used to assign a value to a variable while == is used to get the value. However, this is not the case in zMUD. In zMUD, = and == are interchangeable, although only = is documented.