Common Errors

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.

Skin Migration Support

If you are already using illenium-appearance, no migration is necessary — qs-appearance is automatically compatible with it and will take over without any extra 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.

How to Use the Migration Command

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:

/migrateskins

This 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.

How to Use the Outfit Migration Command

The /migrateoutfits command is only compatible with servers that previously used illenium-appearance. If you were using other systems, this command will not apply.

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:

/migrateoutfits

This 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.

Greenscreen Map Activation (greenscreen-map)

Do not keep greenscreen-map running if you're not using it for screenshots. It may consume unnecessary resources and serves no purpose outside of the /save-images process. It should only be active during the image capturing process.

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.

How to use it?

You must manually start the resource before using the /save-images command, with:

start greenscreen-map

Once you’re done capturing the images, you must manually stop or remove the resource with:

stop greenscreen-map
Support With Other Multichar Systems

This 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
end

This makes it straightforward to extract and reuse a ped’s appearance in any part of your system.

PreviousConfigurationNextCommands & Exports