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

# Potion effects

A potion effect limit blocks an effect from a minimum level, wherever it comes from: potions, beacons, commands or other plugins.

```
/ib block potion <effect> [level:<n>] [in:preset]
/ib unblock potion <effect> [in:preset]
/ib show potion <effect>
/ib list potions [in:preset]
```

```
/ib block potion strength level:2      # Strength I is fine, Strength II is not
/ib block potion invisibility          # every level
```

Levels count from 1, as shown in game: Strength II is level 2.

## What happens

* The effect is not applied, and the player is told.
* Players lose a blocked effect they already have when they join or change worlds.
* Brewing stands do not brew potions that give a blocked effect. See the `brew` [action](/itemblocker/rules/actions.md).

## Bypassing

`itemblocker.bypass.potion` ignores every potion effect limit. A [preset bypass](/itemblocker/rules/exceptions.md) ignores the limits of that preset.

## In the menu

Open a preset, then **Potion effects**. Left click raises the level, right click lowers it, shift + right click unblocks 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/potion-effects.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.