Clients

TL;DR: You can play DreamLand in a browser at https://dreamland.rocks/play, in Mudlet with an auto-installed package, or in any telnet client on dreamland.rocks port 9000. All three get the same game and the same three languages. The browser and Mudlet clients add panels and clickable output, the plain telnet route stays fully playable. Use when: you choose or configure a client, debug garbled letters or doubled characters, or look for the page that documents a client's internals. Source of truth: help articles 2132 (help screenreader) and 2133 (help clients) in dreamland_world/helps/help.xml, dreamland_world/config/settings.json, plug-ins/iomanager/codepage.cpp Verified: 2026-11-02 against dreamland_world 43880467, dreamland_code 88da8302, mudjs 990bf6d, dreamland_mudlet b18afc2

The three routes

Client	Where	What you get
Web client	https://dreamland.rocks/play	Clickable output and item menus, side panels, graph map, chat frames, settings with aliases, macros and triggers, sounds, a script editor. Works on phones. Details in Client-Web-Development and Client-Web-Protocol.
Mudlet	host dreamland.rocks, port 9000	The same panels as the web client, drawn from GMCP, and a map. The game offers the package on first connect. Details in Client-Mudlet-and-GMCP.
Any telnet client	host dreamland.rocks, port 9000	Plain text. TinTin++, zMUD and others are used. Character creation works over telnet.

The public address is dreamland.rocks. Port 9000 is telnet. The web client reaches the server through the site, you do not need another port. Running your own server is covered in Local-Setup.

Languages

At login the game asks for the interface language (English, Ukrainian or Russian) and the player can change it later with config lang. Everything the server prints comes already in that language, so every client shows the same text. English, Ukrainian and Russian players share one world.

Telnet clients: encoding and settings

A telnet client first sees a codepage menu. The choices, in order (plug-ins/iomanager/codepage.cpp): 1 koi8-r, 2 alt (cp866), 3 win (cp1251), 4 iso (ISO-8859-5), 5 mac, 6 transliteration, 7 utf-8. Pick the one your client is set to. Mudlet gets its codepage picked for it.

If letters look wrong, the game's config command has three flags. They are described in help clients:

Symptom	Setting
A Russian capital Я appears where a lowercase я belongs (cp1251)	config noiac off.
One я shows as two	config notelnet off. If you use a client with MCCP compression or other telnet features, turn it on instead.
zMUD	Turn both noiac and notelnet off.
Mudlet	config telnetga on, config noiac off, config notelnet on. The package handles the rest.
The client needs a go-ahead after each status line (Mudlet does)	config telnetga on. It sends a telnet go-ahead sequence after the status line.

The server negotiates MCCP compression, MSSP (server status), EOR and GMCP. Sounds come as MSP lines. Enable MSP in the client if you want them.

Screen readers

Many players are blind, see Accessibility. Every route works with a screen reader.

• Turn on the mode in the game: config screenreader yes. It drops the English names in parentheses after items and mobs, speaks auras instead of colours, replaces ASCII drawings with words, and reports the experience left to the next level after each gain (help screenreader).
• Also consider config color off, the article recommends turning colours off.
• The web client output area is a polite live region and its panels repeat what is in the text. The engine sends a blind player on the web client the same {Iw spans and web tags as any other web reader.
• Mudlet's side panel never holds a fact that is not also in the main window.
• The telnet line editor is the accessible way to write long text. The web client has its own editor, opened by webedit.

The rules for authors are in Accessibility.

Tools that are not clients

The site https://dreamland.rocks has the help search, zone maps, the item searcher and news. They use the same data as the in-game commands.

See also

• Client-Web-Development
• Client-Web-Protocol
• Client-Mudlet-and-GMCP
• Player-FAQ
• Accessibility