|
Well for obvious reasons I tend to lean toward implementation of imc2 mainly because it's what I use and develop for. For that reason I tend to know the server and client code fairly well. Personally I prefer the ability for imc2 to implement multiple servers to handle packet routing. As far as users go they won't notice the difference.
The majority of muds on imc2 are actually Diku derived, and of those, they're mainly Smaug muds because Smaug and several of its descendants have actively maintained imc2 client code in them. But as with I3 and Diku, there's no technical limitation keeping LP or any other codebase family from connecting. The protocol itself is openly documented and there are a couple of custom LP implementations out there.
We tend to be failrly laid back. Most people just chat randomly about whatever comes to mind. We don't tend to have a problem with haters with foul mouths showing up to make everyone miserable. There's a decent number of community developers there to help with coding and building issues as well. We also have a game bot which can run trivia and chaos games.
The server and client code are both freely available from the mudbytes community site and it is not required that you join our network in order to make use of the code.
|