> For the complete documentation index, see [llms.txt](https://docs.mongenscave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mongenscave.com/premium-products/quests/features/premium-pass.md).

# Premium Pass

The plugin has a built-in two-tier pass system: every player is **Free** by default, and players with the `mcquests.premium` permission are **Premium**. Premium players get more quests, more slots and better multipliers — how much better is entirely up to your config.

### Granting premium <a href="#granting-premium" id="granting-premium"></a>

There is no command or purchase system inside the plugin — premium is just a permission node:

```
mcquests.premium
```

Because it's a plain permission, it plugs into anything: rank purchases from your store, temporary passes (`/lp user Steve permission settemp mcquests.premium true 30d`), rank inheritance, and so on.

The check is live — as soon as the permission is added or removed, the player's bonuses change. No restart or reload needed.

### What premium players get <a href="#what-premium-players-get" id="what-premium-players-get"></a>

Everything is configured under the `premium` section in `config.yml`:

```yaml
premium:
  bonus:
    max-accepted: 3
    max-active: 1
    daily-board: 2

  multipliers:
    xp: 1.25
    reward: 1.5
```

#### Bonuses <a href="#bonuses" id="bonuses"></a>

Bonuses are **added on top** of what the player already has from the base values and their level (see [Daily Board](/premium-products/quests/features/daily-board.md) for how those grow).

| Key            | Description                                        |
| -------------- | -------------------------------------------------- |
| `max-accepted` | Extra quests the player can hold at the same time. |
| `max-active`   | Extra quests that can progress at the same time.   |
| `daily-board`  | Extra quests on the player's daily board.          |

Example: with `quests.limits.max-accepted.base: 3` and a premium bonus of `3`, a fresh premium player can hold 6 quests while a free player holds 3.

#### Multipliers <a href="#multipliers" id="multipliers"></a>

| Key      | Description                                                                                                                                                                                                                          |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `xp`     | Multiplies all quest XP earned from `quest_xp` rewards. With `1.25`, a reward of `value: 200` gives a premium player 250 XP.                                                                                                         |
| `reward` | The premium reward multiplier. It is shown to players (GUIs, `%quests_reward_multiplier%`), but reward values themselves are not automatically scaled — `command`, `item` and other reward types run as written in the quest config. |

{% hint style="info" %}
The `xp` multiplier only applies to quest XP (the plugin's own leveling system), not to vanilla XP given by the `xp` reward type.
{% endhint %}

### Premium in the GUI <a href="#premium-in-the-gui" id="premium-in-the-gui"></a>

The quest board shows the player's tier in a few places, all configurable in `guis.yml`:

* **`title-premium`** — premium players get this menu title instead of `title`. Leave it empty to use the same title for everyone. Both titles support `{reset}` for the time left until the daily reset.
* **`{pass-type}`** — usable in the board's item names and lore (the default player head uses it), shows `Premium` or `Free`.
* **`{daily-board-size}`, `{max-accepted}`, `{max-active}`, `{xp-multiplier}`** — these already include the premium bonuses, so premium players see their real limits.

```yaml
quest-board:
  title: "<dark_gray>Quest Board ({reset})"
  title-premium: "<dark_gray>Premium Quest Board ({reset})"
```

### Premium-only quests <a href="#premium-only-quests" id="premium-only-quests"></a>

There's no `premium: true` flag on quests — instead, use a permission condition:

```yaml
conditions:
  - type: permission
    value: mcquests.premium
```

The quest still shows up on the board for everyone in the level range, but only premium players can accept it. Free players clicking it get the conditions-failed message, which makes it a nice upsell spot.