Yeah, the alertness line really hasn't ever been touched by myself, it worked and has worked since well, uh, forever?, only briefly touched its function when the whole line wrap thing was changed so it wasn't stuck at 80.
So life happened, but peeking in from time to time now, and though I can't promise anything, but hopefully things will pan out so I can settle down and look at the mudbot code and fix whatever problems there are with it, but as said …
(Quote)
That is normal behavior, right now MXP on aetolia will send a weird code to the client and mudbot/I_;Mapper, a fix is in process of being made.
generally you get that error, when mudbot is trying to pass things to the client too fast for the client to keep up. Depending on which client you use, you may want to look into how heavy your system is, cmud has a function: ctrl + q
the ability to click the rooms and path to them is mxp. if MXP-Map is disabled this won't work, or if mxp is disabled in your clients, what clients do you use respectively? since it works for me in cmud.
A little idea, not sure if it is possible. However giving the client a button / toggle, option to log in directly to aetolia.com 23, or to attempt to log into mudbot via 127.0.0.1 port 123
I've messaged you ingame, but it doesn't seem to be a cmud or client related issue but rather that your connection is booted by aetolia, try doing what I suggested via the msg
as I wrote on old forum, if interested in helping me with the latest version of mudbot and imapper, getting it tested thoroughly before release, send me a forum message.
If anyone did this on old forum send it again please.