[{"data":1,"prerenderedAt":29},["ShallowReactive",2],{"doc-en-update-fivem-artifacts":3},{"path":4,"slug":5,"title":6,"description":7,"category":8,"subcategory":9,"icon":10,"date":11,"author":12,"order":13,"image":14,"tags":15,"keywords":20,"docGroup":26,"docGroupIcon":26,"link_fr":27,"bodyHtml":28},"\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fupdate-fivem-artifacts","update-fivem-artifacts","How to update your FiveM server's artifacts","Update your FiveM server's artifacts (builds) at Winheberg, choosing the right version, update procedure, and rollback in case of issues.","jeux","fivem","tabler:file-text","2026-07-24","Winheberg",17,"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fupdate-fivem-artifacts.webp",[9,16,17,18,19],"artifacts","fxserver","update","jgscripts",[21,22,23,24,25],"update fivem artifacts","fxserver build","artifacts.jgscripts","stable fivem version","fivem server winheberg","","\u002Fdocs\u002Ffivem\u002Fmise-a-jour-artifacts-fivem","\u003Ch2>Context\u003C\u002Fh2>\n\u003Cp>You manage a \u003Cstrong>FiveM server\u003C\u002Fstrong> at Winheberg and want to \u003Cstrong>update the artifacts\u003C\u002Fstrong> (also called &quot;builds&quot; or &quot;FXServer&quot;)? Whether it&#39;s to get the latest features, fix a bug, or meet the requirements of a new resource, updating artifacts takes just a few clicks from your Winheberg gaming panel.\u003C\u002Fp>\n\u003Cp>This guide explains how to change your artifact version cleanly and how to \u003Cstrong>pick the right version\u003C\u002Fstrong> to avoid nasty surprises.\u003C\u002Fp>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cp>Before you start, make sure you have the following.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>An active \u003Cstrong>FiveM server\u003C\u002Fstrong> on your Winheberg gaming panel\u003C\u002Fli>\n\u003Cli>A \u003Cstrong>recent backup\u003C\u002Fstrong> of your server (recommended in case something goes wrong after the update)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"markdown-alert markdown-alert-warning\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M10.29 3.86L1.82 18a2 2 0 0 0 1.71 3h16.94a2 2 0 0 0 1.71-3L13.71 3.86a2 2 0 0 0-3.42 0z\"\u002F>\u003Cline x1=\"12\" y1=\"9\" x2=\"12\" y2=\"13\"\u002F>\u003Cline x1=\"12\" y1=\"17\" x2=\"12.01\" y2=\"17\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>An artifact update \u003Cstrong>automatically stops and then restarts your server\u003C\u002Fstrong>. Warn your players if your server is active, and avoid updating during a busy session.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>Choosing the right artifact version\u003C\u002Fh2>\n\u003Cp>Before clicking any download button, \u003Cstrong>take a few minutes to pick the right version\u003C\u002Fstrong>. Not all versions are equal, and some contain known bugs that can break your server.\u003C\u002Fp>\n\u003Ch3>❌ Don&#39;t just grab the latest version by default\u003C\u002Fh3>\n\u003Cp>This is the classic mistake, seeing the most recent version at the top of the list and clicking it without thinking. \u003Cstrong>Bad idea\u003C\u002Fstrong>. The very latest versions are often unstable and can introduce regressions or bugs that haven&#39;t hit other servers yet.\u003C\u002Fp>\n\u003Ch3>✅ Check each version&#39;s status on jgscripts\u003C\u002Fh3>\n\u003Cp>The site \u003Ca href=\"https:\u002F\u002Fartifacts.jgscripts.com\u002F\">artifacts.jgscripts.com\u003C\u002Fa> is an \u003Cstrong>essential resource\u003C\u002Fstrong> for FiveM server admins. For \u003Cstrong>each artifact version\u003C\u002Fstrong>, it tracks the following.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Known bugs\u003C\u002Fstrong> on that version\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Features added\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Whether the version is marked as \u003Cstrong>stable\u003C\u002Fstrong> or \u003Cstrong>problematic\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Community feedback\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"markdown-alert markdown-alert-tip\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cpath d=\"M12 16v-4\"\u002F>\u003Cpath d=\"M12 8h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>Our recommendation, before every update, go to \u003Ca href=\"https:\u002F\u002Fartifacts.jgscripts.com\u002F\">artifacts.jgscripts.com\u003C\u002Fa>, find a recent version \u003Cstrong>with no major reported bug\u003C\u002Fstrong>, and use that one. It&#39;s much safer than blindly grabbing the latest.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch3>Why not the official &quot;RECOMMENDED&quot; version?\u003C\u002Fh3>\n\u003Cp>FiveM highlights a \u003Cstrong>RECOMMENDED\u003C\u002Fstrong> version (in green in the panel). It&#39;s a good baseline, but it&#39;s often several weeks behind on new features. If you need a recent feature, you&#39;ll have to go beyond it, and that&#39;s where jgscripts becomes useful to validate your choice.\u003C\u002Fp>\n\u003Ch2>1. Access the Artifacts section\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Log in to your \u003Cstrong>Winheberg gaming panel\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Select your \u003Cstrong>FiveM server\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>In the left sidebar menu, find the \u003Cstrong>CONFIGURATION\u003C\u002Fstrong> section\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Artifacts\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fupdate-fivem-artifacts-1779548449777-b7348cc328ef8c20b2680b4f.webp\" alt=\"Winheberg panel sidebar menu with the Artifacts button highlighted in the Configuration section\" width=\"300\" \u002F>\n\n\u003Ch2>2. Choose and download the new version\u003C\u002Fh2>\n\u003Cp>The \u003Cstrong>Artifacts\u003C\u002Fstrong> page shows the list of all available versions, from the most recent (at the top) to the oldest (at the bottom). The currently installed version is usually marked with a green \u003Cstrong>R\u003C\u002Fstrong> (RECOMMENDED) or another visual indicator.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Find the version you want to install (after checking \u003Ca href=\"https:\u002F\u002Fartifacts.jgscripts.com\u002F\">artifacts.jgscripts.com\u003C\u002Fa>)\u003C\u002Fli>\n\u003Cli>Click the \u003Cstrong>download icon\u003C\u002Fstrong> next to the version number\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fupdate-fivem-artifacts-1779548462891-11b626adb19394fa3f997894.webp\" alt=\"Winheberg panel Artifacts page with the Artifacts menu and a version download button highlighted\" width=\"800\" \u002F>\n\n\u003Ch2>3. Wait for the installation to finish\u003C\u002Fh2>\n\u003Cp>Once you&#39;ve clicked the download button, \u003Cstrong>the panel automatically takes over\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Your FiveM server is \u003Cstrong>stopped\u003C\u002Fstrong> automatically\u003C\u002Fli>\n\u003Cli>The new artifact version is \u003Cstrong>downloaded and installed\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>An \u003Cstrong>installation message\u003C\u002Fstrong> appears in the panel console to track progress\u003C\u002Fli>\n\u003Cli>Your server is \u003Cstrong>restarted\u003C\u002Fstrong> automatically with the new version\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>No need to manually restart your server. The panel handles everything from start to finish, you just need to wait for the installation to complete.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>4. Check the update\u003C\u002Fh2>\n\u003Cp>Once the server has restarted, check that everything is working correctly.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Check the panel&#39;s \u003Cstrong>console\u003C\u002Fstrong> for any startup errors\u003C\u002Fli>\n\u003Cli>Connect to the server in-game and \u003Cstrong>test the main features\u003C\u002Fstrong> of your server (map loading, database connection, essential scripts)\u003C\u002Fli>\n\u003Cli>Check that all your resources load correctly (\u003Ccode>txAdmin\u003C\u002Fcode> or FiveM logs)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If everything works, your server is now running on the new artifact version 🎉\u003C\u002Fp>\n\u003Ch2>What if the new version breaks your server?\u003C\u002Fh2>\n\u003Cp>This can happen, especially if the version has a bug that hadn&#39;t been reported on jgscripts at the time of your update. Don&#39;t panic, \u003Cstrong>you can roll back\u003C\u002Fstrong> easily.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Go back to the panel&#39;s \u003Cstrong>Artifacts\u003C\u002Fstrong> section\u003C\u002Fli>\n\u003Cli>Find the \u003Cstrong>previous version\u003C\u002Fstrong> you were using before the update\u003C\u002Fli>\n\u003Cli>Click its download icon\u003C\u002Fli>\n\u003Cli>The panel will automatically switch back to that version\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cdiv class=\"markdown-alert markdown-alert-tip\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cpath d=\"M12 16v-4\"\u002F>\u003Cpath d=\"M12 8h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>Before every update, \u003Cstrong>note down the number of the currently installed version\u003C\u002Fstrong> somewhere. That way, if something goes wrong, you know exactly which version to roll back to.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>If you run into trouble\u003C\u002Fh2>\n\u003Cp>Here are the most common errors after an artifact update.\u003C\u002Fp>\n\u003Ch3>❌ The server doesn&#39;t restart after installation\u003C\u002Fh3>\n\u003Cp>Check the panel&#39;s \u003Cstrong>console\u003C\u002Fstrong>. You&#39;ll see the exact error there. The most common causes are the following.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A server resource \u003Cstrong>incompatible\u003C\u002Fstrong> with the new artifact version\u003C\u002Fli>\n\u003Cli>A dependency (oxmysql, ESX, QBCore) that also needs updating\u003C\u002Fli>\n\u003Cli>A \u003Ccode>server.cfg\u003C\u002Fcode> syntax that&#39;s changed or outdated in this new version\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ Script errors after the update\u003C\u002Fh3>\n\u003Cp>Some FiveM native functions can change between versions. If your scripts stop working, check \u003Cstrong>artifacts.jgscripts.com\u003C\u002Fstrong> to see if the new version introduced major changes (deprecations, removals). You may need to update your resources.\u003C\u002Fp>\n\u003Ch3>❌ The download stays stuck\u003C\u002Fh3>\n\u003Cp>If the download isn&#39;t progressing anymore, wait a few minutes. If nothing happens after 10 minutes, \u003Cstrong>reload the panel page\u003C\u002Fstrong> and check your server&#39;s status. If the issue persists, contact our support.\u003C\u002Fp>\n\u003Ch3>❌ My players get connection errors\u003C\u002Fh3>\n\u003Cp>An artifact update can create a \u003Cstrong>version mismatch\u003C\u002Fstrong> between your server and players&#39; FiveM clients. Ask them to \u003Cstrong>update their FiveM client\u003C\u002Fstrong> (client-side FXServer) and relaunch their game.\u003C\u002Fp>\n\u003Ch2>Best practices\u003C\u002Fh2>\n\u003Cp>A few recommendations for managing your artifact updates smoothly.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Always check \u003Ca href=\"https:\u002F\u002Fartifacts.jgscripts.com\u002F\">artifacts.jgscripts.com\u003C\u002Fa>\u003C\u002Fstrong> before updating to avoid buggy versions\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Don&#39;t update during an active gaming session\u003C\u002Fstrong>, do it during off-peak hours\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Note the current version\u003C\u002Fstrong> before updating, so you can roll back easily\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Make a backup\u003C\u002Fstrong> of your server (files and database) before a major update\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Test your resources\u003C\u002Fstrong> after the update, especially frameworks (ESX, QBCore, vRP) that can be affected\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Need help?\u003C\u002Fh2>\n\u003Cp>If you run into an issue after an artifact update, or if you can&#39;t roll back to a previous version, our team is here. Open a ticket in the \u003Cstrong>Technical\u003C\u002Fstrong> department from your client area, fill in the \u003Cstrong>Related product\u003C\u002Fstrong> field with the server in question, and specify the current version, the target version, and any error messages from the console.\u003C\u002Fp>\n\u003Cp>Your FiveM artifacts are now up to date, enjoy the latest features 🚀\u003C\u002Fp>\n",1788993141173]