Members are expected to conduct themselves in a mature, respectful and professional manner while representing the unit. This applies during official operations, training events, unit meetings, public servers and any other situation where a member is clearly associated with the unit.

Respect should be shown to all members regardless of rank, role or experience. Disagreements are expected from time to time; however, personal attacks, harassment, unnecessary hostility, discrimination or deliberately disruptive behaviour will not be tolerated.

During official events, members are expected to follow the direction of their appointed leadership and contribute to the operation in a constructive manner.

Realism and immersion are important to us, but members should remember that the purpose of the unit is also to enjoy the game. Good judgement should be used to maintain the balance between professionalism, realism and having fun.

Members should avoid intentionally ruining immersion, disrupting briefings, interfering with other players, ignoring reasonable instructions or otherwise negatively affecting the experience of those around them.

Mistakes are understandable, especially during training, but repeated or deliberate disruption may result in leadership intervention or disciplinary action where appropriate.

Rank and position within the unit are intended to provide structure during training, operations and administrative matters. Rank should not be used as an excuse to belittle, intimidate or unnecessarily control other members.

Members in leadership positions are expected to set the standard through their own conduct and to treat those under their leadership fairly and respectfully.

Likewise, members are expected to respect the authority and responsibilities given to their appointed leadership during official unit activities.

Members are expected to use common sense when interacting on Discord, the unit website, TeamSpeak and other community platforms.

Friendly banter and jokes are welcome and are a normal part of the community. Members should, however, recognise when something has gone too far and respect reasonable boundaries set by others.

Members should contribute positively to the unit and help maintain an environment where people can participate in structured Milsim, improve their skills, enjoy realistic operations and have a good time with the people around them.

Members are encouraged to help one another, welcome newer members and contribute towards the continued improvement of the unit and its community.

All active members are required to maintain a minimum attendance rate of 70% per calendar month. Attendance is calculated from the official operations and events for which the member is expected to attend during that month.

If a member is unable to attend a required event, a Temporary Pass Request (TPR) must be submitted through the appropriate unit system.

A TPR informs leadership of the absence and ensures that the member is correctly accounted for when attendance is recorded.

TPRs must be submitted a minimum of two hours before the NCO briefing. The NCO briefing will usually take place approximately 30 minutes before the unit steps off for the operation.

Members should submit their TPR as early as reasonably possible rather than waiting until the deadline.

If a member knows that they are going to be late to an operation, training event or other required unit activity, they must inform their immediate leadership as soon as reasonably possible.

Members should provide an estimated arrival time where possible so that leadership can account for them when organizing personnel, assignments and the order of battle.

Arriving late without informing leadership may result in the member being marked absent or being unable to participate in the event.

We understand that real life takes priority and that members will occasionally be unable to attend. Work, family commitments, holidays, personal plans and other reasonable circumstances are acceptable reasons for submitting a TPR.

A TPR will not be considered acceptable when the reason for absence is to attend another ArmA event, operation or organized ArmA activity instead of the unit's scheduled event.

Members are expected to remain for the duration of an operation once they have committed to attending. Leaving partway through an operation without a genuine reason can disrupt the mission, affect the rest of the element and create unnecessary difficulties for Zeus and leadership.

We recognize that unexpected real-life situations happen. If a member genuinely needs to leave, they should inform their immediate leadership where possible before disconnecting.

Real-life emergencies and unexpected circumstances will always be treated reasonably.

Deliberately leaving an operation because of frustration, disagreement, an in-game death, a leadership decision or another issue arising during the event is considered rage-quitting.

Rage-quitting is disrespectful to Zeus, leadership and the other members participating in the operation and may result in disciplinary action.

If an issue occurs during an operation, members should remain professional and raise the matter through the appropriate chain of command after the event rather than disrupting the operation for everyone else.

Members are expected to use the established Chain of Command (CoC) when raising questions, concerns, requests or issues relating to the unit.

In most circumstances, a member's first point of contact should be their immediate leadership. Matters should then be passed further up the Chain of Command when they cannot be resolved at that level or require the involvement of higher leadership.

