@WillNode Out of curiosity, what OS and exactly what version of 2017.3 are you running? Wondering because out of the people who have tested it, your are the first one to run into an issue with it loading the skins in this version so im trying to figure out where the issue is coming in exactly so i can fix this. I've never had an issue with this until 2017.3. Out of curiosity what OS and specific 2017.3 version are you using? Myself and a couple of the other testers are unable to replicate this issue. In addition. The skins need to be accessible before unity Deserializes everything, so if i use .delayCall that wont happen and end up causing errors elsewhere because the skin information is not accessible. Like i have said before this entire issue is something related SPECIFICALLY to 2017.3. It does not happen in any previous version of unity, 2017.4 or any of the 2018 versions as far as im aware.