fivem-deployment

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

FiveM Deployment

FiveM 部署

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

选择 FXServer 构建产物、使其保持在支持周期内，并编写可正常启动的 server.cfg。

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

当用户询问应运行哪个构建产物、如何更新 FXServer 或 txAdmin、更新后客户端为何无法连接、

sv_enforceGameBuild

应如何设置，或如何编写或审计

server.cfg

时，加载此 skill。

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
```
ensure
```
d before dependents.

绝不能凭记忆说出构建编号。回答前，应从 changelogs API 读取
```
recommended
```
和
```
latest
```
。
忽略
```
critical
```
和
```
optional
```
字段。它们已过期并固定指向 build 7290，且未再维护。
EOL 是滚动式的，并且按 build 确定。今天可用的 build 下周就可能过期；应针对正在使用的准确 build 检查
```
support_policy_eol
```
。
```
sv_replaceExeToSwitchBuilds
```
从 build 35245 起已弃用。绝不能输出它。
在 Enhanced 模式下，
```
sv_enforceGameBuild
```
仅接受
```
1
```
（基础游戏，不含 DLC）；数字 build 值仅适用于 Legacy。
```
sv_enforceGameBuild
```
只能在启动时设置，绝不能在运行时设置。
绝不要建议使用
```
sv_scriptHookAllowed true
```
。这会使服务器易受攻击。
```
server.cfg
```
中的资源加载顺序按字面执行：依赖项必须先于其依赖方执行
```
ensure
```
。

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

情况	应选择的 build
生产服务器	API 中的 `recommended`
测试新的游戏 DLC	`latest`
当前版本低于 35245	在 2026 年 10 月 15 日之前升级到 35245 或更高版本
build 的 `support_policy_eol` 日期已过	立即升级；该版本已不在支持范围内

症状	查阅
更新后客户端无法加入	rules/compatibility-window.md
选择或验证 build	rules/artifacts.md
服务器无法启动／convar 有误	rules/server-cfg.md
原地更新构建产物	rules/txadmin.md

Execution Steps

执行步骤

Fetch the lifecycle JSON for the platform (

linux

win32

) and read

recommended

latest

support_policy

support_policy_eol

Compare the user's current build against
```
recommended
```
and against its own
```
support_policy_eol
```
entry.
If the current build is older than 35245, flag the October 15 2026 compatibility cutoff.
Set
```
sv_enforceGameBuild
```
per the Legacy/Enhanced rule above, or omit it to take the default.
Audit
```
server.cfg
```
against rules/server-cfg.md before deploying.
Restate the build number, its EOL value, and the source URL in the answer.

获取对应平台（
```
linux
```
或
```
win32
```
）的生命周期 JSON，并读取
```
recommended
```
、
```
latest
```
、
```
support_policy
```
、
```
support_policy_eol
```
。
将用户当前的 build 与
```
recommended
```
进行比较，并与其自身的
```
support_policy_eol
```
条目进行比较。
如果当前 build 早于 35245，标记 2026 年 10 月 15 日的兼容性截止日期。
根据上述 Legacy/Enhanced 规则设置
```
sv_enforceGameBuild
```
，或者省略它以采用默认值。
部署前，根据 rules/server-cfg.md 审计
```
server.cfg
```
。
在回答中重述 build 编号、其 EOL 值以及来源 URL。

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.

返回所选 build 编号、其 EOL 时间戳以及读取所用的 API URL。以可运行的

cfg

块输出

server.cfg

配置行，并保持

ensure

顺序不变。绝不能虚构 build 编号、convar 或 txAdmin 菜单路径。

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/

rules/artifacts.md — changelogs API、recommended 与 latest、滚动 EOL、build 选择。
rules/compatibility-window.md — 2026 年 10 月 15 日截止日期、升级路径、弃用项。
rules/server-cfg.md — server.cfg 基础配置、gamebuild、安全 convar。
rules/txadmin.md — txAdmin 在构建产物更新中的作用及版本配对。

上游文档：https://docs.fivem.net/docs/server-manual/setting-up-a-server/