> 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/getting-started/upgrading.md).

# Upgrading from 1.x

ItemBlocker 2 stores its rules in a new format. When it starts and finds the files of 1.x, it converts them automatically.

## What happens

1. `blocked-items.yml`, `presets.yml` and the old `config.yml` are read. This only happens while there is no `rules.yml` yet.
2. Every preset and rule is written to the new `rules.yml`, and settings to the new `config.yml`.
3. The old files and the old `languages` folder are moved to `plugins/ItemBlocker/backup-1.x/`, so nothing is lost. If that folder exists already, `backup-1.x-2` and so on are used.

The console says what was converted. Rules for items the server does not know are skipped with a warning. Preset names that are not valid any more are changed to valid ones, for example `My Preset` becomes `my-preset`.

## What you should check

* **Custom message texts are not converted.** Messages now live in `lang/<language>.yml`. Copy your texts there by hand. See [Messages and languages](/itemblocker/reference/messages.md).
* **Commands changed.** `/ib block`, `/ib edit`, `/ib unblock` and the others take options such as `actions:` and `in:`. See [Commands](/itemblocker/reference/commands.md).
* **Permissions changed.** See [Permissions](/itemblocker/reference/permissions.md).

## Going back

Stop the server, remove the 2.x jar and `rules.yml`, move the files from `backup-1.x/` back into `plugins/ItemBlocker/` and install the 1.x jar again.


---

# 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/getting-started/upgrading.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.