FiveM for GTAV Enhanced: Early Access Hotfix 9

Hotfix 9 for FiveM for GTAV Enhanced follows close behind the August 11 patch, addressing a few regressions it introduced along with some additional fixes from community reports on the GitHub Discussions page.

Below is the full breakdown of everything in this patch.

Regression Fixes

• NUI loads non-.woff2 font files again, like .ttf and .otf, fixing a regression where custom fonts failed to load with an "unsupported file type" error (#399). Resources that ship their own font files will now render correctly again.
• Vehicles spawned by the server at startup (before any client connects) are visible to players again instead of missing when they join (#400).
• The server no longer crashes when a player enters a routing bucket that holds a vehicle spawned on server boot (#402).

Scripting & Native Fixes

• CreateColshapePolygon now accepts integer coordinates instead of only floating-point values — following up on the August 11 fix that enabled plain arrays of points.
• The Mumble compatibility API now supports creating temporary non-spatial channels, fixing radio channels in voice resources like pma-voice.

New Natives & Events

This patch adds several highly requested scripting additions:

• SetPlayerName — a new server native that can be used during playerConnecting and afterward to set a player's name.
• onPlayerNameChanged — a new event that fires when a player's name changes, reporting the old and new name and the resource that changed it.
• onPedDeath and onPedHealthChanged — new events for tracking ped deaths and health or armour changes, including the attacker and weapon involved.

Dev Tools

• The net graph and resource performance graph dev tools now support hiding individual lines by clicking their titles — a useful quality-of-life improvement for debugging performance issues.

Stability

• Various additional server-side crash and stability fixes.

How to Update

This update is delivered automatically through the FiveM for GTAV Enhanced client. Restart your client to receive it, and server operators should ensure their Cfx Server binaries are up to date.

The Cfx.re team continues to actively monitor the GitHub Discussions page during early access. If you encounter any remaining issues, reporting them there gives the team the best chance of addressing them quickly.