starred/esx_core
1
0
Fork 0
mirror of https://github.com/esx-framework/esx_core.git synced 2026-08-28 17:01:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(es_extended/server/main): use the identity sex for the default skin

Browse Source 
The fallback skin is built from userData.sex, but that field does not exist
yet at this point - it is only assigned further down when the identity data
is read from the result row. The comparison therefore always ran against nil
and every character without a saved skin fell back to the male model.

result.sex holds the value already and is used a few lines later, so read it
directly.

Tested locally on artifact 25770 with a female character whose skin column is
empty: the client used to receive skin.sex 0 and spawned as the male model,
it now receives 1 and spawns female. A male character with an empty skin
column still receives 0.
This commit is contained in:
Selt
2026-07-27 02:52:26 +02:00
parent ca597cf6f4
commit 22ddbadd6e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
[core]/es_extended/server/main.lua
+1 -1
View File
@@ -307,7 +307,7 @@ function loadESXPlayer(identifier, playerId, isNew)
userData.coords = json.decode(result.position) or Config.DefaultSpawns[ESX.Math.Random(1,#Config.DefaultSpawns)]
-- Skin
userData.skin = (result.skin and result.skin ~= "") and json.decode(result.skin) or { sex = userData.sex == "f" and 1 or 0 }
userData.skin = (result.skin and result.skin ~= "") and json.decode(result.skin) or { sex = result.sex == "f" and 1 or 0 }
-- Metadata
userData.metadata = (result.metadata and result.metadata ~= "") and json.decode(result.metadata) or {}