User Flow

1. Log in with an approved PlayMUD.online profile.
2. Choose a server from the top bar server dropdown.
3. Choose charset if needed.
4. Connect.

Changing the server while connected switches the browser to the selected server session and leaves other active server sessions online. PlayMUD.online reloads settings for the selected server scope.

Active Sessions

The session chips beside Connect show visible and background sessions. Background sessions stay connected to their MUDs, keep receiving output, and show a new marker when unread text arrives.

Only the visible server owns browser automation. Output streamed from inactive sessions is buffered for that server and does not fire triggers, Lua triggers, Lua scripts, or Lua aliases until you switch to that server and receive live selected-session output.

Connection Limits

Your user group sets how many MUD connections your account can keep open at once. The allowance belongs to each account; other members of your group do not use your slots.

Active sessions, background sessions, and connection attempts still in progress all count. Closing a tab or logging out can leave its MUD sessions running, so those sessions still count. Returning to an existing session does not use another MUD connection slot.

To free a slot, use Disconnect on a session you no longer need. If your allowance is reduced, existing sessions stay open, but you must get below the new limit before opening another connection.

There is also a separate limit of eight connected client tabs or windows per account across devices. Close an extra client tab if you reach the browser connection limit. See Terminal for reconnect behavior.

Settings Scopes

A settings scope lets related server entries share your setup while unrelated MUDs keep separate automation and preferences. Other players retain their own settings even when they use the same scope name.

This keeps settings separated for different MUDs while still letting related server entries share one configuration.

• BatMUD Secure and BatMUD Regular both use the BatMUD scope.
• Triggers, Lua triggers, aliases, Lua aliases, variables, hotkeys, layout, and revisions are scoped.
• Your account details, password, and login sessions are separate from scoped settings.

Custom Servers

In the desktop client, choose Custom server... from the server dropdown to add a MUD to your account or edit one of your saved custom entries.

• Name is the label in your dropdown.
• Host and Port are the connection details provided by the MUD.
• TLS enables secure telnet when the MUD supports it on that port.
• Scope chooses which of your settings to use. Leave it empty to use a scope based on the host and port, or enter an existing scope name to reuse your setup.

Use Save to keep the entry or Save & Connect to connect immediately. Saved custom servers belong to your profile.

You can keep up to 20 custom servers. Your account can create up to 40 new settings scopes over its lifetime; reusing an existing scope does not consume that allowance. Deleting a server frees a server slot but does not reset the scope-creation allowance.

Supported Addresses

You can add public Internet MUDs without waiting for them to be added to a site list. Use the MUD's published hostname and port. A change to its public IP address does not require you to edit the saved hostname.

Custom servers cannot connect to private or local network addresses, including localhost, or protected infrastructure addresses. A hostname can be saved but still be blocked when connecting if it resolves to a protected address. The same checks apply to regular telnet and TLS.

If you need a private MUD, contact the site operator about a supported server entry. Changing the spelling of its address or reconnecting will not grant access.

Connection Problems

• MUD session limit reached: disconnect an existing MUD session before opening another. If you are below your allowance and it still fails, the site may be at capacity; try again later.
• Browser connection limit reached: close an extra client tab or window, including one on another device, then retry.
• Destination blocked by network policy: check the MUD's published address. Contact the site operator if the correct address is blocked.
• Connection timed out: connection setup has a 15-second timeout. Check the host, port, and whether the MUD is available before retrying.
• TLS certificate error: check the published secure hostname and port. Ask the MUD operator to check its certificate if those details are correct.
• Login required or profile not approved: check your account status on the account page. Contact the site operator if approval is needed.

Deleting Servers

To remove one of your custom servers, open Custom server..., choose Edit beside the entry, and use Delete.

Deleting a custom server removes its entry without deleting your settings or revisions. Reuse the same scope when adding a replacement to access your saved setup.

Import And Export

Profile export includes all settings scopes for the logged-in profile. Modern browsers download a compressed .json.gz bundle; plain JSON is used when compression is not available.

Imports are sanitized and unknown fields are dropped. Auth details are never included.

See Profiles for the broader persistence model.