> 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/actions.md). # Actions An action is something done with an item. Item rules, groups and filters say which actions they block. ## Player actions | Action | Blocks | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | `crafting` | Taking the item from a crafting or stonecutter result | | `pickup` | Picking the item up, or taking it from the creative inventory | | `drop` | Dropping the item | | `use` | Right clicking with the item, eating or drinking it | | `place` | Placing it as a block, emptying it as a bucket, or placing it as an entity: boats, minecarts, armor stands, item frames, paintings and end crystals | | `armor` | Wearing it, however it is put on: right click, inventory, dispenser. Blocked armor is taken off when a player joins or changes worlds | | `inventory` | Moving it into or out of chests and other containers | | `smithing` | Getting it from a smithing table | | `attack` | Hitting a mob or player while holding it | | `break` | Breaking it as a block, or breaking any block while holding it as a tool | | `trade` | Getting it from a villager or wandering trader | ## Actions without a player These happen in the world, so player bypass permissions do not apply. | Action | Blocks | | ------------- | ----------------------------------------------------------------------------------------------------------------- | | `hopper` | Hoppers moving or picking it up. The hopper moves the next allowed item instead, so a blocked item never stops it | | `crafter` | Crafters (1.21 and newer) making it | | `dispense` | Dispensers and droppers using it | | `brew` | Brewing stands making it. Potions with an effect a preset blocks are not brewed either | | `loot` | It appearing in chests and other generated loot; the rest of the loot is kept | | `entity_drop` | Mobs dropping it when they die. Players always drop their own items, so nothing a player owns is ever deleted | ## Items packed in other items For `pickup`, `drop`, `inventory`, `hopper`, `dispense`, `trade`, `loot` and `entity_drop`, the items inside a shulker box or a bundle count too. A shulker box with blocked TNT inside cannot be picked up, put into a chest or moved by a hopper, and the message names the TNT. ## Keywords | Keyword | Means | | -------- | -------------------------------------------------------------------------------------------------------------------- | | `all` | Every action. Rules saved as `all` also cover actions added in later versions | | `obtain` | Every way of getting an item: `crafting`, `crafter`, `smithing`, `brew`, `trade`, `loot`, `entity_drop` and `pickup` | | `none` | No action | `obtain` lets players keep and use an item they have but not get more of it: ``` /ib block mace actions:obtain ``` Actions are written as a comma separated list: ``` /ib block tnt actions:place,crafting,dispense ``` ## Enchanted items An item carrying an enchantment that is [blocked](/itemblocker/rules/enchantments.md) in `block` mode is blocked for every action, whatever the item rules say. --- # 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/actions.md?ask=&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.