Getting Started
Updating
Replace a script with a newer version cleanly, without leftover files from the old one.
Never paste new files over the old folder. Whatever the update removed or renamed stays behind, and that leftover is what usually breaks.
If the notes mention SQL or new config keys, deal with those before you start the server.
Before you touch anything
- Read what changed in the version you're installing. Updates are usually announced in the Discord. Paid assets also get a short summary on the portal.
- Copy the current resource out of
resources. Back up the database too when the update has SQL. - Hold on to that backup until the new version works in game.
Worried you missed a changelog? You don't have to watch for them. Once an update is posted, the version checker warns you in the console on startup if your copy is out of date.
Swap the folder
- Download the new zip from where you bought or found it (Tebex or GitHub) and pull the resource folder out of it.
- Stop the server.
- Delete the old folder, then put the new one in
resourcesunder the same name.
Search resources once to be sure only one copy exists, and that it isn't nested inside a folder of the same name.
Bring your changes over
| What you changed | What to do |
|---|---|
| Config values | Copy them onto the new config. Don't overwrite the new file, since updates add keys your old one lacks |
Locale or resource/open/ edits | Re-apply them on the new files |
| Database | Run the SQL from the notes if there is any |
Check it
Start the server, read the console, and try the script in game. Delete the backup after that.