EQ2Emu
Discord Log in

Slash commands

/entity_command

Show entity-command search 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
/entity_command 241 200 Implemented
/entity_command list 242 200 Implemented

Show entity-command search help.

Implementation: Implemented.

Syntax

/entity_command

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: /entity_command requires status 200 (handler 241). 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_ENTITYCOMMAND (handler 241).

  • WorldServer/Commands/Commands.cpp:6217 — COMMAND_ENTITYCOMMAND.
  • WorldServer/Commands/Commands.cpp:6830 — Command_EntityCommand.

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.

/entity_command list

List matching entity commands and their use distances.

Implementation: Implemented.

Syntax

/entity_command 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 pattern for entity commands.

Behavior and restrictions

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

Permissions

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

  • WorldServer/Commands/Commands.cpp:6218 — COMMAND_ENTITYCOMMAND_LIST.
  • WorldServer/Commands/Commands.cpp:6830 — Command_EntityCommand.

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.

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.