> For the complete documentation index, see [llms.txt](https://docs.luasec.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luasec.org/discord-bot/commands.md).

# Command reference

All slash commands the Luasec Discord bot provides. **Manager** commands are gated to Administrators by default and additionally honour the configured manager role.

## Setup & configuration (manager)

| Command                                  | Description                                               |
| ---------------------------------------- | --------------------------------------------------------- |
| `/login apikey:<key>`                    | Link the server to your Luasec account with your API key. |
| `/config project project:<name>`         | Choose the project this server manages.                   |
| `/config script script:<name>`           | Choose the script that `/script` delivers.                |
| `/config managerrole role:<@role>`       | Role allowed to run manager commands.                     |
| `/config buyerrole role:<@role>`         | Role autogranted to whitelisted users.                    |
| `/config resethwid enabled:<true/false>` | Allow buyers to reset their own HWID.                     |

## Whitelisting (manager)

| Command                             | Description                                                         |
| ----------------------------------- | ------------------------------------------------------------------- |
| `/whitelist user:<@user>`           | Whitelist a user (creates/links their key + grants the buyer role). |
| `/mass-whitelist-role role:<@role>` | Whitelist everyone who currently has a role.                        |
| `/force-resethwid user:<@user>`     | Reset another user's HWID.                                          |

## Buyer self-service

| Command               | Description                                           |
| --------------------- | ----------------------------------------------------- |
| `/resethwid`          | Reset your own HWID (only if the manager enabled it). |
| `/redeem code:<code>` | Redeem a code to get whitelisted.                     |
| `/script`             | Get the script sent to your DMs.                      |
| `/getrole`            | Claim your buyer role.                                |

## Panel (manager)

| Command                   | Description                                                                       |
| ------------------------- | --------------------------------------------------------------------------------- |
| `/panel [message:<text>]` | Post the buyer control panel in the current channel. The message arg is optional. |

## Typical order of operations

1. `/login` → `/config project` → `/config script` → `/config buyerrole` (+ optional `/config managerrole`, `/config resethwid`).
2. `/panel` in a public channel so buyers can self-serve.
3. `/whitelist` (or `/mass-whitelist-role`) as people buy.

{% hint style="info" %}
Autocomplete is available on `/config project` and `/config script` , start typing and pick from your projects/scripts.
{% 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://docs.luasec.org/discord-bot/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.