Finally: in my original road map I mentioned lack of support for the various OPEN/SECURE modes, I now realized it is already here, but somewhat hidden behind the scenes and virtually w/o effects (as many MXP things are in Mudlet). I'd guess, to make it fully work will require only tiny patches here ...

2) Mudlet will force SEND hints to be all uppercase. But not consistently. Without checking every detail, it seems normal <SEND>look</SEND> have a lower case tooltip, but <SEND>say PROMPT</SEND> have it all upper. But if the game explicitly specifies HINTS, they are forced to all upper. You can see ...

Well, 1st things first, I'll be on vacation now for two weeks. I'll be able to react to msgs and are also able to work on code, build mudlet, work on github; but only with very, very little time as my SO will beat me if I sit at the computer for too much time. I just released a bunch of pull request...

Ah, my bad, the powershell script also uses the qmake / make combo. I wonder why it installs cmake first.. but probably there's a reason.

@Tamarindo: Well thanks. About the Windows Build Environment. I still have issues to compile the test code in test/ . From my first work on mudlet some years ago I had some 'make' snippets around that first call qmake with a MudletTest.qmake containing snippets like: Makefile_TEntityResolverTest { S...

While I go through the original PR#4200 stuff - I just made PR#6802 to make simple MXP formats like 'BOLD' etc. work - I realize that this PR might actually be the largest one: When I had it done - and remembering that a colour tag like <C magenta> not closed due to a bug in the mud code (or by a ma...

Hmm, I think the term 'style' from the mxp definition might be a bit misleading here. At the very first, its just some text string that has no effect at all, except that it is returned when the mud asks just <version> and well, <version some-text> does not generate some answer being send to the mud ...

@SlySven: Well this sounds interesting, really.. But as I just got the build environment and I'm also a bit time-constrained, I'd rather not try it yet and break my just created build environment. Hmm... maybe when I'm done with chopping down the MXP PR and resubmitted all pieces.

@Vadi, about MSP segfault: Well sure. At first, this is with 'classical' MSP. According to Mudlet manual/wiki there is a perl regex sound trigger ^!!SOUND\((\S+?)(?: (.+))?\)$ and a similar music trigger ^!!MUSIC\((\S+?)(?: (.+))?\)$ configured, both with actions deleteLine() receiveMSP(matches[1]) ...

Hi people, I've been asked if I wanna revive the 4200 PR, but do it in much smaller chunks, and well, it was done 2 years ago. So, a few tiny things need to be done to it s.t. it fits into the now change development branch. My main goal is, to get all the fixes of 4200 in first (because then mudlet ...