Manage guild membership, permissions, recruiting and events.
Implemented · 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
/guild
252
0
Implemented
Manage guild membership, permissions, recruiting and events.
Implementation: Implemented.
Syntax
/guild <action> [arguments]
Arguments
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
See action syntax below.
1
arguments
action dependent
Values depend on the chosen guild action.
Behavior and restrictions
Guild operations require the relevant membership and guild permissions. Client UI callbacks also use this root.
Current argument/client/target checks (exact source excerpts; branch-dependent):
Local database snapshot, October 6, 2026: /guild requires status 0 (handler 252). 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
Literal rank_name action; retained in the root handler.
1
rank_id
action dependent
First syntax form: <rank_id>. Square brackets mean optional.
2
name
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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
Literal rank_permission action; retained in the root handler.
1
rank_id
action dependent
First syntax form: <rank_id>. Square brackets mean optional.
2
permission_id
action dependent
First syntax form: <permission_id>. Square brackets mean optional.
3
true|false
action dependent
First syntax form: <true|false>. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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
Literal filter_event action; retained in the root handler.
1
event_id
action dependent
First syntax form: <event_id>. Square brackets mean optional.
2
filter_id
action dependent
First syntax form: <filter_id>. Square brackets mean optional.
3
true|false
action dependent
First syntax form: <true|false>. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild kick
Remove a guild member.
Implementation: Implemented.
Syntax
/guild kick <name>
Arguments
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
Literal kick action; retained in the root handler.
1
name
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild demote
Demote a member.
Implementation: Implemented.
Syntax
/guild demote <name>
Arguments
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
Literal demote action; retained in the root handler.
1
name
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild promote
Promote a member.
Implementation: Implemented.
Syntax
/guild promote <name>
Arguments
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
Literal promote action; retained in the root handler.
1
name
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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
Literal points action; retained in the root handler.
1
add
literal
First syntax form: add. Square brackets mean optional.
2
points
action dependent
First syntax form: . Square brackets mean optional.
3
all|online|group|raid|name
action dependent
First syntax form: <all|online|group|raid|name>. Square brackets mean optional.
4
comment
action dependent
First syntax form: [comment]. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild motd
Set guild message of the day.
Implementation: Implemented.
Syntax
/guild motd <message>
Arguments
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
Literal motd action; retained in the root handler.
1
message
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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
Literal recruiting action; retained in the root handler.
First syntax form: <short_text|long_text|flag|min_level|playstyle|tag|true|false>. Square brackets mean optional.
2
values
action dependent
First syntax form: [values]. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild notify_online
Set login notifications.
Implementation: Implemented.
Syntax
/guild notify_online <true|false>
Arguments
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
Literal notify_online action; retained in the root handler.
1
true|false
action dependent
First syntax form: <true|false>. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild event_privacy
Set event privacy.
Implementation: Implemented.
Syntax
/guild event_privacy <true|false>
Arguments
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
Literal event_privacy action; retained in the root handler.
1
true|false
action dependent
First syntax form: <true|false>. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild recruiter
Set a member as recruiter.
Implementation: Implemented.
Syntax
/guild recruiter <name> <true|false>
Arguments
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
Literal recruiter action; retained in the root handler.
1
name
action dependent
First syntax form: . Square brackets mean optional.
2
true|false
action dependent
First syntax form: <true|false>. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild recruiter_description
Set recruiter description.
Implementation: Implemented.
Syntax
/guild recruiter_description <text>
Arguments
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
Literal recruiter_description action; retained in the root handler.
1
text
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild lock_event
Set an event lock flag.
Implementation: Implemented.
Syntax
/guild lock_event <event_id> <true|false>
Arguments
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
Literal lock_event action; retained in the root handler.
1
event_id
action dependent
First syntax form: <event_id>. Square brackets mean optional.
2
true|false
action dependent
First syntax form: <true|false>. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild delete_event
Delete a guild event.
Implementation: Implemented.
Syntax
/guild delete_event <event_id>
Arguments
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
Literal delete_event action; retained in the root handler.
1
event_id
action dependent
First syntax form: <event_id>. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild invite
Invite a named or selected player.
Implementation: Implemented.
Syntax
/guild invite [name]
Arguments
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
Literal invite action; retained in the root handler.
1
name
action dependent
First syntax form: [name]. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild accept
Accept a pending guild invitation.
Implementation: Implemented.
Syntax
/guild accept
Arguments
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
Literal accept action; retained in the root handler.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild decline
Decline a pending guild invitation.
Implementation: Implemented.
Syntax
/guild decline
Arguments
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
Literal decline action; retained in the root handler.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild create
Request creation of a guild for the caller/group.
Implementation: Implemented.
Syntax
/guild create <guild_name>
Arguments
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
Literal create action; retained in the root handler.
1
guild_name
action dependent
First syntax form: <guild_name>. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild search
Open guild recruiting search.
Implementation: Implemented.
Syntax
/guild search
Arguments
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
Literal search action; retained in the root handler.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild recruiting_details
Request guild recruiting details.
Implementation: Implemented.
Syntax
/guild recruiting_details <guild_id>
Arguments
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
Literal recruiting_details action; retained in the root handler.
1
guild_id
action dependent
First syntax form: <guild_id>. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild recruiting_image
Request guild recruiting images.
Implementation: Implemented.
Syntax
/guild recruiting_image <guild_id>
Arguments
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
Literal recruiting_image action; retained in the root handler.
1
guild_id
action dependent
First syntax form: <guild_id>. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild recruiter_adventure_class
Toggle the recruiter adventure-class flag.
Implementation: Implemented.
Syntax
/guild recruiter_adventure_class toggle
Arguments
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
Literal recruiter_adventure_class action; retained in the root handler.
1
toggle
literal
First syntax form: toggle. Square brackets mean optional.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/guild display_heraldry
Toggle guild heraldry display.
Implementation: Implemented.
Syntax
/guild display_heraldry
Arguments
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
Literal display_heraldry action; retained in the root handler.
Behavior and restrictions
The action remains in the root handler; argument 0 is the action token.
Permissions
Internal action: inherits the /guild registration requirement of status 0. No separate database subcommand row exists for this action.
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.