FiveM server deployment: artifacts, server.cfg and the AI skill

View on skills.sh

Updated

Download SKILL.mdCommunity

Don’t want to manage skills yourself? Get the full app.

To deploy a FiveM server, run the recommended FXServer artifact from the official changelogs API, keep it inside its support window and write a server.cfg that ensures dependencies first. This guide covers those rules, the common mistakes and the AI skill.

Deploying a FiveM server comes down to three choices: which FXServer artifact to run, how to keep it inside its support window and how to write a server.cfg that starts. The deployment skill teaches an AI assistant to make those choices from real data instead of memory.

What the FiveM deployment skill gives you

The skill is built around the official changelogs API:

  • Read recommended and latest for your platform (linux or win32) before you answer. Pick recommended for production and latest only to test new game content.
  • Compare your build against its own support_policy_eol entry. End of life is rolling and per build.
  • Flag the compatibility cutoff the skill documents: builds below 35245 need an upgrade before October 15 2026.
  • Set sv_enforceGameBuild according to the Legacy or Enhanced rule, or omit it for the default.
  • Audit server.cfg before you deploy, with resource ensure order kept intact.

Rule files cover artifacts, the compatibility window, server.cfg essentials and how txAdmin handles artifact updates. The upstream reference is the FiveM server manual.

Common mistakes when deploying FiveM

  • Quoting a build number from memory. Build numbers change. Read recommended and latest from the API every time.
  • Using the critical and optional fields. They are pinned to build 7290 and are not maintained. Ignore them.
  • Assuming a working build stays supported. EOL is rolling, so a build that works today can expire next week.
  • Setting sv_enforceGameBuild at runtime. It only applies at startup. On Enhanced, only 1 is accepted.
  • Using sv_replaceExeToSwitchBuilds. It is deprecated as of build 35245. Do not add it to new configs.
  • Enabling sv_scriptHookAllowed. Never recommend sv_scriptHookAllowed true, because it makes the server vulnerable.
  • Starting a resource before its dependencies. Load order in server.cfg is literal, so ensure dependencies first.

Why AI assistants get FiveM deployment wrong

An assistant trained on older forum posts will quote a build number that was current years ago, suggest convars that no longer exist and mix Legacy and Enhanced settings. The answer sounds confident and the server fails to start or drops players.

The deployment skill forces the order: fetch the lifecycle data, compare the build, then answer with the build number, its EOL timestamp and the source URL. It also forbids inventing a build number, convar or txAdmin menu path.

Install the FiveM deployment skill in 30 seconds

  1. Click "Download SKILL.md" at the top of this page.
  2. Unzip it into the skills or rules folder of your AI tool. The install section below shows the exact path for Claude Code, Cursor and VS Code.
  3. Ask the assistant for something concrete, like "which FXServer build should my production server run", and check that it reads recommended from the changelogs API and states the build number, its EOL and the source URL.

How to install this skill

Download the zip, unzip it, and place the folder where your tool loads skills or rules. The exact path depends on the tool:

Claude Code

Unzip into .claude/skills/fivem-deployment/ inside the project (the folder must contain SKILL.md). For every project, use ~/.claude/skills/fivem-deployment/ instead.

Claude Code skills docs

Cursor

Cursor loads project rules from .cursor/rules/. Add a rule file there that points to the unzipped skill, or paste the contents of SKILL.md and the rule files into a rule. The format is .mdc with frontmatter and changes between versions, so check the docs for your version.

Cursor rules docs

VS Code / Copilot

Copilot reads instruction files from .github/instructions/*.instructions.md. Copy SKILL.md there with an applyTo glob for your Lua files, and keep the rule files next to it.

VS Code custom instructions docs

The SKILL.md file

This is the file your AI assistant reads. It links to the rule files bundled in the download.

Skill contents (includes SKILL.md and any other files)

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.

Decision Gates

Situation Build to pick
Production server recommended from the API
Testing a new game DLC latest
Currently below 35245 Upgrade to 35245 or later before October 15 2026
Build's support_policy_eol date has passed Upgrade now; it is out of support
Symptom Read
Clients cannot join after an update rules/compatibility-window.md
Choosing or verifying a build rules/artifacts.md
Server will not start / bad convar rules/server-cfg.md
Updating artifacts in place rules/txadmin.md

Execution Steps

  1. Fetch the lifecycle JSON for the platform (linux or win32) and read recommended, latest, support_policy, support_policy_eol.
  2. Compare the user's current build against recommended and against its own support_policy_eol entry.
  3. If the current build is older than 35245, flag the October 15 2026 compatibility cutoff.
  4. Set sv_enforceGameBuild per the Legacy/Enhanced rule above, or omit it to take the default.
  5. Audit server.cfg against rules/server-cfg.md before deploying.
  6. Restate the build number, its EOL value, and the source URL in the answer.

Output Contract

Return the chosen build number, its EOL timestamp, and the API URL you read it from. Emit server.cfg lines as runnable cfg blocks with ensure order intact. Never invent a build number, convar, or txAdmin menu path.

References

  • rules/artifacts.md — changelogs API, recommended vs latest, rolling EOL, picking a build.
  • rules/compatibility-window.md — October 15 2026 cutoff, upgrade path, deprecations.
  • rules/server-cfg.md — server.cfg essentials, gamebuild, security convars.
  • rules/txadmin.md — txAdmin's role in artifact updates and version pairing.

Upstream docs: https://docs.fivem.net/docs/server-manual/setting-up-a-server/

Frequently asked questions

Which FXServer build should I run in production?
The recommended build from the changelogs API. Use latest only to test new game content, and check the support_policy_eol date of the exact build you run, because end of life is rolling.
What should sv_enforceGameBuild be?
On Enhanced it accepts only 1, which means the base game with no DLC. Numeric build values are Legacy only, and the convar can only be set at startup, never at runtime.
Can I use this skill with ChatGPT?
Yes, with a manual step. The SKILL.md is plain markdown, so you can paste it into the conversation as context. Native skill support is for Claude Code, Cursor and VS Code.

Related guides

Longer reads from the FiveAI blog on the same topic.

More skills