TG Mission Creation Standards *README*

**Shiner** · 08-07-2007, 09:07 AM

One of my goals in assisting the TG community to produce the finest quality of ArmA missions available is to establish a set of community developed standards. These standards are certainly voluntary, but I think a little investment from each mission creator to adhere will help improve the quality and marketability of TG's in-house missions. We are also looking in the future to develop and distribute TG mission packs and will want the submissions to be as uniform as possible.

I am requesting that we adopt the following subject to your feedback:

File Naming Conventions:
(TGMissionTypeSize)_MissionName_version.Sara.pbo || (TGTvT48)_Domination_v01a.Sara || (TGCo11)_SniperHunt_v1-1.Sara

Mission Naming Conventions:
(TG-MissionType-Size) MissionName by Author || (TG-TvT-48) Domination v01a by |TG|Shiner || (TG-Co-11) SniperHunt by SniperH

TG Intro: A short 5-10 second low-overhead scripted intro similar to evolution. I have posted the initial scripted intro and a request for submissions here.

Briefing Notes (anywhere):

Code:

This mission was developed by XYZ who is a member of the TacticalGamer.com community.  TacticalGamer is the PREMIERE online community for mature gamers.  Visit www.tacticalgamer.com for more information and for access to our servers.

Mission Description: Please create a paragraph or more mission description in a text file (description.txt) in the root folder of you mission. This might explain the "actors", the "setting", "story" or the "objectives". This description might ultimately be used to populate a mission hosting reference database, so think what you would want to be posted that would get other players interested in your mission.

Taxi · 08-07-2007, 11:11 AM

Will do, btw I understood from the BAS f manual that points in version numbers in filenames are best avoided (something to do with being able to read only one point in a filename or something). I use - so for instance 0-1-6.

**Shiner** · 08-07-2007, 11:16 AM

Good point Taxi, I have removed the period from my example above. No need to change how you version your files either, those dashes are fine.

Morticus · 04-23-2008, 03:04 PM

Hi guys i have new mission thet would fit great for this Arma Server.
Co21_Covert_landing_v1DTatical.Sara.pbo
you can get it from my site
all the WWW dot morticus dot homecall.co.uk/
Thanks guys

Morticus

08-07-2007, 09:07 AM	#1 (permalink)
Shiner Join Date: Jul 2005 Location: Dallas, TX Age: 30 Posts: 2,247	TG Mission Creation Standards README One of my goals in assisting the TG community to produce the finest quality of ArmA missions available is to establish a set of community developed standards. These standards are certainly voluntary, but I think a little investment from each mission creator to adhere will help improve the quality and marketability of TG's in-house missions. We are also looking in the future to develop and distribute TG mission packs and will want the submissions to be as uniform as possible. I am requesting that we adopt the following subject to your feedback: File Naming Conventions: (TGMissionTypeSize)_MissionName_version.Sara.pbo \|\| (TGTvT48)_Domination_v01a.Sara \|\| (TGCo11)_SniperHunt_v1-1.Sara Mission Naming Conventions: (TG-MissionType-Size) MissionName by Author \|\| (TG-TvT-48) Domination v01a by \|TG\|Shiner \|\| (TG-Co-11) SniperHunt by SniperH TG Intro: A short 5-10 second low-overhead scripted intro similar to evolution. I have posted the initial scripted intro and a request for submissions here. Briefing Notes (anywhere): Code: This mission was developed by XYZ who is a member of the TacticalGamer.com community. TacticalGamer is the PREMIERE online community for mature gamers. Visit www.tacticalgamer.com for more information and for access to our servers. Mission Description: Please create a paragraph or more mission description in a text file (description.txt) in the root folder of you mission. This might explain the "actors", the "setting", "story" or the "objectives". This description might ultimately be used to populate a mission hosting reference database, so think what you would want to be posted that would get other players interested in your mission. __________________ Last edited by Shiner; 08-09-2007 at 10:21 AM.

08-07-2007, 11:11 AM	#2 (permalink)
Taxi Join Date: Mar 2007 Posts: 212	Re: TG Mission Creation Standards README Will do, btw I understood from the BAS f manual that points in version numbers in filenames are best avoided (something to do with being able to read only one point in a filename or something). I use - so for instance 0-1-6.

08-07-2007, 11:16 AM	#3 (permalink)
Shiner Join Date: Jul 2005 Location: Dallas, TX Age: 30 Posts: 2,247	Re: TG Mission Creation Standards README Good point Taxi, I have removed the period from my example above. No need to change how you version your files either, those dashes are fine. __________________

04-23-2008, 03:04 PM	#4 (permalink)
Morticus Join Date: Apr 2008 Posts: 1	Re: TG Mission Creation Standards README Hi guys i have new mission thet would fit great for this Arma Server. Co21_Covert_landing_v1DTatical.Sara.pbo you can get it from my site all the WWW dot morticus dot homecall.co.uk/ Thanks guys Morticus

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Sponsored links

Sponsored links