Display item, spell, recipe or effect information for client inspection.
Implemented · 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
/info
33
0
Implemented
Display item, spell, recipe or effect information for client inspection.
Implementation: Implemented.
Syntax
/info <type> [identifiers]
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
type
text
See inspection forms below.
1
identifier
integer
Meaning depends on type.
2
extra_identifier
integer
Additional client identifier where used.
3
tier
integer
Used by the spell form.
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):
/info recipe_product: with recipe id %u not found (recipe missing or no product in stage 1 assigned).
/info overflow: Unable to retrieve an overflow item.
Permissions
Local database snapshot, October 6, 2026: /info requires status 0 (handler 33). 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.
/info inventory
Inspect an inventory item.
Implementation: Implemented.
Syntax
/info inventory <index>
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
Literal inventory action; retained in the root handler.
1
index
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info equipment
Inspect equipped gear.
Implementation: Implemented.
Syntax
/info equipment <slot>
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
Literal equipment action; retained in the root handler.
1
slot
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info appearance
Inspect appearance gear.
Implementation: Implemented.
Syntax
/info appearance <slot>
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
Literal appearance action; retained in the root handler.
1
slot
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info item
Inspect a master item.
Implementation: Implemented.
Syntax
/info item <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
action
text
Literal item action; retained in the root handler.
1
item_id
action dependent
First syntax form: <item_id>. Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info merchant
Inspect a merchant item.
Implementation: Implemented.
Syntax
/info merchant <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
action
text
Literal merchant action; retained in the root handler.
1
item_id
action dependent
First syntax form: <item_id>. Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info store
Inspect a listed store item.
Implementation: Implemented.
Syntax
/info store <item_unique_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
action
text
Literal store action; retained in the root handler.
1
item_unique_id
action dependent
First syntax form: <item_unique_id>. Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info buyback
Inspect a buyback item.
Implementation: Implemented.
Syntax
/info buyback <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
action
text
Literal buyback action; retained in the root handler.
1
item_id
action dependent
First syntax form: <item_id>. Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info consignment
Inspect a broker item.
Implementation: Implemented.
Syntax
/info consignment <identifier>
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
Literal consignment action; retained in the root handler.
1
identifier
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info spell
Inspect spell details.
Implementation: Implemented.
Syntax
/info spell <spell_id> <client_value> <tier>
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
Literal spell action; retained in the root handler.
1
spell_id
action dependent
First syntax form: <spell_id>. Square brackets mean optional.
2
client_value
action dependent
First syntax form: <client_value>. Square brackets mean optional.
3
tier
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info achievement
Inspect an AA ability.
Implementation: Implemented.
Syntax
/info achievement <group> <spell_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
action
text
Literal achievement action; retained in the root handler.
1
group
action dependent
First syntax form: . Square brackets mean optional.
2
spell_id
action dependent
First syntax form: <spell_id>. Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info spellbook
Inspect a spellbook entry.
Implementation: Implemented.
Syntax
/info spellbook <spell_id> <tier>
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
Literal spellbook action; retained in the root handler.
1
spell_id
action dependent
First syntax form: <spell_id>. Square brackets mean optional.
2
tier
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info recipe
Inspect a recipe.
Implementation: Implemented.
Syntax
/info recipe <recipe_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
action
text
Literal recipe action; retained in the root handler.
1
recipe_id
action dependent
First syntax form: <recipe_id>. Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info recipe_product
Inspect a recipe product.
Implementation: Implemented.
Syntax
/info recipe_product <recipe_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
action
text
Literal recipe_product action; retained in the root handler.
1
recipe_id
action dependent
First syntax form: <recipe_id>. Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info maintained
Inspect a maintained effect.
Implementation: Implemented.
Syntax
/info maintained <slot> <spell_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
action
text
Literal maintained action; retained in the root handler.
1
slot
action dependent
First syntax form: . Square brackets mean optional.
2
spell_id
action dependent
First syntax form: <spell_id>. Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info effect
Inspect a spell effect.
Implementation: Implemented.
Syntax
/info effect <spell_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
action
text
Literal effect action; retained in the root handler.
1
spell_id
action dependent
First syntax form: <spell_id>. Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info your_trade
Inspect your offered trade item.
Implementation: Implemented.
Syntax
/info your_trade <slot>
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
Literal your_trade action; retained in the root handler.
1
slot
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info their_trade
Inspect the partner’s offered trade item.
Implementation: Implemented.
Syntax
/info their_trade <slot>
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
Literal their_trade action; retained in the root handler.
1
slot
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.
/info overflow
Inspect your next overflow item.
Implementation: Implemented.
Syntax
/info overflow
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
Literal overflow action; retained in the root handler.
Behavior and restrictions
Item indices and equipment slots are interpreted using the client version; they are not interchangeable with database IDs.
Permissions
Internal action: inherits the /info registration requirement of status 0. No separate database subcommand row exists for this action.
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.