Sorry for the late response - 4.18.5 should fix this for you now!

Just a heads up that was all machine translated (see context https://discord.com/channels/2835815825 ... 9384709170), so it would be great to have a human double-check those translations!

Are you both on the same internet connection? Latency could play a part here.

Windows builds are unfortunately currently broken. Any help in this area is welcome

MXP is modelled after XML as Jor'Mox posted, and to represent an apostrophe in XML, you need to use '. Here is a selection of links backing this for the game admins: https://www.baeldung.com/xml-encode-special-characters#standard-xml-entities https://en.wikipedia.org/wiki/List_of_XML_and_HT...

Not sure how to do that in a user friendly way that will work for all kinds of users, including the technically challenged ones - but we should do better on our end for sure.

Just as legal as the MUD not escaping ampersand which is not at all. Are other clients supporting MXP? My first port of call wouldn't be to add workarounds to a third party but fix the issue at the source. Adding workarounds to Mudlet carries the risk of breaking another game, and we shouldn't jump ...

Have you tried getting it fixed in the game first?

If there is any other case where an ampersand is shown incorrectly and a space doesn't follow it, this workaround for the game won't work it also has potential to break other games.

Great work

Is your game using MXP? Because if it is, all ampersands do need to be reported as &

You only need to have one version of the mapper installed, so remove the IRE mudlet mapper.