Documentation
This section lists the most frequent issues users may encounter during installation or setup, along with their causes and quick solutions. Review each point carefully before opening a support ticket — most problems can be fixed easily by following these steps.
If your server previously used clothing systems like qb-clothing, esx_skin, or fivem-appearance, you can easily migrate existing player skins to work with qs-appearance using the built-in /migrateskins command. This ensures your player base retains their character look without needing to recreate it from scratch.
This command should be executed only once after switching systems. After migration, make sure to remove or disable the old clothing scripts to prevent data conflicts. To convert existing skin data from older systems, simply use the following command in-game:
/migrateskinsThis will scan your player database and convert all stored appearance data from the following supported systems: qb-clothing, esx_skin, fivem-appearance. All migrated skins will then be stored in the format used by qs-appearance, allowing a seamless transition for your players.
If you are switching from illenium-appearance and previously used its outfit system (saved presets), you can transfer all outfits seamlessly using the built-in /migrateoutfits command.
This migration is optional and intended for those who wish to retain previously saved outfits under the new qs-appearance system.
To migrate, simply execute the following command in-game:
/migrateoutfitsThis will detect and convert all outfits saved under the illenium-appearance format into the qs-appearance compatible structure. Once complete, players will be able to access their old outfits from the wardrobe menu as usual.
The greenscreen-map resource is intended exclusively for use when capturing images of new clothing sets using the /save-images command. If you have already made all the images and are not going to use the command anymore, stop it, otherwise there will be visual problems in the peds.
You must manually start the resource before using the /save-images command, with:
start greenscreen-mapOnce you’re done capturing the images, you must manually stop or remove the resource with:
stop greenscreen-mapThis script fully overrides and handles all core events from illenium-appearance, making it automatically compatible with any multicharacter system that uses illenium-appearance as its configuration—such as qs-multicharacter, qb-multicharacter, or similar—without requiring manual integration. It detects and adapts seamlessly to these systems out of the box.
Additionally, you can easily retrieve a player’s appearance using a simple function like this:
function Appearance:GetAppearanceFromPed(ped)
if not DoesEntityExist(ped) then
Error('Ped does not exist', ped)
return nil
end
local appearance = exports['qs-appearance']:getPedAppearance(ped)
if not appearance then
Error('Failed to get appearance from ped', ped)
return nil
end
Debug('Got appearance from ped', appearance)
return appearance
endThis makes it straightforward to extract and reuse a ped’s appearance in any part of your system.