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 |
|---|---|---|---|
/pet |
137 | 0 | Implemented |
Control your pet.
Implementation: Implemented.
Syntax
/pet <hide|stay|stayhere|follow|followme|preserve_master|guardme|preserve_self|guardhere|backoff|attack|getlost>
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 | Pet control action. |
Behavior and restrictions
- Pet attack uses your current target; guard/follow actions use your owned pet state.
Current argument/client/target checks (exact source excerpts; branch-dependent):
if (client->GetPlayer()->HasTarget() && client->GetPlayer()->GetTarget()->IsEntity()) {
Permissions
Local database snapshot, October 6, 2026: /pet requires status 0 (handler 137). 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_PET (handler 137).
WorldServer/Commands/Commands.cpp:6293—COMMAND_PET.WorldServer/Commands/Commands.cpp:9222—Command_Pet.
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.