Mission name standard

[Celery]

--- Mission name standard ---

This sticky is for everyone who is making multiplayer missions and I ask you to read and follow the standard for the convenience of the whole multiplayer community.

The mission name matters because missions are listed in alphabetical order on a server. There are hundreds of missions out there and many servers have a huge amount of them so keeping things tidy helps everyone pick the mission they want to play with less trouble. The mission name is written in the editor in the same window where you set the weather and time conditions.

Here is an example of your everyday mission name following the standard:

CO 06 Kill the AI

The name specifies these parts:
game type
maximum number of players
mission name


Below is a more complicated name, showing more pieces of information should the need arise:

FDF CTF@ 24 Flag Rambos v1 beta

The name specifies these parts:
mod tag
game type
addon tag
maximum number of players
mission name
version of the mission


PLEASE NOTE: Mission names are written exactly like in the examples, underscores for spaces and (only) lower case are not used. The mission name is only a piece of data inside the file and it doesn't give any trouble to upper case and space allergic systems that try to open them. Read about filenames near the end of this post.



--- Official expansions ---

Official expansions, Queen's Gambit to be precise, do not need a tag for missions using their content. Reason for this is the commonplace use of the expansion in the community and keeping mission names simple in the future.




-- Specific intructions for naming your mission begin here --


--- Mods, leagues and clans ---

If the mission requires a mod (not an addon pack), it should be stated at the start of the mission name to tell the players that the mod should be loaded on their game if they wish to play the mission. It should be written first to make it easier to either browse or skip the mod missions depending on if you can or want to play them or not.

Please note that a compilation of existing addons not specifically made for that compilation doesn't count as a mod, it's an addon pack unless it's large enough to be a total conversion such as FFUR in Flashpoint. Go to the addon tag part to read about missions with addons. If you need to specify which addons are needed, you can put an abbreviation of the addon's name before or after the mission name.


Leagues need a tag to tell their missions apart from public ones. It's up to the league if they want to show their name at the beginning or only after the game type. The advantage of the first option is that all missions of the league can be seen in one whole list, while the second one's advantage lies in ease of public play, so different missions are listed under their respective game types but the league missions are still listed in one bunch.

A mod tag should be included after the league tag if a mod is used. If the league uses its own custom addon pack or mod, only an addon tag should be used.

Two examples of league mission names:
ECL C&H 34 Metal Rain
CTF -Gc- 50 CAYO V1-06beta

Hypothetical league mission using an unchanged mod:
TNT FDF A&D 20 Sauna Wars


A clan tag can also be used. In that case the tag can be either after the game type or after the mission name. If you're only making a single mission and not a series of missions of the same game type, it's best to leave the tag after the mission name for easier alphabetical browsing. A tag after the game type serves to list all missions of the same series together.

Two examples of clan mission names:
CTF [MCY] 60 DOUBLE BLOW v03
DM 10 VODKA! [MCY] v1.10


--- Game types ---

The following abbreviations are used:

CO - Cooperative (only AI opponents)
DM - Deathmatch
TDM - Team Deathmatch
C&H - Capture and Hold
SC - Sector Control
CTF - Capture the Flag
RCTF - Reverse Capture the Flag
Combi - Combination of C&H and CTF
C&K - Capture and Kill
CTI - Conquer the Island
A&D - Attack & Defend
Obj - Objective (Co-op style mission with PvP element)
RC - Race
FF - Flag Fight
TFF - Team Flag Fight
E&E - Escape & Evasion
VIP - VIP Protection/Assassination
RTS - Real Time Strategy
RPG - Role Playing Game
LMS - Last Man Standing
LTS - Last Team Standing
Misc - Miscellaneous (unique concept not fitting in any category)


--- The addon (@) tag ---

The @ sign helps the server admin and joining players see that they must have the unofficial addons the mission requires to play (not included in the vanilla game, expansions or patches). If the mission is made for a mod, a mod tag will suffice to tell everyone that they must have the mod. However if the mission uses an addon that the mentioned mod doesn't include, the @ sign becomes necessary again. The tag is attached to the end of the game type with no spaces.

Mission using an unofficial addon:
A&D@ 16 Addon Wars v666

Mission using the FDF mod:
FDF CO 08 Russian Hell

Mission using the FDF mod and an addon not included in the mod:
FDF TDM@ 12 Wanzer Fight v2


