Troubleshooting
Fixes for common uz_MugShot problems, from missing photos to black backgrounds and weather issues.
Set Config.Debug = true first. The client then prints why a capture waited or was skipped, and the server keeps the unkeyed screenshot next to each photo.
The resource stops right after starting
The folder is not named uz_MugShot. The console shows The resource folder must be named "uz_MugShot". Rename the folder (GitHub's Download ZIP unpacks as uz_MugShot-main) and restart the server.
Cannot find module 'pngjs'
The yarn install did not run. Make sure yarn is started before uz_MugShot in server.cfg. If a previous install was interrupted, delete .yarn.installed in the resource folder and restart.
Access denied for command remugshot
The command is ACE-restricted. Add add_ace group.admin command.remugshot allow to server.cfg and make sure your identifier is in group.admin.
The photo does not update after a clothing change
- With
Config.Debug = truethe client prints the reason, for exampleskipped, player not in plain gameplay: nui_focus. A resource that keeps NUI focus or its own camera active all the time blocks every capture. Fix that resource or close its UI. - Changes made outside a menu (an outfit command, a skin applied by a script) are captured only after they have held still for
Config.FingerprintWatch.settleMs. - Tattoo-only changes are not detected because GTA has no getter for ped decorations. Use
/remugshotorForceRecapture.
No capture at all on login, barber or clothing
If no framework is found 10 seconds after start, the server console prints a no framework detected warning. Check that qbx_core, qb-core or es_extended is running, or set Config.Framework explicitly. A framework that starts after uz_MugShot is picked up automatically.
GetPhotoDataURI returns nil
The ped is an NPC, the character has no photo yet, or the client is sending too many requests and hit Config.RequestLimit. Show your own placeholder when the result is nil.
Solid black background instead of transparent
The chroma wall is not read as magenta. The most common cause is a timecycle modifier from a graphics mod or another script darkening the whole frame.
Thin magenta outline, or neon pink clothing turning see-through
Both come from Config.ChromaProcessing. Raising feather cleans edges but starts eating colours close to magenta (neon pink sits inside the default edge band); lowering it does the reverse. Hair strands one or two pixels wide are left as they are on purpose.
Weather or time looks wrong right after a photo
The studio holds noon and clear weather during the shot. Renewed-Weathersync, qb-weathersync and qbx_weathersync are paused for the shot and take over again afterwards, and the previous clock and weather are put back. Without one of these weathersyncs, the weather keeps cycling as normal. If you use a different weathersync, report it on Discord.