I've noticed over the last day or two that MUSHClient has started to struggle to process text in combat at all. Often not receiving any text at all, or allowing me to send commands, then after a few minutes it'll show me a large block of text and not match any triggers at all.


3776h, 1537m, 3424e, 10p, 17600en, 16015w sSilrxkdb-
You take a drink of a potion of mana from a glowing opal vial.
Your mind feels stronger and more alert.
3776h, 2164m, 3424e, 10p, 17600en, 16015w sSilrxkdb-
You have recovered equilibrium.
3776h, 2164m, 3424e, 10p, 17600en, 16015w esSilrxkdb-
You exert superior mental control and your wounds clot before your eyes.
3776h, 2104m, 3424e, 10p, 17600en, 16003w esSilrxkdb-
Aeden takes a drink from an opal vial.
3776h, 2104m, 3424e, 10p, 17600en, 16003w esSilrxkdb-
You are haunted by the oracular visions of dark possible futures, which fill you with fear and dread.
You stumble as your right leg shrivels into a useless appendage.
You exert superior mental control and your wounds clot before your eyes.
3776h, 2044m, 3424e, 10p, 17600en, 15991w esSilrxkdb-
You exert superior mental control and your wounds clot before your eyes.
3776h, 1984m, 3424e, 10p, 17600en, 15979w esSilrxkdb-
You may apply another salve to yourself.
3776h, 1984m, 3424e, 10p, 17600en, 15979w esSilrxkdb-
You may drink another purgative or curing potion.
3776h, 1984m, 3424e, 10p, 17600en, 15979w esSilrxkdb-

Aeden bows his head and a shimmering light passes through him.
3776h, 1984m, 3424e, 10p, 17600en, 15979w esSilrxkdb-
Aeden bows his head and a shimmering light passes through him.
3776h, 1984m, 3424e, 10p, 17600en, 15979w esSilrxkdb-
Aeden takes a long drag off his pipe.
3776h, 1984m, 3424e, 10p, 17600en, 15979w esSilrxkdb-

This is the most recent example. I've not changed anything recently system wise, for about four days now, and I've not installed any new programs. Likewise, I don't experience this problem in Mudlet when I'm running my Aetolia system which is far less streamlined.

Any suggestions?

The lack of timestamps makes it hard to discern any lag in this log, but I'm experiencing the same sort of thing. It generally has to do with too many complex things going on at once (my problem may be gmcp based).

1. Optimize how many triggers are active and/or firing. For example, your prompt trigger should have a high priority (low sequence number) and prevent other triggers from being checked after it.
2. Optimize your code to call fewer functions, check fewer conditional statements, execute fewer instructions, whatever. Putting a function name in the 'script' box and calling it from your script file is faster than putting the code right into the 'send' box, as it doesn't get re-compiled every time the trigger/alias matches.
3. Watch out for too much memory allocation. MUSHclient's Lua engine tends to take a fairly lazy approach to garbage collection, so I have a timer that does it manually.

I noticed when I was using mushclient that it was NOT very memory efficient, over time it would slow down more and more until eventually I had to quit out and reload.

Since I have swapped to MUDlet I have not had that issue, but on the flipside triggers and the like are not as userfriendly, I have been having a hard time learning how to set up what I had in the past.

MUSHclient itself doesn't have any memory issues, but some scripts are inefficient in their own use of memory.