Weapon Editor
Installation
Dependencies, ensure order and permissions for the Weapon Editor.
#1. Copy the resources
- Copy
ghiaccio_weaponeditorintoresources/. Keep the folder name: the NUI and the patch path depend on it. - Copy
ghiaccio_weaponeditor_patch(the sibling folder in the download) intoresources/as a separate resource.
#2. server.cfg
cfg
ensure ox_lib
# ensure oxmysql # only with Config.Storage = 'oxmysql'
# ... your framework (es_extended / qb-core / qbx_core) and every other resource (weapon packs included)
ensure ghiaccio_weaponeditor
ensure ghiaccio_weaponeditor_patch # AFTER every other WEAPONINFO resource so the patch wins
# REQUIRED: lets the editor write the patch (without it HOT/RESTART values never reach players)
add_filesystem_permission ghiaccio_weaponeditor write ghiaccio_weaponeditor_patch
# permissions (cumulative: admin > hot > edit > use)
add_ace group.admin ghiaccio_weaponeditor.admin allow # everything: global presets, rollback, rescan
add_ace group.admin ghiaccio_weaponeditor.hot allow # HOT fields, ammo, attachments
add_ace group.mod ghiaccio_weaponeditor.edit allow # LIVE fields
add_ace group.mod ghiaccio_weaponeditor.use allow # read-only and preview
# per-player example:
# add_ace identifier.license:YOUR_LICENSE ghiaccio_weaponeditor.admin allow
# optional Discord audit webhook (or ServerConfig.Webhook in config_server.lua; never in config.lua)
# set gwe_webhook "https://discord.com/api/webhooks/..."#3. Permission levels
Levels are cumulative: admin > hot > edit > use.
| ACE | Allows |
|---|---|
ghiaccio_weaponeditor.use | Read-only and preview |
ghiaccio_weaponeditor.edit | LIVE fields |
ghiaccio_weaponeditor.hot | HOT / RESTART fields, ammo, attachments |
ghiaccio_weaponeditor.admin | Everything: global presets, rollback, rescan |
Besides ACE you can map framework groups (Config.Permissions.groups) and jobs with a minimum grade (Config.Permissions.jobs, limited to the edit level) in config.lua. See Configuration.
#4. Framework notes
Detection is automatic (Config.Framework = 'auto'); force 'esx', 'qbcore', 'qbox' or 'standalone' if needed. The framework is only used for permissions (ESX xPlayer.getGroup(), QBCore HasPermission, Qbox/standalone ACE group.<name>).
#5. First start
- Start the server and check the console for errors.
- In game run
/weaponeditor(optionally set a key withConfig.Keybind). - If the mouse stays locked, use the emergency exit
/weaponeditor_close. - Run
/wepeditor_selftestonce (see Commands) to verify the patch can be written.