esx_clotheshop

esx_clotheshop places clothing stores around the map where players change their outfit through the esx_skin menu and pay with cash. After paying, players can optionally save the outfit to their wardrobe (the property datastore used by esx_property).

OverviewCopy Anchor Link

In-game flowCopy Anchor Link

1. Walk into a store marker and press E.
2. Change clothing in the restricted skin menu (t-shirt, torso, decals, arms, pants, shoes, bags, chain, helmet, glasses, watches).
3. Confirm the purchase. The server charges cash and saves the new skin through esx_skin.
4. If a property datastore exists, choose whether to save the outfit and type a name.

If the player cancels, leaves the marker or cannot pay, the previous skin is restored.

InstallationCopy Anchor Link

There is no SQL file. Make sure the dependencies start first:

ensure esx_skin
ensure esx_datastore
ensure esx_clotheshop

To enable saved outfits, create the per-player datastore once:

INSERT INTO `datastore` (`name`, `label`, `shared`) VALUES ('property', 'Property', 0);

ConfigurationCopy Anchor Link

-- Charge 150 per changed piece, minimum 150
Config.Price = 150
Config.ChargePerPiece = true

Server callbacks and eventsCopy Anchor Link

esx_clotheshop:buyClothes (callback)Copy Anchor Link

Triggered by the client with (newSkin, oldSkin). Returns bought, failure where failure is 'not_enough_money' or 'save_failed'.

Server-side safeguards:

• The player must be within Config.ShopDistance of a shop.
• newSkin is validated with exports.esx_skin:ValidateSkin.
• The price is calculated against the skin stored on the server (exports.esx_skin:GetSkin), not the oldSkin sent by the client.
• The money operation is wrapped in beginAccountOperation/endAccountOperation and refunded if esx_skin:SaveSkin fails.
• Only one purchase per identifier can run at a time.

esx_clotheshop:checkPropertyDataStore (callback)Copy Anchor Link

Returns true when the player has a property datastore. The client uses it to decide whether to show the save prompt.

esx_clotheshop:saveOutfit (net event)Copy Anchor Link

TriggerServerEvent('esx_clotheshop:saveOutfit', label, skin)

Saved outfits are appended to dressing in the player's property datastore as { label = string, skin = table }.

Integration tipsCopy Anchor Link

• esx_property reads the same dressing list, so outfits bought here show up in property wardrobes.
• To read outfits from your own resource on the server:

TriggerEvent('esx_datastore:getDataStore', 'property', xPlayer.getIdentifier(), function(store)
    local outfits = store and store.get('dressing') or {}

    for i, outfit in ipairs(outfits) do
        print(i, outfit.label)
    end
end)

• Payment uses the cash account (xPlayer.removeMoney). Edit server/main.lua if you want bank payments.

Common issuesCopy Anchor Link

• Purchase always fails with a "save failed" message: the server distance check uses Config.ShopDistance (3.0). If you moved a shop marker, update the Config.Shops entry, not just the visual marker.
• Outfit not saved: the property datastore is missing, the 60 second window expired, or the player already has Config.MaxOutfits outfits.
• Skin resets after buying: esx_skin failed to save the skin. Check the server console; the purchase is refunded in that case.

RelatedCopy Anchor Link

• esx_skin
• skinchanger
• esx_datastore
• esx_barbershop
• esx_property

Frequently asked questions