> For the complete documentation index, see [llms.txt](https://studioworks.gitbook.io/studioworks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studioworks.gitbook.io/studioworks-docs/weapons/installation.md).

# Installation & setup

Match weapon models, inventory items, ammunition, and components.

## Identify your package type

| Type                      | Installation implications                                                                    |
| ------------------------- | -------------------------------------------------------------------------------------------- |
| Replacement model or skin | Replaces the specified existing weapon; does not automatically create a new inventory weapon |
| Add-on weapon             | Requires the included registration and often integration with your inventory/weapon system   |
| Component package         | Extends only the specified compatible weapons and components                                 |

The store listing and included instructions define which type you purchased.

## Install and test

1. Copy the complete resource and start it as instructed.
2. Check the included weapon and component identifiers.
3. For add-ons, create the required entries according to your inventory/weapon system's documentation.
4. Test giving and equipping the weapon using an existing authorized tool or the intended inventory.
5. Check ammunition, reloading, and only the components included with the product.

An inventory item with an arbitrary name does not automatically register a new GTA weapon. Item name, weapon identifier, and components must match.

## Common issues

**The item exists, but the weapon cannot be equipped:** Check inventory registration and the weapon identifier first, then confirm the resource is loaded.

**The weapon still has its original appearance:** For replacement packages, check whether another resource replaces the same weapon. Test the package by itself on your development server.

**An attachment floats or is missing:** Check that the component belongs to that weapon variant and is supported by your integration. An attachment for a different weapon is not a valid comparison test.

**No ammunition or the wrong ammunition type:** Compare product instructions with your inventory mapping. Do not guess a universal ammo item.

**Equipping causes a crash:** Test the untouched package without other weapon replacements. Record the weapon, component, and exact action.

[Inventory and script issues](/studioworks-docs/troubleshooting/script-integration.md) · [Models & textures](/studioworks-docs/troubleshooting/models-textures.md) · [Crashes](/studioworks-docs/troubleshooting/crashes-performance.md)

***

[StudioWorks Store](https://tebex.studio-works.net/) · [Discord & Support](https://discord.gg/UmqU67rp4v)


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://studioworks.gitbook.io/studioworks-docs/weapons/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.