Skip to content

Player Reference

Kurt edited this page Jul 18, 2026 · 10 revisions

Player Reference

Audience: Player Status: ✅ Ready

Everything you need to connect and play TelosMUD: getting in through the browser sign-in, the everyday command set, communication channels, and — if you use a rich client like Mudlet — turning the game's GMCP data into gauges, a map, and tab-completion.

Connecting

Point a telnet or TLS client at the server's play port. On connect you're prompted to authenticate:

  1. The gate prints a clickable login URL. Open it in your browser and sign in with GitHub (this is standard OAuth — TelosMUD never sees your password). You can make this one-click with a trigger that opens the link automatically — Mudlet or TinTin++.
  2. Once you approve, the game picks up the completed sign-in automatically and drops you into character select / creation.
  3. First-time characters walk a short chargen flow (the exact steps are defined by the world's content pack — often a point-buy over a few attributes).

There is no password to remember and nothing to install on a server; your GitHub identity is your account. (Some development servers instead use a "just type a name" bypass — see Running Locally — but a real server uses the browser flow above.)

Recommended client settings: UTF-8 encoding, and TLS if the server offers an encrypted port. A GMCP-capable client (Mudlet, Mudlet-based, or any client that speaks telnet option 201) unlocks the rich-client features below.

Everyday commands

The core verbs, grouped. All support the Diku targeting grammar (sword, 2.sword, all.coin); abbreviations resolve to the highest-priority match (n → north).

  • Move: north/n, south/s, east/e, west/w, up/u, down/d. Some rooms also have named exits — enter, exit, or out — for a gate or portal; the room's Exits: line shows them.
  • Look around: look/l (bare shows the room; look <target> examines something).
  • Talk: say/' (to the room), tell <who> <msg> and reply (private), tells/replay (your recent private-message history this session), plus channels (below).
  • Items: get/take, drop, put, wear, wield, hold, remove, keep/unkeep (protect from dropping), split (a material stack), inventory/i, equipment/eq.
  • Character: score/sc (your sheet), who (who's online), rest/sit and stand, vitals on|off (show pools in the prompt), audit (your permanent-record trail — creation, deaths, grants).
  • Help: help for the index (topics + the command list), help <topic> for a specific subject.
  • Fight: kill/k, flee (the sanctioned way out mid-fight), assist/as, consider/con (size up a foe).
  • Mail: mail (list), mail read <n>, mail send <name> <subject> | <body>.
  • Utility: clear/cls (wipe the screen).

The full itemized list, including staff/builder verbs, lives on Builder Commands — a player uses the ungated subset above.

Communication channels

Channels are defined by the world's content pack (the demo ships gossip, newbie, and a guild channel). Type the channel's word followed by your message to talk on it, and channels to list them or toggle one on/off (channels off gossip). history <channel> replays that channel's recent scrollback (only if you can currently hear it; toggling it off doesn't lose access). Use ignore to mute a player and afk to mark yourself away. Some channels have access requirements (a minimum stat, or a guild membership flag), so not every channel is available to every character.

Rich clients (GMCP)

If your client speaks GMCP, the server streams structured game state alongside the text: your vitals and stats, the current room and its exits, your inventory, and channel messages. A rich client can turn that into HP/mana gauges, a live automap, inventory panels, and keyword tab-completion.

  • What's available: see the GMCP Reference for every package the server emits (Char.Vitals, Char.Stats, Char.Status, Char.Items.*, Room.Info, Room.Players, Comm.Channel.*).
  • Ready-made recipes: Mudlet Samples has copy-paste scripts for an HP bar, an automapper, and GMCP-driven tab-completion; TinTin++ Setup covers the same for tt++ (including its built-in mapper).

Clone this wiki locally