Members should make reasonable efforts to resolve routine questions and concerns through their immediate leadership before approaching higher levels of command.

For example, a member assigned to a fireteam should normally approach their Fireteam Leader first. Where necessary, the matter can then be raised with the Squad Leader, Platoon Leadership and higher levels of command.

This helps ensure that leadership at each level remains informed and prevents higher leadership from becoming unnecessarily involved in matters that can be resolved at a lower level.

During official operations, training and other structured unit activities, members are expected to follow reasonable instructions given by their appointed leadership.

Members are welcome to provide suggestions and raise concerns, but once a decision has been made, members should support that decision and continue with the task unless the instruction creates a genuine issue that requires immediate attention.

Disagreeing with a decision does not give a member permission to ignore instructions, undermine leadership or disrupt an event.

Members have the right to raise concerns regarding decisions, conduct, training, operations or other matters affecting their experience within the unit.

Where possible, concerns should be raised privately and respectfully through the appropriate Chain of Command rather than argued publicly during an operation, briefing or unit activity.

Operational disagreements that do not require immediate attention should normally be discussed after the event so that the operation can continue without unnecessary disruption.

Members should not routinely bypass their immediate leadership simply because they would prefer an answer from a higher-ranking member or disagree with an answer they have already received.

However, there are circumstances where bypassing the normal Chain of Command is appropriate. This includes situations where the concern directly involves the member's immediate leadership, where the member does not feel comfortable approaching them, or where the matter is sufficiently serious or sensitive to require higher leadership.

Members will not be punished simply for approaching higher leadership in good faith regarding a legitimate concern.

While members are encouraged to use the Chain of Command, unit leadership maintains an Open Door Policy for serious, sensitive or personal matters.

If a member believes that an issue cannot reasonably be handled through their normal Chain of Command, they may approach an appropriate member of higher leadership directly.

The Chain of Command exists to provide structure and communication, not to prevent members from speaking to leadership when they genuinely need assistance.

Members holding leadership positions are responsible for being approachable, fair and professional when dealing with those under their command.

Leaders should make reasonable efforts to resolve matters brought to them and, where necessary, pass those matters to the appropriate person further up the Chain of Command.

Leaders should not dismiss legitimate concerns simply because they are inconvenient, nor should rank be used to discourage members from respectfully questioning or seeking clarification on a decision.

During an operation, the established operational Chain of Command takes priority. Members should communicate through their assigned leadership and avoid unnecessarily contacting higher command elements when their immediate leadership can handle the matter.

If a leader becomes unavailable, incapacitated or disconnected, responsibility should pass to the next designated member in accordance with the element's succession of command.

Members taking over a leadership position during an operation are expected to clearly communicate the change and continue the mission until the original leader returns or another leader is appointed.

Wherever practical, issues should be resolved at the lowest appropriate level of the Chain of Command.

Minor misunderstandings, routine questions and simple administrative matters should not require the involvement of senior leadership when they can reasonably be handled by a Fireteam Leader, Squad Leader or another appropriate member of leadership.

The purpose of the Chain of Command is to maintain clear communication, distribute responsibility and ensure that members know who they can turn to when assistance is required.

At the end of the day, we are here to play a game and enjoy our time together. While we take our operations, training and Milsim structure seriously, ArmA is not real life and should never be treated as such.

Outside of official operations and structured unit activities, members should feel comfortable relaxing, joking around, playing other games and simply spending time with the community.

Rank, position and unit responsibilities should not prevent members from enjoying themselves or interacting normally with one another outside of official unit activities.

Military structure, ranks and procedures exist to support our Milsim experience. They provide organization and immersion during training, operations and other official activities.

Members are not expected to behave as though they are in the military at all times. Outside of situations where the unit's structure is required, members should be able to interact with each other as members of the same gaming community.

We aim to maintain a healthy separation between the structured environment of our operations and the relaxed environment of the wider community.

Rank represents responsibility within the unit; it does not determine a person's importance within the community.

Outside of official duties, members are not expected to constantly address one another by rank, follow military customs or treat higher-ranking members differently simply because of their position within the unit.

