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 |
|---|---|---|---|
/raidsay |
547 | 0 | Implemented |
Send raid chat.
Implementation: Implemented.
Syntax
/raidsay <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 | All remaining text is sent as the message. |
Behavior and restrictions
- Requires membership and the normal permissions for the selected channel.
Permissions
Local database snapshot, October 6, 2026: /raidsay requires status 0 (handler 547). 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_RAIDSAY (handler 547).
WorldServer/Commands/Commands.cpp:6441—COMMAND_RAIDSAY.WorldServer/Commands/Commands.cpp:14174—Command_RaidSay.
Reviewed local revision: 9efddf962ffee075d0db2059d3914c36b0acbdf3; working-tree file checksums identify the exact reviewed bytes. Reviewed dispatch/helper evidence · Reconciliation report.
No upstream Markdown file exists for this registration in the retrieved revision.