Implemented (subcommands have their own status) · Source comparison: October 6, 2026.
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
/reload
65
100
Implemented
/reload entity_commands
240
100
Implemented
/reload factions
243
100
Implemented
/reload groundspawn_items
98
100
Implemented
/reload guilds
255
100
Implemented
/reload items
36
100
Implemented
/reload locations
267
100
Implemented
/reload luasystem
63
100
Implemented
/reload mail
248
100
Implemented
/reload playerscripts
801
100
Implemented
/reload quests
79
100
Implemented
/reload recipes
1011
100
Implemented
/reload regionscripts
524
100
Implemented
/reload rules
519
100
Implemented
/reload spawns
99
100
Implemented
/reload spawnscripts
62
100
Implemented
/reload spells
59
100
Implemented
/reload startabilities
522
100
Implemented
/reload structs
64
100
Implemented
/reload transporters
520
100
Implemented
/reload voiceovers
532
100
Implemented
/reload zoneinfo
1010
100
Implemented
/reload zones
193
100
Unsupported — no active handler
/reload zonescripts
104
100
Implemented
Show available subsystem reload commands.
Implementation: Implemented.
Syntax
/reload
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
The active handler performs the operation described above after the registration permission check.
Permissions
Local database snapshot, October 6, 2026: /reload requires status 100 (handler 65). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload entity_commands
Reload entity-command definitions.
Implementation: Implemented.
Syntax
/reload entity_commands
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload entity_commands requires status 100 (handler 240). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload factions
Reload faction definitions.
Implementation: Implemented.
Syntax
/reload factions
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload factions requires status 100 (handler 243). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload groundspawn_items
Reload groundspawn item data.
Implementation: Implemented.
Syntax
/reload groundspawn_items
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload groundspawn_items requires status 100 (handler 98). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload guilds
Reload guild definitions.
Implementation: Implemented.
Syntax
/reload guilds
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload guilds requires status 100 (handler 255). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload items
Reload all master items or a selected master item.
Implementation: Implemented.
Syntax
/reload items [item_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
item_id
integer
Optional master item ID; omission reloads the full list.
Behavior and restrictions
Revalidates spell-scroll availability when spell activation changes.
Permissions
Local database snapshot, October 6, 2026: /reload items requires status 100 (handler 36). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload locations
Reload location data.
Implementation: Implemented.
Syntax
/reload locations
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload locations requires status 100 (handler 267). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload luasystem
Reload the Lua subsystem.
Implementation: Implemented.
Syntax
/reload luasystem
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload luasystem requires status 100 (handler 63). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload mail
Reload mail data.
Implementation: Implemented.
Syntax
/reload mail
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload mail requires status 100 (handler 248). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload playerscripts
Reload player scripts.
Implementation: Implemented.
Syntax
/reload playerscripts
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload playerscripts requires status 100 (handler 801). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload quests
Reload quest definitions.
Implementation: Implemented.
Syntax
/reload quests
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload quests requires status 100 (handler 79). 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.
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
scope
text
Optional items keyword.
Behavior and restrictions
The active handler performs the operation described above after the registration permission check.
Permissions
Local database snapshot, October 6, 2026: /reload recipes requires status 100 (handler 1011). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload regionscripts
Reload region scripts.
Implementation: Implemented.
Syntax
/reload regionscripts
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload regionscripts requires status 100 (handler 524). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload rules
Reload rulesets and rule overrides.
Implementation: Implemented.
Syntax
/reload rules
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload rules requires status 100 (handler 519). 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.
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
options
option sequence
Parsed by BuildReloadSpawnOptions; optional filters can be combined.
Behavior and restrictions
Bare reload uses the existing full-zone reload. clear_timers clears relevant respawn timers.
Accepted type aliases include plural forms and ground/groundspawn/gspawn variants. Radius also accepts range/distance; grid accepts gridid.
ID selectors include spawn/dbid/database_id/id, location, placement, entry, group/spawngroup/spawn_group, with their _id forms. Invalid or missing filter values return a syntax/error message.
Default type is all. Radius must be greater than zero and uses the caller’s coordinates. grid without an ID uses the current grid. Bare numeric filters are accepted only after a recognized type/scope token. The option parser consumes at most ten tokens after spawns.
Current argument/client/target checks (exact source excerpts; branch-dependent):
if (!has_next || !sep->IsNumber(i + 1)) {
if (has_next && sep->IsNumber(i + 1)) {
else if (sep->IsNumber(i)) {
if (!ids || !has_next || !sep->IsNumber(arg_index + 1)) {
Handler failure/help feedback (sent to the player or logged; % fields are formatted at runtime):
Radius reload distance must be greater than zero.
Permissions
Local database snapshot, October 6, 2026: /reload spawns requires status 100 (handler 99). 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
/reload spawns npc radius 50
/reload spawns all clear_timers
Source-checked forms; not executed against a live world.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload spawnscripts
Reload spawn scripts.
Implementation: Implemented.
Syntax
/reload spawnscripts
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload spawnscripts requires status 100 (handler 62). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload spells
Reload spell definitions and NPC spell lists, or just NPC spell lists.
Implementation: Implemented.
Syntax
/reload spells [npc]
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
scope
text
Optional exact npc keyword.
Behavior and restrictions
Reload items afterward if spell activation changed. Reload spawns/repop to reset spells on existing NPCs.
Handler failure/help feedback (sent to the player or logged; % fields are formatted at runtime):
Reloading NPC Spells Lists (Note: Must Reload Spawns/Repop to reset npc spells)...
Permissions
Local database snapshot, October 6, 2026: /reload spells requires status 100 (handler 59). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload startabilities
Reload starting skills and spells.
Implementation: Implemented.
Syntax
/reload startabilities
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload startabilities requires status 100 (handler 522). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload structs
Reload packet structure definitions.
Implementation: Implemented.
Syntax
/reload structs
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload structs requires status 100 (handler 64). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload transporters
Reload transporter data.
Implementation: Implemented.
Syntax
/reload transporters
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload transporters requires status 100 (handler 520). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload voiceovers
Reload voiceover definitions.
Implementation: Implemented.
Syntax
/reload voiceovers
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload voiceovers requires status 100 (handler 532). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload zoneinfo
Reload zone information.
Implementation: Implemented.
Syntax
/reload zoneinfo
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload zoneinfo requires status 100 (handler 1010). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload zones
Registered reload zones entry; unsupported — no active handler.
Implementation: Unsupported — no active handler.
Syntax
/reload zones (registration only; working syntax unavailable)
Arguments
Working arguments are unavailable. Do not treat historical arguments as supported.
Behavior and restrictions
This registration has no active case in the reviewed dispatch switch. It falls through to the Unhandled command log. No working arguments, target behavior or persistence can be established.
Permissions
Local database snapshot, October 6, 2026: /reload zones requires status 100 (handler 193). 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
No working example is published for this status.
Source evidence
No active dispatch case for handler 193. Checked WorldServer/Commands/Commands.cpp:2280 (complete switch), its default at line 6452, and handler definitions in Commands.h.
No upstream Markdown file exists for this registration in the retrieved revision.
/reload zonescripts
Reload zone scripts.
Implementation: Implemented.
Syntax
/reload zonescripts
Arguments
No manual arguments are used by this operation.
Behavior and restrictions
Reload scope and peer propagation follow the current handler; see its source evidence.
Permissions
Local database snapshot, October 6, 2026: /reload zonescripts requires status 100 (handler 104). 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.
No upstream Markdown file exists for this registration in the retrieved revision.
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.