Update requirements for mission briefings

[TheLocalPub]

Below is my suggestion for the required briefings within missions.

Summary

Alot of missions we've played do not contain a summary, meaning while we wait to go to the role selection screen users cannot read what type of mission they are about to play, meaning if someone potentially wanted to command then they don't know what they're commanding prior to getting to the role selection screen and reading the rest of the brief.

There has been a few time I was thinking of leading, but wasn't aware of the summary of the mission, as a result when we got to role selection screen, by the time I've read enough of the brief for a summary, or almost immediately someone else takes the commanding role and my opportunity was taken, while If I had known prior to the role section it was X type of mission, I may/would have commanded.

Mission notes

Many times missions note have not contained applicable or important information.
Mission notes should contain at least:
End conditions summarised for each team, ratio, setup timer information(For which teams and how long), mission timelimits (and who wins or doesn't if it runs out), author's name.
Recommend making these a requirement.

With a recommendation mission makers should also add:
AO limit (For what teams and anything else), Respawns (For what team and how many, plus any system used to add or remove tickets),

[TheLocalPub]

Bumping this

[joewhite94]

will include this in an updated MM guide whenever we get to it, and potentially in example missions

[TheLocalPub]

Maybe you don't need the Authors name actually as it comes up in the top right hand corner on map screen if I recall.