🔗Exports/Events

Base Usage

Our script is designed to be drag-and-drop. This also means that all events and exports are bridged from the following resources:

  • esx_skin

  • skinchanger

  • qb-clothing

  • illenium-appearance

So you can still use events like:

TriggerEvent('skinchanger:loadSkin')

and all others as usual.

⚠️ Important: When using exports for illenium-appearance, you must still use illenium-appearance as the resource name, not 17mov_CharacterSystem.

✅ Correct: 

exports["illenium-appearance"]:setPedComponents()

❌ Incorrect:

exports["17mov_CharacterSystem"]:setPedComponents()

For more details, check the documentation of:

EXAMPLES

Below you can find examples of events/exports that will work with our resource

SAVING CURRENT SKIN EVENT (CLIENT SIDE)
TriggerEvent("17mov_CharacterSystem:SaveCurrentSkin")
ESX VERSION OF OPENING WARDROBE / OUTFITS MENU (CLIENT SIDE)
TriggerEvent("17mov_CharacterSystem:OpenOutfitsMenu")
QBCORE VERSION OF OPENING WARDROBE / OUTFITS (CLIENT SIDE)
TriggerEvent("qb-clothing:client:openOutfitMenu")
ESX VERSION OF OPENING SKIN MENU (CLIENT SIDE)
TriggerEvent("qb-clothing:client:openMenuCommand")
QBCORE VERSION OF OPENING SKIN MENU (CLIENT SIDE)
TriggerEvent("esx_skin:openSaveableMenu")

Last updated