Mission name standard

[Celery]

How about RPG for mission standard acronym (meaning RolePlayingGame)?

Why not, I added it to the list. If there are other game types that should be in the list, I'll happily receive a PM about it!

[Alpha-Kilo]

I'd like to discuss these thoughts:

1. A similar standard could also be used for SP-missions. The first abbreviation might be SP for Single Player and than mission types could be described, such as TL for Team Leader,
TM for Team Member TS for Teamswitch, SO for Solo, D for Day mission, N for night mission, etc.

2. It should be a rule that readme files should bear the same as the mission plus the word "readme".

"sp_tl_ts_d_missionname_v1-03b.sara.readme" would be the readme file for a Sp-mission, You play as team leader. Teamswitch is enabled. It is daytime. This is follwed by the mission name and version number.

Would this be useful?

[Baddo]

Hi

It is great some standards are formed.

Remember though, the simpler you can keep it, the better.

BR,
Baddo.

[Celery]

I'd like to discuss these thoughts:

1. A similar standard could also be used for SP-missions. The first abbreviation might be SP for Single Player and than mission types could be described, such as TL for Team Leader,
TM for Team Member TS for Teamswitch, SO for Solo, D for Day mission, N for night mission, etc.

2. It should be a rule that readme files should bear the same as the mission plus the word "readme".

"sp_tl_ts_d_missionname_v1-03b.sara.readme" would be the readme file for a Sp-mission, You play as team leader. Teamswitch is enabled. It is daytime. This is follwed by the mission name and version number.

Would this be useful?

I'm not so sure about sp missions. The filenames themselves would do no good unless the mission name is similar. Putting abbreviations in front of the mission name would make the mission list a little dry. I don't know, you can create a topic for larger discussion, personally I'd prefer that the mission description in the list would contain enough information to see what kind of mission it is.

Hi

It is great some standards are formed.

Remember though, the simpler you can keep it, the better.

BR,
Baddo.

I agree. The standard isn't going to get any more complicated since ease of browsing and use is our main goal.

[Alpha-Kilo]

I do agree with Celery: Abbreviations in front of the mission names would be a little dry and if mission names contain enough information the abbreviations would be unnecessary in the first place.

But the abbreviations would make missions which are similar in terms of gameplay appear next to each other in the list regardless of the mission name. I believe this would make sense and I could tolerate a somewhat dry mission list. And I personally don't think that mission names like "Operation Horseshoe" contain sufficient information.

But I do see a practical problem: The mission makers may not want to rename their missions. And if they did, many players would have the same mission appear twice in their mission folder. This confusion would certainly be counterproductive.

A possible solution may be a simple Excel sheet which contains the mission name and the abbreviations in different columns. Sorting the Excel sheet by column would help locating a specific mission type and mission makers would not have to worry about regulations for mission names.

Does this sound like a good idea?

[Sc@tterbrain]

I'm not sure if this has been addressed, sorry if it was and I missed it.

I have seen some maps that seem to use another part of the name to catagorize the specific mission maker, or type of map such as a clan training map.

Using your example:

CO 06 Kill the AI

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

I have seen it added either before or after the mission name in a few variations.

Example:
CO 06 KJ's Kill the AI
or
CO 06 Kill the AI 101st CQB Training 4a.

Hopefully I haven't lost you.

My point is what recomended when trying to put more information into the name.

~KISS? (keep it simple stupid)
~Take your credit in the damn breif?
~

[Celery]

It's best to let people know who made the map in the briefing or the mission itself, or if it's really urgent, in the mission description. Clans may have their own training maps that rarely make sense outside the clan so in that case house rules apply, it's their mission list afterall.

Of course the maker's name can be a part of the mission name, assuming that the maker knows the risk of making a silly impression.

[Jack-UK]

So long as it isnt in the mission name itself i dont really mind where it goes. The mission description is only 1 line long on the waiting screen so theres not much you can fit on there anyway, you can stick your name, or a catchphrase or something in it, or maybe a quick description of the mission if it is 'unique' otherwise i dont think its that useful.

Breifings i usually like to be clear about what to do in the mission instead of having "Made by xxxx" or whatever plastered all over it, use the notes section!!

I shall be using this standard in the future.. =)

[Sc@tterbrain]

Thanks for the repsonse. I think the idea of using notes for such stuff is a good standard. I'm using the notes section for that and to thank testers and give credit to the makers of scripts that I used.

If your really need to show an "I made this", you can always make a QUICK and pretty intro with your name on it.

[ArMoGaDoN]

Have already been using the standard for filenames since OFP, the in-game .sqm names I have until now been using the underscores too, but I will gradually conform my maps to the format specified in here.
There's a game-type missing:

AAS - Advance-And-Secure

Please add it to the list.
On multiplayer browser it will be listed as 'Team' as there's nothing else close enough to the gametype.