FiveM Enhanced Week One: Five Hotfixes and a Public Bug Tracker

FiveM for GTAV Enhanced has been in early access for a week. In that week Cfx.re shipped five hotfixes and moved bug intake to a public GitHub repository, which means the backlog is readable by anyone for the first time in the platform's history. That second change is the more interesting one. We covered the migration question on July 27, when the headline was that Cfx.re itself is telling production servers to wait for Asset Escrow. That advice still stands and we are not repeating it at length here. This piece is about what week one actually looked like. Five hotfixes in seven days Early access began with the announcement post "FiveM for GTAV Enhanced is Available Now in Early Access", published to Cfx Forum Announcements on July 21, 2026 at https://forum.cfx.re/t/fivem-for-gtav-enhanced-is-available-now-in-early-access/5412858. Five hotfix entries were published to the citizenfx/rfc GitHub repository Patch Notes on July 21, 22, 23, 24 and 27, 2026. They are Discussions #59, #127, #176, #220 and #287 in that order. Worth noting for anyone searching the repo: the July 21 entry is titled simply "FiveM for GTAV Enhanced: Early Access Hotfix" with no number, so the numbering visible in the titles starts at Hotfix 2. As of July 28 there is no Hotfix 6. A framing note in our own voice, clearly labelled as analysis: five hotfixes in seven days reads as normal aggressive early-access velocity. A platform shipping daily fixes in its first week is a platform with people watching the issue tracker. Silence for a fortnight would be the worrying outcome. What Hotfix 5 fixed Hotfix 5, published July 27, 2026, is the substantial one for resource developers. Per its changelog: onResourceStart no longer fires for a resource's own start. NetworkGetEntityOwner and NetworkGetFirstEntityOwner return -1 for server-owned entities instead of 65535. DecorSetInt and similar decorator natives now apply properly. SetNuiFocus releases focus immediately again instead of after a long delay. ShutdownLoadingScreenNui no longer relocates local peds. Custom server endpoints restored. The semicolon command separator no longer splits connection strings. Server-created vehicles can be deleted again, unless the server is in protected mode. The "Failed to initialize network" connection handshake error is fixed. Crash fixes for replay recording, map objects and metadata loading. The entity owner change is a behavioural correction rather than a bug squash, and any resource written against the 65535 value on Legacy needs looking at. The bug tracker is now public Cfx.re describes the citizenfx/rfc repository as "a centralized place for the community to report bugs, discuss findings, and increase visibility on known problems across Cfx products". It adds that "Reports are reviewed, triaged, and escalated by our team once validated", and that "For now, we're piloting this process with bug reports for FiveM on GTAV Enhanced only." For server owners the useful part is visibility. Open threads can now be read before you commit a migration. Here is what has traction as of July 28: "Enhanced C# sandbox denies DbConnectionStringBuilder", opened July 22, 2026, 24 comments. The highest-engagement thread on the repo, and it affects database connectivity for C# resources. "Failed to open file 'cfx_resource_ox_lib:/imports/*", opened July 21, 10 comments, Discussion #42. "Enhanced Build v90 to v97 - cfx_resource virtual filesystem cannot resolve nested resource files", opened July 24, 7 comments, Discussion #207. "CreateRuntimeTextureFromImage file not found", opened July 23, 10 comments, Discussion #149. A FXServer early-access b90 Docker startup hang, sitting at 0% CPU before txAdmin prints "All ready!", Discussion #50, opened July 21. The thread identifies the cause as Docker's default seccomp profile blocking the io_uring_setup and io_uring_enter syscalls, with --security-opt seccomp=unconfined as the workaround. One bug that circulated in the first week has already been closed. The streamed base-asset override report at Discussion #92, where minimap.gfx and minimap.ytd were ignored on Enhanced, was reproduced by a maintainer and fixed, with the reporter confirming "Just tested it, works fine now on b95." Some users in that thread still report crashes when replacing Scaleform assets, so it is worth watching rather than treating as fully closed. The C# sandbox thread is the one to watch. Any framework touching a database through a connection string builder in C# is affected, and 24 comments in six days is a lot of engagement for a platform this size. The ox_lib log messages, and why the thread has not settled Several hosting blogs have framed the ox_lib "Failed to open file" messages as ox_lib being broken on Enhanced. The thread at https://github.com/citizenfx/rfc/discussions/42 does not support a clean verdict in either direction, so here is what is actually in it. Cfx.re maintainer FabianTerhorst says the messages are visual only, writing that "These errors are just visual" and that "this is specifically is not breaking any behavior inside it." The mechanism is that ox_lib deliberately attempts to load files that may not exist. On Legacy a failed attempt printed nothing, and on Enhanced the same failed attempt logs a warning. That is not the whole thread. User ArawnLaxus replies that "It is actually causing certain ox_lib dependent scripts to fail like illenium_appearance and even qbx_core", and that "the behaviour of the specified scripts are not working as expected." So the maintainer position is that the logging changed and nothing else, while some server owners report dependent resources misbehaving. Those two accounts have not been reconciled in the thread. If you run illenium_appearance or qbx_core, treat this as unresolved and test rather than assuming either answer. The technical baseline underneath all of this Development Update #3, posted to Cfx Forum on July 15, 2026 at https://forum.cfx.re/t/development-update-3-fivem-for-gtav-enhanced/5415045, sets out what Enhanced is meant to deliver: Tick rate raised to "up to 120 updates per second, up from the previous 30 (or 40 with sv_useAccurateSends enabled)". Multi-core entity culling. .NET 10. NodeJS 26 server side and V8 14.6.202 client side. State bag sets "10x faster". RAM usage down "up to 50%". The server binary renamed "Cfx Server". Perfetto replacing the legacy profiler. Over 80 Prometheus compatible metrics, where there were previously three. In the same update, Cfx.re said it is "now looking to push beyond the current 2,048-player cap on a single server", with public playtesting planned. No date has been given for that, and no number above 2,048 has been named. One developer's account, labelled as such Developer Valdarix published a first-hand write-up on Medium around July 24, 2026 describing a from-scratch C# framework built on Enhanced with no ESX, no QBCore, no ox_lib and no oxmysql, using PostgreSQL and Svelte. He reports that the runtime "reports net10.0 on Microsoft.NETCore.App 10.0.0, self-contained, with its own bundled runtime. Mono is gone." On the performance claims he writes that "The headline claim held up." His overall verdict is mixed: "Some answers were better than I hoped. Several were worse." That is one developer, self published, working on an unusual stack that avoids most of the ecosystem other servers depend on. It is a useful datapoint about the runtime and a poor guide to what a typical ESX or QBCore server will experience. Confirmed, reported and unconfirmed Confirmed (Cfx.re operated channels): Early access began July 21, 2026 per the Cfx Forum announcement. Five hotfix entries were published to the citizenfx/rfc Patch Notes on July 21, 22, 23, 24 and 27, 2026, as Discussions #59, #127, #176, #220 and #287. The July 21 entry carries no number in its title, so visible numbering starts at Hotfix 2. There is no Hotfix 6 as of July 28. The Hotfix 5 changelog items listed above are as published. Confirmed (Cfx.re, repo description): citizenfx/rfc is "a centralized place for the community to report bugs, discuss findings, and increase visibility on known problems across Cfx products". "Reports are reviewed, triaged, and escalated by our team once validated", and "For now, we're piloting this process with bug reports for FiveM on GTAV Enhanced only." Confirmed (open threads on that repo): The C# sandbox DbConnectionStringBuilder report opened July 22 with 24 comments, the ox_lib file-open report at Discussion #42, the cfx_resource virtual filesystem report at Discussion #207, the CreateRuntimeTextureFromImage report at Discussion #149, and the Docker b90 startup hang at Discussion #50. Confirmed as fixed, not open: The minimap base-asset override bug at Discussion #92 was reproduced and fixed, with the reporter confirming it works on b95. Some users in the thread still report crashes when replacing Scaleform assets. Confirmed (Development Update #3, July 15, 2026): 120 tick rate, multi-core entity culling, .NET 10, NodeJS 26 and V8 14.6.202, state bags "10x faster", RAM "up to 50%" lower, the "Cfx Server" rename, Perfetto, and over 80 Prometheus compatible metrics. Cfx.re is "now looking to push beyond the current 2,048-player cap on a single server", with public playtesting planned. Contested, unresolved (Discussion #42): Cfx.re maintainer FabianTerhorst says the ox_lib "Failed to open file" messages "are just visual" and are "not breaking any behavior inside it". User ArawnLaxus reports in the same thread that dependent scripts including illenium_appearance and qbx_core fail. The two accounts have not been reconciled. Treat the "ox_lib is broken" framing in some hosting blogs as unproven, and the "purely cosmetic" framing as disputed. Our analysis, labelled as such: Five hotfixes in seven days reads as normal early-access velocity rather than evidence of a troubled launch. Reported, single self-published developer account: Valdarix on Medium, around July 24, 2026, on building a C# framework with no ESX, QBCore, ox_lib or oxmysql, reporting the runtime as "net10.0 on Microsoft.NETCore.App 10.0.0, self-contained, with its own bundled runtime. Mono is gone", that "The headline claim held up", and that "Some answers were better than I hoped. Several were worse." Not confirmed: Any date for Enhanced leaving early access. Any Cfx.re statement on asset escrow timing for Enhanced. Any end-of-life date for FiveM Legacy. Any relationship between Enhanced and GTA 6, on which Cfx.re has said nothing at all. Week one looks like what a serious early access should look like: daily fixes, a visible backlog and a clear pilot process for reports. The escrow question is still the one that decides migrations, and it still has no date. We will track the hotfix cadence and the open threads on our news hub, and you can see which communities are already experimenting on our servers list.