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 |
|---|---|---|---|
/achievement_add |
310 | 0 | Implemented |
Add or rank up an AA ability and apply its spell effect.
Implementation: Implemented.
Syntax
/achievement_add <client_value> <spell_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 | client_value |
text | Client token checked for presence; not otherwise used. |
| 1 | spell_id |
integer | Must identify an existing AA entry below its maximum rank. |
Behavior and restrictions
- The handler checks arg[0] but reads the spell ID from arg[1]. It adds or upgrades the spellbook entry, then processes the spell on self.
- An AA display update is sent on client versions 843 and later.
Current argument/client/target checks (exact source excerpts; branch-dependent):
if (sep && sep->IsSet(0)) {
if(client->GetVersion() >= 843)
Permissions
Local database snapshot, October 6, 2026: /achievement_add requires status 0 (handler 310). 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_ACHIEVEMENT_ADD (handler 310).
WorldServer/Commands/Commands.cpp:6357—COMMAND_ACHIEVEMENT_ADD.WorldServer/Commands/Commands.cpp:13115—Command_AchievementAdd.
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.