Thanks for the new update @Pained_Psyche <3
The error you got says that one of the data pieces I had to add to implement face blending is not there.
Your character was most likely created/saved with some other creator (like esx_skin). You need to wipe the skin column of your users table (for all players) completely when switching from esx_skin.
You didn’t follow the instructions. You need to modify esx_identity and replace the code that opens the default esx_identity window. If you use extendedmode, you also need to edit spawnmanager.
It’s all spelled out in comments in shared/config.lua
2 Likes
Ok thank you i found out that I have to remove skinchanger from the resources folder. But now I have another question because my esx_ambulancejob now doesnt work anymore because esx_skin is not activated. Do you have a solution for this?
Not yet, but I’m trying to adapt this right now.
1 Like
Ok so all jobs doesn’t work yet because policejob also not working 
UPDATE (esx job scripts)
Added some sort of compatibility with resources that use esx_skin or skinchanger.
By some sort of, I mean that they will actually load and work, but I can’t guarantee they will be bug free and if serious bugs occur it probably is not possible to fix them without editing those resources.
Since some of these jobs change how your character looks like when ‘on duty’, you can mess it up if you go to a clothes shop after going on duty and for example press ‘cancel’ button. In such case the character will be reset to their original appearance and not their ‘on duty’ appearance. Or you can do an even worse thing, press ‘accept’, then your regular appearance will be overwritten with your ‘on duty’ appearance in the database.
It is not possible to detect whether a character is on duty or not and prevent them from accessing any clothes shop or other character editing places if they are, since the job scripts don’t offer any exports. If they did, that would be an easy fix.
UPDATE (creator opening on login bug)
It’s possible to somehow corrupt your users table so in place of identifier you get license:identifier or even license2:identifier. In such case the query inside esx_identity that retrieves your character doesn’t find the identifier (because it’s prefixed in the db) and it proceeds just like your character did not exist.
This is managed by esx and (I guess, not sure) it’s caused by not correctly emptying all the tables that refer to identifier when switching from esx_skin. I have no idea how to fix it.
Edit:
It looks to me like some sort of compatibility problem between latest esx_identity and extendedmode where esx_identity uses raw identifier hash and extendedmode uses license2:hash. It does not happen with v1 final.
I feel it’s one of those problems where a “general fix” is not really possible and everyone should tune it to whatever they use on their server.
Best I can offer is the following ‘hack’:
Open esx_identity/server/main.lua, find:
if string.match(v, 'license:') then
identifier = string.sub(v, 9)
break
end
and replace it with:
if string.match(v, 'license2:') then
identifier = v
break
end
2 Likes
Is it possible to turn off the blackscreen after joining ?
1 Like
You could do it by editing the code but I don’t recommend it. The result will look really bad.
The blackscreen is there so you don’t see the character spawn (it’s always little above ground so an awkward fall immediately follows it) and the swap from default model.
Also cui_character’s camera targets ped position, so on first login (that opens the creator) it would target the character while still in the air resulting in weird/wrong camera position.
Ah ok good to know
Hello ! thanks a lot for the mod!
I tried the update but, even though they loaded correctly, resources using esx_skin and skinchanger (clotheshop and barbershop for example) don’t seem to work.
I can press E in the shop, but nothing happens.
I did that mostly for people who use the job scripts. With this resource clothes shop and barber shop are pointless as they are built in.
1 Like
UPDATE:
Added masks (that I previously forgot) to the clothes tab.
3 Likes
hello, I have been your fan since the day you release this resource 
Your resource is soooo fascinating(?), I have implemented it into my server
and think I found that neck_thickness has been forgotten in the feature page
Shame that not every script is using the esx_service or some kind of other global script to check if a player is on duty.
That will solve your problem of detecting. Like if esx.player.isOnDuty then can’t use the cloth shops.
Would be a nice feature 
arms and tattoos might be ok <3
can you use the “esx_clotheshop” without changing the character? i say this to maintain clothing sets and others
this script here has its own clothing shop so you have to remove the esx_clotheshop
i know it, but the clothes from the inventory of police work and other jobs, how does it work? return character to default?
this all works it fixed in the latest update. But if you are on duty you shouldnt go into clotheshop and change your style this would destroy your character
