> For the complete documentation index, see [llms.txt](https://opuszek.gitbook.io/itemblocker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://opuszek.gitbook.io/itemblocker/rules/presets.md).

# Presets

Every rule lives in a preset. A preset groups rules that belong together, for example everything for an arena or an event, and says where they apply.

## The default preset

The `default` preset always exists and applies everywhere unless you limit it. Commands that take `in:<preset>` use `default` when you leave it out.

## What a preset holds

| Part                                                      | Page                                                                      |
| --------------------------------------------------------- | ------------------------------------------------------------------------- |
| Item rules: which actions are blocked for an item type    | [Item rules](/itemblocker/rules/items.md)                                 |
| Item groups: rules for every item matching a pattern      | [Item groups and allowed items](/itemblocker/rules/groups-and-allowed.md) |
| Allowed items: item types the preset never blocks         | [Item groups and allowed items](/itemblocker/rules/groups-and-allowed.md) |
| Item filters: rules for specific items                    | [Item filters](/itemblocker/rules/filters.md)                             |
| Stack and inventory limits                                | [Stack and inventory limits](/itemblocker/rules/limits.md)                |
| Blocked enchantment levels                                | [Enchantments](/itemblocker/rules/enchantments.md)                        |
| Blocked potion effect levels                              | [Potion effects](/itemblocker/rules/potion-effects.md)                    |
| Worlds and WorldGuard regions the whole preset applies in | [Worlds and regions](/itemblocker/rules/worlds-and-regions.md)            |
| A description, shown in listings                          |                                                                           |
| A reason, added to the messages players get               |                                                                           |

## Managing presets

```
/ib preset create pvp
/ib preset edit pvp description Arena rules
/ib preset edit pvp reason &cNot in the arena
/ib preset edit pvp worlds arena arena_nether
/ib preset list
/ib preset show pvp
/ib preset delete pvp
```

Names are 1 to 32 characters of `a-z`, `0-9`, `_` and `-`. They are lowercase; `PvP` and `pvp` are the same preset.

Rules are added to a preset with `in:`:

```
/ib block ender_pearl actions:use in:pvp
```

In the menu, presets are created with the button at the bottom of the preset list, and a preset's description, reason, worlds and regions are under **Settings**. Presets can also be created from [templates](/itemblocker/features/templates.md).

## When several presets block the same thing

Presets are checked in order: `default` first, then the others alphabetically. The first preset that blocks an action decides, and its reason is shown to the player. For [limits](/itemblocker/rules/limits.md), the smallest limit of all presets that apply wins.

## The reason

A preset's reason is added to every message about a restriction from that preset:

```
[ItemBlocker] You cannot place TNT. (Raids are disabled)
```

It supports `&` colors and hex colors such as `&#ff8800`. `/ib preset edit <name> reason` without text removes it.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://opuszek.gitbook.io/itemblocker/rules/presets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.