> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vetox.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Command reference

> How Vetox commands work — permissions, cooldowns, restrictions — and an index of all 66 commands.

Vetox registers **66 commands**. Two are containers with subcommands, giving **84 things you can actually run**.

<CardGroup cols={2}>
  <Card title="General" icon="message" href="/en/commands/general">
    **13** — Vito, reputation, colours, suggestions, translation, dice, help.
  </Card>

  <Card title="Information" icon="circle-info" href="/en/commands/information">
    **9** — avatars, banners, profiles, invites, roles, server details.
  </Card>

  <Card title="Leveling" icon="chart-line" href="/en/commands/leveling">
    **5** — rank cards, the server leaderboard, XP administration.
  </Card>

  <Card title="Moderation" icon="gavel" href="/en/commands/moderation">
    **39** across two pages — [member moderation](/en/commands/moderation) and [server moderation](/en/commands/server-moderation).
  </Card>
</CardGroup>

## Every command is guild-only

<Warning>
  **No Vetox command works in DMs.** All 66 are restricted to servers. A command typed in a DM with the bot will not appear.
</Warning>

## Permissions

Two separate checks run on every command.

<Steps>
  <Step title="Your permissions">
    Some commands require a Discord permission — `Manage Server`, `Ban Members`, `Manage Roles` and so on. These are listed per command.
  </Step>

  <Step title="The bot's permissions">
    Vetox must itself hold the permission to carry out the action. A moderator with `Ban Members` cannot ban through Vetox if Vetox lacks `Ban Members`.
  </Step>
</Steps>

<Warning>
  For anything involving roles or members — bans, kicks, mutes, role changes, nicknames — **the Vetox role must sit above the target's highest role**. Discord refuses the action otherwise, no matter what permissions are granted.

  See [Permissions](/en/permissions).
</Warning>

## Cooldowns

Per user, per command. Most are 3–15 seconds; a few heavy commands are longer.

| Cooldown      | Commands                                                                       |
| ------------- | ------------------------------------------------------------------------------ |
| **0 seconds** | `/avatar`, `/banner`, `/invites`, `/roles`, `/server-avatar`, `/server-banner` |
| 2–5 seconds   | Most moderation and configuration commands                                     |
| 10–15 seconds | `/profile`, `/rank`, `/top`, and most general commands                         |
| 20–30 seconds | `/unban-all`, `/role-multiple`, `/add-emoji`                                   |

## Restricting commands

From the [Commands](/en/server-management/command-management) page you can disable any command for your server, restrict it to specific roles or channels, and set per-server aliases.

<Note>
  Aliases are a per-server setting. No command ships with one built in.
</Note>

## No command is premium-gated

<Note>
  **Every one of the 66 commands is available on every tier**, including Starter. Premium gates apply to dashboard features and limits, not to command access.

  The one nuance is `/rep`, whose daily allowance varies by the user's personal [Membership](/en/premium/membership) — the command itself is free to run.
</Note>

## Module toggles

Four commands stop working when their module is switched off in [Server Setup](/en/server-management/setup):

| Command                             | Module      |
| ----------------------------------- | ----------- |
| `/colors`, `/color-set`             | Colors      |
| `/suggest`, `/suggestion`           | Suggestions |
| `/starboard`, `⭐ Send to Starboard` | Starboard   |

<Warning>
  **`/ticket` is not covered by the Tickets toggle.** Turning Tickets off in Server Setup does not disable the `/ticket` command — it continues to work inside existing ticket channels.
</Warning>

## The context-menu command

One entry is not a slash command: **⭐ Send to Starboard**, reached by right-clicking a message → Apps.

<Note>
  Because it is a context-menu entry rather than a slash command, it does not appear on the dashboard's Commands page and its per-server settings cannot be changed there.
</Note>

## Troubleshooting

<AccordionGroup>
  <Accordion title="A command does not appear when I type /">
    It is disabled for your server, restricted to roles or channels you are not in, or Discord has not refreshed its command list — try restarting your client.
  </Accordion>

  <Accordion title="Vetox says it cannot do that to a member">
    Role hierarchy. The Vetox role must be above the target's highest role.
  </Accordion>

  <Accordion title="Nothing happens in DMs">
    Expected — every command is guild-only.
  </Accordion>

  <Accordion title="A ticket subcommand is missing">
    The dashboard lists a `tag` subcommand that the bot does not register. It cannot be run. Every other subcommand works.
  </Accordion>
</AccordionGroup>