EQ2Emu
Discord Log in

Slash commands

/location

Show location-editing help.

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
/location 268 200 Implemented
/location add 270 100 Implemented
/location create 269 100 Implemented
/location delete 273 100 Implemented
/location list 274 200 Implemented
/location remove 272 100 Implemented

Show location-editing help.

Implementation: Implemented.

Syntax

/location

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: /location requires status 200 (handler 268). 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_LOCATION (handler 268).

  • WorldServer/Commands/Commands.cpp:6241 — COMMAND_LOCATION.
  • WorldServer/Commands/Commands.cpp:8174 — Command_Location.

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.

/location add

Add your current position to a location.

Implementation: Implemented.

Syntax

/location add <location_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 location_id integer Existing location.

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 (sep && sep->arg[0] && sep->IsNumber(0))

Permissions

Local database snapshot, October 6, 2026: /location add requires status 100 (handler 270). 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_LOCATION_ADD (handler 270).

  • WorldServer/Commands/Commands.cpp:6242 — COMMAND_LOCATION_ADD.
  • WorldServer/Commands/Commands.cpp:8191 — Command_LocationAdd.

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.

/location create

Create a named location.

Implementation: Implemented.

Syntax

/location create <name> [include_y]

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 text Quote names containing spaces.
1 include_y integer Defaults false; positive values enable.

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 (sep->arg[1] && sep->IsNumber(1) && atoi(sep->arg[1]) > 0)

Permissions

Local database snapshot, October 6, 2026: /location create requires status 100 (handler 269). 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_LOCATION_CREATE (handler 269).

  • WorldServer/Commands/Commands.cpp:6243 — COMMAND_LOCATION_CREATE.
  • WorldServer/Commands/Commands.cpp:8216 — Command_LocationCreate.

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.

/location delete

Delete a location.

Implementation: Implemented.

Syntax

/location delete <location_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 location_id integer Location identifier.

Behavior and restrictions

The active handler performs the operation described above after the registration permission check.

Persistence evidence in the active path: database.DeleteLocation. Each call is subject to its surrounding validation; not every branch saves.

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: /location delete requires status 100 (handler 273). 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_LOCATION_DELETE (handler 273).

  • WorldServer/Commands/Commands.cpp:6244 — COMMAND_LOCATION_DELETE.
  • WorldServer/Commands/Commands.cpp:8244 — Command_LocationDelete.

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.

/location list

List locations, location points or respawns.

Implementation: Implemented.

Syntax

/location list <locations|points|respawns> [location_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 kind text locations, points or respawns.
1 location_id integer Required for points.

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):

else if (strncmp(option, "points", strlen(option)) == 0 && sep->arg[1] && sep->IsNumber(1))

Permissions

Local database snapshot, October 6, 2026: /location list requires status 200 (handler 274). 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_LOCATION_LIST (handler 274).

  • WorldServer/Commands/Commands.cpp:6245 — COMMAND_LOCATION_LIST.
  • WorldServer/Commands/Commands.cpp:8266 — Command_LocationList.

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.

/location remove

Remove a location point.

Implementation: Implemented.

Syntax

/location remove <point_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 point_id integer Location point identifier.

Behavior and restrictions

The active handler performs the operation described above after the registration permission check.

Persistence evidence in the active path: database.DeleteLocationPoint. Each call is subject to its surrounding validation; not every branch saves.

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: /location remove requires status 100 (handler 272). 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_LOCATION_REMOVE (handler 272).

  • WorldServer/Commands/Commands.cpp:6246 — COMMAND_LOCATION_REMOVE.
  • WorldServer/Commands/Commands.cpp:8295 — Command_LocationRemove.

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.

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.