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
/guilds
258
0
Implemented
/guilds add
261
10
Implemented
/guilds create
259
0
Implemented
/guilds delete
260
10
Implemented
/guilds list
263
200
Implemented
/guilds remove
262
10
Implemented
Show administrative guild-management help.
Implementation: Implemented.
Syntax
/guilds
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: /guilds requires status 0 (handler 258). 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
guild
integer or text
Existing guild ID or quoted name.
1
player_name
text
Optional online name; otherwise your selected player.
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 (sep->IsNumber(0))
else if (client->GetPlayer()->GetTarget() && client->GetPlayer()->GetTarget()->IsPlayer())
Permissions
Local database snapshot, October 6, 2026: /guilds add requires status 10 (handler 261). 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
guild_name
text
Quote a multiword name when a player argument is supplied.
1
player_name
text
Optional online player for administrative direct creation.
Behavior and restrictions
Direct administrative create uses the named/selected player, or creates a guild without members if neither is provided. Player/prompted creation uses its confirmation flow.
Current argument/client/target checks (exact source excerpts; branch-dependent):
Local database snapshot, October 6, 2026: /guilds create requires status 0 (handler 259). 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
guild
integer or text
Existing guild ID or quoted name.
Behavior and restrictions
The active handler performs the operation described above after the registration permission check.
Persistence evidence in the active path: database.DeleteGuild. Each call is subject to its surrounding validation; not every branch saves.
Current argument/client/target checks (exact source excerpts; branch-dependent):
if (sep->IsNumber(0))
Permissions
Local database snapshot, October 6, 2026: /guilds delete requires status 10 (handler 260). 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.
The active handler performs the operation described above after the registration permission check.
Permissions
Local database snapshot, October 6, 2026: /guilds list requires status 200 (handler 263). 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
guild
integer or text
Existing guild ID or quoted name.
1
player_name
text
Optional name; otherwise selected player.
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 (sep->IsNumber(0))
else if (client->GetPlayer()->GetTarget() && client->GetPlayer()->GetTarget()->IsPlayer())
Permissions
Local database snapshot, October 6, 2026: /guilds remove requires status 10 (handler 262). 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.
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.