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

# Preset templates

Templates are ready-made presets. Creating one makes a normal preset that you can change like any other.

```
/ib template                         # list the templates
/ib template <name> [as:<preset>]    # create a preset from one
```

```
/ib template lifesteal
/ib template survival as:main
```

Without `as:`, the preset is named after the template. In the menu, use the templates button at the bottom of the preset list. It needs `itemblocker.preset`.

## survival

Keeps creative-only and operator items out of survival.

* Every action blocked: bedrock, barrier, light, structure void, structure block, jigsaw, command blocks, command block minecart, debug stick, knowledge book.
* Spawners cannot be placed, traded for or found in loot.
* End portal frames and reinforced deepslate cannot be placed.

## lifesteal

Common rules of lifesteal servers.

* End crystals and respawn anchors cannot be placed; TNT minecarts cannot be placed or crafted.
* Maces cannot be obtained.
* At most one totem of undying, one enchanted golden apple and 16 golden apples.
* Sharpness V is lowered to IV and Protection IV to III; Thorns is removed.
* No Strength II.

## pvp

Fair fights without one-shot explosions.

* End crystals, respawn anchors, TNT and TNT minecarts cannot be placed.
* No attacking with maces.
* At most one totem of undying, one enchanted golden apple and 16 ender pearls.
* Sharpness V and Power V are lowered to IV.
* No Strength II and no Resistance III.

Items a server does not know, such as the mace before 1.21, are left out.


---

# 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/features/templates.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.
