MUD Client Setup
Modern MUD clients have come a long way from the bare telnet days. You can play most MUDs instantly in a browser, or connect with a polished desktop client that gives you logging, triggers, aliases, mapper work, Lua scripts, and GMCP-driven UI. A browser client is the fastest, lowest-friction way to start. Mudlet is the strongest next step on Mac and Windows, while Blightmud is the standout choice for Linux and terminal users.
Use the browser client first. It removes setup friction and already understands Icesus-specific data.
Use Mudlet when you want local logs, profile backups, custom UI, Lua, mapper experiments, and richer triggers.
Start with the browser client and type screenreader on in-game. See the accessibility notes before building a custom client stack.
Connection Settings
Any MUD client that can open a telnet-style connection can reach Icesus. Use these settings when a client asks for host and port.
| Setting | Value |
|---|---|
| Game | Icesus MUD |
| Host | icesus.org |
| Standard port | 4000 |
| TLS port | 4443 |
| Encoding | UTF-8, if the client asks |
| Website | https://icesus.org |
| Browser client | https://play.icesus.org |
Which Client Should You Use?
| Use case | Best fit | Reason |
|---|---|---|
| First login, quick return, mobile or borrowed machine | Browser client | No install, Icesus-aware UI, good defaults, screen reader support, GMCP, hotkeys, exits, maps, manual momentum buttons, and basic triggers. |
| Experienced MUD player building a durable setup | Mudlet | Cross-platform desktop client with aliases, triggers, Lua, mapper, GMCP, logging, profiles, and package export. |
| Windows veteran with an existing profile | MUSHclient, CMUD, or zMUD | Perfectly usable if you already know the client. Expect more manual work for modern Icesus GMCP/UI features. |
| Terminal-first player | Blightmud, TinTin++, or TinyFugue | Fast, scriptable, keyboard-native, and comfortable over SSH or in a terminal multiplexer. Blightmud is the recommended modern terminal client — it has an official Icesus package that drops in a GMCP status bar with no scripting required. TF and TinTin++ are veterans. |
The Browser Client
The Icesus browser client should be the default recommendation for anyone who wants to play now. It is not a toy fallback; it is an Icesus-specific client with strong GMCP support, visible exits, mobile controls, hotkeys, screen reader behavior, momentum buttons, and basic trigger support.
It is also the reference point for how Icesus client data is meant to feel. If you later build a Mudlet HUD, the web client is worth studying: vitals, room data, party state, casting progress, cooldowns, and momentums are presented as player-facing information, not as unattended automation.
Use the browser client when you want:
- Immediate play without installing a mud client.
- A clean default layout for Icesus-specific information.
- Screen reader support and keyboard-friendly controls.
- Basic trigger support without writing Lua.
- A safe baseline before building your own desktop setup.
Mudlet
Mudlet is the best mud client choice for many serious Icesus players because it combines a modern desktop UI with powerful client-side customization. It is especially strong if you care about long-session comfort: readable fonts, searchable logs, aliases, highlights, custom windows, mapper experiments, GMCP dashboards, and portable packages.
There is now an official Icesus Mudlet package: one .mpackage install gives you the same panels the browser client uses — vitals, EXP, casting, cooldowns, status effects, an enemy bar, exits, and a channel feed — without writing a single trigger. Most players should start there. Build the rest of your profile (logging, aliases, highlights) on top of it.
GMCP — Structured Data from Icesus
Icesus speaks the Generic MUD Communication Protocol (GMCP) alongside the plain text stream. While room and combat lines scroll past, GMCP quietly delivers the same information as structured data the client can act on directly: current HP / SP / EP, room name and exits, party member vitals, casting progress, cooldowns, momentums, screen-reader mode state, and more. That feed is what makes a sidebar HUD, a vitals bar, or a manual momentum panel possible without scraping the text stream for numbers.
Any modern Icesus client setup should turn GMCP on. The browser client uses it natively for its side panels, vitals bars, exit list, and party grid. Mudlet and Blightmud have first-class APIs. Older terminal clients can reach the same data through scripting, with more glue.
| Client | GMCP | What you get on Icesus |
|---|---|---|
| Browser client | Native | Side panels, vitals bars, exit list, party grid, manual momentum UI — wired up out of the box. |
| Mudlet | Built-in | Install the official Icesus Mudlet package for a ready-made HUD over GMCP, or wire your own handlers using the Mudlet GMCP guide. |
| Blightmud | Built-in | Install the official Icesus Blightmud package for a drop-in two-row status bar over GMCP, or wire your own handlers using the native gmcp Lua API. |
| TinTin++ | Via scripting | GMCP arrives as Telnet subnegotiation; #event {IAC SB GMCP} handlers can parse and react. Works, but more manual than Mudlet or Blightmud. |
| TinyFugue | Via scripting | Same telnet-subneg story. Possible, but Icesus GMCP is rarely used from TF in practice. |
| MUSHclient / CMUD / zMUD | Yes | Each has its own GMCP plugin pattern; copy the standard idiom from the client's documentation. |
| Plain telnet | No | GMCP frames are silently dropped. You only see the text stream — fine for testing, not for play. |
For the deep dive on which Icesus GMCP modules exist (vitals, room, party, casting, cooldowns, momentums, screen-reader state) and how to handle them on the client side, read the Icesus Mudlet GMCP guide. The module list and event names apply equally to Blightmud or any other GMCP-capable client; only the language around the handlers differs.
Other Desktop Clients
MUSHclient
WindowsclassicLua
MUSHclient is familiar to many long-time MUD players and can be a comfortable Windows setup if you already have scripts or muscle memory. For a fresh Icesus profile, expect more manual setup than Mudlet, especially around modern UI and GMCP presentation.
UTF-8 note: MUSHclient does not handle UTF-8 out of the box, so Scandinavian characters (ä, ö, å) come through garbled. Install Shikan’s UTF-8 plugin for MUSHclient, switch the output font to one with full Unicode coverage (Lucida Console works), and tick the UTF-8 (Unicode) box in Game → Configure → Output.
~/.tintinrc for Icesus.
TinyFugue
terminalvisual modeworlds
Compact TF5 setup with visual mode, UTF-8 (8-bit clean), /addworld autoconnect, and auto-reconnect.
Blightmud
terminalRustLuaGMCPofficial package
Modern terminal client. Drop in the official Icesus package for an instant two-row GMCP status bar (HP/SP/EP, EXP, time, per-enemy HP), then extend with your own Lua triggers, timers, and keybinds.
CMUD and zMUD
Windowslegacyprofiles
CMUD and zMUD still matter because many veteran players have old setups. They can connect to Icesus, but new players are usually better served by the browser client or Mudlet.
Plain telnet
minimaltesting
A plain telnet-style client can be useful for testing connection problems, but it is not a comfortable long-session setup. You will miss logging, history, highlights, trigger management, and structured client data.
What a Good Icesus Client Setup Does
A good client setup is mostly boring in the best way. It connects reliably, keeps readable logs, makes important text visible, and helps you type deliberate commands accurately.
- Display: readable font, ANSI colors that do not blur together, sensible line width, and visible prompts.
- Logging: raw logs for quests, syntax, bug reports, and trigger testing.
- Aliases: build-specific shortcuts, such as combat point assignments or explicit spell commands.
- Triggers: highlights, alerts, food/drink helpers, party readability, crafting repeaters, and other rule-safe quality-of-life tools.
- GMCP: use structured data for vitals, room info, party state, casting, cooldowns, and manual momentum display when the client supports it.
- Backups: export your profile before major changes.
Automation Rules Matter
Icesus allows client-side quality-of-life work, but it does not allow unattended play. Do not build scripts that hunt, fish, move, heal, loot, fight, or use combat momentums while you are not actively controlling the character. Triggers should make you a better present player, not an absent one.
Before building serious triggers, read the in-game help files through the game or the local web snapshots: help triggers and help robots.
Accessibility
If you use a screen reader, start with the browser client and type screenreader on after logging in. The browser client is designed for screen reader use and adapts to Icesus screen reader mode. Desktop clients can also work well, but their accessibility depends on operating system, screen reader, font settings, color choices, sound alerts, and how aggressively you gag or rewrite output.
Read the Icesus accessibility page before building a custom setup. Do not make color or sound the only signal for important events.
Practical Setup Path
- Open play.icesus.org and play enough to learn what information you actually care about.
- If you want a desktop client, install Mudlet and create a clean Icesus profile.
- Enable logging before writing triggers.
- Add aliases for your own combat assigns, spell commands, and skill commands.
- Add highlights and alerts from real Icesus log lines.
- Use GMCP for vitals, room, party, casting, cooldown, and momentum display instead of scraping text where possible.
- Back up the profile before importing packages or writing larger Lua scripts.