Updates & Backups

Updates are safest when you treat your config as your own work and the downloaded resource as the new base.

Before Updating

Back up the old resource folder before replacing anything.

Example:

sky_ambulancejob/
sky_ambulancejob_backup_2026-05-30/

Also back up your database before larger updates, especially if the changelog mentions SQL changes.

Do Not Blindly Overwrite Configs

New updates may add new config keys. If you overwrite the new config with your old config, the new version may miss required values.

Recommended update flow:

1. Download the new resource.
2. Keep a backup of your old resource.
3. Compare your old config/ files with the new config/ files.
4. Copy your custom values into the new config.
5. Import new SQL changes if the changelog asks for it.
6. Restart the server and check the console.

Files Usually Safe To Edit

These files are normally intended for configuration:

config/config.lua
config/functions.lua
config/sv_functions.lua
config/webhooks.lua
config/locales/*.lua

Some resources include additional config files. Follow the product-specific documentation for those.

Files You Should Avoid Editing

Avoid editing internal source files unless support specifically asks you to.

source/client/*.lua
source/server/*.lua
source/html/*

Changing internal files can make updates harder and may break escrowed code.

After Updating

Check these things before opening a support ticket:

• The resource starts without console errors.
• The SQL import or migration ran successfully.
• Your framework, inventory, target, and SQL settings are still correct.
• Old conflicting resources are still stopped.
• Your server artifacts are reasonably up to date.

Keep Notes

When you change something, write it down. A simple note like this saves a lot of debugging time:

Changed ambulance garage vehicles in config.lua
Added new medical items to ox_inventory
Updated sky_base and sky_ambulancejob
Imported ambulance import.sql