Zugg Software :: View topic

Apprentice Joined: 26 Sep 2001 Posts: 124

Hello people :)

I have noticed that sometimes, while triggers/scripts/functions are being processed by Zmud, that the mud output in that particular moment doesn't undergo trigger processing.

This is most noticable during long speedwalks, or while there is an automated script running.

Is there anyway around this? (apart from getting a faster machine)
I have tried increasing the process priority for zmud, this helps a little but doesn't fix the problem.

Running zmud 7.11a (7.05 does this too) on WinXP Pro 1.6ghz , 512MB Ram

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

No, not really. You can perhaps fiddle with your triggers to make them:

1)faster -- the faster they work, the less processing time they take up

2)more explicit -- the more specific the trigger pattern, the less it will fire (by the way, failing a trigger pattern is much faster than testing for a success)

3)more textual -- using more text in the pattern means the pattern can be parsed faster

4)disabled when not applicable -- all settings take up memoryspace, we can't do anything about that without resorting to data files (which are slower and maybe would slow you down even more). However, only the active settings are considered when matching trigger patterns, calling aliases, and so on. Turning off the class folder containing your hunting triggers when you are not hunting will probably save you about %10-20 of your processing power, depending on how detailed you got with that triggerset.

Beyond this, the only real difference-maker is to close down programs you aren't using--filesharing, word processing, other games, etc.

Apprentice Joined: 26 Sep 2001 Posts: 124

Thanks, unfortunately for me ive done all of that already.

The problem isn't really that everything slows down (except when i cannot input anything due to trigger processing).. the bigger problem is that output is just skipped.
Im not sure that this isn't a bug.. or if there is a setting somewhere which would prevent any lines from being parsed to the screen before they go through the trigger tests.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

No, it's not a bug. ZMud can only work so fast and you can actually kill the processing speed by having too many triggers active, really bad triggers, or too much of other kinds of processing. I don't exactly know if Zmud deliberately drops processing if it gets a certain amount behind or if it's simply in the middle of a process and simply doesn't get to see the next few lines. I don't think it'd really matter, though, unless on the off-chance you have some sort of corrupted setting causing an otherwise normal trigger to act weirdly.