Saved Today

• Automation folders, triggers, Lua triggers, aliases, Lua aliases, and scripts.
• Variables such as target.
• Hotkeys.
• Layout and terminal preferences such as panel size and font size.

These settings are saved per settings scope. BatMUD secure and regular telnet share the same BatMUD scope, while other MUDs can use their own scopes. Activity log entries are temporary browser data and are not saved with the profile.

Settings Scopes

A settings scope groups your saved client settings. Related server entries can share one scope, while unrelated MUDs can keep separate automation and preferences. Each profile keeps its own settings, even when several players use the same scope.

Deleting a custom MUD server does not delete its settings scope or your saved settings and revisions.

See MUD Servers for server selection and scope behavior.

Account Access

The account page handles login, registration, logout, and password changes. The desktop and mobile clients use your active login session.

You must log in with an approved profile to connect to a MUD or load, save, restore, import, or export your settings. There is no anonymous settings access. A new profile starts pending approval; contact the site operator if it remains pending.

Some sites require a CAPTCHA when creating a profile. If login or registration reports too many requests, wait before trying again; repeated attempts can extend the wait.

Logout And Password Changes

Logging out signs out the tabs using that browser login. Other devices with separate logins stay signed in. Your MUD sessions can remain connected and resume after you log back in. To leave a MUD and free a connection slot, use Disconnect before logging out.

Change your password from the account page using your current password. A successful change keeps that browser signed in and invalidates previous logins on other browsers and devices. Open client tabs disconnect from the browser session and can reconnect after authentication; your underlying MUD sessions are preserved.

If your account is disabled or its password is reset for you, your MUD sessions end. A site restart or the MUD itself can also end a connection.

An account can retain up to 20 active logins. When a new login replaces the oldest one, that browser must log in again. See Terminal for connection resume behavior.

Account Deletion

Account deletion ends your logins and MUD connections and removes your active settings, revision history, reports, and custom server entries. Export any settings you want to keep beforehand. Contact the site operator to request deletion.

An archived deletion keeps a copy of your profile details, settings, and revisions for later review, without your account password or login sessions. Full deletion also removes earlier application archives under the same profile name. Report screenshots are scheduled for removal in both modes; temporary storage errors can delay their removal.

Copies outside the application, such as backups or files you downloaded, are handled separately. Ask the site operator about any backup retention that applies.

User Groups And Quotas

Your user group determines your settings allowance. New profiles start in Starter, whose default active settings allowance is 1 MiB. Check the quota shown for your account, since the site's allowances may differ.

The top bar shows your profile name, user group, current settings size, and saved revision size using the group quota that is active right now. Revision storage has a separate limit equal to 10 times the current group quota.

If either quota is full, the quota badge turns bright red. You can still open settings and clean up, but creating new automation or editing trigger, alias, Lua trigger, Lua alias, or script content is locked until there is room again.

Your group also sets how many MUD connections your account can keep open at once. This is separate from settings storage: an unlimited settings allowance still has a connection limit. See MUD connection limits for what counts and how to free a slot.

Saving And Conflicts

Settings save automatically after edits. You can keep editing while a save finishes; newer edits are queued for the next save. On desktop, the top bar shows whether settings are saving, saved, unsaved, or have an error.

If another tab or device changes the same settings, your stale save is rejected and your local edits stay in the current tab. Desktop and mobile show a notice with Download my edits and Load saved settings. Download first if you want to keep your work: loading saved settings replaces your local edits for the selected MUD. You can then reapply selected changes to the saved version.

For a connection or quota error, resolve the problem and use Retry save. Switching MUDs within the same client keeps unsaved drafts in memory; return to the affected MUD to resolve its error. Save or download your edits before reloading, closing the tab, or logging out. A browser may warn before leaving with unsaved changes, but that warning is not guaranteed, especially on mobile.

Import And Export

Settings export produces a bundle of your settings across scopes. It excludes your email, password, login sessions, and other account details.

Export waits for pending settings saves. If a save fails, resolve the error before exporting; Download my edits in the error notice can still preserve the selected MUD's local draft.

Modern browsers export a compressed .json.gz file. If browser compression is unavailable, PlayMUD.online falls back to plain JSON.

Settings import sanitizes known PlayMUD.online fields, drops unknown fields, limits bundle size and scope count, and skips scopes that do not exist on this PlayMUD.online server.

A bundle's accepted scopes are saved together. If one exceeds your quota or changes in another tab during the import, the entire bundle is rejected and none of its scopes are saved. Bundles with duplicate scopes are rejected. Imports wait for pending saves and briefly pause settings edits while loading the result.

A plain settings file, including a file from Download my edits, replaces the currently selected MUD's settings. Importing it is a deliberate replacement of that scope. Review imported Lua before enabling triggers, aliases, or scripts.

Revisions

PlayMUD.online keeps the newest 10 settings revisions for each selected server scope. Autosaves made close together merge into the latest revision so small edits do not flood the history. Restoring a revision replaces the active settings and saves that restored copy as the newest checkpoint.

Restoring waits for pending saves. If the saved settings change elsewhere before restoration completes, the restore is rejected; load the saved settings and choose the revision again.