> 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/japanese/plugin-usage/adding-content/player-emotes/particles.md).

# Particles

### Configure the special particle location bone

Open your `.iaentitymodel` model file with **Blockbench**.\
Create a new bone, it can have any name.

![](/files/q1Cvj7hGkSmGTFnrAOoZ)

Rightclick on the bone and select "**Bone Config**"

![](/files/rJ2QsYWDkjRiIypvOlJr)

Check the "**Locator**" option and press "**Confirm**".

![](/files/oITcK5LNEw9Cx2vii6wn)

Switch to "**Animate**" view.

![](/files/PvVGTnuKVw4uGnSWpUh4)

Select one of your animations.

![](/files/xQKYCt34Vhka85rpFjWl)

Select the magic wand icon "**Animate Effects**"

![](/files/UWDFeKvbMApWKpctLBII)

Click on the **+** icon near "**Particle**" effect type to create a new particle keyframe.

![](/files/cwoAdhnkXPtogzIWEb6Y)

Edit the values on the "**Keyframe**" panel.

* Name: name of the particle, use the ingame Minecraft particle name.
* Bone (locator): is the name of the bone created in the first part of this tutorial. It will be the location of the particle.
* Speed: speed of the particle emission.
* Count: amount of emitted particles.
* XYZ delta: specifies the dimensions (in number of blocks) for each dimension of the particle effect, with **x y z** in the center. Each coordinate specifies the number of blocks from the center that the particles will appear. You can set decimal numbers.\\

![](/files/zo1zfesAafP6UDEsj0U8)

## Done


---

# 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/japanese/plugin-usage/adding-content/player-emotes/particles.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.