Documentation
Quasar Appearance brings a complete clothing experience to FiveM with clothing stores, barber shops, tattoo parlors and plastic surgery. It ships with an automatic catalog, outfit management, job clothing rooms, addon clothing support and full compatibility with illenium-appearance exports. Compatible with ESX, QBCore and QBox.
Before installing Quasar Appearance, make sure your server meets the minimum requirements. The resource requires OneSync, a working MySQL database, and both ox_lib and oxmysql installed and running.
If you're using a modern ESX, QBCore, or QBox server, these dependencies are usually already installed.
Requirement | Status | Download |
|---|---|---|
| Required |
| Required |
| Required | Included in the download |
| Optional |
| Optional |
| Optional |
| Optional | Compatibility only |
Quasar Appearance automatically detects your framework and integrates with qs-inventory and rcore_tattoos when available. Target support requires Config.UseTarget = true, and screenshot-basic is only needed if you plan to capture catalog images for addon clothing.
After purchasing Quasar Appearance, the resource is automatically linked to your CFX Portal account.
Sign in to the CFX Portal using the same account used during checkout, then open Granted Assets and locate Appearance in your asset library. Download the latest version and extract the archive.
After extracting the download, you should have the following folders:
qs-appearance
greenscreen-map
[sql]Folder | Description |
|---|---|
| Main resource (required). |
| Green screen map used to capture catalog images. |
|
|
Never rename the resource folder. It must remain qs-appearance, otherwise the resource and its user interface will fail to load correctly.
Move the qs-appearance and greenscreen-map folders into your server's resources directory. Although the resources can be placed anywhere inside the folder, keeping Quasar resources organized inside their own directory is recommended.
A typical installation looks like this:
resources/
└── [quasar]/
├── qs-appearance/
└── greenscreen-map/Once the resources have been copied, open your server.cfg and ensure every required dependency starts before Quasar Appearance.
ensure oxmysql
ensure ox_lib
# Framework
ensure es_extended
# ensure qb-core
# ensure qbx_core
ensure greenscreen-map
ensure qs-appearanceThe loading order matters. Always start your framework, oxmysql, ox_lib and greenscreen-map before starting qs-appearance.
Quasar Appearance stores all player skins, outfits and job outfits inside your server's database, allowing them to persist across server restarts.
Open your preferred database manager (such as phpMyAdmin, HeidiSQL, DBeaver, or Navicat), select your server's database, and import the main.sql file included in the [sql] folder of the download.
This script creates the required tables used by Quasar Appearance:
playerskins
player_outfits
management_outfits
clothing_player_outfits
clothing_job_outfitsThe script uses CREATE TABLE IF NOT EXISTS, so running it multiple times is completely safe and will never overwrite or delete your existing data.
The [sql] folder also includes wipe.sql, which deletes all player appearance data. Only run it if you want to start from scratch.
Do not import any
.sqlfile found inside theqs-appearancefolder. The catalog tables (prefixed withqs_appearance_) are created and populated automatically on the first startup thanks toConfig.CatalogAutoSeed. No manual SQL is needed for them.
If the tables are created successfully, Quasar Appearance will automatically detect and load them the next time the resource starts.
After completing the installation, restart your FiveM server.
If everything has been configured correctly, the server console will display messages similar to the following:
[script:qs-appearance] [qs-appearance] Schema up-to-date (version=1)
[script:qs-appearance] [qs-appearance] Catalog seed up-to-date (version=281766c012d3)During the first startup, the catalog seed may take a few seconds to finish, since all qs_appearance_ tables are being created and populated automatically. This only happens once — on later restarts you will simply see the up-to-date messages shown above.
If the console shows Config.Framework = 'none', your framework is not started before qs-appearance or has been renamed. Check the loading order in your server.cfg.
Finally, join your server with an administrator account and execute the following command:
/appearanceIf the Appearance interface opens successfully and the clothing catalog is populated, Quasar Appearance has been installed correctly and your server is ready to use.