Troubleshooting

The things that actually go wrong, and where to look.

A change to a file did nothing

A plain restart does not re-read fxmanifest.lua. If you added a file — a new locale, say — type refresh in the server console first, then restart mic_chameleon. Changes to config.lua and the locales only need the restart.

“You do not have permission to use this command”

With the shipped config, the menu opens for players on the permission list and for the mechanic and police jobs, nobody else. Either:

add the player with /chameleongive and their server ID, or
add their job to Config.AuthorizedJobs, or
set Config.Permissions = false to let everybody paint.

The same message from /chameleongive itself means you are not an admin as the bridge sees it: the admin or superadmin group on ESX, admin or god on QBCore.

“Could not get player steam identifier”

The permission list stores Steam IDs. The player has to have Steam running when they connect, or they cannot be added. Give them a job from Config.AuthorizedJobs instead, or switch permissions off.

Nothing happens when I type /chameleon

You have to be sitting in a vehicle; otherwise you get “You are not in a vehicle”. If you are, and nothing at all appears, check the console for [Camaleon] lines — no framework found means the resource started before ESX, QBCore or QBox. Put ensure mic_chameleon below your framework in server.cfg — on QBox, below qbx_core.

The messages are in Spanish

The shipped config.lua has Config.Locale = "es". Set it to "en" or another of the nine codes in locales/. The marker prompt and the menu title are not in the locales: change them in config.lua and html/ui.html.

The paint looks like a flat colour

The colours are shifting paints from the newer vehicle colour set, and twenty of them (223 to 242) come from this resource’s data/ and stream/ folders.

Make sure both folders are still in the resource and have not been renamed.
Data files are read when a player connects. After installing, players already on the server need to reconnect.
Your server needs a game build recent enough to have chameleon paints. If you force an old one with sv_enforceGameBuild, raise it.

Reset says “No original color found for this vehicle”

The original colour is remembered the first time a car is painted, keyed by its model and plate. It cannot be reset if:

the car was painted before the resource was installed, or by another script;
its plate has changed since;
vehicle_original_colors.json was deleted.

In those cases, paint it back at your usual mechanic.

The paint is gone after a restart

This resource paints the car in front of you; it does not write to your garage. Whether the colour survives being stored and taken out again is up to your garage script saving vehicle properties. What this resource keeps across restarts is the original colour, so that Reset still works.

Using a paint item does nothing

In order:

Is Config.UseItems on? The console should say it registered 82 items on start.
Is the item defined in your inventory under exactly the same name — chameleon_paint_200, not chameleon_200? See the files in items/.
Are you sitting in a vehicle? The item is only consumed when you are.
Does your inventory honour the framework’s usable items? This resource registers them through ESX or QBCore, not through the inventory directly.

If you turned on Config.ItemsRequirePermission and the server console shows an error when an item is used, turn it back off and send us the error on Discord.

The items have no pictures

No images ship. Add PNGs named after the items (for example chameleon_paint_200.png) to your inventory’s image folder.