Mudlet Setup for Icesus: Install, Connect, Start Clean

Mudlet is a strong desktop MUD client for long Icesus sessions, but it is not the fastest way to see the game. If you are trying Icesus for the first time, open the browser client. It has solid GMCP support, screen reader support, hotkeys, maps/exits, momentum buttons, and basic trigger support without installing anything. Come to Mudlet when you want a local profile, deeper logging, Lua, mapper experiments, and client code you fully control.

Connection Settings

Setting	Value
Profile name	`Icesus`
Host	`icesus.org`
Standard port	`4000`
TLS port	`4443`
Encoding	`UTF-8`, if Mudlet asks or lets you choose
Website	https://icesus.org
Browser client	https://play.icesus.org

Install Mudlet

Download Mudlet from mudlet.org. Use the current stable build unless you are testing a specific bug fix.

Windows: install the 64-bit build. If Windows asks about firewall access, allow Mudlet to make outbound connections. Watch for OneDrive or other sync tools if you later move profile folders.
macOS: choose the Apple Silicon or Intel build that matches your Mac. Keep Mudlet in Applications and use the normal macOS security prompt on first launch.
Linux: use the official Linux build or a current distribution package. Test font rendering, clipboard behavior, and sound alerts before relying on them during play.

Create the Icesus Profile

Open Mudlet and create a new profile named Icesus.
Set the host to icesus.org.
Use port 4000 for a normal connection.
If you want TLS, configure the profile for a secure connection and use port 4443.
Connect and log in or create a character.

If TLS fails, test port 4000 before changing anything else. That separates secure-connection setup from account, network, or typo problems.

First Commands to Test

Before importing packages or writing scripts, confirm that ordinary Icesus commands work exactly as expected:

look to reread the room.
who to see who is online.
score to check your character.
inventory to see what you carry.
help living for practical Icesus basics such as combat assigns, food, drink, healing, and death.
help settings, help prompt, help triggers, help robots, and help combat points before serious customization.

Make the Profile Comfortable

Choose a readable monospace font, a comfortable size, and colors with enough contrast to survive long sessions. Icesus can send ANSI color; if your display looks strange, check your terminal setting in-game and Mudlet's profile preferences. In Icesus, term ansi and a suitable screen size are useful baseline settings for modern clients.

Enable logging early. Logs are where you recover syntax hints, room clues, party advice, and exact trigger text. Keep one raw log even if you later create cleaner side windows or notebooks.

Do not tune everything on the first night. Play first, collect real output, then build from what Icesus actually sends. A setup copied from another MUD is usually wrong in small ways that become annoying later.

What to Configure First

Command history: make sure up/down history and scrollback behave naturally.
Logging: know where logs are saved and how to search them.
Fonts and colors: prioritize room text, channels, tells, combat lines, and prompt readability.
Aliases: check alias -global in-game before recreating shortcuts Icesus already provides. Mudlet aliases are most useful for your character-specific combat point assigns, spell commands, skill commands, and reporting habits.
Backups: export the profile before importing packages or writing substantial Lua.

Useful First Mudlet Aliases

Good Icesus aliases are usually not i, n, or hh. The game already has global aliases for common habits, and alias -global shows them. Use Mudlet aliases for things that are specific to your build and annoying to type accurately during play.

Mudlet alias	Sends	Why it is useful
`ba`	`battle -a attack`	Quickly assigns combat points toward melee/offense, matching the Icesus combat help.
`bc`	`battle -a casting`	Quickly assigns combat points toward spellcasting, matching the magic help.
`bt`	`battle`	Checks current battle settings before you assume your assigns are correct.
`as <target>`	`cast arrow of steam at <target>`	A concrete spell-command pattern from Icesus help magic; replace it with your actual spell.
`ero <target>`	`cast erosion at <target>`	Another help-magic style example for a complete targeted spell.

For Mudlet regex aliases, ^as (.+)$ can run send("cast arrow of steam at " .. matches[2]). Keep the target explicit. If an alias can quietly hit the wrong target or send a private message to the wrong player, make it longer and safer.

Mudlet Concepts in One Pass

Aliases react to what you type. In Icesus, do not waste your first client work on movement aliases or one-letter commands that already exist as global aliases. Better Mudlet aliases are explicit action builders: ba sending battle -a attack for a melee setup, bc sending battle -a casting for a spellcasting setup, or as rat sending cast arrow of steam at rat if that is a spell you actually use. Triggers react to what the game prints. They are best for highlights, alerts, logging, and carefully limited active-play helpers. Scripts are Lua code shared by aliases, triggers, buttons, and GMCP event handlers. Packages bundle related client work so you can export or disable it cleanly.

Mapper support is useful after you know how Icesus presents rooms and exits, but it is not a first-login requirement. GMCP is structured client data. Icesus uses it heavily in the browser client, and Mudlet can use it too, but build that after your base profile is stable.

What to Leave for Later

Mudlet can do a lot: aliases, triggers, timers, scripts, packages, mapper work, GMCP events, custom UI, and sound packs. Do not wire all of that before you understand the game output. Start with a boring profile that connects reliably and logs well. Then add one layer at a time.

Icesus Mudlet Triggers Build safe trigger sets around Icesus rules, class roles, party play, crafting, and combat momentums. Icesus Mudlet GMCP Use Icesus GMCP data for vitals, rooms, party grids, casting, cooldowns, screen reader state, and manual momentum UI.

Mapper Notes

Mudlet's mapper is useful, but Icesus rooms, special exits, and dangerous areas deserve respect. Learn the mapper in safe areas. Compare your personal map with the public Icesus maps, but do not speedwalk blindly through unfamiliar or hostile terrain.

Accessibility Notes

The Icesus accessibility page should be your reference if you use a screen reader. The browser client is explicitly built for screen reader use and reacts to in-game screen reader mode. In Icesus, type screenreader on to optimize output for text-to-speech. Mudlet can be made comfortable too, but its exact accessibility behavior depends on your operating system, screen reader, fonts, colors, and sound choices.

Safe Automation Baseline

Icesus has strict trigger and robot rules. Read help triggers and help robots. As a baseline: make the client help you read, remember, and type while you are actively playing. Do not make the client play while you are absent, and do not create triggers that run visible commands outside the allowed cases.

Common First Problems

Cannot connect: check that the host is icesus.org, not a web URL, and that the port is 4000 or TLS 4443.
TLS fails: confirm the Mudlet profile is configured for a secure connection, then test the standard port to isolate the problem.
Colors look wrong: test term ansi, review Mudlet's ANSI/color settings, and avoid adding highlight triggers until the base display is readable.
Output wraps badly: set a sensible Mudlet window size and in-game terminal size. The browser client sets a wide terminal automatically; desktop clients may need tuning.
Logs are missing: confirm logging is enabled and that your operating system allows Mudlet to write to the selected folder.
Imported package behaves strangely: disable it, return to the clean profile, and re-enable pieces one at a time.

Next Steps

Once the profile connects, logs, and displays comfortably, improve it from real play. Add a few aliases. Add highlights for important text. Inspect GMCP. Export a backup. Then decide whether Mudlet, the browser client, or both fit how you actually play Icesus.

Related Guides

Want the fastest working client before you customize anything?

Open the browser client