FiveM for GTAV Enhanced: Early Access Patch Notes September 30

The September 30 patch for FiveM for GTAV Enhanced is a server performance patch — and it's one of the more consequential ones for anyone running a busy server. It covers parallel sync processing, leaner connect and disconnect handling, and tighter state bag limits, plus a gameEventTriggered regression fix from the GitHub Discussions page and a batch of client crash fixes.

Below is the full breakdown of everything in this patch.

🚀 Server Performance & Scaling

• Sync updates are now processed in parallel, which lifts the main limit on how many players a server can hold. This is the headline change: if your server has been running into a ceiling on player count, that ceiling is the thing being moved. It's on by default, and can be turned off with set onesync_multithreadedPacketProcessing false if you need to isolate a problem.
• Player connects and disconnects are carried in the entity creation data instead of their own separate packets, which cuts server cost at high player counts. Another direct scaling win — join/leave churn is exactly what a packed server spends its time doing.
• Net game events are now rate limited by two new limiters — netGameEvent and netGameEventFlood — configured the same way as the existing rate limiters. Worth knowing both as a tuning knob and as a hardening measure against event spam.

📦 State Bags — Tighter Limits

State bag payloads got a significant tightening:

• State bag values are now limited to 32kb per key, down from 256kb.
• Key names keep their 1024 character limit.
• The server now warns when a key name goes over 256 characters or a value goes over 1kb.

If any of your scripts stash large payloads in state bags — seralised tables, base64 images, big inventories — that approach is now eight times tighter than it was. The warnings are deliberately early: you'll see them at 1kb, long before you hit the 32kb ceiling.

🔌 Scripting Fix

• gameEventTriggered fires for CEventNetworkPlayerEnteredVehicle again, after it stopped reaching scripts entirely in the last patch (#562, #552). If your resources detect vehicle entry through that event, this restores them.

💥 Client Crash Fixes

• Vehicle data validation from FiveM for GTAV Legacy now runs on Enhanced as well, catching invalid vehicle data before it reaches the game and crashes the client. Given how much of the community's content pipeline comes from Legacy-era assets, this should reduce a whole category of crashes on mod-heavy servers.
• The landing gear part pool no longer fills up and crashes the client on servers streaming large numbers of planes.
• The vehicle stream request pool no longer fills up and crashes the client on servers streaming large numbers of vehicles.
• Fixed a client crash from the ped prop renderer running out of space.
• Fixed a client crash involving ragdolls.
• Fixed a remaining case where setting certain mods on a vehicle that is not a car still crashed the client.

🖥️ What This Means For Your Server

• Update the server build before anything else. The protocol changes mean an out-of-date cfx-server will hand players a connection error. Update the server first, then let your community update their clients — exactly the same pattern as the September 22 patch.
• This is the biggest player-capacity change in a while. Parallel sync processing plus cheaper connect/disconnect handling are both aimed squarely at servers with a lot of players. If you've been refusing to grow past a certain population, re-test your limits after updating — and remember you can flip set onesync_multithreadedPacketProcessing false to compare behaviour if something feels off.
• Audit your scripts for big state bag values. A drop from 256kb to 32kb per key is a hard change for anything storing large payloads server-side. Watch for the new warnings in your logs — over 1kb for a value, over 256 characters for a key name — and fix those before they become 32kb surprises.
• Two new rate limiters give you control over event spam. netGameEvent and netGameEventFlood are configured like the existing limiters, so if your community has had issues with event flooding from broken clients or malicious actors, you now have the tools without writing anything custom.
• Fewer client crashes means fewer "your server broke" tickets. The Legacy vehicle validation is the standout here: catching bad vehicle data before it reaches the game removes a crash cause that was never really your server's fault, but was always your problem to field.
• The vehicle and landing gear pool fixes matter for content-heavy servers. If your community streams large numbers of vehicles or planes, that was a hard client-side ceiling. Re-test the content that used to trigger crashes.

Running a FiveM community? NolimitHost FiveM server hosting keeps you on current builds with fast high-clock CPUs, NVMe storage, DDoS protection and automated backups. If your players are still waiting on big resource downloads, FiveM Resource Caching serves that content from our edge instead of your game server.

Conclusion

September 30 is a server-first patch: parallel sync processing lifts the main limit on how many players a server can hold, connects and disconnects ride along in entity creation data to cut cost at high population, and net game events gain two configurable rate limiters. State bag values tighten from 256kb to 32kb per key with early warnings at 1kb, gameEventTriggered fires for CEventNetworkPlayerEnteredVehicle again, and six client crashes are fixed — led by Legacy vehicle data validation now running on Enhanced, plus the landing gear and vehicle stream pool crashes that bit servers streaming large numbers of vehicles and planes.

Update your server build first — the protocol changes will turn away players on an old build — then re-test your player ceiling and your state bag usage.