Skip to content

Quality Checklist

Jump to bottom
Mike-MF edited this page Aug 16, 2023 · 40 revisions

This page will detail what goes into the "Quality Checklist"

You should move through this list yourself and ensure it is fully ready by the time it is submitted.

Mission Reviews

Mission reviews will be checking for the following:

  • Autotest is successful
  • AI Grouping
  • Briefing is complete with no errors
  • script_component.hpp is filled out correctly
  • Difficulty is acceptable
  • Naming convention was followed
  • Slot order is correct
  • Triggers are acceptable

Additionally things like the following will also be checked.

  • init.sqf
  • initPlayerLocal.sqf
  • initServer.sqf
  • Any custom functions added

Your review is not negotiable, if a change is suggested you are expected to change it yourself and learn from it. Nobody will do it for you. With the review process taking place on Github any changes made after a review can be seen in detail. Large changes will need to be reviewed again and if the changes are close to the date it will be ran, it may not be reviewed again and updated on the server.

Before submitting your mission for a review, you should do the following:

  • Test mission objectives for successful completion (Local multiplayer and Server)

These should never be done in a single player environment. Nor should you ever assume everything "Just works" without testing it, see the ArmaQDL page for an easy method of testing in a server environment.

AI Grouping

AI Groups over 8-10 will be extremely ineffective and will not be accepted. Units will not react or follow orders until the group leader iterates through the entire group.

Single unit groups are a performance hog. It's better to have 8 units in 1 group with only one group running commander calculations than 8 groups.

Autotest

The mission autotest will help detect any issues in your current mission, ideally this should all read with green checkmarks within reason.

This states that there are no outstanding issues.

This states in the findings that there is a warning, this may be ignored or the mission master may explain how you can correct this.

If any of the boxes have failed this must be corrected before the mission is submitted for review.

Briefing

The briefing must be filled out fully before the mission is submitted. To do this navigate into functions\fnc_briefing.sqf

Here you will find the Intelligence, Equipment, Objectives & Situation sections.

Each section needs to have complete information as this will be what is posted to the details on the website.

Under Equipment, if you have 6 Arcadian GTs and 1 MH-60 you should have the following:

<br/><font color='#0ECE68'>GROUND ASSETS:</font color>
<br/>- 6x Arcadian GT
<br/>
<br/><font color='#0ECE68'>AIR ASSETS:</font color>
<br/>- 1x MH-60

If the mission has a lot of equipment adding a newline with <br/> is a line break.

The only sections allowed to be removed are stated as such in the briefing file itself.

DLC

If any mission is going to require any DLCs beside Apex and Western Sahara it must be noted in the mission parameters.

If specific slots require a specific DLC simply add it to the role description: Rifleman (Contact DLC)

Limited-Slot Non-Contracts

If your mission is designed based around a small team and the current mission master has allowed it, you must navigate to description.ext

In here you will find the following lines

class Header {
    gameType = "COOP";
    minPlayers = 1;
    maxPlayers = 36;
};
  • minPlayers should never be changed, the minimum player is always 1.
  • maxPlayers should be changed to accomodate however many slots you are allowing in the mission, i.e 15 player missions + 1 headless client means the maxPlayers would be 16.

Scripts

If you have included any scripts you found online, but did not ask if its acceptable to utilise it, do not be surprised if you're told to remove it. Performance in Theseus missions is key.

Slot Order

When previewing your mission in multiplayer the role selection screen should immediately select Blufor and list the playable slots. These should be in order.

  • Actual
  • Ares 1
  • Ares 2
  • Ares 3
  • Helios

If role select is blank and it hasn't "pre-selected" blufor, go back to the editor and copy (CTRL+C) the headless client module that came with the template. Delete them, then paste (CTRL+V) them back in. This will make blufor the primary role select instead of the headless client.

Triggers

Any triggers utilised in the mission will be checked to ensure that they will function when the time comes. However, triggers should not be enormously big if it is not necessary.

Unless a trigger is repeatable, delete it after use. (Ensure the deleteVehicle is wrapped in if (isServer) then {

if (isServer) then {
    [{
        deleteVehicle MY_TRIGGER;
    }, [], 5] call CBA_fnc_waitAndExecute;
};

Pages

Clone this wiki locally