> 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/untitled.md).

# Create Weapon

In **Aurora FPS**, the creation of weapons is performed in several steps.

1. **First of all**, we need to create a **unique identifier** of the weapon (**asset file**), with the help of it, the **system will understand** what kind of weapon it is and perform the necessary actions. 
2. **Next**, we need **a model of a weapon** **with the hands of a character**, which you can buy from people who are engaged in 3D modeling or download free models from the Asset Store, as well as make a model with your own hands.
3. **Then** you need to put the necessary components on the model so that the weapon can function, for this we advise you to familiarize yourself with :

{% content-ref url="/pages/-MbzkkLtzNnoN38k--kc" %}
[Configurate Weapon](/aurora-engine/weapon/configurate-weapon.md)
{% endcontent-ref %}


---

# 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/untitled.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.