Use Coupon WELCOME to save 20%

$ USD
  • $ USD
  • € EUR
  • £ GBP
  • $ AUD
  • R$ BRL
  • CHF CHF
  • ¥ JPY
dpClothing for FiveM

dpClothing: Source, Setup and Outfit Compatibility

Short answer: dpClothing is a client-side FiveM clothing-toggle menu published by dullpear/andristum. The creator repository is still reachable and identifies its manifest as version 1.0.3, but its latest default-branch commit is dated August 2, 2021 and GitHub shows no declared repository licence. Treat it as a historical resource that needs staging and source review, not as a guaranteed current solution for every ESX or QBCore clothing stack.

Repository, manifest and original Cfx.re release checked by RPCrate on September 1, 2026.

What the creator source actually contains

The official repository contains client scripts, locale files, streamed assets and an fxmanifest.lua. The manifest names the resource dpClothing+, version 1.0.3, and loads configuration, clothing, variation and GUI scripts on the client. It does not declare ESX or QBCore as a dependency. That makes framework compatibility a server-specific integration question rather than a blanket promise.

The original release documents a GUI on the Y key plus commands for bags, bracelets, ears, glasses, gloves, hair, hats, masks, neck items, pants, shirts, shoes, tops, visors and watches. It also documents /revertclothing, /bagoff and /clothingexit. Commands and key bindings can be changed in the locale and configuration files, so check your downloaded revision instead of copying a list blindly.

Source and maintenance status

Source check Observed result Meaning
Creator repository github.com/andristum/dpclothing is public and not archived. Use it to inspect the exact source and history.
Manifest Version 1.0.3; client-side Lua resource. Do not describe the resource as a current framework package without testing.
Repository push timestamp October 14, 2022; distinct from the default-branch commit dated August 2, 2021. Review open issues and current game/server behavior before production use.
Licence No licence is declared by GitHub. Public source is not automatic permission to redistribute a modified mirror.

Install from the source you can inspect

  1. Download or clone the creator repository and record the commit you tested. Avoid a renamed mirror when its relationship to the repository cannot be established.
  2. Place the resource in a staging server and start it by its actual folder name. The original instructions use start dpclothing; ensure dpclothing is the current equivalent when the folder is named dpclothing.
  3. Review these resource files: Client/Config.lua, the active locale and Client/Variations.lua before giving players access.
  4. Test male and female freemode peds plus any custom EUP, hair, mask and clothing packs. Variation numbers are tied to the clothing assets on your server.
  5. Use the documented dpc:EquipLast event when a player enters a clothing store, barber flow or outfit system, then confirm the saved outfit still restores correctly.

Compatibility and regression checks

  • Toggle every exposed component, restore it, reconnect and respawn.
  • Change job uniforms and saved outfits before and after using the menu.
  • Test handcuffs, death/revive, character switching and any appearance resource that writes clothing state.
  • Check the GUI at common resolutions and confirm players can close it if focus gets stuck.
  • Verify that custom hair and EUP variants do not remove or replace the wrong drawable.

dpClothing is a quick-toggle utility, not a character creator, clothing store or uniform database. Keep those responsibilities separate and document which system owns the saved outfit.

Rollback

Back up the resource configuration and variation map, remove its ensure line, restart the server and retest the owning clothing or appearance system. If a player saved an outfit while a component was hidden, restore the outfit through that owning system rather than guessing drawable values.

Official dpClothing sources

Repository history rechecked on September 10, 2026: default-branch revision 62d24c3b67c6e3cb6315fcb3162978125e858487. A repository push timestamp is not a new release or a compatibility test.