Slash commands

/guildsay

Send a message to guild members.

Implemented · Source comparison: October 6, 2026.

Aliases: /gu

Reviewed October 6, 2026. This page covers the root, registered subcommands and documented internal actions.

Confirmed aliases: /gu. Alias URLs redirect here; each registration retains its own permission.

Registration permissions

Registration Handler Required status (local DB, Oct 6) Implementation
/gu 250 0 Implemented
/guildsay 250 0 Implemented

Send a message to guild members.

Implementation: Implemented.

Syntax

/guildsay <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 message remaining text Guild message body.

Behavior and restrictions

  • Requires guild membership and guild-chat permission. /gu shares this handler.

Permissions

Local database snapshot, October 6, 2026: /guildsay requires status 0 (handler 250). 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.

Source evidence

Dispatch: COMMAND_GUILDSAY (handler 250).

  • WorldServer/Commands/Commands.cpp:6227 — COMMAND_GUILDSAY.
  • WorldServer/Commands/Commands.cpp:7236 — Command_GuildSay.

Reviewed local revision: 9efddf962ffee075d0db2059d3914c36b0acbdf3; working-tree file checksums identify the exact reviewed bytes. Reviewed dispatch/helper evidence · Reconciliation report.

Original upstream Markdown · Archived original. The original text is historical evidence; the corrected contract above takes precedence.

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.