> For the complete documentation index, see [llms.txt](https://docs.vames-store.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vames-store.com/assets/vms_multichars/developer-api/commands.md).

# Commands

<table><thead><tr><th width="384">Command name</th><th>Information</th></tr></thead><tbody><tr><td>/deletecharacter charID:identifier</td><td>Character deletion but you must specify charID for example char1:identifier</td></tr><tr><td>/setslots identifier count</td><td>Setting a specific number of slots for a player, this requires the use of identifier without charID/steam/license, just identifier numbers alone</td></tr><tr><td>/removeslots identifier</td><td>Removal of custom number of player slots, this requires identifier without charID/steam/license, just identifier numbers alone</td></tr><tr><td>/enablechar charID:identifier</td><td>Enable player to select character but you must specify charID example char1:identifier</td></tr><tr><td>/disablechar charID:identifier</td><td>Disable the player's ability to select a character but you must provide a charID example char1:identifier</td></tr><tr><td></td><td></td></tr></tbody></table>


---

# 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://docs.vames-store.com/assets/vms_multichars/developer-api/commands.md?ask=<question>&goal=<endgoal>
```

`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.