Embedded Skin trouble.

[Disciple-X]

GZdoom throws out my wad for having an embedded and customized skin. GZdoom loads up fine, no crash outs or anything, but it leaves a small blue-text message in the console saying that it refuses to load my wad for having a skin in it. Seems a little odd for it to act that way considering that almost all Zdoom based ports support wad projects with embedded skins. I was just curious as to why it does this.

Wait, my mistake, even regular Zdoom and the current SkullTag throw out the wad, except they do not show the blue message. I Wonder why embedded skin functions were altered with the current Zdoom cores.

[Graf Zahl]

This was done to prevent skins from forcing crap resources onto the unsuspecting player. Another reason is to have a clean namespace for the skin's resources which otherwise wouldn't be possible.

Skins have to be separate WADs and you can't embed them into other WADs.

[Cutmanmike]

You should use classes now anyway.

[Disciple-X]

Makes sense. If things work another way though, I will not need embedded skins. Thanks for answering the question, greatly appreciated.