Differences

This shows you the differences between two versions of the page.

--- tmf:mission-standards [2016/03/19 15:23] – created snippers
+++ tmf:mission-standards [2025/08/03 14:24] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+===== Mission Standards =====
 ==== Mission Name and Description are given ====
 The mission name is set via Attributes -> General (from the toolbar)
@@ Line 21: / Line 23: @@
 ==== Briefings ====
-The briefings should be clear to anyone what the mission is.
+The briefings should be clear to anyone what the mission is. It is best practice to stay with the following guidelines:
@@ Line 63: / Line 65: @@
 === Credits ===
 Don’t forget to credit yourself!
+==== Testing checklist ====
+  * **Script Errors** - Turn on the “-showScriptErrors” parameter and ensure there are no script errors. Snippers, Nick and others can help fix them. When in doubt the mission making channel on Discord is a good bet.
+  * **Mission standards** - Ensure the mission makers standards are in place.
+  * **Fireteam colour team assignments** - Ensure both fireteams in a squad are divvied up into 4 unique colour teams, two for each fireteam.
+  * **Gear assignment** - Test the assign gear scripts:
+    * Binoculars or Rangefinders? Rangefinders are given to most element leads but rangefinders have night vision built into them which is not ideal if you dont want the team to be able to see in the dark.
+    * Enough free space for radios?
+    * Ideally test as many positions as possible (in single player editor whilst previewing the U key can be used to switch between playableUnits).
+  * **Vehicle gear assignment**: Check the gear inside of vehicles/that vehicles in the area of play are locked if they shouldn’t be accessed by players.
+  * **AI** - Are the AI there and shooting back? A simple play test is enough to check that there are actually AI at the objectives and that nothing has gone wrong.
+  * **Briefing** - Check the briefing for missing information/miscommunications
+  * **Greenfor alignment** - Double check who greenfor are friendly to, as this could be problematic.
+  * **Triggers/Objectives** - Check all the triggers and objectives to make sure they are properly triggered.
+  * **End conditions** - End conditions are nice to have working properly, but optional as a session host can easily end the mission, but if you do not have your own end conditions setup. Ensure that you notify the session host on what conditions the mission should end (perhaps include in briefing if appropriate).