
The first thirty seconds a player spends on your server, and every wardrobe they open for the rest of their time on it. A cinematic character selector and a complete appearance engine, in one resource.
You do not install a clothing script alongside it. The engine is built in, so both halves share one ped pipeline, one database schema and one UI. Nothing to reconcile, nothing fighting over the ped, and one thing to update.
Built for QBCore servers that would rather run one resource than a multicharacter, a clothing script, a spawn selector and an apartment script that all have to agree with each other. If your current stack is working and you like it, keep it. If you have ever spent an evening working out which of four resources reset someone's outfit, this is the one that ends that.
This is the screen every player sees before they see anything else you have built. It is worth having it look like yours.
Every other multicharacter hard deletes. The player confirms, roughly ninety tables are cascaded, and the character is gone along with their house, their vehicles and their inventory. Restoring it means rebuilding it by hand, badly.
This one flags the character instead. Nothing else is touched, so a restore brings the character back whole rather than approximately. A retention window you set (30 days by default) runs before anything is destroyed for real, and the player is told the exact number of days on a confirmation that also makes them type the character's name.
In practice: the "I deleted the wrong one" ticket stops being a rebuild and becomes two clicks in the admin panel.
/mgthumbs new only shoots what you have added since.Players shop by looking at clothes instead of scrolling through numbers, which is the whole difference between a wardrobe someone enjoys and one they close.
Restrict any garment, prop or hairstyle to a job (optionally at or above a rank), a gang, a permission, a specific character, or nobody at all. Rules are written from the admin panel or by pressing Restrict inside any wardrobe and clicking the item. Either way it applies immediately, server wide, with no config file to edit and no restart.
Each rule can hide an item or show it locked, so you can choose between "this does not exist" and "this is something to work toward". Restricted clothing is stripped when a player loads in, so nobody keeps the uniform by logging out in it, and grants unlock automatically the moment someone joins the job or gang.
Your staff can lock down a police vest at 2am without waiting on whoever owns the config file.
Every character is issued two documents at creation, both carried as inventory items.
Both use your own artwork. Replace one image and move the field positions, which are percentages in a single table.
Five addresses, built in. No housing script required. Each one is a private instance with a wardrobe for your saved outfits and a stash that works with whichever inventory you run. Eleven interiors are catalogued, so you can give each address a different one or point them all at the same.
In game, ACE gated, no database client required.
Every destructive action is behind a confirmation, and every one of them is logged. Your moderators get the tools without getting your database password.
/mgthumbs new shoots only what is missing after you add one.Measured, not asserted. resmon 1, single player, 111 fps:
Under 1% of a frame in the heaviest state. Almost nothing runs while you are simply playing: the shop zones use ox_lib zones rather than a distance check per shop per frame, and there is exactly one per frame loop in the resource. /mg-perf prints all of it on your own server, so you do not have to take my word for any of it.
Server authoritative throughout. Prices, entitlements and restrictions are decided on the server. The client is never asked what something costs or whether it is allowed.
The script is escrowed, but everything you need to configure it stays open: all config files, the appearance engine's settings and shop locations, the SQL, the ped and tattoo catalogues, every catalogue JSON, and every captured photograph. The thumbnails stay open because the resource writes to them itself.
ox_target or qb-target are optional and only needed if you turn targeting on.
Remove any existing appearance resource before installing: illenium-appearance, fivem-appearance, qb-clothing, esx_skin or skinchanger. This replaces all of them.
Delivered through Cfx.re Keymaster. After purchase the resource appears in your Keymaster account under the same Cfx.re account you buy with, ready to download. Just make sure the Cfx account you check out with is the one your server licence belongs to.
A full INSTALL.md comes with it, written to be read once and followed: what to remove first, the admin permissions, the database import, the config walkthrough, the inventory items the two ID cards need, and how to photograph thumbnails for any clothing packs you add. If you get stuck on any of it, that is what the Discord is for.
One thing to plan for. Wardrobe thumbnails are not included and cannot be, because every server runs a different set of clothing packs. Capturing them is a one-time automated job you run on your own server, and it takes roughly 30 minutes to 2 hours (depending on your server) on a stock install, longer if you run a lot of packs. Everything works before you do it; the tiles just fall back to plain icons until then.
Join the Discord and open a ticket: discord.gg/pkm8pvvwK9