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
spawn_id
integer
Database spawn ID.
1
x
number
Optional X.
2
y
number
Optional Y.
3
z
number
Optional Z.
4
heading
number
Optional heading.
5
location
integer
Optional location/grid value.
Behavior and restrictions
Defaults to your current coordinates and heading. Runs pre-spawn/spawn scripts and adds NPC loot when applicable.
Current argument/client/target checks (exact source excerpts; branch-dependent):
Handler failure/help feedback (sent to the player or logged; % fields are formatted at runtime):
All parameters are optional except the id. The spawn id must be in the database.
Permissions
Local database snapshot, October 6, 2026: /spawn requires status 200 (handler 1). 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
spawn_group_id
integer
Existing spawn-group ID or the keyword new.
1
spawn_group_name
text
Group name.
2
percentage
number
Optional spawn chance.
Behavior and restrictions
A spawn already assigned to a group must first be removed before reassignment.
Persistence evidence in the active path: database.SaveSpawnEntry, database.SaveSpawnInfo. Each call is subject to its surrounding validation; not every branch saves.
Current argument/client/target checks (exact source excerpts; branch-dependent):
Local database snapshot, October 6, 2026: /spawn add requires status 100 (handler 43). 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
operation
number or text
Radius selection or add/remove/save.
1
group_name
text
Optional name for save.
Behavior and restrictions
The active handler performs the operation described above after the registration permission check.
Current argument/client/target checks (exact source excerpts; branch-dependent):
Local database snapshot, October 6, 2026: /spawn combine requires status 100 (handler 80). 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
spawn_type
text
Supported type.
1
race_type
integer
Race/model type.
2
class_type
integer
Class ID.
3
level
integer
Level.
4
name
text
Quote a multiword name.
5
difficulty
integer
Optional difficulty.
6
size
number
Optional size.
Behavior and restrictions
The active handler performs the operation described above after the registration permission check.
Current argument/client/target checks (exact source excerpts; branch-dependent):
Handler failure/help feedback (sent to the player or logged; % fields are formatted at runtime):
All parameters are required except difficulty and size. Valid types are Object, NPC, Sign, or GroundSpawn
Permissions
Local database snapshot, October 6, 2026: /spawn create requires status 100 (handler 44). 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
section
text
Optional details section.
Behavior and restrictions
aggro and spells require an NPC target.
Use a numeric argument for a radius; radius is not a literal keyword in this handler.
Current argument/client/target checks (exact source excerpts; branch-dependent):
if(cmdTarget->IsNPC() && ((NPC*)cmdTarget)->Brain()) {
if (cmdTarget->IsNPC()) {
if(client->GetPlayer()->GetTarget() && client->GetPlayer()->GetTarget()->IsEntity()) {
if (sep->IsNumber(0))
if (spawn->IsEntity()) {
if (spawn->IsNPC())
if (spawn->IsNPC()){
if(spawn->IsEntity())
if (spawn->IsNPC()) {
Handler failure/help feedback (sent to the player or logged; % fields are formatted at runtime):
required_hp_ratio:
Permissions
Local database snapshot, October 6, 2026: /spawn details requires status 200 (handler 52). 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
slot
integer
Equipment slot/appearance or color component.
1
appearance_id
integer
Equipment slot/appearance or color component.
2
red
integer
Equipment slot/appearance or color component.
3
green
integer
Equipment slot/appearance or color component.
4
blue
integer
Equipment slot/appearance or color component.
5
highlight_red
integer
Equipment slot/appearance or color component.
6
highlight_green
integer
Equipment slot/appearance or color component.
7
highlight_blue
integer
Equipment slot/appearance or color component.
Behavior and restrictions
The active handler performs the operation described above after the registration permission check.
Persistence evidence in the active path: database.SaveNPCAppearanceEquipment. Each call is subject to its surrounding validation; not every branch saves.
Current argument/client/target checks (exact source excerpts; branch-dependent):
Local database snapshot, October 6, 2026: /spawn equipment requires status 100 (handler 51). 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.
/spawn group
Manage selected-spawn group membership, association, chance and levels.
Implementation: Implemented.
Syntax
/spawn group <create|add|remove|chance|associate|deassociate|level> [arguments]
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
Group operation.
1
value
action dependent
Group name, group ID, chance, on/off or minimum level.
2
maximum_level
integer
Used by level ranges.
Behavior and restrictions
level off disables the range; level on enables an existing range or accepts min/max; level min max sets the range. Requires a valid selected spawn.
Current argument/client/target checks (exact source excerpts; branch-dependent):
Handler failure/help feedback (sent to the player or logged; % fields are formatted at runtime):
You must select a valid spawn to use this command.
Permissions
Local database snapshot, October 6, 2026: /spawn group requires status 100 (handler 169). 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.
/spawn list
Search database spawn names.
Implementation: Implemented.
Syntax
/spawn list <name>
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
name
remaining text
Name search pattern.
Behavior and restrictions
The active handler performs the operation described above after the registration permission check.
Permissions
Local database snapshot, October 6, 2026: /spawn list requires status 200 (handler 47). 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
placement
text
Optional house-item placement orientation.
Behavior and restrictions
openheading/closeheading require a widget target; myloc moves immediately to the caller. Other forms enter object placement mode.
Persistence evidence in the active path: database.UpdateSpawnLocationSpawns. Each call is subject to its surrounding validation; not every branch saves.
Current argument/client/target checks (exact source excerpts; branch-dependent):
if (cmdTarget && cmdTarget->IsPlayer() == false) {
Permissions
Local database snapshot, October 6, 2026: /spawn move requires status 100 (handler 40). 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.
/spawn remove
Remove the selected spawn’s location/group assignment.
Implementation: Implemented.
Syntax
/spawn remove
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.
Current argument/client/target checks (exact source excerpts; branch-dependent):
if(spawn && !spawn->IsPlayer()){
Permissions
Local database snapshot, October 6, 2026: /spawn remove requires status 100 (handler 46). 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.
/spawn set
Edit selected-spawn attributes and stored spawn data.
Implementation: Implemented.
Syntax
/spawn set list
/spawn set <attribute> [value]
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
attribute
text
See the attribute list generated from the current constructor mappings.
1
value
text
Attribute value; location uses your position without a value.
2
extra_value
attribute dependent
Additional level-range values for group_level forms.
Behavior and restrictions
group_level min max sets a group level range; group_level on enables it; group_level_off disables it.
Script paths should be quoted when needed. Changes to expansion/holiday flags require a spawn reload.
Persistence evidence in the active path: database.SaveBotFloats, database.SaveSpawnInfo, database.UpdateSpawnLocationSpawns, database.UpdateSpawnScriptData. Each call is subject to its surrounding validation; not every branch saves.
Current argument/client/target checks (exact source excerpts; branch-dependent):
Local database snapshot, October 6, 2026: /spawn set requires status 100 (handler 45). 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
selector
integer or text
Database spawn ID or radius.
1
distance
number
Radius search distance; not a location ID.
Behavior and restrictions
The active handler performs the operation described above after the registration permission check.
Current argument/client/target checks (exact source excerpts; branch-dependent):
Local database snapshot, October 6, 2026: /spawn target requires status 100 (handler 50). 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.
/spawn template
List, save, remove or instantiate spawn templates.
Implementation: Implemented.
Syntax
/spawn template list [name|location_id]
/spawn template save <name>
/spawn template remove <template_id>
/spawn template spawn <template_id|name>
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
list/save/remove/spawn.
1
selector
integer or text
Template name/ID or list filter.
Behavior and restrictions
save requires a selected database-backed spawn and unique template name. Template operations use the database; creating from a template is restricted in personal-house instances.
Persistence evidence in the active path: database.SaveSpawnTemplate. Each call is subject to its surrounding validation; not every branch saves.
Current argument/client/target checks (exact source excerpts; branch-dependent):
if (!sep->IsSet(1))
if (sep->IsNumber(1))
if ( target && (target->IsNPC() || target->IsObject() || target->IsSign() || target->IsWidget() || target->IsGroundSpawn()) )
if (sep && sep->arg[1][0] && !sep->IsNumber(1))
if (sep && sep->arg[1][0] && sep->IsNumber(1))
Handler failure/help feedback (sent to the player or logged; % fields are formatted at runtime):
ERROR: Failed to add new template '%s' for spawn '%s' (%u).
ERROR: Failed to add new template '%s' - Already exists!
ERROR: Saving a new spawn template requires a valid template name!
ERROR: You must target the spawn you wish to save as a template!
ERROR: Failed to remove spawn template ID: %u
ERROR: Removing a spawn template requires a valid template ID!
ERROR: Failed to spawn the new spawn location from template ID: %u
ERROR: Failed to spawn the new spawn location from template: '%s'
ERROR: Spawning a new spawn location requires a valid template name or ID!
ERROR: Unknown /spawn template command.
Permissions
Local database snapshot, October 6, 2026: /spawn template requires status 100 (handler 143). 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.