Respond to an artifact support warning

EOS and EOL warnings concern the server artifact, not a player’s need to reinstall GTA. The pinned Cfx.re support policy  distinguishes a gray end-of-support warning, which still allows joining, from a red end-of-life warning that can prevent connection.

Published timeline

Recommended artifacts retain support until six weeks after the next release in that line. Latest/optional artifacts retain support until two weeks after the next release in their line. The clock is not simply “two weeks since I installed it.” If an optional build is superseded on March10, its example14-day support window ends March24.

The manual additionally says unsupported artifacts older than three months are not joinable through the browser. Unsupported binaries may still run; process uptime therefore does not prove current support or joinability. Check the actual release track and official warning rather than inferring eligibility from a made-up date.

Server-owner workflow

Record the current artifact, track and last known-good configuration. Download an appropriate recommended release from the official server download page . Back up server data, resources, database and configuration, stop the test instance, and replace the binary installation without overwriting server data. Test startup, admission, core resources, persistence, voice and a client join before production cutover.

A framework dependency or protected asset may impose additional artifact requirements. Verify those explicitly; do not suppress EOS/EOL messages with an unrelated ConVar. Use artifact updates and backups for the operational procedure.

Player workflow

For a gray warning, report it to the server owner; there is normally no client repair to perform. For a red warning with a failed join, the owner must update the server. Send the exact warning and server identification privately where necessary. Deleting client cache or changing firewall rules cannot update someone else’s server binaries.

Reporting a regression

Reproduce on a supported artifact with a minimal resource set and record expected versus actual behavior, old/new artifact numbers, track, reproduction steps and redacted logs. Report a platform regression through the official bug-report channel . Community-resource failures should first go to their maintainers. A rollback is an operational recovery step, not a permanent exception from support policy.