> For the complete documentation index, see [llms.txt](https://wiki.vortexdevelopment.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.vortexdevelopment.net/projects/vortexsellchests/commands-and-permissions.md).

# 📜 Commands & Permissions

Manage your **VortexSellChests** ecosystem with a powerful, hierarchical command system. All administrative commands are nested under the base `/vsc` label.

***

#### 👤 Admin Commands

| Command                                          | Description                                                | Permission                             |
| ------------------------------------------------ | ---------------------------------------------------------- | -------------------------------------- |
| `/vsc give <player> <type> [amount]`             | Grants a specific Sell Chest tier to a player.             | `vortexsellchest.admin.give`           |
| `/vsc fuel give <player> <type> [amount]`        | Grants specific fuel items to a player.                    | `vortexsellchest.admin.fuel.give`      |
| `/vsc booster global <type> [duration]`          | Activates a server-wide sell multiplier.                   | `vortexsellchest.admin.booster.global` |
| `/vsc booster player <player> <type> [duration]` | Activates a private booster for a specific player.         | `vortexsellchest.admin.booster.player` |
| `/vsc booster stop <type>`                       | Force-stops all active boosters of a specific type.        | `vortexsellchest.admin.booster.stop`   |
| `/vsc booster list`                              | Displays all currently active boosters and remaining time. | `vortexsellchest.admin.booster.list`   |
| `/vsc prune`                                     | Cleans up the database by removing orphan chest entries.   | `vortexsellchest.admin.prune`          |
| `/vsc echo <message>`                            | Test MiniMessage formatting via the chat.                  | `vortexsellchest.admin.echo`           |

***

#### 🔑 Permission Nodes

{% hint style="success" %}
The wildcard `vortexsellchest.admin.*` is recommended for server administrators to ensure full access to all future subcommands.
{% endhint %}

| Node                              | Description                                                |
| --------------------------------- | ---------------------------------------------------------- |
| `vortexsellchest.admin`           | Root permission required to use any `/vsc` command.        |
| `vortexsellchest.admin.help`      | Allows viewing the command help menu.                      |
| `vortexsellchest.admin.bypass`    | Allows opening and breaking chests owned by other players. |
| `vortexsellchest.admin.booster.*` | Grants access to all booster management subcommands.       |
| `vortexsellchest.admin.fuel.*`    | Grants access to all fuel management subcommands.          |

{% hint style="success" %}
**Pro Tip:** Use `/vsc booster types` to see a list of all configured booster IDs from your `boosters/` folder!
{% endhint %}


---

# 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.vortexdevelopment.net/projects/vortexsellchests/commands-and-permissions.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.