A FiveM game build selects the GTA V content baseline a server expects clients to use. Server owners use sv_enforceGameBuild when a resource needs assets or natives from a particular DLC build. The newest available build is not automatically the safest choice for an established server.
The configuration and code examples here target FiveM for GTA V Legacy. Enhanced has different runtime and compatibility rules; check Cfx.re’s Legacy-to-Enhanced changes before applying them to an Enhanced server.
What sv_enforceGameBuild changes
The server variable asks connecting clients to use the configured game build. That can expose DLC vehicles, maps, clothing, weapons and related natives required by resources. It does not update your scripts, repair incompatible assets or prove every client resource supports the selected build.
# server.cfg — example only; choose a tested supported build
set sv_enforceGameBuild 2189
The example selects the Cayo Perico baseline, not a universal recommendation. Set this value at startup and fully restart FXServer. Use the supported values in the current Cfx documentation. Do not paste a build number from an undated article into production.
When to change the build
- A documented resource requires content or natives introduced in a newer build.
- Your current build is no longer supported by the platform or a critical dependency.
- You have a defined release window, staging evidence and rollback plan.
Do not change it only because a larger number exists. Every enforced-build change can affect maps, clothing, vehicles, scripts and client downloads at the same time.
Build change checklist
- Back up the database, server configuration and complete resource set.
- Record the current build and artifact versions.
- Update staging first and clear only the caches the official procedure requires.
- Test joining, character selection, clothing, interiors, vehicles, weapons and voice.
- Exercise resources that use build-specific natives or assets.
- Test with a normal player account, an admin and more than one client.
- Review server and F8 console errors and compare performance with the baseline.
- Keep the previous configuration and artifacts ready for rollback.
Game build versus server artifacts
They solve different problems. The game build controls the GTA content baseline; FXServer artifacts deliver the server runtime. Updating one does not imply the other must change in the same release. Separate the changes when possible so a regression has one clear cause.
Common failures
Missing models or interiors usually point to an asset/build mismatch. Script errors may indicate a native or dependency assumption. A mass client failure immediately after the change is a release incident: roll back first, then reproduce on staging. Keep the exact error, affected resource and old/new versions with the incident record.
For runtime maintenance, continue with updating FiveM server artifacts.