MUD Client Setup

You can play Icesus, like most MUDs (the multiplayer branch of the text RPG), in a browser tab, or connect with a desktop client that gives you logging, triggers, aliases, a mapper, Lua scripts and a GMCP-driven display. The browser client is the quickest way to start. Mudlet is the usual next step on Mac and Windows, and Blightmud suits Linux and terminal users.

Play in Browser Set up Mudlet Set up Blightmud

New or returning?

Use the browser client first. There is nothing to set up, and it already shows Icesus vitals, exits and party data.

Long sessions?

Use Mudlet when you want local logs, profile backups, custom UI, Lua, mapper experiments, and richer triggers.

Screen reader?

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?

Best MUD Clients in 2026 compares Mudlet, Blightmud, TinTin++, TinyFugue, MUSHclient and browser clients for any MUD. This table is for Icesus.

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	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 terminal client: its official Icesus package adds a GMCP status bar with no scripting. TinTin++ and TinyFugue are older and take more setup.

The Browser Client

The Icesus browser client is the place to start if you want to play now. It is built for Icesus, with GMCP support, visible exits, mobile controls, hotkeys, screen reader behavior, momentum buttons and basic triggers.

If you later build a Mudlet HUD, copy how the browser client does it: it shows vitals, room data, party state, casting progress, cooldowns and momentums, and leaves every action to you.

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.

Every part of its screen, its settings, hotkeys, triggers and keyboard shortcuts are explained on the wiki's Web client page.

Mudlet

Many long-time Icesus players use Mudlet, a desktop client you can customise heavily. It suits long sessions: readable fonts, searchable logs, aliases, highlights, custom windows, mapper experiments, GMCP dashboards, and portable packages.

The official Icesus Mudlet package is one .mpackage install. It gives you the same panels the browser client uses (vitals, EXP, casting, cooldowns, status effects, an enemy bar, exits and a channel feed) and an automapper, without writing any triggers. Start there and build the rest of your profile (logging, aliases, highlights) on top of it.

Icesus Mudlet Package Drop-in HUD with vitals, EXP, casting, cooldowns, enemies, channels, and exits, plus an automapper. One install, no triggers to write. Mudlet Setup Install Mudlet, connect to Icesus, enable logging, choose sane fonts and colors, and keep the first profile clean. Icesus Mudlet Triggers Build safe trigger sets around Icesus rules, class roles, food and drink messages, crafting, party tools, and momentums. Icesus Mudlet GMCP Use structured Icesus data for vitals, rooms, party grids, casting, cooldowns, screen reader state, and manual momentum UI.

GMCP: Structured Data from Icesus

Icesus speaks the Generic MUD Communication Protocol (GMCP) alongside the plain text stream. Alongside the room and combat text, GMCP sends the same information as structured data: 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 built-in GMCP APIs. Older terminal clients can reach the same data through scripting, with more work.

Client	GMCP	What you get on Icesus
Browser client	Native	Side panels, vitals bars, exit list, party grid, manual momentum UI, all set up already.
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 drop-in status rows and saved hotkeys 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	Also telnet subnegotiation. Possible, but few Icesus players use GMCP from TF.
MUSHclient / CMUD / zMUD	Yes	Each has its own GMCP plugin pattern; copy the standard idiom from the client's documentation.
Plain telnet	No	GMCP is dropped and you see only the text. Use it to test a connection.

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 WindowsclassicLuaUTF-8 plugin Comfortable Windows setup if you already know the client. Icesus serves it the full 256-colour palette automatically; the UTF-8 plugin makes äöå work in both directions. Full setup guide. TinTin++ terminalsplit-screenscriptable Fast terminal client. Split-screen visual input, UTF-8, autoconnect, and a working ~/.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 GMCP status rows (exits, momentum, casting, cooldowns, enemies, HP/SP/EP, exp) and your saved hotkeys, then extend with your own Lua triggers, timers, and keybinds. CMUD and zMUD Windowslegacyprofiles Still supported: Icesus drops to 16-colour ANSI and transliterates UTF-8 to ASCII for these clients, so maps stay readable. Setup, terminal type, and when to move on.

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 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.

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.