# permissions

## Player permissions

| Permission                 | Default | Description                                                                                                  |
| -------------------------- | ------: | ------------------------------------------------------------------------------------------------------------ |
| `practicebot.use`          |  `true` | Legacy spawn permission. Kept for compatibility.                                                             |
| `practicebot.spawn`        | `false` | Generic permission that grants access to all player-owned bot types when configured as the spawn permission. |
| `practicebot.spawn.normal` |  `true` | Allows spawning Normal PvP bots.                                                                             |
| `practicebot.spawn.cpvp`   |  `true` | Allows spawning Crystal PvP bots.                                                                            |

The generic spawn permission is controlled by:

```yaml
commands:
  spawnbot-permission: "practicebot.spawn"
```

A player can spawn a specific bot type if they have either the type-specific permission or the configured generic spawn permission.

## Admin permissions

| Permission                          |                          Default | Description                                              |
| ----------------------------------- | -------------------------------: | -------------------------------------------------------- |
| `practicebot.admin`                 |                             `op` | Main admin permission. Includes child permissions below. |
| `practicebot.admin.license`         | `op` through `practicebot.admin` | Manage license status and license key.                   |
| `practicebot.admin.template.spawn`  | `op` through `practicebot.admin` | Spawn template bots.                                     |
| `practicebot.admin.despawn`         | `op` through `practicebot.admin` | Despawn PracticeBot NPCs.                                |
| `practicebot.admin.template.create` | `op` through `practicebot.admin` | Create templates.                                        |
| `practicebot.admin.template.edit`   | `op` through `practicebot.admin` | Edit templates.                                          |
| `practicebot.admin.template.cancel` | `op` through `practicebot.admin` | Cancel active editor sessions.                           |
| `practicebot.admin.template.delete` | `op` through `practicebot.admin` | Delete templates.                                        |

## Recommended permission groups

### Public player

```yaml
practicebot.spawn.normal: true
practicebot.spawn.cpvp: false
```

### Crystal PvP player

```yaml
practicebot.spawn.normal: true
practicebot.spawn.cpvp: true
```

### Arena staff

```yaml
practicebot.admin.template.spawn: true
practicebot.admin.despawn: true
```

### Template builder

```yaml
practicebot.admin.template.create: true
practicebot.admin.template.edit: true
practicebot.admin.template.cancel: true
practicebot.admin.template.delete: true
practicebot.admin.template.spawn: true
```

### Owner/admin

```yaml
practicebot.admin: true
```

{% hint style="warning" %}
Give `practicebot.admin.license` only to trusted owners. It can change the saved license key.
{% endhint %}


---

# Agent Instructions: 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://edelweiss-network.gitbook.io/practicebot/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.