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

# Stack and inventory limits

Limits keep an item usable but cap how much of it a player has.

| Limit        | Means                                            |
| ------------ | ------------------------------------------------ |
| `stack:`     | the largest stack of the item                    |
| `inventory:` | the most of the item a player may carry in total |

```
/ib limit <item|hand> [stack:<amount>|none] [inventory:<amount>|none] [in:preset]
```

```
/ib limit ender_pearl stack:4 inventory:16
/ib limit totem_of_undying inventory:1
/ib limit ender_pearl stack:none            # remove the stack limit, keep the other
```

Options you leave out keep their value. `/ib list limits` lists them and `/ib show <item>` shows them next to the item's rules.

## How limits are kept

* **Picking up** only takes as much as the player may carry and as fits into stacks within the limit. The rest stays on the ground.
* **Taking items out of a container** over the inventory limit is denied.
* **Anything else**, such as crafting or items from other plugins, is fixed right away: stacks above the limit are split into free slots, and what does not fit or exceeds the inventory limit is dropped at the player's feet.
* Items are never deleted.

Limits are also checked when players join, change worlds and respawn.

## Several presets

If several presets that apply where the player is limit the same item, the smallest limit wins.

## Bypassing

`itemblocker.bypass.limit` ignores every limit. See [Exceptions and bypassing](/itemblocker/rules/exceptions.md).

## In the menu

Open an item's editor: left click on the stack or inventory button adds 1, right click takes 1 away, with shift 16. At 0 there is no limit.


---

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