Missiontesting Checklist

The purpose of this is to list common mistakes that were found during missiontesting and that should actively be checked during missiontesting.

It also serves as a reference for missionmakers so that they can make sure their mission fulfills the requirements which makes acceptance more likely.

• mission name conforms to our naming scheme. Both the mission title and the file name. Additionally the FAMDB Name should be the same (apart from special characters,casing,...)
• No script errors (enable "Show Script Errors" in the game launcher)
• groupID and groupMarkers
  • all groups must have correct/working IDs and markers.
  • Briefing/ORBAT must show correct names.
• ending triggers should work
  • Or briefing should explain that admin has to end mission
• Briefing
  • no empty pages
  • credits should (probably) mention the titles of any included music
• Framework version needs to be up to date.
• Gear makes sense (also vehicle gear)
• Slotting:
  • Parameters?
  • Description
  • Slots that require a DLC must be marked (unless a workaround script is used).
• Default AI Skill makes sense:
  • For jungle/Tanoa missions: "Low" to "Medium" skill usually makes more sense than "High"