--- Player amount ---

The two digits before the mission name give away the maximum amount of people who can play the mission. Spectator slots should be left out of the count so players won't be confused when they don't get to play in the actual game afterall. The number always has to be written with two digits unless the mission actually has 100 slots or more. If the amount is lower than 10, a zero is written as the first digit so that the alphanumeric order is not confused.


--- Version ---

A version number is completely optional but highly recommended to better recognize possible different versions of the mission at first glance. The format of version numbering is free as long as it's consistent with other versions of your missions to make it easy to see which one is a more recent version.


--- Filenames ---

Although the mission name is the most visible part in Armed Assault, you should not forget about the significance of the filename. When managing missions on a server, the missions show with only their filenames in the ftp program and that's why it's smart to extend the naming format there. There are some differences, though.

1. Use small case letters only
The upcoming Linux server release may bring out a problem with upper case letters. If it's anything like in Flashpoint, an upper case letter in a filename prevents the mission from loading correctly on a Linux server. Although Linux admins can rename the mission themselves, you can save a lot of trouble this way. Remember to convert the .Sara or .Intro extension to lower case, too!

2. Use underscores in place of spaces
Linux servers may have some problems with the space bar. Underscores (_) should be used instead.

3. Leave dots to the extentions
If you have a dot (.) in the name of your mission, leave it out. If the version number uses a dot, replace it with a hyphen (-) in the filename.


Examples of filenames:
ctf_gc_50_everon_v1-06beta2.sara.pbo
dm_16_vanilla_v1-03b.sara.pbo



--- Ending words ---

This standard's purpose is to make everyone's browsing easier and faster both as server admins and as players joining a game. Selfish naming policies such as adding special characters or brackets at the beginning of the name to make your mission show at the beginning of the list only disrupts the system so I ask you to have the willpower and discipline to follow the standard, no matter how special you think your mission is. The standard is open for changes as long as it contributes to its purpose or if there is a mistake somewhere in the current edition of this post.

[Celery]

Reserved for further info.

[jerryhopper]

i'd say WOOT.

ok - im building in a 'filter' that filters out all missions that use this convention. these missions will be shown in my ArmA:Monitor website.

i hope that together we can make a 'front' and sorta Force this standart for once and for all


// more info follows on my developments.....

[Celery]

ok - im building in a 'filter' that filters out all missions that use this convention. these missions will be shown in my ArmA:Monitor website.

I was planning to make a similar list of mission makers who use the standard in the second post of this thread, like a hall of fame. I hope that most mission makers will use it in the future.

There may be demand and much honor for a person who hauls missions with non-standard names and converts both the mission and filenames and re-releases them in packs. It would seriously help make mission lists cleaner.

[5133p39]

good job, nice to see this. If i ever finish any mission i am working on, i will certainly use these rules.

[jerryhopper]

Standards will lead to conveniance in usage.
like the Addon Tags system.


i have to say: the post from celery, he doesnt discuss but SETS the standard.
And that is what i like from this, and therefore i support this.
Endless discussions on how things should be, are useless.

i'll make changes in my system ASAP so only those custom ***missions using this tag convention will be shown.
Im sure it will be a long and hard way of 'pushing' and polishing this standard.

in short, ***im supporting this wherever i can, starting with the ArmA:Tracker file-hosting and ArmA:Monitor.

[cervomix]

Excellent Idea Celery! If you agree we will post your article on our site!

[Celery]

Excellent Idea Celery! If you agree we will post your article on our site!

Only on the condition that you do it ASAP.

[jerryhopper]

dang! im getting stuck on the OFPEC tags system.
i'll put that issue a few priorities up... as its a essential thing.

OFPEC WAKE UP!

[rundll.exe]

Hmm this doesnt really go with the (cr)CTI mission naming standard we thought of ourself...

crCTI 1.0 @DVD 1.1 Central Everon
would become:

CTI@ 28 crCTI 1.0 DVD 1.1 Central Everon
or more strict
DVD CTI@ 28 crCTI Central Everon 1.0 1.1

wich is quite unreadable. and has 2 times CTI in it.

so while this is a good idea for most missions, it isnt really good for readability for complex missions with sub-mods of it.

and second, I like to sort the list by mission name so I have a list of all CTI missions that are playing. but now I get a list ordered by mod OR mission type...