Exports

XDEV Appearance exposes multiple exports to simplify external integrations without requiring direct access to internal resource logic.

The export system was designed for:

Export Philosophy

Most appearance systems tightly couple functionality to internal events or callbacks.

XDEV instead exposes reusable exports to improve:

modularity
compatibility
maintainability
developer flexibility

Exports are intended to provide:

safe access
external integrations
resource communication
appearance control

without modifying protected files.

Purpose:

open first character creation workflow

Example:

exports('startPlayerCustomization', function()

end)

Example usage:

exports['xdev_appearance']:startPlayerCustomization()

The export internally:

loads freemode model
detects gender
opens appearance menu
starts first creation state

Common use cases:

multicharacter systems
spawn selectors
identity systems
registration systems

The export was specifically designed to support:

first spawn workflows
new player creation
identity initialization

without requiring direct event access.

The export integrates naturally with:

QBCore
custom multicharacter systems
legacy character systems

depending on server implementation.

Exports may internally trigger:

menu events
ped synchronization
appearance rebuilds

through the internal event system.

The export automatically handles:

mp_m_freemode_01
mp_f_freemode_01

selection based on player gender.

Exports intentionally avoid exposing direct internal structures.

Purpose:

safer integrations
update stability
reduced dependency conflicts

Recommended usage:

external spawn systems
identity registration
new player onboarding

The export system was intentionally designed to support future expansion.

Potential external integrations include:

appearance retrieval
outfit loading
tattoo rebuilding
cache handling
ped synchronization

depending on server needs.

XDEV exports intentionally remain:

lightweight
modular
framework-independent

to simplify cross-resource communication.

Exports should generally be preferred over:

direct event spoofing
internal state editing
protected file modifications

whenever possible.

This improves: