Wiki
/wiki — namespaced, categorised pages with full edit history and diffs. Staff control who may
edit what.
Every SharpMUSH server serves a web portal from the same origin as the game. It is not an optional add-on or a separate deployment: the Blazor portal is baked into the server image, so if the game is running, the website is running.
This is where most administration happens. There is no mush.cnf to edit and no @config incantation
to remember for the common cases — you change a setting in a form and it takes effect.
A fresh install has no accounts. The first visitor to /setup claims the admin account and
creates the God character, then the route closes.
SharpMUSH separates the account you log in with from the characters you play. One account can own several characters.
| Page | What it is for |
|---|---|
/register, /login | Account signup and login |
/characters | The characters this account owns |
/characters/new | Character creation |
/character/{name} | A public character profile |
/account, /settings | Account details, per-character settings, theme |
Because the login is an account rather than a character, switching characters does not mean disconnecting and reconnecting, and a lost password is an email recovery rather than a staff ticket. Guest access upgrades into a real character without losing the session.
/play is a full terminal in the page — telnet-equivalent access with no MU* client installed.
It connects over a WebSocket served by the connection server, and out-of-band data from the game
drives the live side panes.
The terminal’s Server URI must point at the connection server’s /ws endpoint. On a deployment
behind the supplied proxy config that is wss://<your-domain>/ws; see
Run with Docker for why
this is its own hostname and path.
Wiki
/wiki — namespaced, categorised pages with full edit history and diffs. Staff control who may
edit what.
/mail — read and compose in-game @mail from the web.
Scenes
/scenes — browse logged scenes, and watch running ones at /scenes/active as poses land.
Help
/help — the server’s own helpfiles, searchable, with working cross-links.
Games can also publish Dynamic Applications at /apps/{slug} — forms such as chargen or job
requests, defined by admins as a softcode schema rather than written as web code.
/admin is the staff dashboard. What a given staffer sees is governed by roles, not by a single
wizard bit.
/admin/config — the server’s configuration, grouped into categories and rendered as typed
form fields, including array and dictionary values as editable lists./admin/config/restrictions — command and function restrictions./admin/config/sitelock — sitelock rules./admin/config/bannednames — disallowed character names./admin/config/import and /admin/database/import — bring a PennMUSH configuration and
database across. See Compatibility./admin/players — the player list, with a detail view per player./admin/accounts and /admin/characters — the account and character sides of the same
people./admin/moderation — the moderation queue./admin/roles — define what staff roles may do./admin/suggestions — player suggestions./admin/wiki and /admin/wiki/assets — wiki administration and uploaded assets./admin/media — the image library./admin/profiles — character profile templates and fields./admin/layout — the portal’s own layout: which widgets appear on which pages, edited per
scope in a layout editor./admin/packages — installed softcode packages, plus browse, remotes, review and
author views. See Softcode Packages./admin/applications — the Dynamic Applications published at /apps/{slug}./admin/server — server status and control./softcode is a Monaco-based editor for attribute code, with multi-tab editing, syntax
highlighting, hover help drawn from the helpfiles, and signature help for functions. It shares its
analysis engine with the language server, so the diagnostics it
shows are the real parser’s, not an approximation.