Leaders are members of the community just like everyone else. Rank should never be used to demand unnecessary formality, special treatment or authority in situations where unit structure is not relevant.

Members are encouraged to have fun, joke around and enjoy the social side of the community. Friendly banter, light-hearted conversations and messing around outside of official events are all part of being a gaming community.

There is a time and place for seriousness. During a briefing, training exercise or operation, members should respect the level of discipline required for the event. Once the event is over, members should be able to relax.

We do not expect members to remain "in character" or behave as soldiers simply because they are part of a Milsim unit.

Banter is welcome and is an important part of the community, but members are expected to use common sense and understand that everyone has different boundaries.

If someone makes it clear that they are genuinely uncomfortable with something, members should respect that boundary. A joke stops being a joke when it is deliberately continued at another member's expense after they have asked for it to stop.

Members should be able to give and receive friendly banter without using it as an excuse for genuine hostility, harassment or personal attacks.

Frustration can happen during operations. Plans go wrong, mistakes are made, people die in-game and leadership decisions will not always be agreed with.

Members should avoid carrying unnecessary frustration from an operation into the wider community. If something genuinely needs to be addressed, it should be discussed calmly with the appropriate person or through the Chain of Command.

An in-game disagreement should not become a personal disagreement between members once the operation has ended.

Members are free to play other games, spend time with friends and participate in other gaming communities. Being a member of the unit does not mean that ArmA or the unit must become someone's entire gaming experience.

We encourage members to play games together outside of ArmA and to use the community as somewhere they genuinely enjoy spending their free time.

This does not override the unit's attendance requirements for scheduled ArmA events, including the policy regarding missing a required unit event specifically to attend another organized ArmA event.

Existing members should make a reasonable effort to welcome new members into the community and help them become comfortable within the unit.

New members will not immediately understand every unit procedure, inside joke, abbreviation or expectation. Questions should be answered constructively, and genuine mistakes should be treated as opportunities to help someone learn.

A strong community depends on new members feeling like they are becoming part of the group rather than simply filling a position on an ORBAT.

No rank, qualification, billet, award or length of service makes one member inherently more important than another. Different positions carry different responsibilities, but every member contributes to the community.

Members should avoid unnecessary ego, superiority or competition over rank and position. Leadership positions exist to help the unit function, not to create status outside of the responsibilities attached to them.

The purpose of the unit is to provide an enjoyable, immersive and structured Milsim experience with people we enjoy playing alongside.

We want our operations to feel organized and immersive, our training to have purpose and our members to take their responsibilities seriously when it matters. At the same time, we are still playing ArmA together in our free time.

Take the operation seriously, not yourself. Once the operation is over, relax, have fun and enjoy being part of the community.

Campaign Operations use a staggered load-in period to give leadership sufficient time to prepare, receive the operation brief and organize their elements before step-off.

NCOs are required to load into the server 30 minutes before the scheduled hour. This time is used for the NCO briefing, coordination with Zeus and any final preparation required before personnel begin forming up.

Non-NCOs are required to load into the server 15 minutes before the scheduled hour. This provides sufficient time to prepare equipment, organize into assigned elements and be ready for the operation.

All members are welcome to load into the server from 30 minutes before the scheduled hour, regardless of rank.

Members choosing to load in early must remember that the first 15 minutes are primarily reserved for the NCO briefing.

Non-NCOs who are already present must remain quiet around the briefing area and must not interfere with or distract those participating in the brief.

Members who wish to talk while waiting should move away from the NCO briefing area and ensure that their conversations cannot be heard or cause a distraction.

The NCO briefing is reserved for the personnel specifically required to attend.

Non-NCOs should not attend, gather around or listen in on the NCO briefing unless they have specifically been requested to do so by leadership.

The purpose of the NCO briefing is to allow leadership to receive the mission plan, ask questions, coordinate their elements and clarify responsibilities without unnecessary interruptions or background noise.

If you are not required at the briefing, use this time to prepare yourself and your equipment for the operation.

Upon loading into the server, members should begin preparing their assigned kit and equipment for the operation.

Members should ensure that they have the correct weapons, ammunition, medical supplies, radios and any specialist equipment required for their assigned role.

