Skin naming convention for the IL2 Great Battles skins creator community...

[GenMarkof007]

Hi All,

 

Just wanted to know if anyone has a rule for naming (planes & tanks) IL2 skins.
I remember a long time ago that I saw a naming convention that was asked of all ROF, and IL2 skin creators.
Please let me know if you have any info or help on this.

This was a method of naming skins: 

 

Ex.: v_!_SCG_PzIII-M_summer_NN&1#1  -  v(historic skin) _!(indicator for a squadron skin) _SCG(squadron tag) _PzIII-M(name of tank or plane - same spelling as the skin folder) _summer (type of skins) _NN(no number) _NN&1#1(extension for this tank skin)   
*** If possible, use the underscore between each info of the skin naming.

 

Another skin name: 

Ex.: v_!_1PL_SpitfireMkIXe_Banzai  (the only modification in this naming, is that the author did put his name tag at the end).    
*** If possible, use the underscore between each piece of info of the skin naming.

v = historic skin name
z = personal/fictional skin name
_summer = summer skin
_winter = winter skin

 

It would be great if we could create a convention for naming skins inside the IL2 community creators.
Please take note, this is not to rule anything about creating skins, but more to help the Il2 Sturmovik community to understand more what skins they want or not to add to their skins listing. Also, since much of the community is using the (HSD) Haluter's Skin Download for IL2 Great Battles... this could also generate better naming for any skins added to the app.

 

Cheers,
GenMarkof

 

** If possible, we should try not to use some naming that gives no info about the type of plane or tank, no info if this is historic or personal/fictional... and no other info that will not help the pilot or tanker to find a skin!  

 

Very Important Update: It seems that the HSD app (Haluter) will add the (!) character in the next few weeks. So this means that we will be able to add the squadron indicator (!) inside the naming of IL2 skins. Thx to SCG_Baryonyx for this info update.

 

Edited June 11, 2023 by GenMarkof007

[JV44HeinzBar]

S!,

I use a naming system for most of my skins w/ the exception of some earlier models while I was (still) learning Photoshop. I usually followed this order:

1. Model ID

2. Historic number & unit*

3. Location

4. Year

5. Artist initials**

 

*I've had so many requests for models w/o numbers I added "NN" (no number) at the end of the naming convention.

**Optional

 

I don't do very many fantasy, racing skins or silly skins,  e.g. Hello Kitty. However, there are numerous examples where the unit is a mystery, but have an interesting camouflage pattern. In place of the missing historic number & unit, I use "unidentified unit". I try to provide as much information as possible.

 

Due to some vanity and ease of recognition, I added _HB to the end of later skins. It helps me recognize my skins when choosing from so many.

 

Examples:

PzVIH1_812_8_SS_Pzr_Rgt_2_Das_Reich_Charkov_4_43_Anthrazitgrau or PzVIH1_812_8_SS_Pzr_Rgt_2_Das_Reich_Charkov_4_43_Anthrazitgrau_NN

 

PzVIH1_833_8_SS_Pzr_Rgt_2_Das_Reich_Charkov_4_43_darkgray or PzVIH1_833_8_SS_Pzr_Rgt_2_Das_Reich_Charkov_4_43_darkgray_NN;

 

PzVd_Unidentified_Unit_Erp_Holland_9_44

 

In the examples above, I added the color to distinguish this skin from an exact replica that used a slightly different grey, but I'm sure everyone gets the idea.

 

Although, it may seem redundant to add the model ID at the beginning, I remember downloading a bunch of skins from the forums w/o the model ID. I sometimes placed Panthers in the Tiger folder or somewhere the model shouldn't be. The ID allowed me to easily paste the model in the correct folder.

 

I agree a naming convention would be helpful for those of us that enjoy using custom skins.

 

Just my $.02. 

 

HB

 

 

Edited June 10, 2023 by JV44HeinzBar
Added bold marker; added line #5