Powered by jgscripts/fivem-artifacts-db

FiveM Server
Artifacts

Track the evolution of the server engine. Every build, every known issue, every recommended version — in one place.

25Builds Tracked
25963Recommended
24Known Issues
25987-25988Known Issue

Node.js sandboxing seems to be causing issues for people - best to avoid for now

21547Known Issue

Multiple (unconfirmed) reports of server-sided natives throwing errors or causing crashes; best to avoid

17462Known Issue

Failed build, ignore

16276Known Issue

Multiple reports of issues loading JS within resources

14583-14716Known Issue

Crash when using the new onEntityBucketChange

14583-14862Known Issue

Timeouts due to latency units being in nanoseconds

13759-13890Known Issue

Mumble (voice) external connections blocked by default

13380-13458Known Issue

Server crashing due to integer encoding (PR#3235)

13079Known Issue

Failed Linux build (works OK if using Windows!)

12933-13045Known Issue

Still crashes (sometimes) when restarting resources due to Node.js 22

12913-12932Known Issue

Causes a crash when restarting Node.js 22

12767Known Issue

os.date() appends null terminator; can break Lua scripts

12651Known Issue

Failed Linux build, ignore

12509Known Issue

Failed build, ignore

12255Known Issue

Unconfirmed, but several reports of server-side issues that don't persist when downgrading; best to avoid

12160-12165Known Issue

Cannot use entity native calls in entityRemoved

12151Known Issue

Crashing if using newest title update (TU)

12092-12135Known Issue

SetPlayerModel may cause SIGSEGV crashes on some clients due to changes in player handling. 12031 and below works fine.

12078-12083Known Issue

Some clients will fail to connect with 'ReadBulk of header failed' error