The complete command table

48 user-facing slash commands — 16 public, 2 group-admin, 30 owner-or-staff — plus the bare-uppercase STOP and UNDO keywords and an unbounded set of per-bot dynamic commands. 5 further slash spellings are Memescale platform-admin or fleet-operator tooling and are excluded entirely.

How this table works

Every built-in command is matched by one regular expression, ^/?(?:name)(@\w+)?(\s|$), case-insensitive (cmd_re, scripts/telegram/utils/commands.py:25-26). The leading slash is optional, an @<botusername> suffix is accepted, and case never matters, unless a row below says the slash is required — a minority of built-ins are matched by a hand-written pattern instead of cmd_re, and a few of those also refuse the @bot suffix.

cmd_re(name) — the default pattern

^/?(?:name)(@\w+)?(\s|$)

The five columns

Menu-scope legend

A chat that isn’t authorized for the bot at all gets an empty command menu pushed deliberately, regardless of any row below — see Groups and access, chapter 1.2.

Platform-admin commands are not documented here

5 further slash spellings are Memescale platform-admin or fleet-operator tooling, restricted to platform staff or two hardcoded usernames in one hardcoded chat: /newbot, /topicid, /updatepfp, /id, /fleet. They are intentionally excluded from the table below.

• Groups and access

Public commands

16 spellings, subject to whatever authorization or toggle each row states — “public” describes who the code lets try, not that every attempt succeeds.

16 public spellings, 14 rows (2 rows carry an alias)

Group-admin commands

Both exist only once Admin Moderation is switched on in the dashboard — off by default. The route itself is always registered; with the toggle off, moderate() returns before doing anything, and the route has already consumed the message — so a disabled /ban or /mute is silent, not an error.

• Moderation

Owner-or-staff commands

30 spellings, 24 rows. Every command below shares one gate: the bot’s Memescale owner or a Memescale platform-admin username — never a Telegram group’s own admin standing, in any group. A non-owner sending one of the buy-bot commands gets no reply at all; tapping a buy-bot button as a non-owner gets the alert Owner / admins only.

General

8 rows, 10 spellings

Buy bot

16 rows, 20 spellings — one gate, buybotctl.py’s is_owner(...), no chat-type restriction on any of them

• Commands and the settings card
• Reference images
• Queue and GPU status

STOP, UNDO, and dynamic commands

STOP and UNDO

Both are matched as the exact message text, case-insensitively, with nothing else in it — stop, Stop and STOP all match; STOP please does not.

Dynamic commands

Every bot also carries commands with no fixed spelling, sourced from that bot’s own memebot.json and matched with the same slash-optional shape as the built-ins:

Per-bot dynamic commands

Text and button commands share one trigger namespace with each other and with character triggers — a trigger can’t be reused across the three. Every fixed built-in above is matched first, at the router; a custom command of the same name never gets a turn. None of the three are gated by the group allowlist on their own — see below.

• The trigger namespace

Two cross-cutting facts

The group allowlist (allowedGroups) is not one gate for the whole bot — each feature that cares checks it independently, at its own call site, and several (/holders, /presets, /cancelpresets, text and button commands, the scanner, the calls commands) never check it at all. The buy bot keeps an entirely separate posting-target pool, bots[].buyBot.targetGroupIds, capped at 10 — distinct from the allowlist, which has no cap anywhere.

• What the allowlist gates
• The buy bot’s separate pool