New change to mission naming process

**Jeepo_SAS** · 05-26-2009, 07:25 AM

OK guys, as part of the expanding profile and list of missions created by TacticalGamer users and HOSTED here at TacticalGamer.com we would like to propose a change to mission naming from this moment onwards. In order to simplify the missions lists for admins to monitor latest and old versions, we would greatly appreciate it if you would use the following naming profile;
[TG]CoOp50_ACE_Operation_Jumpingfox_V1.0 ; i.e.

TG then the type of mission (CoOp or TvT), the number of players, Whether it uses ACE mod or not, then the mission name. If you wanted to then host it elsewhere you can simply change the front two letters and save a new version.

We would also appreciate it if you would add the following line (many of you do this already and we greatly appreciate it)
Brought to you by TacticalGamer.com - The PREMIERE online community for mature gamers

We would greatly appreciate your consideration in this, as this will help us enormously in managing missions for the future.

Many thanks,

Jeepo

Sam Hoy · 05-26-2009, 02:49 PM

Won't this only make it harder to differentiate between version types because, well, there is no version number in the name?

**Jeepo_SAS** · 05-26-2009, 03:20 PM

Edited, Version to go after the name.

DLBlue · 07-24-2009, 11:16 PM

The name could get huge though...

I cant see some mission versions already because names are too large and I am playing at 1080p

**Blackdog1** · 07-26-2009, 11:21 PM

Then pick shorter names!

NickNitro · 07-28-2009, 01:33 PM

'Brought to you by TacticalGamer.com - The PREMIERE online community for mature gamers'

Is that after the title or as a subtitle within the game at mission start?

DLBlue · 07-29-2009, 04:09 AM

Make a trigger of type none, with condition true

In the on Act field put

Code:

null = execVM "titleScreen.sqf";

and titleScreen.sqf should have this:

Code:

titleText ["SOME QUOTE YOU WANT THEM TO SEE FIRST", "PLAIN DOWN"];
sleep 4;
cutText ["MISSION TITLE","PLAIN"];
sleep 4;
titleText ["Brought to you by TacticalGamer.com - The PREMIERE online community for mature gamers", "PLAIN DOWN", 0.6];
sleep 6.5;
cutText ["Mission by YOUR NAME", "PLAIN DOWN"];

Change where appropriate. Make sure the quote isn't longer than a sentence or they wont get much time to read it. For instance, Tales of Courage 3 has this:

Code:

titleText ["'Field Experience is something you earn after you need it' -Murphy's Laws", "PLAIN DOWN"];
sleep 4;
cutText ["Tales of Courage 3: Field Experience","PLAIN"];
sleep 4;
titleText ["Brought to you by TacticalGamer.com - The PREMIERE online community for mature gamers", "PLAIN DOWN", 0.6];
sleep 6.5;
cutText ["Mission by |TCO| Bellicosity", "PLAIN DOWN"];

As far as the naming convention goes, if the mission goes on the TG servers... its a TG mission for the most part. So the TG tag can probably go. If its on the Alpha server is a coop, if its on bravo its a tvt, so that part can go. I would suggest something like:

#vVersionNumber_Name

So ToC1: The Landing would be something like:

46v13_ToC1TheLanding

The version should be in front of the name because its always going to be much smaller.

Sc[ + ]pe · 07-29-2009, 05:41 AM

Version number traditionally comes at the end of a file, though. No reason to upset the natural balance of things.

Also, with the mismatching of maps with regards to Alpha and Bravo, I still like to see Co or TvT in the title. [TG] is also nice to have because it instantly separates those missions made by TG members/regulars from those made by other people, and is also a good recruitment tool since many of us upload our missions to ArmAholic.

Fincuan · 09-30-2009, 08:23 AM

Bump! Just taking the opportunity to remind mission makers that this convention is a good one

Yesterday we had some trouble choosing missions as the names of some had gotten so long the relevant information wasn't visible in the selection screen anymore. I'd suggest three changes to the convention to make the names a bit more informative when choosing missions:

Move the [TG]-tag to the end of the name
Change the tag CoOp to CO
Put an underscore(_) between the gametype-tag and playernumber

With these changes the example mission [TG]CoOp50_ACE_Operation_Jumpingfox_V1.0 would thus be:
CO_50_ACE_Operation_Jumpingfox_V1.0[TG]

**LowSpeedHighDrag** · 09-30-2009, 05:05 PM

Operation = Op
that would shorten it too.

Fincuan · 11-10-2009, 11:01 AM

Any updates to this convention? I'm about to upload a mission but having a hard time deciding on how to name it exactly. The missions currently in missions depot each use a different convention, so no help there either.

Sc[ + ]pe · 11-10-2009, 03:58 PM

There is still a big problem with mission names being convoluted, uninformative, long, or simply out-of-place. I've started doing a few things to help shorten and simplify my mission titles, including:

-replacing "[TG]" with "TG";
-replacing "CoOpXX" with "CXX";
-replacing any underscores or spaces with periods or similar low-weight ASCII
-replacing a standard numeric version number ("100" for 1.00) with a numeric-alphabetic system ("1a" for 1.00, "1b" for the next iteration, etc.)

So a mission that was originally [TG]CoOp36_Deus_Ex_Machina_v130 becomes TG.C36.Deus.Ex.Machina.v1c

Rommel · 11-10-2009, 04:33 PM

Include whether the mod is needed as well! Maybe at the end have @TG to show that it uses the mod pack.

**LowSpeedHighDrag** · 11-10-2009, 04:40 PM

Or "TGm.C68.Op.BunnyFury.v1a"