FiveM Deployment

Choosing an FXServer artifact, keeping it inside its support window, and writing a server.cfg that starts.

Activation Contract

Load this skill when the user asks which artifact to run, how to update FXServer or txAdmin, why clients cannot connect after an update, what sv_enforceGameBuild should be, or how to write or audit server.cfg.

Hard Rules

• Never state a build number from memory. Read recommended and latest from the changelogs API before answering.
• Ignore the critical and optional fields. They are stale-pinned to build 7290 and are not maintained.
• EOL is rolling and per build. A build that works today can expire next week; check support_policy_eol for the exact build in use.
• sv_replaceExeToSwitchBuilds is deprecated as of build 35245. Never emit it.
• On Enhanced, sv_enforceGameBuild accepts only 1 (base game, no DLC); numeric build values are Legacy-only.
• sv_enforceGameBuild can only be set at startup, never at runtime.
• Never recommend sv_scriptHookAllowed true. It makes the server vulnerable.
• Resource load order in server.cfg is literal: dependencies must be ensured before dependents.