FiveM Artifacts Tracker
Known broken FiveM server artifact builds. Avoid running these versions on your server to prevent stability issues.
Last updated: Mar 21, 2026, 07:47 AM
⚠️ We recommend avoiding the latest FiveM artifact — it's often unstable and can cause errors on your server. We prefer to wait until bugs are reported and resolved before recommending it.
Node.js sandboxing seems to be causing issues for people - best to avoid for now
Node.js sandboxing seems to be causing issues for people - best to avoid for now
Failed build
Multiple (unconfirmed) reports of server-sided natives throwing errors or causing crashes; best to avoid
Failed build, ignore
Multiple reports of issues loading JS within resources
Timeouts due to latency units being in nanoseconds
Crash when using the new onEntityBucketChange
Mumble (voice) external connections blocked by default
Server crashing due to integer encoding (PR#3235)
Failed Linux build (works OK if using Windows!)
Still crashes (sometimes) when restarting resources due to Node.js 22
Causes a crash when restarting Node.js 22
os.date() appends null terminator; can break Lua scripts
Failed Linux build, ignore
Failed build, ignore
Unconfirmed, but several reports of server-side issues that don't persist when downgrading; best to avoid
Cannot use entity native calls in entityRemoved
Crashing if using newest title update (TU)
SetPlayerModel may cause SIGSEGV crashes on some clients due to changes in player handling. 12031 and below works fine.
Some clients will fail to connect with 'ReadBulk of header failed' error
Failed build, ignore
sv_experimentalNetGameEventHandler enabled by default; can cause server crashing and reports of issues downgrading after upgrading
GetVehicleNumberPlateText server native broken, will cause issues with scripts involving vehicles
Crashing when players join
State bags not replicated to clients