mcpField
F
fivem-deployment

fivem-deployment

github.com/germanfndezCloud & DevOps1966 installsUpdated 2w ago
Repository

About fivem-deployment

A deployment skill for FiveM server operators covering FXServer artifact selection, updates, and server.cfg checks. It requires current lifecycle data and applies rules for support status, security settings, and resource load order.

Key features

  1. 01Check FXServer builds and lifecycle status
  2. 02Guide Legacy and Enhanced game-build settings
  3. 03Audit server.cfg and resource ordering
  4. 04Consult txAdmin and update guidance

Use cases

  1. 01Choose a supported build for production
  2. 02Investigate clients unable to connect after an update
  3. 03Review startup configuration and resource dependencies

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/germanfndez/fiveai-skills --skill fivem-deployment

After installing, type/fivem-deploymentin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

rules/
artifacts.md
compatibility-window.md
server-cfg.md
txadmin.md

Details

From the project README

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

SituationBuild to pick
Production serverrecommended from the API
Testing a new game DLClatest
Currently below 35245Upgrade to 35245 or later before October 15 2026
Build's support_policy_eol date has passedUpgrade now; it is out of support
SymptomRead
Clients cannot join after an updaterules/compatibility-window.md
Choosing or verifying a buildrules/artifacts.md
Server will not start / bad convarrules/server-cfg.md
Updating artifacts in placerules/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/

Comments

Markdown supported