Updating

An update replaces the script and keeps everything you set up. What you configured lives in two places the update never needs to touch: your config.lua and the saved/ folder. Your photos are in a separate resource.

What to keep

Keep	Why
zaiders_appearance/shared/config.lua	Your options. A new version's options work even if your file doesn't have them: they take their defaults, and the console names them on start.
zaiders_appearance/saved/	Everything you saved in the admin panel: shops, prices, stock, theme, peds, the photo framing. Also scan/ (what each photo's garment files had inside) and hairswatch/ (the swatches of the packs' hairs).
zaiders_photos/ (the whole folder)	Your catalog photos. Don't replace it.
Your edited language files, if any	An update brings new language files. Put your changed lines back afterwards.

zaiders_studio/ is the other way round: it holds no data, so replace it whole.

Steps

1. Download the new version

   From portal.cfx.re → Granted assets, with the account that owns it.

2. Make a backup

   Copy your current zaiders_appearance folder somewhere safe, or at least shared/config.lua and saved/.

3. Replace the script

   Stop the server, or at least the resource. Replace the zaiders_appearance folder with the new one, then put back your shared/config.lua and your saved/ folder.

4. Leave zaiders_photos alone

   Don't replace that folder: it holds your photos. The package's zaiders_photos has no photo list, so copying it over wouldn't erase the list. Copy over it only the package's fxmanifest.lua, writer.lua and upgrade.js.

5. Replace zaiders_studio whole

   Delete the old zaiders_studio folder and copy the package's. It holds no data, and it still doesn't go in server.cfg.

6. Run the SQL file if it changed

   Appearancez.sql only creates tables that don't exist yet, so running it again is safe. The resource also creates missing tables on its own.

7. Start and read the console

   The console lists the options your config.lua doesn't have yet and the values it fixed. Copy the new options from the new version's config.lua if you want to change them. An option a version removed (such as Config.Barber.handsOn or Config.Barber.colorCard.matchClothes) is named once, no longer exists in this version: it is ignored: delete that line. New features that need a decision come off: character height arrives with Config.Height.enabled = false. See How the config is checked.

From 1.x to 2.0

Version 2.0 gives everything an English name. Nothing is lost: the resources move their own files the first time they start.

1. Rename zaiders_fotos to zaiders_photos

   Then copy into it the package's fxmanifest.lua, writer.lua and upgrade.js. On start it moves its folders to the new names (fotos/ → photos/, datos/ → data/, tatuajes/ → tattoos/).

2. Replace zaiders_appearance, keeping your config.lua and its datos/ folder

   On start it moves datos/ to saved/ with English file names (tiendas.json → shops.json, tatuajes.json → tattoos.json…). The shops, tattoo prices and ped settings saved with Spanish names are read as before.

3. Replace zaiders_estudio with zaiders_studio

   Delete the old folder and copy the new one. It doesn't go in server.cfg.

4. Change one line of server.cfg

   ensure zaiders_fotos becomes ensure zaiders_photos.

A config.lua of 1.x keeps working as it is. Its Config.Photos.resource = 'zaiders_fotos' becomes zaiders_photos by itself while there's no zaiders_fotos (the console says that resource is now called zaiders_photos, so zaiders_photos is used); change that line when you like. Config.PedByName = 'todos' / 'nadie' is read as 'everyone' / 'nobody', and the ped categories with their Spanish names as the English ones. The console commands now have English names: zappearance_clean_photos, zappearance_tattoo_images, zappearance_changes and zappearance_migrate.

Changing clothing packs

Adding, removing or repacking a clothing pack isn't an update of the script, but it changes the garment numbers:

• Restart the whole server, not a single pack. FiveM numbers the clothing in start order, so restarting one pack while the server runs gives the players who join afterwards different garment numbers.
• Join once with an admin afterwards. The admin's game tells the server which garment is behind each number again.
• A repacked pack keeps its photos: each photo follows its garment by what its files have inside. Clothing packs → Changes lists the garments whose model or texture changed, to take only those again. See Catalog photos.

Related

• Escrow & editable files
• Installation
• Troubleshooting & FAQ