Read what changed firstLink to this section
Every release has a changelog on the script’s docs page and on the changelog. A breaking change is always listed first, with the old and the new value, so you know what to edit.
Versions follow semver, and the number tells you how careful to be:
| Change | Example | What it means |
|---|---|---|
| Major | v1.4.2 to v2.0.0 | Something breaks. Read the breaking change before you update. |
| Minor | v1.4.2 to v1.5.0 | New features. Existing setups keep working. |
| Patch | v1.4.2 to v1.4.3 | A fix. Safe to drop in. |
UpdateLink to this section
Step 1: Back up your settings
On FiveM, copy the config file and any locale files you changed somewhere outside the resource folder. On Minecraft, copy the plugin’s own folder inside
plugins.Step 2: Get the new version
Free releases: download the new version from its docs page on this site. FiveM Pro scripts: download the asset again from the Cfx.re portal.
Step 3: Swap the files
On FiveM, delete the old resource folder and put the new one in its place, with the same name; copying over the top can leave removed files behind. On Minecraft, take the old jar out of
pluginsbefore adding the new one, so two versions never load together, and leave the plugin’s settings folder where it is.Step 4: Put your settings back
Compare your backup with the new config rather than pasting over it. New versions can add keys, and a breaking change can rename one.
Step 5: Run any new SQL, then restart
If the release notes mention a database change, run the SQL that came with it before you restart. On Minecraft, stop and start the server rather than using
/reload.
What gets updatedLink to this section
Pro scripts are maintained for as long as they are sold. Free scripts come as they are: they are documented and tested like everything else, but there is no promise of future updates.