> 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/it/weapons-editor/changelog.md).

# Changelog

## 2.0.0

Versione attuale.

* Editor in-game di tutte le armi (158 armi vanilla e 464 accessori, più le risorse di armi avviate sul server).
* Modifiche LIVE (danno o moltiplicatore, dispersione, rinculo della camera, raggio esplosione, 4 moltiplicatori globali giocatore) applicate subito a tutti i giocatori.
* Modifiche HOT (tutti gli altri tag numerici di `CWeaponInfo`, munizioni, accessori) scritte nella risorsa separata `ghiaccio_weaponeditor_patch` e valide al prossimo ingresso o riavvio.
* Livelli di permesso ACE cumulativi (`admin` > `hot` > `edit` > `use`), gruppi e job del framework opzionali.
* Preset, cronologia con rollback, import/export JSON ed export `.meta`, confronto, strumenti colpi per uccidere e TTK.
* Persistenza JSON o oxmysql, audit log e webhook Discord opzionale (`config_server.lua` o convar `gwe_webhook`).
* Diagnostica `/wepeditor_selftest` e `/gwe_rescan`.

### Deprecati dalla v1

* `Config.AllowedLicenses`: usa `add_ace identifier.license:... ghiaccio_weaponeditor.admin allow`.
* `Config.Webhook` in `config.lua`: usa `ServerConfig.Webhook` o il convar `gwe_webhook`.


---

# 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/it/weapons-editor/changelog.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.