Equipment should be prepared before the main briefing and step-off so that unnecessary delays are not created once the operation is ready to begin.

Members who load in while the NCO briefing is taking place should immediately switch to an appropriate whispering voice level when near the briefing area.

Conversations should take place away from the NCO briefing wherever possible. Even when whispering, members should be conscious of their surroundings and avoid creating unnecessary background noise.

If you want to have a normal conversation while waiting, move away from the NCO briefing area until the briefing has concluded.

The pre-operation period should be relaxed, but members are expected to use common sense and avoid behaviour that interferes with preparations for the operation.

Members should not unnecessarily run around the staging area, climb on buildings or vehicles, wander away from the designated preparation area, fire weapons, interfere with equipment or otherwise mess around in a way that causes disruption.

You are not expected to stand silently in formation while waiting. Talk with other members, prepare your equipment and enjoy the time before the operation, but remain sensible and allow leadership and Zeus to complete their preparations.

Once loaded into the server, members should remain available to their Fireteam Leader, Squad Leader or other assigned leadership.

Do not disappear across the base, take vehicles without permission or place yourself somewhere that makes it difficult for leadership to find you when personnel begin forming up.

If you need to temporarily step away from your computer, inform your immediate leadership or another member of your element where practical.

When leadership calls personnel to form up for the main briefing, members should finish their conversations and move promptly to their assigned position.

By this point, members should have their equipment prepared and should be ready to receive the final briefing and begin the operation without unnecessary delays.

During the main briefing, members should remain quiet unless asked to speak. Questions should normally be directed through the appropriate leadership after the briefing unless the briefer specifically opens the floor for questions.

The objective of the load-in period is simple: when the scheduled operation time arrives, the unit should be ready to go.

Members should use the time provided to sort their kit, resolve technical issues, receive instructions and prepare themselves rather than waiting until the last few minutes to begin getting ready.

Have fun and enjoy the pre-operation atmosphere, but do not allow your actions to delay the operation or interfere with the people working to get it started.

Field Training Exercises (FTXs) use a more relaxed load-in procedure than Campaign Operations.

All personnel are required to load into the server 15 minutes before the scheduled start time. This applies equally to NCOs and Non-NCOs.

Once loaded in, members should collect and prepare their assigned kit, ensure their weapons, radios and equipment are ready, and then wait in the designated staging area for further instructions.

Members are free to talk and relax while waiting for the exercise to begin. Unlike Campaign Operations, there is generally no dedicated NCO briefing period unless leadership or an instructor specifically requests one.

Members should still avoid unnecessary messing around that could delay the start of training. Once your kit is prepared, remain reasonably close to the training area and be ready when leadership or the instructor calls everyone together.

The expectation for an FTX is simple: load in 15 minutes prior, get your kit ready, and wait for instructions.

A Leave of Absence (LOA) is intended for members who expect to be unavailable from the unit for an extended period.

An LOA should generally be used when a member expects to be absent for a period of more than two weeks. Shorter absences from individual events should continue to be handled through the normal Temporary Pass Request (TPR) procedure.

LOAs are not requested through the Operations Center or the TPR system. Members requiring an LOA must speak directly with Unit Command.

Members requiring a Leave of Absence must speak directly with Unit Command. LOAs are handled manually by Unit Command.

When speaking with Unit Command, members should provide an approximate length of time they expect to be unavailable. An exact return date is not required if circumstances make this difficult to determine.

Once agreed with Unit Command, the LOA will be manually recorded and the member will be placed on Leave of Absence for the agreed period.

While an approved LOA is active, the member is considered temporarily inactive and is not expected to meet the unit's normal attendance requirements.

Members on an LOA are not required to submit individual TPRs for events that take place during their approved period of leave.

When a member begins an approved LOA, a Service Record entry will be created recording the beginning of their Leave of Absence.

Upon returning to active status, an additional Service Record entry will be created recording the member's return from LOA.

A member's Time in Grade (TIG) is paused for the duration of their Leave of Absence.

Once the member returns to active status, their existing TIG will continue from where it was paused. An LOA does not reset previously accumulated TIG.

