Mudlet The Mud Client

Mudlet is a quality MUD client, designed to take mudding to a new level.

It’s a new breed of a client on the MUD scene – with an intuitive user interface, a specially designed scripting framework, and a very fast text display. Add to that cross-platform capability, an open-source development model, and you have a very likable MUD client.


Latest news

Windows download link inoperational

January 31st, 2014

The link to download the Windows version of Mudlet is not currently working, so use this one instead. We are currently investigating the issue.

Posted in Uncategorized | Comments Off

Call for MUD map stats!

November 30th, 2013

In complement to the Mudlet map call, we’d also like to gather MUD map statistics from those who haven’t got a Mudlet map for their game. If possible, please provide detail on our forums or email privately to The details we are interested in are:

  • total map size (including wilderness / grid-space – so all rooms in the MUDs)
  • total number of exits, number of wilderness (grid-zone) areas, number of non-wilderness areas, number of wilderness rooms, number of non-wilderness rooms.

Thank you!

Posted in Uncategorized | Comments Off

Call for maps!

November 29th, 2013

We on the Mudlet team are investigating Mudlet’s pathfinding performance. Mudlet has been available to players for five years now, and the mapper capability of it for about three – allowing plenty of time for people to find ways to push the client to the limits. We’ve had anecdotal evidence that the pathfinding performance isn’t up to par on everybody’s combination of machine and map – so we’d like to do some concrete investigation on this, and improve the performance.

We’ll do the investigation in two stages:

  1. collect real-world Mudlet maps: this would show us what kinds of scenarios are practically used out there, so that when optimizing the pathfinding algorithm, we account for all cases that are practical, and don’t need to have the impractical ones slowing pathfinding down.
  2. create a benchmark: this would help us test current performance on all of the maps we gather, and improved performance as we optimize the algorithm. We’ll also release this benchmark to you, the users, so you can test on  your own hardware setups and give us some numbers.


We’ll start by collecting maps to analyze. If you’ve mapped something in Mudlet, please help us improve by submitting your map!

Posted in Uncategorized | 1 Comment »

Updated Linux installers

September 21st, 2013

The generic Linux installers have been updated to include the recent libhunspell library that they require, since some older systems (ie, Ubuntu 10.10) provide an older version than Mudlet requires.

In other news, development on Mudlet 3.0 is steadily coming along as well! Mudlet is also five years old now, with work having started back in August 2008.

Posted in Uncategorized | 5 Comments »

Mudlet 2.1!

January 7th, 2013

Hot on the heels of 2.0, Mudlet 2.1 is here – bringing more useful features and fixing things up.

New Mapper features

Two new features were added to the mapper: showing of doors on the map, and setting weights on exit.


tK6fS Mudlet 2.1!

Mudlet mapper doors

The mapper can now visually show you where doors are with a little rectangle on the exit. The graphic we went with is minimalistic and looks good on both small and big zooms – a square in the middle of the exit. The doors status can be set to – open (green color), closed (yellow color) or locked (red color).

Doors are purely visual and don’t affect pathfinding, however your speedwalking scripts can make use of the information to auto-open doors and so forth.

Doors are set the the API – see setDoor() and getDoors() functions for doing so.

Exit weights

The next feature that does affect pathfinding are exit weights. Like room weights which Mudlet already has, exit weights can make certain exits be more or less desirable for taking. For example, if one exit takes away your ability to talk for 5 seconds while the other doesn’t at all, but you have two of them in a row – obviously the two in a row are more desirable than the one. Using exit weights, you can tell Mudlet which exits are more or less desirable to take, and thus be quicker in your speedwalking.

See the new setExitWeight() and getExitWeights() functions for doing so.

New map format

With these two map features in, Mudlet’s map format was upgraded. This means that maps made earlier 2.1 and on 2.1 will load on Mudlet 2.1 okay, but maps maps made on the new 2.1 will not load properly on 2.0, and anything earlier.

Open Telnet support

Mudlet 2.1 gains open telnet support – which means that the users are now able to implement, with their effort, support for new telnet protocols in Mudlet. Mudlet already supports Aardwolf’s 102, ATCP, GMCP and MXP protocols – these are built-in and require no effort to enable. However, if you’d like to make something else work, such as MSDP or MSP, you now have the ability to make it happen. See the addSupportedTelnetOption(), sendSocket() functions and the sysTelnetEvent event for making it happen – along with this guiding writeup. Enjoy!

New MUD added

Slothmud has been added to Mudlets pre-existing MUD list. It’s a long-running game that makes great use of MXP, and was used for MXP compatibility testing during Mudlets MXP development.

Improvements in this update

  • added a cancel button in label-making
  • added addSupportedTelnetOption() and a sysTelnetEvent event for open telnet support
  • added IRE.Rift to default list of enabled modules
  • added multiview option to menu bar
  • added setDoor(), getDoors() for adding foors to maps
  • added setExitWeight(), getExitWeights() for adding weights to cardinal or special exits
  • added setMergeTables() for specifying which GMCP modules should be merged, and which should be replaced (only for use in certain low-level scripts)
  • display({}) will now show {} instead of {\n}
  • improved script editor timer’s view to make it more intuitive

Fixes in this update

  • fixed display() showing ‘nil’ after non-table items
  • fixed Geyser.MiniConsole:setTextFormat()
  • fixed gmod.enableModule() to work again
  • fixed mapOpenEvent to go off on createMap(), Geyser.Mapper:new() or Vyzor.Map()
  • map label message stayed on screen
  • Package Exporter won’t show temporary items
  • sysDisconnectionEvent will properly fire when the MUD disconnects you


Big thanks to everybody who provided feedback on desired new features and problems! Communicating with us is the best way to bring relevant issues to our attention.

Posted in Uncategorized | 7 Comments »

« Previous Entries