Mission Submission SOPs - Revision history

Briland: Redirected page to Mission Submission SOP

2016-02-15T18:02:03Z

Redirected page to Mission Submission SOP

Briland at 18:01, 15 February 2016

2016-02-15T18:01:17Z

Briland at 17:33, 15 February 2016

2016-02-15T17:33:59Z

Briland at 17:30, 15 February 2016

2016-02-15T17:30:42Z

Briland at 03:16, 15 February 2016

2016-02-15T03:16:44Z

Verox at 23:02, 14 December 2014

2014-12-14T23:02:29Z

Verox at 13:20, 22 November 2014

2014-11-22T13:20:30Z

Impulse 9: Protected "Mission Submission SOPs": Official Documentation ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2014-11-22T09:04:07Z

Protected "Mission Submission SOPs": Official Documentation ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Impulse 9: Created page with "==General== Once a mission is complete and ready to be submitted, the mission maker must ensure that the Mission Requirements are fulfilled, as per the Mission Requirements SO..."

2014-11-22T09:03:45Z

Created page with "==General== Once a mission is complete and ready to be submitted, the mission maker must ensure that the Mission Requirements are fulfilled, as per the Mission Requirements SO..."

New page

==General==
Once a mission is complete and ready to be submitted, the mission maker must ensure that the Mission Requirements are fulfilled, as per the Mission Requirements SOP for ARMA2 or ARMA3. 
 
Missions which violate the Mission Requirements will necessitate a “strike” on the offending mission maker. 
Three strikes effects the suspension of automatic acceptance of new missions in lieu of quality control by the Mission Making Office. 
 
The mission maker is then expected to upload the mission to the /final directory on the game specific SRV3 (Test 1) FTP. Information regarding how to access and use the FTP is provided in the mission making forum. 
The mission maker is expected to update the appropriate mission list with the pertinent information. 
 
Updates to existing submissions must include a change log. 
Edit existing entries when providing a new version (update) of a mission, rather than creating a new entry. 
Your submission's description field must contain a summary of your briefing. At a minimum: who are you, who is the enemy, what is the mission? 
 
Submissions will be transferred to the play servers at the Mission Making Office’s leisure and review. 
Submissions which are not SOP Compliant will be rejected, and moved to the Rejected category under New/Updated. 

==To submit a brand new mission==
Access the New/Updated category of the appropriate mission list 
 
ArmA 2 Mission List / ArmA 3 Mission List 
Press the Add Mission button 
Fill out the form completely 
 
You will know your mission has been uploaded when it is moved from the New/Updated category to the Live Missions category 
 
View your new submission and look for the Follow button to the top right, click it to follow changes and comments on your submission. For reference it appears as: 
 
Posted Image 

==To submit an update to a previous version of your mission:==
Locate the existing entry in the Live Missions category or the Broken/Removed category. 
Choose Edit Mission and adjust the form appropriately for the new update. Be sure to choose New/Updated from the category drop down. (See image) 
 
Posted Image 
Note that if you create a new entry where you should have updated an existing entry, the new entry may be deleted without notice and your mission not uploaded. 

==If your submission is rejected==
Don't panic. 
Review the comments below the mission. 
Correct the mission so that it becomes SOP Compliant per the comments. 
Change the category back to New/Updated. 

==To remove your mission from the server==
Locate your mission in the Live Missions category 
Change the category to Broken/Removed 
Kindly leave a comment on the mission with the reason for removal 
The mission will be removed during the next server restart 

==Reporting broken missions==
Reference this post 
[[Category:Official Documentation]]
[[Category:Mission Maker Office]]

@@ Line 1: / Line 1: @@
 {{Depreciated}}
 {{protectbox officialdoc}}
 ==General==
 Once a mission is complete and ready to be submitted, the mission maker must ensure that the Mission Requirements are fulfilled, as per the Mission Requirements SOP for ARMA2 or ARMA3.<br />

@@ Line 1: / Line 1: @@
 {{Depreciated}}
 {{protectbox officialdoc}}
 ==General==
 Once a mission is complete and ready to be submitted, the mission maker must ensure that the Mission Requirements are fulfilled, as per the Mission Requirements SOP for ARMA2 or ARMA3.<br />

← Older revision		Revision as of 17:33, 15 February 2016
Line 1:		Line 1:
		+	{{Depreciated}}
	{{protectbox officialdoc}}		{{protectbox officialdoc}}
	==General==		==General==

@@ Line 50: / Line 50: @@
 ==Reporting broken missions==
 Reference this post <br />
-[[Category: Mission Making Office]]
+[[Category: Depreciated]]

@@ Line 50: / Line 50: @@
 ==Reporting broken missions==
 Reference this post <br />
-[[Category:Standard_Operating_Procedures]]
+[[Category: Mission Making Office]]

← Older revision		Revision as of 13:20, 22 November 2014
Line 1:		Line 1:
		+	{{protectbox officialdoc}}
	==General==		==General==
	Once a mission is complete and ready to be submitted, the mission maker must ensure that the Mission Requirements are fulfilled, as per the Mission Requirements SOP for ARMA2 or ARMA3.<br />		Once a mission is complete and ready to be submitted, the mission maker must ensure that the Mission Requirements are fulfilled, as per the Mission Requirements SOP for ARMA2 or ARMA3.<br />

← Older revision	Revision as of 09:04, 22 November 2014
(No difference)