> For the complete documentation index, see [llms.txt](https://documentation.rcore.cz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.rcore.cz/paid-resources/rcore_drugs/features/commands-and-permissions.md).

# Commands and Permissions

`rcore_drugs` has a small set of commands for admins and players.

## ⌨️ Commands

| Command            | Who uses it    | Description                                        |
| ------------------ | -------------- | -------------------------------------------------- |
| `/drugs_admin`     | Admins         | Opens the admin panel.                             |
| `/drugs_addiction` | Players        | Shows your current addiction level.                |
| `drugs_seed`       | Server console | Imports default gameplay data after first install. |

{% hint style="warning" %}
Run `drugs_seed` from the server console, not from in-game chat.
{% endhint %}

## 🛡️ Admin Access

Admin access depends on your framework.

{% tabs %}
{% tab title="ESX" %}
ESX checks the groups in `Config.FrameworkAdminGroups`.

Default groups:

```lua
[Framework.ESX] = { 'superadmin', 'admin' }
```

{% endtab %}

{% tab title="QBCore" %}
QBCore checks ACE permission for admin access.

Make sure your admins have the needed command permission in your server permissions setup.
{% endtab %}

{% tab title="QBX" %}
QBX checks ACE permission for admin access.

Make sure your admins have the needed command permission in your server permissions setup.
{% endtab %}

{% tab title="Standalone" %}
Standalone checks this ACE permission:

```cfg
rcore_drugs.admin
```

{% endtab %}
{% endtabs %}

## ✏️ Change Commands

Edit `Config.Commands` in `config.lua`.

```lua
Config.Commands = {
    Admin = "drugs_admin",
    CheckAddiction = "drugs_addiction"
}
```


---

# 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:

```
GET https://documentation.rcore.cz/paid-resources/rcore_drugs/features/commands-and-permissions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.