Artifact update SOP

Record the build you run today

Keep a tiny note next to the server. This note is your rollback plan. Without it you cannot get back to a known-good build cleanly.

Current build: <number>
Known-good: yes
Updated: <date>
Rollback build: <previous number>

"Known-good" means you have actually joined this build and it worked. The "rollback build" is the one you ran before this one, in case the current one ever turns out to be bad.

Back up the artifact binaries before you touch anything

Your server folder has two halves. The artifact binaries are the FXServer files you downloaded and extracted: FXServer.exe, run.cmd (or run.sh on Linux), the citizen folder, and the rest of the runtime. Your server-data is everything you own: the resources folder, server.cfg, your database, your .env. An update only swaps the binaries. It must never touch server-data.

Copy the current binaries to a dated backup, for example a folder named fxserver-2026-06-12. That copy is your undo button if the new build misbehaves. Leave resources, server.cfg, and your database exactly where they are.

Install the recommended build

Open the Cfx.re Windows artifacts page and download the latest recommended build. It is the highlighted green row, and it is the build Cfx.re's own guidance tells you to run.

https://runtime.fivem.net/artifacts/fivem/build_server_windows/master/

The newest build at the very top of the list is only for when you need a brand-new fix; it is less tested, so leave it unless you have a specific reason. On Linux, use the same recommended build from https://runtime.fivem.net/artifacts/fivem/build_proot_linux/master/.

Stop FXServer. Extract the new archive into a fresh artifact directory, then point your existing txAdmin and server-data setup at that new directory. Replacing the whole directory avoids a mixed build with stale files left over. Never extract over resources, server.cfg, txData, or the database. Then start the server.

If a build ever misbehaves after you update, drop one build down and test that instead. Run the recommended build by default. Drop down only if it breaks.

Smoke-test, then mark known-good or roll back

Run the same checklist every time so a regression cannot hide. F8 is the in-game client console you open by pressing F8 while the FiveM game window is in focus.

• Console clean. Watch the FXServer console as resources load. No new red errors, and no resource that failed to start.
• Connect. Join your own server from the FiveM client. If it is running on the same PC, press F8 in the game and type the command below (30120 is the default FXServer game port). You should reach character select or spawn, not a load loop.

connect 127.0.0.1:30120

• Spawn. Confirm your ped (your player character) actually spawns into the world.
• Framework health check. Use one documented, non-destructive action you already verified on the previous build, such as opening character selection or reading player and job data. Do not assume /car, /setjob, or /giveitem exists or is safe on every framework.
• resmon. resmon is a developer-only client command that shows each resource's CPU cost. It only works if you launched the FiveM client in developer mode (add the launch argument +set moo 31337). On a normal client, resmon 1 returns Access denied for command resmon. With developer mode on, open F8, type resmon 1, and confirm no resource is suddenly burning CPU it did not burn before. resmon 0 closes it. A build change can shift timing. If you cannot run developer mode, watch txAdmin's performance panel instead.

resmon 1

If every line passes, update the note to the new build and mark it known-good. If any line fails, do not debug live. Stop the server, restore the dated artifact backup from Step 2, start it again, and you are back on the build you trusted this morning.