Almost every MUD has shops and/or player trade, and each has their own UI for this (some of which are better than others). I think trade could be a nice place to improve upon. There's nothing right now that I specifically need above a plain stream of text, but a non-out-of-band protocol would allow for nice things like marking player names as players, items as items etc. MSDP and GMCP basically do the exact same thing with the only significant difference being that GMCP uses JSON and MSDP doesn't. In all the years I've been using MUSHclient and GMCP, I've never once had a problem merging tables. Merging two structures is not the responsibility of a parser. A parser converts a stream of text into a structure. Some JSON parsers don't support merging tables It also has nothing to do with the protocol and is just an example of how two different entities use the protocol very slightly differently which is possible with all protocols and has no bearing on the goodness of the protocol in question. This is such a non-issue and can in fact be handled automatically. You know that and you treat all data accordingly. If you're looking for an HP value and you see '10' vs 10 it doesn't matter. Uh.so? In order to actually use values, you have to know what they mean semantically. Reported problems with GMCP is that Aardwolf reports some values as strings that IRE reports as numbers I'm a MUSHclient fan and also a friend of the author of MUSHclient and also basically an authority on what is or isn't a problem in MUSHclient, and I strongly disagree with this statement. If you're a mushclient fan than MSDP is the way to go. Tintin and Mudlet both support merging tables. Reported problems with GMCP is that Aardwolf reports some values as strings that IRE reports as numbers and that some JSON parsers don't support merging tables which is a huge problem with mushclient.

If you're a tintin fan it doesn't matter much as both MSDP and GMCP are equally supported. So if you're a Mudlet fan than GMCP is the way to go because there's better community support. Mudlet has GMCP enabled by default while MSDP is disabled and needs to be manually activated, which complicates things further. MSDP scripts for Mudlet are hard to find, it appears the developers are heavily invested in GMCP and IRE, and Mudlet has special routines that are only accessible through GMCP. There are over 50 MUDs using MSDP though it appears nothing really interesting or innovative has happened in recent years. Scandum's snippet has some interesting features and some interesting solutions and might be the better choice for people who aren't interested in clickable links.īoth Mudlet and Tintin support SSL as well as MSDP and Kavir also provides an MSDP GUI for Mushclient. Kavir's snippet only uses MXP to handle clickable links, so it's a minimal implementation of the protocol.

They are very different implementations and both snippets are public domain. Kavir's snippet supports MXP and MSDP, while Scandum's snippet supports MSDP and MTTS. The only advantage to GMCP is that on some platforms you can use a JSON parser to easily process the data, but writing an MSDP parser is 'relatively' simple. The GMCP protocol has a few issues, I tried to implement it myself but I quickly realized that MSDP is better in every possible way.

Mudlet mxsp