Most of the time, the server should tell Mudlet to enable UTF-8, but if it doesn't, you can do it manually by going to Settings > General and modifying the setting Server data encoding to UTF-8 (Recommended) Tell Mudlet to NOT highlight your command history text as you scroll through it by going to Settings > Input Line and ❎unchecking Highlight history. Tell Mudlet to not keep the last input in your input bar by going to Settings > Input Line and ✅checking Auto clear the input line after you sent text. You can find more information on the Mudlet gui article.Ĭommon configuration changes Do not keep last input Threshold has an unofficial, if useful, UI package that can be installed from within game. 2.2 Do not highlight input history text.sysDisconnectionEvent will properly fire when the MUD disconnects youīig 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.I cant think of any other specs to support. CHARSET (42) - Probably no need to support CHARSET, I know if I send a IAC DO 42 to mudlet 2.1.0 it just says IAC WONT 42, meaning it doesnt care, and just send whatever youve got I guess. Package Exporter won’t show temporary items NAWS (31) - Mudlet sends 100 width and 58-64 height, dunno what other clients send.fixed mapOpenEvent to go off on createMap(), Geyser.Mapper:new() or Vyzor.Map().fixed gmod.enableModule() to work again.fixed Geyser.MiniConsole:setTextFormat().fixed display() showing ‘nil’ after non-table items.improved script editor timer’s view to make it more intuitive.added setMergeTables() for specifying which GMCP modules should be merged, and which should be replaced (only for use in certain low-level scripts).
added setExitWeight(), getExitWeights() for adding weights to cardinal or special exits.added setDoor(), getDoors() for adding foors to maps.added IRE.Rift to default list of enabled modules.added addSupportedTelnetOption() and a sysTelnetEvent event for open telnet support.It’s a long-running game that makes great use of MXP, and was used for MXP compatibility testing during Mudlets MXP development. Potentially unlimited concurrent telnet server sessions supported. High performance multi-threaded and asynchronous. Compatible with all telnet clients and supports UTF-8 and Unicode.
#MUDLET 2.1 WINDOWS#
Slothmud has been added to Mudlets pre-existing MUD list. SLNET v6.2 is available for Windows Server 2012, 20. See the addSupportedTelnetOption(), sendSocket() functions and the sysTelnetEvent event for making it happen – along with this guiding writeup. This is on A Moment in Tyme MUD located at port 6969. However, if you’d like to make something else work, such as MSDP or MSP, you now have the ability to make it happen. Public bug reported: Auto-login worked fine in mudlet 2.1, but since upgrading to 2.1 whenever it submits the username/password the MUD responds with: Name contains invalid characters, try again. Mudlet already supports Aardwolf’s 102, ATCP, GMCP and MXP protocols – these are built-in and require no effort to enable. 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.
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.
Edit: Image edited to omit some information at the request of person I am posting for. With these two map features in, Mudlet’s map format was upgraded. Okay So this has been tested across all version of mudlet and crash still occurs. See the new setExitWeight() and getExitWeights() functions for doing so. Using exit weights, you can tell Mudlet which exits are more or less desirable to take, and thus be quicker in your speedwalking. 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. Like room weights which Mudlet already has, exit weights can make certain exits be more or less desirable for taking. The next feature that does affect pathfinding are exit weights. I was going to suggest you might have more luck on the Mudlet forums, but it looks like theres a thread about this over on. The doors status can be set to – open (green color), closed (yellow color) or locked (red color).ĭoors 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.ĭoors are set the the API – see setDoor() and getDoors() functions for doing so. 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 mapper can now visually show you where doors are with a little rectangle on the exit.
0 kommentar(er)
