Implemented (subcommands have their own status) · Source comparison: October 6, 2026.
Reviewed October 6, 2026. This page covers the root, registered subcommands and documented internal actions.
Registration permissions
Registration
Handler
Required status (local DB, Oct 6)
Implementation
/player
307
10
Implemented
/player coins
308
10
Implemented
Show player coin-management help.
Implementation: Implemented.
Syntax
/player
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
The active handler performs the operation described above after the registration permission check.
Permissions
Local database snapshot, October 6, 2026: /player requires status 10 (handler 307). Other worlds may configure different values.
The dispatcher checks the resolved registration status before invoking the handler. In-handler guild, group, ownership, client-version and target checks still apply.
Examples
The syntax forms above are the source-based invocation examples. Replace identifiers with values valid for your world; client callback fields are supplied by the game client.
Position is zero-based in sep, after a registered database subcommand has been removed. Internal action tokens remain at position 0. Angle brackets are required; square brackets are optional. Alternative forms may change field meanings.
Position
Argument
Accepted value / type
Meaning
0
action
text
add
1
denomination_or_amount
text or integer
Without a denomination, value is copper.
2
amount
integer
Required after an explicit denomination.
Behavior and restrictions
The active handler performs the operation described above after the registration permission check.
Current argument/client/target checks (exact source excerpts; branch-dependent):
if (player->HasTarget() && player->GetTarget()->IsPlayer()) {
if (sep->IsNumber(1)) {
else if (sep->arg[2] && sep->IsNumber(2)) {
Permissions
Local database snapshot, October 6, 2026: /player coins requires status 10 (handler 308). Other worlds may configure different values.
The dispatcher checks the resolved registration status before invoking the handler. In-handler guild, group, ownership, client-version and target checks still apply.
Examples
The syntax forms above are the source-based invocation examples. Replace identifiers with values valid for your world; client callback fields are supplied by the game client.
No upstream Markdown file exists for this registration in the retrieved revision.
Permissions are from a read-only snapshot of the configured local world database on October 6, 2026; deployed worlds may differ. Argument and behavior evidence comes from the reviewed WorldServer checkout. Examples were checked against source and were not executed in a live world.