Weapon Meta Editor changelog

GTA takes melee damage from its combat action tables, not from weapons.meta, so the old raw meta editor for melee weapons never actually did anything — the Damage field and other meta values have no effect on melee hits, and FiveM can't safely stream those combat tables to change that. Melee weapons now expose a single damage multiplier instead (0.1-10x, 1.0 = vanilla), applied directly at hit time so it affects every player right away with no restart needed.

Both of these looked editable before but weren't reliably applying. Now fixed:

• Magazine size — editing it used to save fine but often had zero effect in-game, because on vanilla weapons the real magazine size comes from the weapon's default clip attachment, not the ClipSize field you were editing. The editor now detects when a default clip attachment is active, locks the slider with an explanation, and gives you a one-click way to switch it off (or jump straight to that attachment) so your edit actually takes effect.
• Ammo cap (AmmoMax) — these values live in a separate ammo-type entry, not in the weapon's own data, and edits to them were being silently dropped — never written anywhere, with no error shown. The UI also displayed placeholder numbers instead of the real saved values. Both are now fixed: edits write to the correct ammo entry and apply to every other weapon that shares that ammo type, and the UI shows real values.

On startup, the resource checks for known framework recoil scripts (currently qb-weapons and qbx_smallresources' recoil module) — it confirms the resource is running, the specific client file is actually loaded, and that file still calls camera-kick natives (so a disabled or stripped-down copy doesn't trigger a false alarm). If it finds a live conflict, admins get an in-game prompt with two choices: Accept (dismiss it, no behavior change, decision remembered) or Use framework recoil (disables this resource's recoil system server-wide so the other script has sole control). Renamed forks or escrowed (.fxap) copies of a conflicting script can't be detected.

Drive-by now has a real per-weapon panel: a Mode selector (off / effects / full), a global Scale slider (0-3x), and four per-weapon effect toggles (impulse shake, sustained shake, camera blur, screen ring), each of which falls back to a sensible per-class default when left unset. The global Scale is a multiplier on top of whatever amount the weapon/class uses — it doesn't replace the per-weapon settings, both apply together.

Three modes, chosen globally or per weapon (per-weapon always wins when set): Off (no recoil while seated), Effects (shake/blur/ring only — camera doesn't move, so your aim never drags), and Full (adds real camera kick on top, so aim can drag like it does on foot). Full automatically falls back to Effects in first-person view, since FiveM's camera-pitch native doesn't work in that view.

This is a real tuning change, not just a refactor. Heavy weapons (miniguns, RPGs, railguns) used to inherit shotgun timing, which was too fast for their fire rate and left blur/ring effects stuck on — they now have their own class with correct timing. Revolvers previously matched only when your saved recoil table already had an entry for that exact weapon name; unconfigured or unrecognized revolver variants fell through to default behavior. They're now matched by weapon hash as a fallback, so every revolver variant gets the REVOLVER class even without a saved entry.

These fields were locked in an earlier build after testing showed the game engine doesn't reliably pick up re-declared vanilla component/animation data. Further testing showed the lock was too strong — it's inconsistent rather than fully broken (the same edit can apply to one weapon and silently not apply to another), so editing is unlocked again with an inline warning that changes may not take effect, since this is a known FiveM/engine limitation rather than something this resource can fully control.

Addon weapon components and animations used to be declared both in the addon's own resource and in a mirrored copy under the resource's asset system, risking duplicate registration. The addon's own declarations for those two file types are now disabled at prepare-time so only the asset mirror loads. If an addon is later renamed or removed, its old mirror folder is detected automatically on startup and moved aside instead of being left behind as dead weight.

The editor now shows a live projected-vs-cap usage figure for the addon component pool, so you can see how much headroom you have left before you hit the limit instead of finding out when components stop loading.

Press Ctrl+K to search across every tuning field for the currently selected weapon — roughly 215 fields spanning Damage, Firing, Accuracy, Camera, HUD, Force, FX, Flags, Ammo, Animations, and Recoil.

• Matches on the field's display label, its internal meta key (e.g. typing "damage fall off" matches DamageFallOffRangeMin), the tab/section it lives in, and its tooltip text — every word you type has to match something, in any order.
• Selecting a result normally jumps you to that field: switches tab, opens the right sub-panel, scrolls it into view, and flashes it.
• Toggle Edit inline in the palette header to skip the jump entirely — the real field control (slider, dropdown, checkbox, etc.) renders right there in the results, so you can change the value without leaving the palette. This preference is remembered between sessions.
• A weapon has to be selected first, since the palette shows that weapon's live values. Per-component attachment fields aren't indexed and won't show up in search.

Component and animation edits apply immediately in the editor but need a resource (and sometimes a second asset-resource) restart before they're live in-game. A banner now tracks this and tells you exactly how many changes are waiting, with a Restart button right there — no more guessing whether an edit actually took effect. Ordinary weapon-field edits (damage, recoil, etc.) are unaffected; they save live and never trigger this banner.

The resource now hashes each vanilla-override addon file's content and compares it against the hash recorded when you last edited it. If the addon author ships an update, you get a prompt naming the file, the source addon, and the affected weapons, with a choice: Keep my edits (do nothing) or Migrate (replace your edits with the addon's new version). Previously an addon update could silently overwrite your changes with no warning.

For addons that override a vanilla weapon (rather than adding a new one), every restart used to re-copy the addon's shipped file over your saved edits, silently reverting them. Edits are now treated as a persistent layer that's only rebuilt from the addon's file when it's genuinely missing or untouched — a normal restart no longer wipes them.

A fixed set of fields only function in GTA's single-player mode — AmmoMax/AmmoMax50/AmmoMax100, ReloadTimeSP, and two SP-only FX chance fields — and FiveM reads their MP-suffixed counterparts instead. These are now locked in the editor with an inline note naming the live field to edit instead, plus a separate lock for GTA Online rank-gated fields that have no equivalent on FiveM at all.

Setup guidance now branches by the actual problem instead of showing one generic message — a missing filesystem permission prints the exact add_filesystem_permission line to add for that asset resource, a blocked addon-rename capability prints the add_unsafe_child_process_permission line instead, and separate notes cover stale FXServer builds, a missing bin/ upload, unsupported OS, and a non-executable helper binary.

The AI feature now reads your API key's prefix to pick the provider automatically (sk-or- for OpenRouter, gsk_ for Groq), falling back to Groq if the prefix isn't recognized — no provider field to set or get wrong in the config anymore.

is now built in. The script ships ready-to-use translations for Arabic, Bulgarian, Catalan, Danish, German, Spanish, Farsi, French, Hebrew, Italian, Japanese, Korean, Portuguese, Russian, Thai, Turkish, Chinese, and English. Set Config.Locale in your config to switch language server-wide.

when an addon resource supplies a replacement for a base-game weapon, the scanner now detects and tracks it separately from true addon weapons. Server owners can reset any overridden vanilla weapon back to its original GTA values directly from the menu.

now appears in the weapon list for any vanilla weapon that is being sourced from an addon. Hovering the badge shows a tooltip explaining the override, with long tooltip text wrapping cleanly instead of overflowing the menu.

is shown inside the menu while the base meta initialises on first startup, so players and admins see clear feedback instead of a blank or partially loaded state.

lets you control which addon resource wins when multiple addons each attempt to override the same base-game weapon.

now report when two or more addon resources define the same weapon name, showing the real resource names and all shadowed sources so you can resolve conflicts without guesswork.

the mirror directory layout has been flattened to meta/<addon>/<hashed-name> so paths never approach the 260-character Windows limit. A startup warning is also logged if any path gets close to the limit.

added to the server startup sequence, so outdated or mismatched helper binaries are flagged immediately on boot.

when using ox_inventory, the script now adds the weapon with 250 rounds, deduplicates already-owned weapons, and skips re-equipping a weapon the player is already holding.

let you enable or disable specific categories of server-side logging to keep your console output clean.

(--flatten) automatically reorganises an existing mirror directory to the new safe layout on first run after upgrading — no manual file moves required.

server owners can now adjust slider caps and field defaults in config to match the real values used by their weapon mods, without being constrained by built-in limits.

of addon resources that contain broken vanilla meta files, preventing corrupt data from being applied and causing silent failures.

if an addon that was overriding a vanilla weapon is removed, the scanner automatically backs up the orphaned override file rather than leaving stale data in place.

checks for any asset writes that the scanner expected to complete but did not, surfacing missed writes as clear log entries instead of silent failures.

players are now held at the connection screen until the weapon metadata scan completes, preventing players from spawning before weapon configs are ready.

Exclusions are persisted so they survive resource restarts.

Server-side exports that let other resources assign players to recoil groups (or custom recoil parameters) on the fly — no script restart, no config edit. Assignments are per-player and per-weapon, and are pushed to the client immediately.

setWeaponGroup

Assigns a player's weapon to a predefined recoil group.

local ok = exports['onex-weaponmeta']:setWeaponGroup(source, weaponName, groupId)

Returns: true on success, false if the player is invalid, groupId is empty, or the group does not exist.

setWeaponParams

Assigns a custom recoil parameter table to a player's weapon, bypassing predefined groups entirely.

local ok = exports['onex-weaponmeta']:setWeaponParams(source, weaponName, params)

Returns: true on success, false if the player is invalid or params is not a table.

removeWeaponGroup

Clears a runtime assignment, reverting the player back to default recoil behaviour.

local ok = exports['onex-weaponmeta']:removeWeaponGroup(source, weaponName)

Returns: true on success, false if the player is invalid.

getWeaponGroup

Reads back the current runtime assignment for a player's weapon.

local assignment = exports['onex-weaponmeta']:getWeaponGroup(source, weaponName)

Returns: the assignment table — { group = "<id>" } or { params = {...} } — or nil if no runtime assignment exists.

Use Cases

• VIP / job perks — give a police or VIP job tighter recoil on duty weapons, then removeWeaponGroup when they clock off.
• Buffs & debuffs — apply a temporary "shaky hands" recoil profile when a player is injured, drunk, or affected by a status effect.
• Minigames & arenas — normalise recoil across all participants in a deathmatch or shooting range for fair competition.
• Attachment / gunsmith systems — swap recoil parameters live when a player adds or removes a weapon attachment.
• Progression systems — reward weapon mastery with reduced recoil as a player levels up a skill.

The resource automatically falls back to a statically compiled helper binary when the standard binary is incompatible with the host system.

were previously skipped by the scanner due to a case-sensitivity issue. The scanner now correctly detects and includes all addon weapons regardless of prefix casing — this fixes compatibility with Cyber Weapons and many other addon weapon scripts.

Recoil now ramps smoothly from the very first shot.

The resource now correctly verifies writability using the appropriate FiveM file API.

The AI has been completely overhauled. Here's what's new:

What it can do now that it couldn't before:

• Distance-aware damage — "What's the headshot damage at 80m?" now returns the real number with falloff applied. Previously distance was ignored entirely.
• Inverse tuning — Tell it the outcome you want: "Make headshot damage 150 at 20m for player" and it computes the exact field value. No more trial and error.
• Recoil by feel — "Make this rifle feel punchy" resolves into real vertical kick, horizontal drift, and recovery values — not guesses.
• Correct NPC math — NPC headshots have a hidden 1.5× engine multiplier that player headshots don't. The AI now accounts for it. Ask for 4 shots to kill, it dies in exactly 4.
• Bulk edits — Multi-field changes like falloff curves are bundled into a single Apply All instead of separate chips.
• Value validation — Every suggested value is range-checked before appearing as a chip. Out-of-bounds values are clamped or dropped automatically.

For a full breakdown and test prompts see the AI update guide.

Is it far superior to before?

Yes. The old chat could answer simple "how many shots to kill" questions and suggest single field changes through text markers. That was it. Distance was ignored. Recoil was guesswork. The math had a 33% error on every NPC headshot calculation. Bulk edits weren't a thing.

The new chat understands range, solves inverses, derives recoil from feel, gets the engine math right, and can explain what it's doing in plain prose. It's a different tier.

The server now logs a clear warning when your installed weapon count exceeds default pool limits, helping you catch configuration issues before they affect players.

(Config.ExcludedAddons): Specific weapon addons can now be excluded from scanning entirely, with safe revert support if they're re-included later. This is useful when an escrowed weapon addon has malformed meta files that don't crash in-game but cause issues inside the weapon meta editor — just add it to the exclusion list.

When an API key is missing or rejected, the AI assistant now shows a clear, actionable error explaining what to fix rather than failing silently.

The server startup output is now split by permission level and grouped for readability, making it easier to see what the resource has access to on boot.

The resource now automatically repairs its internal manifest on every startup, reducing issues caused by incomplete or corrupted state from previous sessions.

Presets are now weapon-agnostic — a preset made on any weapon can be applied to any other, regardless of category. Create a preset on an SMG and apply it directly to a pistol as a base. No category restrictions.

The AI assistant now supports multiple backend providers. Configuration is friendlier with improved error messages and an automatic retry countdown when rate-limited.

The server can now automatically prepare blocked weapon addons, including weaponcomponents.meta and weaponanimations.meta files, without requiring manual intervention.

Weapon addons that use globbed data_file paths in their resource manifests are now correctly detected and handled.

The Live Preview button in the editor now shows a visual indicator when the in-game preview is out of date with your current unsaved changes.

The editor now blocks interaction and shows a clear message when the required server.cfg permissions are not configured, preventing silent failures.

The pause-blocker tick now runs at a capped rate, the recoil tick skips processing when no weapon is held, and damage number updates are now event-driven rather than polled — saving approximately 0.17ms per frame at idle.

Current Resmon Status :

• idle : 0.00ms
• active : 0.03 - 0.04ms (max)

For detailed resmon info check product page

The pitch baseline is now correctly re-anchored on each toggle.

Changes are now correctly preserved across restarts.

The reset now recovers correctly in this state.