Members on an LOA of one month or less will normally retain their current billet.

If an LOA extends beyond one month, the member's billet is no longer guaranteed and may be reassigned where necessary.

Reassignment of a billet is not considered a demotion or disciplinary action.

When a member is ready to return, they should contact Unit Command so that they can be restored to active status.

Attendance requirements and TIG will resume, and a Service Record entry will document the member's return.

Promotions are based on the prerequisites established for each individual rank.

Depending on the rank, requirements may include Time in Grade (TIG), required Schools, activity levels, billet requirements, leadership experience or approval.

Some ranks may only require TIG, while others require a combination of several prerequisites.

The current prerequisites for every rank are maintained on the unit's Ranks Page.

View Rank & Promotion Requirements

Members should refer to the Ranks Page when checking the requirements for their next promotion.

As an example, promotion to E-4 Specialist requires:

1. Four (4) months TIG as E-3 Private First Class.

2. Completion of:
   — Jump School
   — Air Assault School

3. No significant lapse in activity levels.

Reaching four months TIG alone therefore does not satisfy the requirements for Specialist. The required Schools and activity requirement must also be completed.

Time in Grade (TIG) represents the amount of active time a member has served at their current rank.

Reaching the required TIG does not automatically guarantee promotion where additional prerequisites are listed.

Certain ranks require specific unit Schools or qualifications before the member becomes eligible for promotion.

Members are encouraged to review their next rank ahead of time so that required Schools can be completed before their TIG requirement is met.

Some ranks require the member to maintain an appropriate level of activity within the unit.

Where there must be no significant lapse in activity, leadership may consider recent participation and general involvement when determining eligibility.

Completing the listed prerequisites makes a member eligible to be considered for promotion. It does not necessarily guarantee immediate promotion on the exact day the final requirement is completed.

Members should focus on remaining active, completing their requirements and continuing to develop within the unit.

All formal disciplinary actions within the unit are handled by Unit Command.

Leadership may raise concerns, document incidents or attempt to resolve minor issues, but formal disciplinary decisions remain the responsibility of Unit Command.

Wherever reasonably possible, we prefer to resolve issues through conversation rather than immediately resorting to punishment.

Members will make mistakes and disagreements will happen. In many cases, a conversation and an understanding of what went wrong is enough to resolve the issue.

The objective of disciplinary action is to correct a problem and protect the community, not to unnecessarily punish someone.

Unit Command will make reasonable efforts to ensure that disciplinary action is proportionate to the seriousness of the situation.

Severity, intent, previous history, the member's response and relevant circumstances may all be considered.

Minor issues will normally be addressed informally before more serious disciplinary action is considered, where appropriate.

This may include a conversation, clarification of policy or a warning.

Where an issue is sufficiently serious, repeated or cannot be resolved informally, Unit Command may take formal disciplinary action.

Possible actions may include:

— Formal Warning
— Time in Grade (TIG) Freeze
— Removal from a Billet or Leadership Position
— Demotion
— Suspension from Unit Activities
— Dishonourable Discharge from the Unit

These are not necessarily progressive steps. Serious incidents may warrant more significant action without every lesser action first being applied.

A Time in Grade Freeze pauses the member's progression towards their next promotion for a period determined by Unit Command.

Once the freeze concludes, TIG may continue from where it was paused unless otherwise determined by Unit Command.

More serious disciplinary matters may result in removal from a billet, leadership position or rank.

Removal from a billet does not necessarily require a demotion. Unit Command may determine that reassignment is the more appropriate action.

A Dishonourable Discharge results in the member being removed from the unit and is reserved for serious circumstances.

This may include serious misconduct, repeated significant violations or circumstances where Unit Command determines that continued membership is no longer appropriate.

Where practical, members involved in a disciplinary matter will be given an opportunity to explain their side before Unit Command reaches a final decision.

Providing context or respectfully disagreeing with an allegation will not itself be treated as misconduct.

Once a disciplinary matter has been dealt with, members are generally expected to learn from it and move forward.

We would much rather resolve a problem through an adult conversation than punish someone unnecessarily. Formal discipline exists for situations where that approach is not enough.