629ac004bf
#### Brief overview of PR changes/additions - A DCS/SOS/PM/APC/OSC sequence (`ESC` followed by `P`, `X`, `^`, `_` or `]`) now ends at the end of the line it started on if the game never sends a terminator, instead of discarding everything that follows it for the rest of the session. - Half of a sequence left over from a dead connection is dropped when the next one starts, and the 4096-byte cap no longer leaves the parser stuck with no way out. - Well-formed sequences are untouched: Sixel images and Kitty graphics are still swallowed whole, including ones larger than the cap or split across packets. Their idle-flush carriage returns no longer hide a String Terminator either. #### Motivation for adding to Mudlet One stray escape byte from a game could black out every line it sent afterwards - across line breaks, `clear()` and a full reconnect - with only a BEL able to restore output. #### Other info (issues closed, discussion etc) Fixes #9757. The `ESC ]` half of this is not a 5.0 regression, it behaves identically in 4.22.0, so the bound covers the whole `mGotOSC`/`mGotString` path rather than just the four introducers 5.0 added. Answering the open question in the issue: text lost to the blackout is missing from the log as well, because it never reaches the buffer the log is written from - `logFollowsTheDisplayThroughAnUnterminatedSequence` covers that. New `TelnetStringSequenceRecoveryTest` - 46 cases over a real TCP socket via `TelnetServerStub`. With the fix reverted, 24 of them fail. **Test case:** connect to any game and have it send `PRE<ESC>Ppayload` followed by a newline and a few more lines. Every line after it must still be displayed. Repeat with `X`, `^`, `_` and `]`. |
||
|---|---|---|
| .claude/commands | ||
| .devcontainer | ||
| .github | ||
| .signpath | ||
| .vscode | ||
| 3rdparty | ||
| CI | ||
| cmake | ||
| docker | ||
| docs | ||
| src | ||
| templates | ||
| test | ||
| translations | ||
| .clang-format | ||
| .clang-tidy | ||
| .crowdin.yml | ||
| .cursorrules | ||
| .DirIcon | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .imgbotconfig | ||
| AGENTS.md | ||
| asan-suppressions.txt | ||
| CLAUDE.md | ||
| CMakeLists.txt | ||
| COMMITMENT | ||
| COMPILE | ||
| COPYING | ||
| CPPLINT.cfg | ||
| dangerfile.js | ||
| icon_1024x1204.png | ||
| icon_dev_1024x1204.png | ||
| icon_ptb_1024x1204.png | ||
| mudlet.desktop | ||
| mudlet.png | ||
| mudlet.svg | ||
| README.md | ||
| SECURITY.md | ||
| UI-design-philosophy.md | ||
Mudlet
Play immersive, multiplayer, pure-text RPGs on Mudlet.
About • Key Features • Download • How To Use • Roadmap • Credits • License
About
Mudlet is a quality MUD client, designed to take mudding to a new level.
It’s a modern breed of a client on the gaming scene – with an intuitive user interface, a specially designed scripting framework, and a very fast text display. That, along with cross-platform capability and an open-source development model result in a very likable game client.
Key Features
- Simple to use
- Very, very fast
- Active development
- Big, thriving community
- Powerful trigger engine
- Rich Lua-based coding functionality (API)
- Excellent script editor
- 2D and 3D mapper with autowalk
- Powerful and simple to use GMCP
- Discord integration
- Completely themable
- Open-source and Free
- Cross platform: runs on Windows, macOS and Linux
- Full compatibility: run same scripts on any of the above
Explain?
Easy to use client
We’re big on usability, and as such, creating an easy to use client and interface is one of the defining goals of the project. This applies to both the power users and usual gamers – everyone will feel at home with Mudlet, without having to waste too much time figuring out how to do something.
Designed for speed
Mudlet is designed and built to be very fast and efficient right from the start. Its scripting engine is designed to scale to large systems without bogging down – and the text display is designed to handle thousands of lines in under a second. All in all, we are very serious about Mudlet being quick – and take all measures to make it so.
Powerful Scripting
Mudlet features a scripting framework using Lua – a small, fast and efficient scripting language. This allows Mudlet to leverage the existing community and large ecosystem of existing packages for Lua without the many drawbacks of creating a Mudlet specific scripting language. Best of all, the Lua API is seamlessly integrated in Mudlet and shared by all aliases, triggers, scripts, keybindings, buttons and other Mudlet components.
Cross-Platform love
We believe in making Mudlet available to people on all major platforms, and we work on keeping cross-platform compatibility right from start. Mudlet is available on Linux (both 32bit and 64bit), Windows, and macOS; you may be able to run it on additional platforms as well.
Download
Download for free from mudlet.org.
How To Use
- Download and double-click on Mudlet to run
- Pick an existing game and hit
Connect - ... or play one of your choosing:
- Click
New - Enter
Server addressandPortof your game (found on the game's website, e.g.mygame.comand2003) - Pick a
Profile name - Hit
Connect
- Click
Compiling
If you'd like to compile Mudlet yourself instead of downloading, you can find instructions to do so here.
Vision
Mudlet's vision is to build the best text gaming experience possible to nurture & grow this niche scene.
Roadmap
See the project's roadmap to get an idea of where it's headed
Contribute
Join in, contributions are welcome! Find out how you can start Contributing.
Credits
Author: Mudlet Makers.
This software wouldnt've been possible without these open source packages:
- Qt
- Lua
- PCRE
- edbee
- DBLSQD
- argparse
- Boost Graph Library
- Busted
- Ccache
- Communi
- Hunspell
- lua-http
- lua-yajl
- lua-zip
- LuaFileSystem
- Luarocks
- LuaSQL
- luautf8
- pugixml
- SQLite
- yajl
Credit to Markdownify for the README inspiration.
Windows code signing provided by SignPath.io, certificate by SignPath Foundation.
License
GPL2+