Version and updating
Version declared by the ox_target archive, backup procedure, comparing configuration files and carrying your settings over during an update.
Goal: install a new archive without losing your settings.
Documented version
This site documents the archive whose fxmanifest.lua declares version '1.17.2'. No version history is published here: what an update brings is announced by MrPoulpi Labs on Discord. To know the version installed on your server, open fxmanifest.lua or type resmon and find ox_target.
What belongs to you
Your settings live in four plain-text files: config.lua, config_interactions.lua, config_client.lua and config_server.lua. If you edited bridge/client.lua or bridge/server.lua to add a preset, write those changes down separately: prefer hooks, which an update does not overwrite.
Procedure
Back up the whole
ox_targetfolder (timestamped copy outsideresources/).Export your configuration: in the configurator, import your current Lua files or your JSON project, then export the JSON project. It will be your reference.
Replace the resource with the new archive, without overwriting your four configuration files yet.
Compare the newly shipped
config*.luafiles with yours (your editor’s diff tool). Look for new keys in the shipped files: they must be added to your files, otherwise the script will use its default behaviour or anilvalue.Carry your settings over into the new files, key by key, rather than copying your old files on top.
Restart (
restart ox_targetor the server) and repeat the first test: F8, server console, player target, self, vehicle, ped, object.
Common mistakes
- Copying the old
config.luaonto a new version: new keys are missing. - Forgetting
config_server.lua: your server actions disappear and options calling them are refused as an unknown action. - Updating without restarting dependent resources: their options added through exports do not come back.