> For the complete documentation index, see [llms.txt](https://renownedgames.gitbook.io/aurora-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://renownedgames.gitbook.io/aurora-engine/weapon/custom-effects.md).

# Custom Effects

![](/files/-McLHeu7cM3VyxMm0obD)

There are two default effects for weapons in **Aurora FPS :**

![](/files/-McLI-Rvieu0th6WTSRu)

If you want, you can always add your effects via the **API.**

## Weapon Position

![](/files/-McLKRDs6HRbfFdk4YjQ)

We can specify a set of weapon behavior under a certain state or set of states.

To do this, we write the number of behavior sets we need in **Size**.

![](/files/-McLL08JEf1rxj9aMal-)

**Next**, we proceed to configuring the behavior sets themselves.

![](/files/-McLLYDoQDP2gIcewRjg)

### State 

We select the states we need from the list provided.

![](/files/-McLM0xyoHMPV0MEBwPB)

{% hint style="success" %}
If all the selected states are active, the changes you set will occur.
{% endhint %}

| Name     | Description              |
| -------- | ------------------------ |
| Position | The weapon shift vector. |
| Smooth   | Smoothness of the shift. |

## Weapon Sway

![](/files/-McLKCVsaNv7p344hZ27)

> Here we set the settings for swinging our weapons when walking and turning the camera.


---

# 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://renownedgames.gitbook.io/aurora-engine/weapon/custom-effects.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.