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
/merchant
244
200
Implemented
/merchant list
245
200
Implemented
Show merchant-description search help.
Implementation: Implemented.
Syntax
/merchant
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: /merchant requires status 200 (handler 244). 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.
/merchant list
Search merchant descriptions.
Implementation: Implemented.
Syntax
/merchant list <description>
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
description
remaining text
Description pattern for the merchant database lookup.
Behavior and restrictions
The active handler performs the operation described above after the registration permission check.
Permissions
Local database snapshot, October 6, 2026: /merchant list requires status 200 (handler 245). 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.