Update a resource
Replace an installed FiveM resource with a newer version from your RPCrate account without losing your config or data.
Updates are delivered through your account: when a product's file changes, the next download from My account is the new version. The version number, where the creator provides one, is shown on the product page.
Update without losing your settings
Back up
Copy the installed resource folder somewhere outside resources, and export your database.
Compare before you replace
Download the new version and read the creator's changelog and upgrade instructions, including any required intermediate versions. Compare it with your copy, at least config.lua, any locales and any .sql files. A tool such as WinMerge or VS Code's compare view shows the differences.
Try the complete update on a separate test server and a copy of the database first. Check the required framework and dependency versions; changing an inventory or game edition is a migration, not just a file replacement.
Replace the files and merge the config
Schedule a maintenance window and stop the affected resource, or the server if the update changes the core, inventory or shared definitions. Replace the resource folder with the new one, then copy your own settings back into the new config.lua. Do not copy the old config file over the new one: new versions often add options, and a missing option can stop the script.
Apply database changes
Use the migration supplied for your installed version and follow its order. An update may legitimately create new tables or insert rows; the first SQL keyword does not tell you whether a file is for a fresh install.
Read every statement. DROP TABLE, TRUNCATE, DELETE, REPLACE and even ALTER TABLE operations such as dropping a column can remove data. Do not rerun a fresh-install dump or select statements by keyword. If there are no clear update instructions, ask the creator or support before applying SQL. See Database precautions.
Restart and test
Restart the server, watch the server and F8 consoles, and test the feature in game. Check existing items, jobs and saved data as well as new features; reconnect to confirm persistence.
If you need to roll back
Stop the affected resource and keep a copy of the failed version and its logs. Restore the previous files and config. If SQL or a dependency changed, restoring files alone may not be enough: use the creator's supported reverse migration or the tested database backup, together with matching dependency versions.
A database restore replaces data written since the backup. Keep players offline, identify which database or tables need restoring, and preserve the current database before doing it. Do not overwrite unrelated player data to fix one resource. Ask support if the rollback scope is unclear, then see Startup errors.
Downloads and your account
Where to find the files you bought or claimed on RPCrate, how to sign in without a password, and what to do when a download does not work.
Install a server pack
Set up an RPCrate FiveM server pack on a separate server and database, configure your own credentials, and test it before launch.