![]() I'll probably have it CC-BY, which is to say that it'll require attribution but otherwise you can fold/spindle/mutilate it at will.Ĭan't make any promises about when this'll happen though - Chahiero and I both have pretty demanding day jobs, so we can never really stick to deadlines. But at the very least the handshakes and sending of the telopt data. I say that as a backwards way of saying 'I dont know how much of the functionality we'll take the time to make independent of our own codebase'. We'll be releasing our TELOPTs module back to the nakedmud community, though we'll probably have to rewrite large segments of it since it uses a lot of custom code - our mud is based on nakedmud but its been changed drastically. But I don't mean to start a holy war or something saying that. body of its archmage leader Tazmekian became the vessel which imprisoned his. It took all the might of Serins Knights of Valour to corner him, and the live. of the ancient dark lord, the Lord of Wrath, Sheundan, commited the most murder. Im not entirely sure why other muds use more complex protocols when a lot of it is unnecessary. Of the seven original evils monsters that scourged Serin after the obliteration. We chose MSDP because it was the most straightforward and standardised really. Got a pingback on the MUD news about this discussion. I'm also toying with the idea of adding an xterm 256 colour function - if muds got it "for free" with their protocol snippet they might be more tempted to use it. I've got commented sections showing where you would add support for MCCP, ATCP, ZMP and MSP, so perhaps that's enough. I'm not sure if I should add any other protocols to it, or keep it simple. MSDP will rely more heavily on the mud, because of the variables, but I'm going to try and keep it as generic as possible. So far I've got it supporting TTYPE and NAWS - I've added the snippet to a copy of GW1 to test it, and it requires only a few simple changes to the mud. I'm planning to release my snippet as PD, so people shouldn't be discouraged by licencing conditions. Nice! I've spoken to a few mud owners who expressed a mild interest - I doubt they'd go to the effort to implement it themselves, but they might be convinced to add a simple snippet. ![]() It is script-able with Perl.While on the MSDP subject, a second MUD server added MSDP support last week. Irssi is first of all a text-based IRC client for Unix-like systems, but can also run command-line programs such as telnet in the same session. TinyFugue - TinyFugue is a Unix MUD Client with a minimal interface and incredibly powerful scripting support. Dated but usable.Ītlantis - Designed from the ground up entirely in Cocoa, and integrates with system services - such as the Mac OS X spellchecker - as much as possible. MudWalker - Last release was around 2005. The client is also freeware, which is a plus. MUSHclient - A powerful client with many scripting languages, active boards, and good support. ZMud - Retired from development, this client was and is still one of the most popular choices.(Free 30 day trial)ĬMud - The new and improved zMud, CMUD is faster and offers a variety of new 'features'. TinTin++ - TinTin is one of the oldest clients available, and is quite flexible if you're willing to overcome the learning curve. It uses LUA for scripting and has a very powerful mapping utility. ![]() Mudlet is a modern client which works on PC, Mac, and Linux systems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |