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.

Settings Scopes

A settings scope is a shared bucket for client settings. It lets related server entries share one setup while unrelated MUDs keep their own automation and preferences.

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.
• Profile auth details, email, password, admin status, and sessions are not scoped settings.

Admin Management

Admins manage servers from the admin area in the MUD Servers section.

• Name is the label users see in the dropdown.
• Host and Port define the telnet target.
• TLS enables secure telnet for that target.
• Enabled controls whether users can choose the server.
• Settings scope chooses whether the server shares an existing settings bucket or creates a new one.

Choose an existing scope when two server entries should share settings. Choose New scope when a server needs its own settings; PlayMUD.online creates a scope using the server name.

Deleting Servers

Deleting a MUD server removes only that server entry. It does not delete the settings scope, settings, or revisions.

This is intentional. A server entry might be deleted by mistake, recreated with a different host or port, or temporarily replaced. Keeping the scope prevents accidental loss of triggers, aliases, variables, and Lua scripts.

If no server uses a scope anymore, it is marked unused in the Settings Scopes section. You can either keep it for later reuse or click Delete unused. Scope deletion requires typing the scope name and shows how many settings and revisions will be removed.

PlayMUD.online refuses to delete a scope while any MUD server still points at it. Reassign or delete those server entries first.

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.