Just had a chat with some of the admins and it seems they disagree that the MXP protocol states that bare ampersands must be escaped in MXP mode. Looking at the spec for the protocol here https://www.zuggsoft.com/zmud/mxp.htm I can't see where it says that. I think applying Jor'Mox's REGEX should be...

Thank you, Jor'Mox. Yes, I wrote that too quickly last night under insomniac conditions :-). You are right that the rule to only allow those specific characters i.e. the REGEX &[a-zA-Z_][a-zA-Z_0-9:.\-]; would work in most cases to flush out naked ampersands. Could an entity start in one buffer ...

So that rule and regex helps the case where someone has written a naked ampersand in the form of "You are standing at the intersection of Church St & University Road" but not in the case "You flick on the TV and see the closing credits to the Tom&Jerry show". It also does...

p.s. Can we please change the title of this thread to "MXP processing hang - unescaped ampersands" - it might signpost the way for others in the future.

No reply yet from our Admins from the game's message boards, I will try them on live chat and also via email. I wonder if the MXP spec says what the maximum length for an entity name is? If it is 255 (like C variable names) then Mudlet could: - Warn the user if no semi-colon was found for a correspo...

I've asked the admins.
I'm currently running with my local patched build of Mudlet.
Looks like someone else had a similar issue with this on another MUD: http://www.slothmud.org/forum/viewtopic.php?f=7&t=5002
I don't think MUDrammer has MXP, not sure about the mud connector one.

Not yet, our MUD isn't very well supported these days, for one reason. I'm interested in what we can do in Mudlet to fix this. I'm also curious why other clients are able to cope with this, but Mudlet is not. For example the Mud Connector web-based session (screenshot above) and MUDrammer iPhone cli...

Hi Vadi,

Yes, MXP is supported on my MUD, so the naked & is wrong in the output. I think Mudlet could check if '& ' (i.e. ampersand space) was present and if so treat it as a bare ampersand. If you agree I can raise a PR - I have figured out a minimal change to check that.

After much debugging I finally figured this issue out. It is not due to ANSI codes but MXP processing. It is due to the line '& = blinking' line. The ampersand is not written as & and so it is interpreted as the start of an MXP entity which is never closed. All subsequent output from the...

Hi, This is Mudlet 4.17.2 on MacOS 12.7. Connecting to cthulhumud.com:8889 via the mudconnector I can run the 'help color' command fine. When I run that command in Mudlet, the output hangs, although I can still type commands to the mud and the mud sends output back the Mudlet (this is visible in the...