The way VT's skin system works is not "Skin1 skin2' etc, and most past addons agree. Most. Recently, though, people (like that guy behind Love Live skinpack) have done the Skin1 Skin2 phenomena. Anyway. If it really WAS that way, then people would probably be making intensely high numbers to not conflict, but hey, they're using names. Follow them.
A diffuse's name should not be something like "Su-37_Skin3.dds". It should be less generic than that.
For instance, let's say you made Yellow.
Your skin name SHOULD be
Of course, if you're worried about Yellow's popularity, we can go further.
"Su-37_Yellow-Adam". "Adam" represents the skinner's name.
You should do the same with your .skin files.
But, that's not the end. You can get as unique as you want with your diffuse's name.
Fairly soon, all my skins will follow the convention named above. You should be unique too. And even if you do use my conventions, I won't get mad: As long as your name is also not Stinger, I'm okay. And besides, people likely to make these mistakes use .dds files. The new standard skin file is .png, so join our glorious .png race.
This is all.
People have been saying wise words about skin naming and such, as well as how the game behaves.
According to Nergal:
Nergal01 wrote: Another very important note; having multiple skin images with the same name among different plane will override each other's skin in-game. Having two planes with a skin image named grey.png will make the skin override each other so adding a prefix on the image name (Su-37_Skinname.png) is highly encouraged.
TL:DR, using the same name between two planes' skins is bad. J-35J_Espada and RafaleM_Espada work pretty reasonably, though having "Espada.png" in BOTH the Rafale-M's (as if) and J-35J's folders is not good.