> For the complete documentation index, see [llms.txt](https://itemsadder.devs.beer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://itemsadder.devs.beer/russian-work-in-progress/faq/multiple-atlases-used-in-model.md).

# 1.21.11 - Multiple atlases used in model

{% hint style="info" %}
This happens in 1.21.11+ clients
{% endhint %}

`[Worker-Main-108/WARN]: Unable to bake item model: 'minecraft:netherite_sword'`

`java.lang.IllegalStateException: Multiple atlases used in model, expected minecraft:textures/atlas/blocks.png, but also got minecraft:textures/atlas/items.png`

## How to fix

Add the model name (in this case `netherite_sword` ) in `config.yml` and regenerate your pack.

```yml
      fix_1_21_11_plus_atlas_items_models:
        enabled: true
        models:
          - "paper"
          - "potion"
          - "netherite_sword"
```

Another solution is to make sure to avoid mixing up block and item textures for the same model.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://itemsadder.devs.beer/russian-work-in-progress/faq/multiple-atlases-used-in-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.