> 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/exceptions.md).

# Exceptions and bypassing

There are four ways to let someone ignore restrictions, from broad to narrow.

| Permission                                    | Ignores                                                                                      |
| --------------------------------------------- | -------------------------------------------------------------------------------------------- |
| `itemblocker.bypass`                          | every restriction                                                                            |
| `itemblocker.bypass.<action>`                 | one action, for example `itemblocker.bypass.place`; also `enchantment`, `potion` and `limit` |
| `itemblocker.bypass.preset.<name>`            | everything in one preset, for example `itemblocker.bypass.preset.pvp`                        |
| the rule's own permission, set with `bypass:` | just that one rule                                                                           |

## Operators

`itemblocker.bypass` is given to operators by default, so **operators ignore every restriction**. Test rules with a player who is not an operator, or set both `bypass.enabled: false` and `bypass.per-action: false` in [config.yml](/itemblocker/reference/config.md), then run `/ib reload`.

`bypass.per-action: false` turns off the per-action permissions independently of the global permission. Operators inherit these permissions too, so changing only `bypass.enabled` does not make them subject to restrictions.

## Preset and rule permissions

These are meant for ranks. They only count when they are granted explicitly, for example with a permission plugin, so operators do not get them just for being operators.

```
/ib block elytra actions:armor bypass:vip.elytra
/ib group add *_sword actions:use bypass:rank.knight in:pvp
/ib filter add excalibur hand bypass:quest.excalibur
/ib edit elytra bypass:none                   # remove the exception
```

```
/lp group vip permission set vip.elytra true
/lp group arena-staff permission set itemblocker.bypass.preset.pvp true
```

In the menu, the rule editor has a button for the bypass permission; type it in the chat, or `none` to remove it.

## What bypassing does not cover

Actions without a player, such as hoppers, dispensers, crafters, loot and mob drops, are never bypassed. The [API](/itemblocker/developers/api.md) can let single actions through with `ItemBlockedEvent`.


---

# 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/exceptions.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.