This is an odd one that I haven't found documented anywhere or mentioned in a tutorial, so I'm hoping it's just something silly I've maybe missed.
The deal is this: Following the skinning tutorial by the Ravensoft guy, I have a custom Lando skin. It has both a red and blue version for online play and the resulting files are as follows: - icon_default_custom.jpg - icon_red_custom.jpg - icon_blue_custom.jpg - custom_torso.jpg - custom_torso_blue.jpg - custom_torso_red.jpg - model_default_custom.skin - model_red_custom.skin - model_blue_custom.skin
The only differences between the .skin files and the originals is that anything using lando_torso[_color].tga has been changed to the appropriate file-name above (ending in .tga, I never found a reason for this but it seemed to be convention and worked so I stuck with it).
Anyways, I packaged up the skin in models/players/lando/ into a .pk3 file and threw it into my multi-player base folder. Thus circumventing the default "Pure" setting for new multiplayer games.
So I can now open up multiplayer and select the skin quite happily and play an FFA match. I can even switch to one of the colored varieties and it will work just fine, no bother at all; my modification (the words "LANDO RULES" on the front =) shows up fine with the colored bits as expected for each variation.
Sounds fine then? Here's the problem; if I choose the skin and play a team game on multiplayer, even though the correct skin is selected, it will switch me to normal Lando, or something else entirely. Making sure I select the skin (or select something else then try to switch back) makes no difference. For whatever reason, despite the fact that my team-colored skins seem to work fine normally in free-for-all type matches, they don't actually work in a team game! This for a team-game that I've set-up myself, custom downloaded characters work fine (though disappointingly few have color variations, most are fubared in team games).
As you can imagine I'm rather confused as to why this is happening, as I say there's no obvious reason why it should do this as I can select blue and red with impunity in FFA matches, but come an actual team-match it won't work =S
Hmm, it seems my skin works just fine if I rename the folder to models/players/lando_custom/ and then change the logo and .skin files to just model_default, model_red etc.
But this requires me to copy in the model and sound files as well, seems a bit wasteful to have to do that!
In this case it's as though a custom skin using an existing model won't be accepted as a team-color, even if it's correctly named as lando_red_custom and shows up in the list of choices. It just doesn't work at all in team-games as detailed in my original post. But in its own folder and thus as its own player, it works just fine.
As a result I've a solution, but it's not a perfect work-around, so I'm still wondering if there are any alternatives? It'd be nice to have it working as it was supposed to work, rather than essentially creating a whole new (albeit mostly identical) character!
You'll have to do it by duplicating the folder. The team skins will always run off the model_blue and model_red .skin files, no matter what you do, since team color files are hardcoded into the game.
I don't know how, and I don't know why, but this is totally Sheep's fault.