Common Errors

Framework not detected#

Config.Framework = 'none'

Cause: your framework is not started before qs-appearance, or the resource has been renamed.

Solution: check the loading order in your server.cfg and make sure es_extended, qb-core or qbx_core starts first. If you renamed your framework resource, adjust the frameworks table inside config/main.lua.

The catalog appears empty#

Cause: the automatic catalog seed did not complete.

Solution:

• Make sure oxmysql is installed and started before qs-appearance.

• Verify that Config.CatalogAutoSeed = true in config/main.lua.

• Check the server console on startup — you should see the schema and catalog seed messages. If an SQL error appears there, fix it and restart.

Images are not being saved#

Cause: the FiveManage token is missing, or screenshot-basic is not running.

Solution: set your token in config/fivemanage.lua, enable Config.ImageSaver.enable = true, and make sure both screenshot-basic and greenscreen-map are started.

Remember to set Config.ImageSaver.enable = false once you finish capturing, to protect your token.

Props stuck on the ped#

Cause: hats, glasses or masks were not cleared correctly after an animation or script conflict.

Solution: run /clearstuckprops and keep Config.MaskFix = true in config/main.lua.

Target interaction not working#

Cause: target support is disabled, or the target resource is not running.

Solution: set Config.UseTarget = true and make sure ox_target or qb-target is started before qs-appearance.

Inventory not detected#

Cause: you are using an inventory other than qs-inventory, which is the only one detected automatically.

Solution: edit the files inside client/custom/inventory/*.lua to adapt the integration to your inventory.

The resource or UI fails to load#

Cause: the resource folder was renamed.

Solution: the folder must remain qs-appearance. Any other name will break the resource and its user interface.

Enabling debug mode##

If none of the above solves your issue, enable debug mode to get detailed console output:

Config.Debug = true

Set it back to false in production, as it generates a large amount of console output.