Curator Guidelines

**Leading SMEs: BigBear & VanDyne**

 This document will serve as a community guideline for Curators at Sigma Security Group. Sigma Staff will always reserve the right to ask you to change aspects of your operation within reason. Failure to do so will result in your operation being deleted from the #schedule, canceled or ended. For more severe cases, "Zeus / Curator" privileges may also be suspended.

For the purpose of this document, *CURATOR* / *CURATORS* will refer to both members with the ⚡️Curator Lighting Bolt symbol and those without. Curator Tag will refer to those members who have been assigned their ⚡️Curator Lightning Bolt and discord role.

At Sigma Security Group we believe in providing the freedom for our *CURATORS* to be creative with their operations. That being said, *CURATORS* are to be reminded that we are a MILSIM unit and that they should reflect our mission and unit charter in their operations. Operations that do not suit our Mission, are classified as meme ops, or that do not adhere to our Unit Charter, may be cancelled at Staff's discretion.

## **Curator Restrictions**

* Only members with the Pay Grade of Operator or above are permitted to host or co-zeus operations. Operators are THE standard that we expect at Sigma and are therefore entrusted with hosting operations and upholding our standards.
* Contractors who have the ⚡️ tag and Curator Role, due to demotions, are exempt from this rule as the ⚡️tag and Curator Role supersedes any Pay Grade restrictions.
* CURATORS can allow Associate+ to be role-players provided that they don't use that privilege to co-zeus. Understand that the *CURATOR* will be ultimately held responsible for the role-player's actions in-game and for following the unit charter.

## **Event Guidelines**

### Operation Scheduling

* *CURATORS* shall only schedule operations when they have a COMPLETE idea of what their operation will entail (impromptu operations are excluded). Simply put, don’t hog a time slot when you have no idea what you are doing in the mission.
* *CURATORS* shall not schedule any restricted attendance ops that start, or run, within two hours of the "prime time" slot: 18:00 - 19:00 UTC or 13:00 - 14:00 ET. This means limited attendance operations may not be scheduled or ongoing between 14:00 and 21:00 UTC, or 09:00 and 16:00 ET.

* *CURATORS* must be on time for their operation. If you are not in the discord command voice chat and you have not responded to any pings 15 minutes after operation start, your slot and event will be forfeited.

* ALL Arma 3 events must be deleted from the #schedule when the AAR is over, at the latest.

### Operation Naming Conventions

* Operation titles shall have “Operation” as a prefix and a realistic operation name behind it.

Tip: Search existing IRL operation names or use an operation name generator from google if you can’t think of one.

### Operation Description

Try to provide enough information in the description for your peers to understand what your operation will entail. If you don’t want to divulge certain information to enhance storytelling, leave it out but give a general idea of what’s happening. Is it a HVT/HVI capture/kill? Destroy an asset? etc.

Note:  “Sigma has been tasked to conduct an operation in the AO” is an example of an unacceptable description. The description should minimally include a brief description of the backstory, the mission objective(s), and the enemy faction that players are expected to face.

If there are any specific player assets, write them in the description. First come first serve basis. If the person doesn’t show up, you can assign or ask around again, on a first come, first-serve basis. Please remember to write the estimated operation time with the SSG Bot when scheduling your operation.

### Operation Time Padding

* Allow **AT LEAST 1-hour** padding between scheduled Arma events.
* If you have scheduled an event before anybody else, but know there is an event after yours within the 1 hour time frame, it is your responsibility to ensure that you do not overrun your allotted time. If you happen to do so, minimize overrun and inform the next event creator immediately.

## **Discord Guidelines**

### Discord Event Pings

Ping in #arma-discussion, NOT in #general with @here or @everybody to remind everybody that your event is up. It is generally accepted that you use 1x @here and 1x @everbody, it doesn’t matter in which order. Spamming discord pings to populate your operation is punishable as per the Unit Charter. Specify in event pings if late joins are welcome or not. *CURATORS* reserve the right to disallow late joins at a later stage e.g. if the operation is about to end.

### Discord Move Privileges (Curator Tag Only)

* *CURATORS* may only use their discord move permissions to move operation participants from the Deployed Channel to the Command Channel.
* Abuse of Move privileges will result in having your Curator Tag revoked.

