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 |
|---|---|---|---|
/flymode |
57 | 200 | Implemented |
Set flying or no-clip movement.
Implementation: Implemented.
Syntax
/flymode <0|1|2>
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 | mode |
integer | 0 disables, 1 enables flight, 2 enables no-clip flight. |
Behavior and restrictions
- Available movement differs by client; older clients do not provide the same vertical flying controls.
Current argument/client/target checks (exact source excerpts; branch-dependent):
if(sep && sep->arg[0] && sep->IsNumber(0)){
Permissions
Local database snapshot, October 6, 2026: /flymode requires status 200 (handler 57). 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_FLYMODE (handler 57).
WorldServer/Commands/Commands.cpp:3368—COMMAND_FLYMODE.
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.