Submission information updated

[Skuzzy]

First, we would like to express our thanks for all the work the skinners do for Aces High.  It is very much appreciated.

With that said, we need to take a little harder line on the actual format of the submissions.  Right now we have a backlog of skins to get approved.  The backlog occurred for several reasons, but in order to get through them, we will be returning submissions which do not comply with the skins submissions requirements (i.e. if there is no "info.txt" file, the skin will be returned, for example).

We really need all skin submissions in the proper format.  This will help get the skins through the approval process much faster.

Thank you

[Easyscor]

Skuzzy, while you’re clarifying this, let me ask if I’ve got this right.

I’ll use the b17g as an example.

I create a new zip file named b17g# where number is the next skin slot number on my FE.

I load in the files “b17g1.bmp”, “b17g2.bmp”, “b17g.txt” and “info.txt”.

I then zip the whole thing and send it, right?

Now if I’m sending in multiple skins, I make a different zip files for each aircraft with the skin slot number being the difference in the name, right?

The files will automatically unzip into a folder named b17g#.

How do you want this handled if I don’t have Winzip?

[Skuzzy]

You use a relative path for the files in the zip.  In other words, if you list the zip file, the contents would be:

b17g1.bmp
b17g2.bmp
b17g.txt
info.txt

Note:  no directories/folders.  This allows me to unzip them into the correct folder so we can look at them.  Does that answer the question?

[Easyscor]

Yes thanks.  I was thinking of my first submittal when I sent you two versions of the 9-0-9; which I corrected in the second submital but I used an improperly named Word file for the documentation.

[Easyscor]

One last thing.

Do you have a preference on the name of the zip file or can we name it for the plane i.e. simply "Little Patches" or whatever?  Not that I would do it that way but clearly you'll need to rename the folder that unzip creates.

[oboe]

Skuzzy the skins I submitted were before the naming format was adopted (which is a good idea I think - very smart to have FG before squad ID):

2) Check the object.txt (replace the word object with the actual object name, for example p51d.txt) to make sure the string in that file is not too long (20 characters or less will be fine).
We have adopted a naming convention for the information in this file. Here is an example: 51FG/214FS by player_id
Basically, the flight group, and the flight squadron, separated by the '/' symbol. We are aware this convention does not work for all planes, but you get the idea.
Replace player_id with your game/pilot handle.

Should I correct this and resubmit all skins, or will you guys just change it as you examine them?   I don't want to make any more work for you than you've already got...

[Skuzzy]

Oboe, do not worry about resubmission, unless we kick it back to you.

Easy, the name of the zip file does not matter, but it would be nice if it were named using the name of the plane in AH (i.e. p51d.zip..._.

[Easyscor]

Thanks

[Kev367th]

Have noticed that skins prior to the new policy of the info.txt only rather than including the info in the emails are being sent back.

IMO this shouldn't happen, we have already taken the time to do the skin and submit it using the prior policy.
If I have any more that are like this please don't send me a email saying the info.txt is missing, just delete them.

Been fun doing skins, won't be doing any more, too many policy changes that are affecting prior skins. Don't have the time to go round digging out stuff for information that it is the ORIGINAL email AS PER THE POLICY IN PLACE AT THE TIME.

[Skuzzy]

The original policy has always stated we need the 'info.txt' file included with the submission.  We had been manually putting them together ourselves.  There was no change to the actual policy, other than making some text bold and reinforcing the "info.txt" file as being included in the zip file.

The defining of what we 'would' like to see in the plane description file is not going to get a skin rejected.

However, the number of skin submissions have over-run the ability to keep creating files which should be part of the zip data (i.e. the skins are getting submitted faster than we can keep up).  We need some help.  If you are not willing to help us with this, it is your choice.
Our goal is to get skins through the process as fast as possible.  By getting the files submitted in a consistent manner, it will greatly reduce the amount of time any one skin needs.

Again, we appreciate the effort, but need a little help here.

[Kev367th]

Yes it did but it also said that we could include the information in the email. You did not specify you needed both, it read as an either/or.
In fact since the change all my skins have been submitted with an info.txt file. It's only the earlier ones that have it as part of the email.

Also "51FG/214FS by player_id" will not work for the RAF etc

"313 Sqn by player_id" would, they were not called fighter squadrons by the RAF in the way it is used in your naming convention.

[oboe]

I read the original instructions the same way - as either /or .   But I am happy to go back and make whatever changes are necessary to speed things along, as I think custom skins are the greatest feature of AH2.

Regarding Kev's British aircraft scheme, I agree completely, with the additional caveat that if it's not a British bird, or if its a British aircraft in another nation's air service, please include the standard air force abbreviation prior to the squad name.  For example, the RAF P-51B skin I did would read "RAF 112 Sqn", or a Australian Spitfire skin would be "RAAF xxx Sqd".

Thoughts?

[Skuzzy]

Yes, there are many areas where the naming convention cannot specifically work and we are aware of that.  There is a great deal of flexibility in this, but if we can get close, just as you suggested Kev, then it is fine.

Sorry for the confusion for the info.txt file, but this iteration only changed the bolding and added the reinforcing of needing it to be included in the zip file.  The first iteration did indeed allow it to be included in the body of the email.
In hindsight, it was a bad choice.  We really did not expect such a great turn out of skins to be done.  It really has been impressive and we just want to get them into the game.

It being a new process for us, it was bound to need some adjustments.  There is no intent to upset anyone.