Basically, when running GMCP and MXP on this Mud, every " becomes a &. As per this thread (http://www.materiamagica.com/forum/12-s ... and-mudlet) this was also seen in CMUD and had to be corrected in the client.
Normally I'd just turn off MXP but without that I get no prompt, which just won't work.
Issue with " transforming to & in Materia Magica
Re: Issue with " transforming to & in Materia Magica
MM is using MXP/HTML >/< tags outside of the context of MXP lines. Mudlet does handle these tags, but only in MXP lines, not in regular text lines. I consider this a MUD bug, but you can use a trivial workaround.
Simply setup 2 substring triggers that match > and < and then replace them by ". This will settle the issue.
I can load these 2 triggers as the MM default package for new users in the future.
script:
Simply setup 2 substring triggers that match > and < and then replace them by ". This will settle the issue.
I can load these 2 triggers as the MM default package for new users in the future.
script:
EDIT: added a package
- Attachments
-
- MateriaMagical_MXP_fix.xml.xml
- (3.46 KiB) Downloaded 666 times
Re: Issue with " transforming to & in Materia Magica
That didn't work for me. After creating the triggers, or importing that package, say " still displays You say, '&'.
Re: Issue with " transforming to & in Materia Magica
This was indeed a client bug. It's already fixed in forthcoming git and 2.0 stable release. The fix makes above package superfluous.
Re: Issue with " transforming to & in Materia Magica
The MM server has a few bugs also (forward to MM admins please):
1. first login fails with obvious gmcp + mxp parsing problem at the server end (the server doesn't understand the clear text login because it's input buffer is somehow full of garbage at this point and this garbage (obviously GMCP package leftovers) are being added to the login.
2. The first welcome message contains MXP i.e. the clear text " symbol is being expanded to " outside of MXP context. MXP is only being enabled afterwards.
1. first login fails with obvious gmcp + mxp parsing problem at the server end (the server doesn't understand the clear text login because it's input buffer is somehow full of garbage at this point and this garbage (obviously GMCP package leftovers) are being added to the login.
2. The first welcome message contains MXP i.e. the clear text " symbol is being expanded to " outside of MXP context. MXP is only being enabled afterwards.