Zeus Guidelines

Leading SMEs: Xyrage, Patrick

This document will serve as a community guideline for Zeuses at Sigma Security Group.

At Sigma Security Group we believe in providing the freedom for our Zeuses to be creative with their operations while adhering to the unit Mission and Unit Charter.

Zeus Restrictions
Anybody at level of contractor can host or co-zeus operations. If you want help in learning how to zeus please ping @Zeus or @Curator and have them co-zeus with you.

Event Guidelines
Operation Scheduling

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

You shall not schedule any restricted attendance ops that start, or run during or into the "prime time" slot: 18:00 - 19:00 UTC.

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.

Player Controlled Assets

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.

Note that teams should NEVER be forced to crew an asset. If nobody volunteers to crew a particular asset, you must forgo this asset and plan around it.

If a person is constantly hogging an asset for multiple operations, other interested parties should be given priority to use the asset.

Operation Time Padding

Allow at least 1 hour padding between scheduled Arma events. This is to allow other Zeuses to setup and build their operation.

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

Use pings in #arma-discussion for operations in moderation i.e. with 1x @here or @everyone to remind everybody that your event is up. Zeuses reserve the right to disallow late joins at a later stage e.g. if the operation is about to end. When sending out pings near the start of an Operation in order to notify of last-minute changes, only use the @here ping.

You may use 1x @here OR 1x @everyone to ping members for a sign-up sheet, a poll on campaign choices, or for changes in important operation details. (Limited to 1 per sign-up sheet, poll, changes to operation details).

Barbie should not be called more than 30 minutes before briefing.

Discord Move Privileges (Curator Discord Role Only)

You 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 Role revoked.

Discord Priority Speaker (Curator Discord Role Only)

You may only use your discord priority speaker ability within the command channel to ensure that the AAR is not sidetracked.

Server (In-game) Guidelines

Briefing / Barbie

Late joins are not allowed to join the operation if they are not in the spawn 5 minutes prior to step-off. Exception to be granted to if the Zeus and Actual agree to halt the operation momentarily to facilitate late joins.

Briefing is to be conducted within 5 minutes of the scheduled start time. Zeuses 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.

Zeuses should try their best to provide briefings and answer questions IN CHARACTER. If there is no way to do this, you may do so in an Out of Character (OOC) manner, briefly.

Kicking from Server

You, as the Zeus, are primarily responsible for ensuring that all aspects of your operation adheres to the Sigma Security Unit Charter (Rules) and Mission. You are to give verbal warnings should anybody not adhere to the goals or charter. If the warning has no effect, please contact Sigma Staff if you can't solve the situation maturely yourself.

Controlling AI

Control AI only for RP purposes.

Do not abuse the AI controllability 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 you task players to play as enemy characters, it is your responsibility to ensure that role players continue to RP within reason and that they do not ruin the fun. (i.e. player-controlled enemy sniper killing the whole Hitman team while providing medical is NOT ok.)

Zeus Misc Notes

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

Updated: 9 May 2021