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

# Troubleshooting & FAQ

{% hint style="info" %}
First step for any HOT/patch problem: run `/wepeditor_selftest` as an admin and read the report in the **server console**.
{% endhint %}

### The editor does not start: "ox\_lib is not started"

`ox_lib` is required. Add `ensure ox_lib` **before** `ensure ghiaccio_weaponeditor`.

### I changed the clip size (or another HOT field) but nothing happens

HOT values apply on the **next join (reconnect) or server restart**, not instantly. Check also:

1. `add_filesystem_permission ghiaccio_weaponeditor write ghiaccio_weaponeditor_patch` is in `server.cfg` (selftest S6 prints the line if missing).
2. `ensure ghiaccio_weaponeditor_patch` comes **after** every other weapon resource.
3. Run the S7 check: set Pistol `ClipSize` to 50, save, reconnect, then `/wepeditor_selftest check`.

### Should I enable `Config.HotReload`?

No. It is experimental and does not work on build 3258: after restarting the patch at runtime, the weapon and attachment `ClipSize` keep their old values until the player reconnects.

### The mouse stays locked after closing the editor

Use `/weaponeditor_close` (emergency exit).

### "You are not allowed to use this command" / "You do not have permission for this action"

Check your `add_ace` lines and the cumulative levels (`admin` > `hot` > `edit` > `use`). Jobs can grant at most `edit`. See [Commands & permissions](https://ghiaccioscripts.gitbook.io/ghiaccioscripts-docs/weapons-editor/commands-and-permissions.md).

### "The UI did not load (web/dist missing?)"

The resource folder is incomplete or renamed. Re-download from [portal.cfx.re](https://portal.cfx.re) > Granted Assets and keep the folder name `ghiaccio_weaponeditor`.

### Weapons from my weapon pack are missing

Run `/gwe_rescan`. If the pack uses globs and `io.popen` is unavailable (selftest S5), list its files in `Config.ExtraMetaFiles`. For a weapon with no meta at all, use `Config.ExtraWeapons` (LIVE fields only).

### "This weapon has no meta block: only LIVE fields are editable"

The weapon was not found in any meta file (for example it comes from `Config.ExtraWeapons`). Only LIVE fields can be edited.

### Damage changes do nothing on knives or explosives

`Damage per shot` does not work for melee and explosive weapons: use the **Damage multiplier**.

### "Value out of range" / "Values are inconsistent with each other"

The server validates every value. Falloff start must be lower than or equal to falloff end; headshot min distance must be lower than or equal to max distance.

### "Too many requests: retry in a second."

The per-player rate limit (`Config.RateLimit`, default burst 12, 4 per second) was hit. Wait a moment.

### "Another save is in progress" / "Change conflicts with a newer save"

Someone else saved at the same time. Wait and retry; reload the weapon if needed.

### A warning says `Config.Webhook` is deprecated

Move the URL to `ServerConfig.Webhook` in `config_server.lua` (or the `gwe_webhook` convar) and empty `Config.Webhook`: `config.lua` is readable by every player.

### Can players cheat LIVE values?

A cheater can always change their own local LIVE multipliers. The editor is not an anti-cheat.

### Does it cost performance?

Idle cost is **0.00 ms**: no permanent threads, only state bag handlers, events and NUI callbacks.


---

# 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://ghiaccioscripts.gitbook.io/ghiaccioscripts-docs/weapons-editor/troubleshooting.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.
