Coming from another clothing menu
Players keep their characters. ZAIDERS Appearance reads the looks your previous menu saved, in the same tables and formats, so nobody has to make their character again. Outfits and job uniforms come over with one console command, the tattoos kept inside the saved looks come by themselves (or with one command), and the old menu's tables are never changed.
What happens to each thing
| What | What to do |
|---|---|
Saved looks (playerskins, users.skin) | Nothing. It reads illenium-appearance's, fivem-appearance's, qb-clothing's and esx_skin's formats as they are. |
Players' outfits (illenium-appearance or qb-clothing, player_outfits) | One console command (below). |
Job and gang uniforms (illenium-appearance, management_outfits) | One console command (below). |
| Tattoos kept inside the saved looks (illenium-appearance, fivem-appearance) | Nothing, or one console command (below). Each character's come over by themselves the first time they enter. On ESX with esx_skin, use the command. |
| Tattoos bought in another tattoo resource (in its own table) | They aren't brought over. If you keep using that resource for tattoos, ZAIDERS Appearance's tattoo shop turns itself off. See Tattoo shop. |
Outfits already in ps_outfits / ps_job_outfits | Nothing. They show up in the wardrobe as they are. |
| Scripts that call the old menu (multicharacter, housing, jobs) | Nothing. While the old menu isn't running, this one answers its exports and events. See Frameworks & compatibility. |
Moving over
Back up your database
Nothing is deleted, but a backup before any change to a live server is always worth it.
Install ZAIDERS Appearance and stop the old menu
Follow Installation. Remove the old menu's
ensure, and leave its tables where they are.See what can be brought over
In the server console:
textzappearance_migrateIt only reads. It says how many outfits, uniforms and tattoos it found, how many are new, and the command to bring each one. When the server starts and finds something to bring, the console also says so.
Bring the outfits
textzappearance_migrate outfits confirmIt copies the players' outfits from illenium-appearance or qb-clothing (
player_outfits) intops_outfits.Bring the job uniforms
textzappearance_migrate uniforms confirmIt copies illenium-appearance's job and gang uniforms (
management_outfits) intops_job_outfits, with the grade each one is seen from. If a uniform had no minimum grade, every grade sees it, and the console says how many. Set the grade from the wardrobe. See Wardrobe & outfits.Bring the tattoos
textzappearance_migrate tattoos confirmIt saves in
zaiders_tattoosthe tattoos illenium-appearance or fivem-appearance kept inside each saved look, for the characters with none saved here yet: only the designs this shop sells, with their darkness as layers. Without the command they come anyway, each character's the first time they enter (Config.Tattoos.importFromLooks). On ESX with esx_skin they only come with the command, because any player can writeusers.skinthroughesx_skin:save: run it right after installing.
Safe to run again
The migration never changes or deletes the other menu's tables, and never brings the same thing twice. If it stops halfway (for example, the database went down), run the same command again and it picks up the rest.
Faster wardrobes
If your ps_outfits or ps_job_outfits tables came from another resource without indexes, these make the wardrobe faster. Run each one once; skip one that says the index already exists:
ALTER TABLE `ps_outfits` ADD INDEX `identifier` (`identifier`(64));
ALTER TABLE `ps_job_outfits` ADD INDEX `job` (`job`(50));