esx_accessories

esx_accessories adds shop markers where players buy masks, helmets, glasses and ear accessories, and a personal menu (default key J) to put them on and take them off again. Purchases are stored per character in esx_datastore, so the accessory survives relogs.

OverviewCopy Anchor Link

In-game flow:

1. The player walks into a shop marker (Config.Zones) and presses E.
2. esx_skin opens a restricted menu that only shows the <type>_1 and <type>_2 sliders of that accessory.
3. On confirmation the server charges Config.Price from cash and stores the chosen drawable and texture.
4. Later the player presses J, picks Helmet, Ears, Mask or Glasses and toggles the saved item on or off.

InstallationCopy Anchor Link

INSERT INTO `datastore` (name, label, shared) VALUES
	('user_ears', 'Ears', 0),
	('user_glasses', 'Glasses', 0),
	('user_helmet', 'Helmet', 0),
	('user_mask', 'Mask', 0)
;

ensure oxmysql
ensure es_extended
ensure esx_lib
ensure skinchanger
ensure esx_skin
ensure esx_datastore
ensure esx_accessories

ConfigurationCopy Anchor Link

All keys live in config.lua.

Setting Config.Type = -1 skips the whole marker thread. Because the markers also handle enter and exit detection, the shops then stop working. Use a very small Config.Size or a transparent color if you only want to hide the visuals.

The default Config.ShopsBlips only adds a blip for the mask shop because the other zones sit inside clothing stores that esx_clotheshop already marks on the map.

Server eventsCopy Anchor Link

esx_accessories:payCopy Anchor Link

TriggerServerEvent('esx_accessories:pay', accessory)

Charges Config.Price and opens a purchase session for that accessory. The server checks that the player exists, stands near a matching zone and has enough cash. The built-in client uses the esx_accessories:buy callback instead, which runs the same logic and returns the result.

esx_accessories:saveCopy Anchor Link

TriggerServerEvent('esx_accessories:save', skin, accessory)

Writes has<Type> = true and skin = { <type>_1, <type>_2 } into the user_<type> datastore. The server rejects the call unless there is an unexpired paid session for that accessory and the player is still near the shop. The session is consumed on success.

CallbacksCopy Anchor Link

Callbacks are registered with xLib.callback.registerCompat, so both xLib.callback and ESX.TriggerServerCallback can call them.

Example: check whether the local player owns a helmet before offering it in your own menu.

xLib.callback('esx_accessories:get', false, function(hasHelmet, helmetSkin)
    if not hasHelmet then
        return ESX.ShowNotification('You do not own a helmet yet.')
    end

    TriggerEvent('skinchanger:getSkin', function(skin)
        TriggerEvent('skinchanger:loadClothes', skin, helmetSkin)
    end)
end, 'Helmet')

Client eventsCopy Anchor Link

These are local events (not network events) fired by the marker zones. You can listen to them, for example to show your own help text.

Reading the stored data from another resourceCopy Anchor Link

The data is a normal private datastore, so server scripts can read it through esx_datastore:

local xPlayer = ESX.GetPlayerFromId(source)

TriggerEvent('esx_datastore:getDataStore', 'user_mask', xPlayer.getIdentifier(), function(store)
    local owned = store.get('hasMask') or false
    local skin = store.get('skin') or {}
    print(('Owns mask: %s, drawable %s'):format(owned, skin.mask_1))
end)

Common issuesCopy Anchor Link

• "No mask/helmet" notification although the item was bought. The datastore rows from the SQL file are missing, or esx_datastore started after the purchase. Check that user_mask and the others exist in the datastore table.
• Purchase charged but nothing saved. The player walked out of Config.ShopDistance or took longer than Config.PurchaseSessionDuration in the confirmation menu. The money is not refunded in that case.
• Shop does nothing when pressing E. You changed Config.Type to -1 or renamed a zone key. See the configuration notes above.
• Masks taken off show a blank head. Mask "off" sets drawable 0; props (helmet, glasses, ears) use -1. Custom clothing packs may need other values.

RelatedCopy Anchor Link

• esx_datastore
• esx_skin
• skinchanger
• esx_clotheshop
• esx_accessorymanager

Frequently asked questions