P

PlayMUD.online

Profiles

Persistence

Settings belong on the server, not only in the browser.

PlayMUD.online saves your client settings with your login profile. Your automation and preferences can follow you between browsers and devices.

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 is a bucket of saved client settings. Related server entries can share one scope, while unrelated MUDs can keep separate automation and preferences.

Deleting a MUD server does not delete its settings scope or profile settings. This prevents a server cleanup from accidentally wiping triggers, aliases, variables, hotkeys, or scripts. An unused scope can be deleted separately by an administrator.

See MUD Servers for server selection and scope behavior.

Profile Auth

The account page handles login, registration, logout, and user password changes. The desktop and mobile clients use your active login session and do not show profile password fields inside the MUD client.

There is no anonymous profile. Settings remain unloaded until a user logs in, and every profile name represents a normal authenticated account.

New profiles may need administrator approval before they can connect. Administrators can approve, disable, promote, reset passwords, search users, view archive history, or delete users from the admin area.

Archive delete keeps a server-side copy for later review before removing the live profile. Full delete removes the live profile without creating that archive copy.

Users can change their own passwords from the account page with their current password. Admin password resets never send email.

Connecting to a MUD requires an approved profile login. Some PlayMUD.online sites may also protect registration with an anti-abuse check.

User Groups And Quotas

Every normal user belongs to a user group. Fresh PlayMUD.online installs create a Starter group with a 1 MiB active settings quota, and new non-admin users start there. Administrators are unlimited, even when they belong to a normal group.

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.

Administrators can create, rename, delete, resize, and mark user groups as unlimited from the admin area. A group named Admin is still a normal group unless its unlimited quota option is enabled. The admin dashboard also shows the top 10 users by stored settings and revision data inside each group.

Import And Export

Settings export produces a bundle for all settings scopes owned by the logged-in profile. It excludes email, password, sessions, admin status, and other auth details.

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.

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.