### Discord Priority Speaker (Curator Tag Only)

* *CURATORS* may only use their discord priority speaker ability within the command channel to ensure that the AAR is not sidetracked.

## **Server Guidelines**

### Briefing / Barbie

* Briefing is to be conducted within 5 minutes of the scheduled start time. *CURATORS* shall allow AT LEAST 15 minutes for barbie after briefing prior to step-off (unless all team members are ready before the allotted time or unless barbie is not applicable for the mission due to RP reasons)
* Make sure that mission critical items such as an arsenal (if applicable) is placed down before briefing commences.
* Briefing is to be conducted with a placed character. There will be no hover over “ghost / god” briefings.

### Server Admin Log-in

* Only Curator Tags are allowed to log-in as the server admin.
* Do not remain AFK while logged-in as server admin.
* Do not modify server or addon settings as admin without prior approval from staff.
* If you lose your Curator Tag and are found abusing the server admin log-in you are subject to disciplinary actions.

**DO NOT** share the Server Admin login details.

### Kicking from Server

*CURATORS* are primarily responsible for ensuring that all aspects of their operation adheres to the Sigma Security charter and goals. *CURATORS* are to give verbal warnings should anybody not adhere to the goals or charter. If the warning has no effect, *CURATORS* reserve the right to kick the participant from the server, within reason. Contact Sigma Staff if you don’t have privileges to kick or solve the situation maturely yourself.

### Banned AI Factions

Until further notice the following AI factions are not to be used in any operation:

* Turkish Forces (or any derivatives or sub-faction of it)

Use default AI factions with extreme caution! (FIA, CSAT, Looters, etc.) Some are very over powered.

### Controlling AI

* Control AI only for RP purposes.
* Do not abuse the AI control ability just to “punish” players.
* Avoid controlling AI if you know there is a chance they may be killed as it will cause desync on the server and not allow players to interact with any placed units. Instead, it is advised to hover over AI characters if you wish to speak as their “voice”.

### "God (OOC) Voice"

* Make sure not to hover over players while talking OOC as this will break immersion.
* Ensure that you are set to whisper at least so that you minimize your range.

### Player Controlled Enemies

* Inform your participants in the briefing in an out-of-character manner if there are player-controlled enemy assets/infantry in the operation that does not fall within RP reason.
* If *CURATORS* task players to play as enemy characters, it is their responsibility to ensure that they continue to RP within reason and that they do not ruin the fun. (i.e. player-controlled enemy sniper killing the whole echo team while providing medical is NOT ok.

## AAR Structure

ALL Sigma operations shall end with an After-Action-Review (AAR) in the Command voice channel. Barring serious circumstances, ALL operation participants are REQUIRED to attend the AAR. The AAR is hosted by the CURATOR who scheduled the operation and shall follow the following structure. Remember that all comments and feedback MUST remain constructive. Only 1 person is to be talking at any given time.

### Curator & Team Leads Section

* *CURATOR*: Ensures that all players that were in the operation are in the AAR.
* *CURATOR*: Starts the AAR with a brief explanation of what happened / what was supposed to happen during the operation then performs an evaluation of the performance of all teams and their teamwork, communication, and execution of the operation + any additional comments.
* Echo 1 Actual: Performance evaluation of teamwork, communication, and execution between teams and within his own team + any additional comments..

* Echo X / Support Team Lead: Performance evaluation of teamwork, communication, and execution between teams and within his own team + any additional comments.

### Other Participants Comments

* *CURATOR*: Provides an opportunity for other operation participants to provide comments. Time permitting, *CURATORS* may choose between top-to-bottom, bottom-to-top, or open to the floor.

### Commendations & Recommendations for Promotions

* *CURATOR*: Provides the opportunity for members to commend and recommend their peers for promotions based on their actions in the operation. Take note, *CURATORS* may NOT be recommended for promotion while hosting an operation. Demotions are never discussed in the AAR. Praise publicly, discipline privately.

### End of Official AAR

* *CURATOR*: After all commendations and recommendations are made, the *CURATOR* will verbally state the end the Official AAR. At this point, everybody is free to leave or stay behind for war stories.