MANIK STUDIOS / SERVER CLOTHING HELP

FiveM clothing not showing: a safe troubleshooting flow

Trace missing FiveM clothing from resource startup and folder nesting to body compatibility, drawable selections, appearance menus and conflicting packs.

Start with the symptom

No new choices

Check resource discovery and startup, metadata, body support, then the clothing menu’s limits or filters.

A choice is invisible

Verify the selected drawable and texture, then compare the supplied files with the untouched download.

The wrong garment appears

Check whether the number is global or collection-local, and whether another resource uses the same asset identity.

Only a saved outfit fails

Compare a fresh selection with the stored outfit. The saved indexes or appearance record may no longer match the installed wardrobe.

Note whether one player, one body, one texture or everyone is affected. This makes a support request much more useful than “the pack does not work.”

1. Confirm the resource is found and started

Read the server console when the resource is started. Look for missing manifests, dependency failures, missing data files or entitlement errors. Record the exact error before changing anything. A folder appearing in your file manager is not proof that FiveM has loaded it.

Example only: the manifest belongs at the resource root

resources/
  [clothing]/
    example-clothing/
      fxmanifest.lua
      stream/
      ...supplied metadata

An extra ordinary folder such as example-clothing/example-clothing/fxmanifest.lua can leave the manifest one level below the resource FiveM is trying to load. Bracketed category folders have a specific role; follow the installation guide rather than flattening every directory.

For a newly added resource, an administrator can use refresh to rescan resource manifests, then ensure example-clothing with the real resource name. Ensure can restart an already running resource: use staging or an agreed maintenance window. It does not repair broken clothing metadata or automatically rebuild your appearance menu.

2. Check the actual character model

Test the listed freemode model, not a custom ped that looks similar. MP Male clothing targets mp_m_freemode_01; MP Female targets mp_f_freemode_01. A custom body can also need separate fitting and component combinations. Use the supplied torso and undershirt settings before deciding that a top is broken.

The body compatibility checks explain what to confirm with the creator. Renaming male files to female filenames is not a conversion.

3. Check component, drawable and texture

Start with a fresh test outfit. Select the component the pack actually supplies, then a valid drawable and texture. Tops, legs, masks and props are different selections. A screenshot from another server does not prove the same global number will select your garment.

Ask whether the README’s number is local to a named collection or global across the installed wardrobe. If you use a global-index menu, let the developer identify the equivalent selection on this server. Avoid copying a number into every player’s saved outfit. The add-on guide’s index diagram explains the distinction.

4. Separate the clothing resource from the appearance system

QBCore, ESX and Qbox identify server frameworks; they do not by themselves identify the menu version or its configuration. Record the exact resource and version: for example qb-clothing, illenium-appearance, fivem-appearance or a customised fork.

Check its maintained documentation for restricted items, job or shop access, drawable bounds and how lists are rebuilt. After the server-side change, reconnect and reopen the menu. If a fresh selection works but an old outfit does not, investigate the saved appearance record with a backup rather than deleting everyone’s outfits.

A developer can test the item independently of the shop on staging. If it renders there, focus on menu exposure and persistence; if it does not, continue with the resource and asset checks.

5. Isolate conflicts without damaging the live wardrobe

Compare the supplied manifest and metadata with the original archive. Check referenced paths and filename case. Do not remove YMT files or rename YDD/YTD files at random. On staging, reproduce the problem with the affected pack and its documented dependencies, then reintroduce other packs in small groups.

Keep game build, character, component selection and test location consistent. If the issue starts only when a second resource is enabled, record that pair. If the model is visible but the surface is missing or blurry, continue with the texture troubleshooting guide.

6. Gather evidence before cache changes

A cache reset is not a general fix for a missing manifest, wrong body or naming conflict. First compare an untouched download and a second client. Follow targeted current advice from the creator or platform support only when there is evidence of stale client data. Do not delete arbitrary server folders or ask players to erase unrelated files.

Resource name and version; whether files were modified.
Server game build and appearance resource/version.
Ped model, component, drawable, texture and collection if known.
Exact console error and a screenshot of the symptom.
Whether a fresh outfit, second player and isolated staging test reproduce it.

For a Manik pack, send these details through the support route on its product page. Remove passwords, tokens and personal player data from logs before sharing them.