> 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/adding-content/entities/advanced-settings.md).

# Advanced Settings

In `ItemsAdder/config.yml` you can find some advanced settings about custom entities.

```yaml
entities:
  max-furniture-vehicles-per-chunk: 30
  max_furniture_per_chunk: 20
  custom_entities:
    enabled: true
    emotes: true
    max_per_chunk: 5
    expert_users:
      delay_packets: false
      extract_emotes_shaders: true
  furniture:
    auto_convert_to_item_display: false
```

### `delay_packets`

This option delays the sending of packets to lower down the CPU processing, but creates stuttering animations on some servers.

This is not something you should enable without knowing the side effects.

`max_per_chunk`

Max possible entities per chunk.

`emotes`

Disable or enable emotes. Requires `/iazip` to remove the data from the resourcepack.

`extract_emotes_shaders`

Decide if you want to include the emotes shaders. Disable this if you want to work on your own shaders (shouldn't really be used by novice users).


---

# 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/adding-content/entities/advanced-settings.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.