> For the complete documentation index, see [llms.txt](https://wiki.arkvalkyrie.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.arkvalkyrie.com/server-features/player-commands.md). # Player Commands These commands are available to **all players**. Type them directly in the chat box every command starts with `@`. ### Server & Character Info #### @rates ``` @rates ``` Displays the server's current **experience and drop rates** Base EXP, Job EXP, normal drops, card drops, and any active rate modifiers (such as EXP events). Use this to check if a rate event is currently running. #### @refresh ``` @refresh ``` **Re syncs your character with the server.** If your character looks stuck, is position-lagged, sprites look wrong, or other players/monsters appear frozen, use `@refresh` to reload your view without relogging. This fixes most visual desync issues instantly. ### Database Lookup Commands #### @mobinfo (@mi) ``` @mobinfo ``` Shows complete information about a monster: HP, base/job EXP, race, element, size, stats, and its **full drop list with drop rates**. Example: `@mobinfo Poring` or `@mi 1002` #### @iteminfo (@ii) ``` @iteminfo ``` Shows details about an item: item ID, type, weight, sell price, and other basic info. Example: `@iteminfo Jellopy` or `@ii 909` #### @whodrops ``` @whodrops ``` Shows **which monsters drop a specific item**, sorted by highest drop rate. Perfect for planning where to farm. Example: `@whodrops Elunium` #### @whereis ``` @whereis ``` Shows the **maps where a monster spawns** and how many spawn on each map. Combine this with `@whodrops` to find the best farming spot. Example: `@whereis Anolian` ### Homunculus Commands *(For Alchemist / Creator / Genetic classes with an active Homunculus.)* #### @hominfo ``` @hominfo ``` Displays your Homunculus' general information: name, level, HP/SP, intimacy, hunger, and accessory. #### @homstats ``` @homstats ``` Shows your Homunculus' **detailed stat breakdown**, including how its current growth compares to the minimum and maximum possible values for its level. Use this to evaluate whether your Homunculus rolled good stat growth. #### @homtalk ``` @homtalk ``` Makes your Homunculus "speak" the message in an overhead chat bubble. Example: `@homtalk Protect the master!` ### Display Toggles These commands are **on/off toggles** type the same command again to disable it. #### @showexp ``` @showexp ``` Displays the **exact Base and Job EXP you gain** from each kill in your chat window, including the percentage of your EXP bar. #### @showzeny ``` @showzeny ``` Displays the **amount of Zeny you gain** whenever you pick up money or receive Zeny. #### @noask ``` @noask ``` **Auto-rejects all incoming requests** trades, party invites, guild invites, friend requests, and duel invitations. Turn this on when farming or AFK to stop request spam. Type `@noask` again to turn it off. ### Vending #### @at (Autotrade) ``` @at ``` *(Also works as `@autotrade`.)* For **Merchant classes with an active vending shop**: puts your vendor into **autotrade mode** your shop stays open and selling while you are **logged out**. Simply set up your vend as usual, then type `@at` and your client will close while your shop keeps running. * Your character remains visible in-game as a vendor. * To reclaim the character, just log back into it. *** ## PVP Duel Commands The **Duel System** lets you fight other players 1 on 1 (or in small groups) **anywhere**, without needing a PVP map. Duels are consensual both sides must agree before any fighting happens. ### How to Start a Duel 1. **Create the duel:** ``` @duel ``` Creates a duel and gives it a duel number. You can also limit the number of participants with `@duel ` (e.g. `@duel 2` for a strict 1v1). You can also directly challenge someone by name: ``` @duel ``` This creates the duel **and** sends the invitation in one step. 2. **Invite your opponent** (if you haven't already): ``` @invite ``` The player must be online. They will receive a duel invitation message. 3. **Opponent responds:** * To **accept** the invitation and join the duel: ``` @accept ``` * To **decline** the invitation: ``` @reject ``` 4. **Fight!** Once both players are in the duel, you can attack each other directly, even outside PVP maps. Players **not** in your duel cannot be attacked and cannot attack you. 5. **Leaving the duel:** ``` @leave ``` Removes you from the duel. When everyone leaves, the duel ends. ### Duel Rules & Notes * **Consent required.** You can never be forced into a duel nothing happens unless you type `@accept`. * **Only duel members can hit each other.** Bystanders are completely unaffected. * **Cooldowns may apply.** There may be a short cooldown between duels or between invites, depending on server settings. * **Blocking invites:** If you have `@noask` enabled, duel invitations are automatically rejected. ### Quick Reference | Command | Description | | ---------------- | ------------------------------------------------------------------------- | | `@duel` | Create a duel (optionally `@duel ` or `@duel `) | | `@invite ` | Invite a player to your duel | | `@accept` | Accept a duel invitation | | `@reject` | Decline a duel invitation | | `@leave` | Leave your current duel | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://wiki.arkvalkyrie.com/server-features/player-commands.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.