commands

---

title: Client Commands description: The Ryzom client command system — how chat slash commands work, and a categorized reference of player, admin, and development commands published: true date: 2026-07-05T00:00:00.000Z tags: editor: markdown dateCreated: 2026-07-05T00:00:00.000Z

Any chat line starting with / is executed as a client command (chat_window.cpp hands the rest of the line to NeL's ICommand::execute). Commands are registered in the client with the NLMISC_COMMAND macro — around two hundred of them, mostly in ryzom/client/src/commands.cpp, with the chat and social ones in interface_v3/people_interraction.cpp and a few scattered near the systems they operate on.

/help lists the available commands and /help <command> shows a command's usage — this is the built-in, always-up-to-date reference. It also takes wildcards: /help reload* or /help *ui searches the command list by prefix or suffix. The tables below are a curated orientation, not a replacement for it.

Availability. Three tiers:

• Player commands are compiled into every build.
• Development commands — the majority — are wrapped in #if !FINAL_VERSION and only exist in development builds. In the tables below they are marked dev.
• Admin commands are not client commands at all: /a, /b and /c forward the rest of the line to the server, which checks the account's privilege before executing. The set of admin commands is server-side (see shard commands).

Separately from all of this, AllowDebugCommands in the client configuration exposes the debug category of interface actions and macros in retail builds; it does not affect the compiled command set.

Player commands

Command	Purpose
/who [GM | <channel>]	List players in the region, GMs, or a chat channel
/where	Report your current position
/follow	Follow your target
/afk [message]	Set away-from-keyboard with an optional custom message
/random [min] <max> [hide]	Roll a die and announce the result
/invite, /leaveTeam, /kickTeammate	Team management
/ignore <player>	Toggle ignoring a player
/party_chat, /add_to_party_chat	Party chat channels
/chatLog	Toggle logging chat to file
/createGroup, /equipGroup, /moveGroup, /deleteGroup, /listGroup	Named equipment groups (outfit switching)
/naked	Unequip everything
/mount	Mount your mektoub target
/time	Current in-game and real time
/version	Client version
/bugReport [screenshot]	Launch the bug report tool with a state dump

Admin forwarding

Command	Purpose
/a <cmd> <args>	Run a server admin command on yourself
/b <cmd> <args>	Run a server admin command on your target
/c <name> <cmd> <args>	Run a server admin command on a named character

Privileges are checked server-side; without them these do nothing.

Development commands (dev builds)

A selection of the larger set, grouped by what they are for. Use /help in a dev client for the full list.

Scene and rendering

Command	Purpose
/shape <file>	Spawn a shape in the scene — also takes particle systems (e.g. /shape tr_fx_bigbird.ps); /clearShape removes them, /setShapeX /setShapeY /setShapeZ /setShapeDir move the last one
/boxes [0|1]	Show selection/bounding boxes
/particle <fx>	Spawn a particle FX
/playAnim <anim>	Play an animation on the selection
/vP, /altLook, /color	Tweak entity visual properties
/reloadAnim, /reloadAttack, /reloadSky, /reloadWeather	Hot-reload data
/dumpFogDayMap, /dumpFogDepthMap, /dumpRainMap, /dumpVillages	Dump environment state to files

Entities and movement

Command	Purpose
/entity <slot> <sheet>	Spawn a client-side entity
/removeEntity <slot>	Remove one
/pos <x> <y> [z]	Teleport the user entity (client-side)
/move, /moveRel, /moveTo, /orient	Move/orient entities
/mode, /behaviour	Force an entity's mode or behaviour
/watchEntity	Watch an entity's state in the info panel
/logEntities	Dump all entities in vision to entities.txt

Interface, database, scripting

Command	Purpose
/ah <handler> <params>	Invoke any interface action handler
/db <property> [value]	Read or write a client database property
/loadui <xml>	Load an additional interface XML file
/saveIntCfg, /loadIntCfg	Save/load the interface layout
/execScript <file.cmd>	Execute a text file of commands
/setDynString, /dynstr, /serverstr	Inspect/fake dynamic strings

Diagnostics

Command	Purpose
/verbose <system>, /verboseDatabase, /verboseAnimSelection, /verboseAnimUser	Toggle per-system debug logging
/log <system> <pos|neg|del|reset> [filter]	Add/remove log filters at runtime
/dump [name]	Write a full client state dump
/record, /replay, /stopRecord	Record and replay network sessions
/reconnect	Reconnect to the shard

See also

• Client Configuration — startup configuration, including AllowDebugCommands
• Console commands and variables in NeL — the ICommand system these are built on
• Shard commands — the server-side admin command set behind /a /b /c
• Admin Command Cookbook — working /a recipes for development shards (items, fame, teleports, NPC spawning)