Mudlet The Mud Client

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.

Doors

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 Responses

  1. 13.1.1 update | m&m

    [...] 2.0, and Mudlet 2.1 have been released! With this update, feel free to upgrade your Mudlet. Your m&m and normal [...]

  2. Steve

    How can you expect to have a successful mud client if you only support Windows? You have to be platform-independent, or you won’t get any traction. I’m trying to revive my old mud, but Mudlet is obviously not for me or a significant fraction of the old players, who are often rabid Linux and Mac supporters. Why not JAVA or HTML5 or anything platform-independent? You have to at least port the client to both OS X and Linux, or your client is not even worth a closer look.

  3. Vadi

    Doesn’t look like you had any look at the client at all to begin with. Visit the downloads page, you’ll find that Mudlet is a completely cross-platform client supporting Windows, Mac and Linux right from the start. All Mudlet scripts are cross-platform as well.

  4. Steve

    Oh, sorry, I guess you are multiplatform, but your “Downloads” page is very misleading, and other parts of your website are quite uninformative or completely lacking in information. Get it together, guys!

  5. Vadi

    Does your browser support Javascript properly? The downloads page clearly shows that you can select your chosen platform, and it defaults to Windows (the most common one).

  6. Steve

    Yes, I see it now, but there was soo much space between the Windows options and the other ones, and then with the light coloring scheme, I just didn’t see it at first. But yeah, my bad.

  7. Vadi

    Alrighty! The spacing was improved, cheers.