Server Administration Procedures

This is the Document Release Information
Article Number:	***
Scope:	Server Administration
Version:	Version 1.0
Effective Date:	27 NOV 18
Last Modified Date:	DDMMMYYYY
Approving Authority:	Regimental Commander
Point of Contact:	Chief of Staff

Rules of Engagement (ROE)

Click to show full Squad ROE

Scope of the Rules of Engagement This document is a compendium of the rules of the Squad servers. If a rule is not listed in this document it does not exist and is not enforceable. Each rule will have specific definitions as well as an elaboration of its intent. By the end of this document, no question should remain as to what a rule means and how it applies to the player. Squad – Rules of Engagement (ROE) No team killing. Do not intentionally waste assets. No offensive behavior. No camping the main base. All Squad Leaders must have a microphone and utilize an SL kit and communicate in English. Do not play unassigned. No soloing vehicles Vehicle claims are by squad name No Squad baiting. No locked public infantry Squads Do not recruit for non-7Cav communities on our server (Perm Ban). Specific definitions of Squad Server Rules The following numbered list of all server rules are in accordance with the list of above. Each rule has a subsection explaining the intent of the rule. 1. No Team Killing.---- The purposeful killing of a teammate is not allowed on this server - Accidents should be avoided Intentionally Team Killing a 7th Cavalry Admin while actively engaged in admin duties will result in an instant ban from the server If you accidentally Team Kill or hurt a team member apologize immediately in All Chat (J by default) Spirit of the rule - Intentionally team killing other players is detrimental to the spirit of team play. While friendly fire is a reality on the battlefield, it is unacceptable and should be avoided. 2. Do not intentionally waste assets.---- This includes purposeful disregard and gross negligence. A purposeful disregard example: Using a logistics truck as a personal taxi to the front and dumping it. A Gross Negligence example: Flying a helicopter in a live match despite having no idea how to actually fly. Other examples at Admin discretion. Spirit of the rule - This rule is similar in spirit to the first rule. There's already enough concern with the enemy trying to destroy that armor or aviation asset. 3. No offensive behavior.---- No racism nor sexism of any kind. Any racist or discriminating remarks or names will result in an instant ban; No political or religious discussions or references including names; No disrespect towards other players or admins; No disrespect towards the 7th Cavalry Gaming Regiment; No disrespect towards the deceased; No disrespectful or offensive abbreviations; No elitist attitude towards others or taunting; No mic spamming, including music; No trolling; Spirit of the rule - The 7th Cavalry tries to create a fun environment without drama where people can just get together, play and have fun in a tactical environment. 4. No camping the Main Base---- Intentionally choking the Main Base, Main Roads or blocking all areas of egress from Main base is against the rules; There is no set distance, all Calls will be at admin discretion. If you are told to move away, you will be expected to move away as soon as possible; This rule does not apply to HAB’s/Rally points; Spirit of the rule - This rule is about fair competition. We want everyone to have fun, therefore everyone should get the opportunity to fight back. If you see that the enemy is unable to get out of their spawn area you need to fall back; if you don´t you are ruining their fun. 5. All Squad Leaders must have a microphone, utilize the SL kit and communicate in English.---- Squad Leaders must have a microphone to communicate with their squad and other Squad Leaders; Squad Leaders must utilize an SL kit in order to utilize all functions and assets of the position; Using text chat only is not acceptable; All communication must be in English; Failing to do so will result in being kicked from the squad; Spirit of the rule - It is too difficult to lead while using text chat only, voice communication must be used to be an effective leader. Not having an SL kit also prohibits the squad from placing down required assets for organized play. 6. Do not play unassigned.---- Commonly called "lone-wolfing". You must join a Squad, if they are full, wait for a new one or start a new one. Follow your Squad Leaders orders, they have the discretion to kick you from the squad for not following orders. All communication must be in English. Failing to do so will result in admin intervention Spirit of the rule -You need to be part of your squad and team to be able to contribute to the objectives, "lone-wolfing" does not contribute to that. This also helps us keep AFK players off the server. 7. No Soloing Vehicles---- Vehicles which require a Crewman slot to operate must have two persons crewing it. Any Light armored/Reconnaissance vehicle with an onboard weapon system may be subject to admin discretion. Helicopters and ALL logistical vehicles are excluded. Spirit of the rule - You should be trying to avoid the wastage of vehicle assets in Squad, if the vehicle has room for a driver and gunner, you’ll be most effective with a driver and gunner. 8. Vehicles must be claimed by Squad name.---- Vehicles are claimed by Squad name - first person to create a squad with the vehicle name, lays rightful claim to that vehicle. Naming conventions that are acceptable include - MBT, Heli, BMP. A generic name such as “Armour” is not acceptable. Spirit of the rule- First come first served is the fairest method for vehicle squads. If you want that vehicle make the squad name suit that. We can easily arbitrate this rule by looking at the squad number rather than who spawned and ran to the vehicle first. 9. No Squad baiting.---- Creating a squad and then leaving or promoting another player is not allowed. Spirit of the rule - Creating a squad out of frustration and then leaving the SL role is not acceptable. If you don't intend to lead a squad, wait until another squad opens. It wastes time and inevitably leads to a squad without an SL or just ends up being disbanded. 10. No locked public infantry Squads.---- The only squads that are allowed to Lock are: Any Vehicle Squad Admins on Duty Mortar/Logistics Squads must be named as such Any TAGGED community squad above 5 members Any squad during the staging phase waiting for friends (must be unlocked by Live) Spirit of the rule - We want to make sure that new players have a place to play on our server. Locked squads not only prevent that but team cohesion is damaged when there are 10+ 3-4 man locked squads. 11. Do not recruit for non-7Cav communities on our server (Perm Ban).---- Do not recruit for external communities on this server. This will be considered disrespect to the 7th Cavalry Gaming Regiment and punishable by permanent ban. Seeding Rules of Engagement (RoE) Until 20 v 20 players, the following rules apply. All Squad leaders must have a Microphone and use the SL role. Squad Leaders are to communicate and lead their section using tactical gameplay. Keep combat centered on the objectives. No building of Observation Towers during the seeding phase. Company SOP/REG/POL/DOC Document Number Policy Letters 7CAV-E2-001 Makeup Section Practice 7CAV-E2-002 Official Of The Month 7CAV-E2-003 Platoon / Company FTX's 7CAV-E2-004 Section / Platoon Reports 7CAV-E2-005 Roll Call Posting 7CAV-E2-006 Operation Slot Priorities 7CAV-E2-007 Echo Practice Times 7CAV-E2-008 Squad Rules of Engagement Document Number Document 7CAV-E2-007 Squad Admin Info & Commands

Click to show full Hell Let Loose ROE

Scope of the Rules of Engagement This document is compendium of the rules of the Hell Let Loose servers. If a rule is not listed in this document it does not exist and is not enforceable. Each rule will have specific definitions as well as an elaboration of its intent. By the end of this document, no question should remain as to what a rule means and how it applies to the player. </noinclude> Hell Let Loose– Rules of Engagement (ROE) No intentional team killing/griefing No offensive behavior or names. (Ex. racism et al) No spawn camping (For HQ only) All squads must have an OFFICER Squad Leaders and Commanders must have a microphone No Solo Tanking Ever or Solo Locked Recon Seeding - Combat Strength Under 20 vs. 20 The following rules apply for seeding: The middle sector point will be the only playable objective Combat Area - only the two rows/columns (map dependent) that contain the playable objective Armor crewman roles may not leave the HQ. No use of Artillery until the 20v20 (40 Total Players) has been reached. In-game squad leaders are responsible for reporting any infraction from their in-game section to a 7th Cavalry Admin (MP) or Member with tags to enforce these rules. Spirit of the rule - When both teams have less than 20 players, both teams agree to only play over the central sector (map dependent) with reduced combined arms to promote a better player experience until there are enough players to seed vanilla gameplay. Specific definitions of Hell Let Loose – Team vs. Team Server Rules The following numbered list of all server rules are in accordance with the list of above. Each rule has a subsection explaining the intent of the rule. 1 No intentional team killing/Griefing Commonly called 'TK'ing' or 'Team Killing' - the purposeful or accidental killing of a teammate - is not allowed on this server. Do not team kill, this is grounds for instant banning. Intentionally Team Killing a 7th Cavalry Admin while actively being an admin will result in an instant ban from the server. If you accidentally Team Kill or hurt a team member apologize immediately. Intentional destruction or disabling of friendly equipment, e.g., getting vehicles stuck so others can not use them. Spirit of the rule - Intentionally team killing other players or griefing teammates is detrimental to the spirit of team play. While friendly fire and equipment loss is a reality on the battlefield, it is unacceptable and should be avoided. 2 No Offensive Behavior No racism nor sexism of any kind. Any racist or discriminating remarks or names will result in an instant ban. No inappropriate discussion, political or religious discussions or references including names. No inappropriate usernames are allowed. IE. Sexual, Racist, Inappropriate/Offensive in nature. No disrespect towards other players or admins. No disrespect towards the 7th Cavalry Clan. No disrespect towards the deceased. No disrespectful or offensive abbreviations. No elitist attitude towards others or taunting. No mic spamming. No trolling. Spirit of the rule - The 7th Cavalry tries to create a fun environment without drama where people can just get together, play and have fun in a tactical environment. 3 No Camping Headquarters Bases Intentionally choking an uncapturable spawn area, blocking all areas off from escape. Enemy Combatants may engage players using artillery as artillery pieces are located in HQ The HQs may only be engaged freely if the final Objective is active and located in its sector. You cant attack the north HQ spawn if the objective is in the south HQ sector. You must be actively trying to move forward and leaving your base unless utilizing artillery. No camping the HQ behind enemy lines, play the objectives. Spirit of the rule - This rule is about fair competition. We want everyone to have fun, therefore everyone should get the opportunity to fight back. If you see that the enemy is unable to get out of their spawn area you need to fall back; if you don't, you are ruining their fun. The exception would be if the game mode forces you to move in to spawn. 4 Each Squad Must Have an Officer/Squad Leader All Squads in game must have even either a Squad Leader or an Officer Kit. The 7th Cavalry Regiment encourages focused team-play mechanics that are synonymous with the in-game mechanics of Hell Let Loose. Not having an Officer/Squad Leader prevents the section from having outposts and from placing Garrisons. We believe requiring an Officer/Squad Leader to be in each section enriches the server environment and contributes to a high level of game play and enjoyment. 5 All Squad Leaders And Commanders Must Have A Microphone Squad Leaders must have a microphone to communicate with their squad and other Squad Leaders. Commanders must have a microphone to communicate with their team and other Squad Leaders. Using text chat only is not acceptable. Spirit of the rule - It is too difficult to lead while using text chat only, voice communication must be used to be a effective leader. 6 No Solo Tanking or Solo Locked Recon Do not use armor until teams are 20 v 20. Armor must be occupied by at least 2 people. No "lone-wolfing" armor. Armored sections must follow orders of Team Commander. No Solo Locking recon, all recon must be open or have a sniper Spirit of the rule - Armor is a vital asset to each team. Before there are 20 people on each team, it can be annoying to have an armor asset decide the course of the battle due to low population. To make best use of the armor, there needs to be 2-3 players in each tank. Locking squads prevents players from possibly having the experience they joined our server for. 7 Seeding - Combat Strength Under 20 vs. 20 (40 players total) The middle sector point will be the only playable objective. Combat Area - only the two rows/columns (map dependent) that contain the playable objective. Armor crewman roles may not leave the HQ. In-game squad leaders are responsible for reporting any infraction from their in-game section to a 7th Cavalry Admin (MP) or Member with tags to enforce these rules. No use of Artillery until the 20v20 (40 Total Players) has been reached. Spirit of the rule - When both teams have less than 20 players, both teams agree to only play over the central sector (map dependent) with reduced combined arms to promote a better player experience until there are enough players to seed vanilla gameplay.

Click to show full ARMA ROE

Scope of the Rules of Engagement This document is to serve as a complete compendium to the rules of the servers. This document contains all rules of the server in which the document was written for. If it is not listed in this document it does not exist and is not enforceable. Each rule will have specific definitions of the rule as well as elaborating the specified intent of the rule along with examples to help clarify the rules true intent. By the end of this document, no questions should be remaining as to what the rule meant and how it applies to the player. </noinclude> Arma 3- Public Server Rules No fratricide or destruction of friendly equipment. No offensive or disruptive behavior All support assets must be on call and TeamSpeak 3 You must play your role and cooperate with your team Specific definitions of ARMA 3 - Public Server Rules The following is a numbered list of all server rules that are in accordance to the list of section 2. Each rule will have a subsection explaining the intentions of the rule and specific cases of the rule. 1. No fratricide or destruction of friendly equipment Fratricide is the killing of one's own forces in war and is used to describe 'friendly fire', or commonly called 'TK’ing' or 'Team Killing'. This means the purposeful or accidental killing of another player or friendly equipment is not allowed. This also means that acts of “revenge killing” are against this rule. The only action a player needs to take against someone who killed them is reporting said team killer to our Military Police or a Game Admin. Spirit of the rule - This rule is a common rule for team-based First Person Shooter games. Team killing is universally considered in bad taste and bad form. The idea is to have fun and not to have to worry about a chaotic free for all. 2. No offensive or disruptive behavior. No racism nor sexism of any kind. Any racist or discriminating remarks or names will result in an instant ban. No political or religious discussions or references including names. No disrespect towards other players or admins. No disrespect towards the 7th Cavalry Gaming Regiment. No disrespect towards deceased 7th Cavalry members. No disrespectful or offensive abbreviations. No elitist attitude towards others or taunting. No mic spamming. No trolling or griefing. Discharge or firing of any weapon on base is strictly prohibited. No vehicles parked on the runway or landing pads. Spirit of the rule - The 7th Cavalry tries to create a fun environment without drama where people can just get together, play, and have fun in a tactical environment. 3. All support assets must be on call and Teamspeak. This means the pilot/operator of any aircraft, artillery, mortars, or UAV. TeamSpeak 3 meaning 7th Cavalry's TeamSpeak 3 server. They must also have a working microphone, and be willing to coordinate over TeamSpeak. Support assets, except tanks, are not to engage the enemy on their own accord. Enemy air assets and enemy anti-air are the only exceptions to this rule. They are allowed to be engaged to make way for safe transport to the AO for friendly troops. All attack aircraft are to maintain a safe holding area, pattern, or stay on base until called in to maintain the longevity of the aircraft. Artillery, including mortars, must remain silent until called to fire by infantry. Assets in immediate danger that need to act against danger can defend themselves to preserve their lives or asset, but shall not provoke the engagement. Spirit of the rule - This rule is meant to help preserve some enemy for friendly infantry to still fight when there are powerful support assets like aircraft or artillery in play, as well as the coordination of those assets with ground forces to foster organized gameplay. Fire support and other force multipliers, unless specifically approved above, are on call until a call for fire is made. This is done to balance the power of support assets with the infantry. 4. You must play your role and cooperate with your team. “Lone wolfing” should be avoided whenever possible. Follow the instructions of your Squad Leader and/or mission commander. Play the role you’re slotted for. If you wish to change your role you must reslot. For example, if you were a pilot and wish to fight on the ground you must reslot as an infantryman. No AFK’ing in limited slots. Spirit of the rule - “Lone wolfing” can cause enemies to spawn in remote locations away from the main group and thus detract from server resources, as they are limited. “Lone wolfing” should be avoided when possible to ensure cohesion across all roles, to help foster tactical realism and organized gameplay, and to ensure the mission file is running as intended. Arma 3 - Training Server Rules The Training Server is first and foremost an area for 7th Cavalry members to practice skills that will be utilized in either operations or public spaces. There will always be a 7th Cavalry member responsible for the server. No public members. Specific definitions of ARMA 3 - Training Server Rules 1. The Training Server is first and foremost an area for 7th Cavalry members to practice skills that will be utilized in either operations or public spaces. Simply put: RTC > Unit Training > Fun-time. The above hierarchy of use shall always be observed, however, this does not mean that two groups can't be doing two things at once. Spirit of the rule - Simply as the hierarchy of use states, the training server is first and foremost the 7th Cavalry 1st Battalion training server; everything else comes secondary to this mission. RTC will always have priority of this server during the scheduled training times (check with RTC for currently scheduled bootcamps), as they are responsible for replenishing and growing the ranks of the 7th Cavalry, and they will not be hindered in this mission. 2. There will always be a 7th Cavalry member responsible for the server. Whenever the server is running, there will be at least one member that is in charge of the operations of all members in the server. Generally speaking, this member will be the operational admin or the training admin. This member is responsible for all conduct on the server. Spirit of the rule - Responsibility of use of 7th Cavalry assets always needs to fall on someone. As such, before entering the server as a group, either the ranking officer/NCO assumes this responsibility, or a pre-designated member of the group needs to be responsible (such as when there are NCOs running trainings for officers, etc). 3. No public members. No public members. Members of allied clans are allowed to attend events if first approved by the regimental commander. Spirit of the rule - Being as the servers are for 7th Cavalry members, as a matter of privilege for those of the yellow and black, public players are not welcome in these servers. Allied clans are allowed to visit the grounds if prior to the event the Regimental Commander provides written permission for them to attend.

Chain of Command

Generally speaking the highest ranking 7th Cavalry member on the server is responsible for administration. They hold the responsibility with their rank, but may choose to delegate that responsibility to any lower ranked admins if needed. This goes in all cases except for when there is an MP presence in the server. The MP stands higher in the administrative Chain of Command. Their rank has no reflection on this Chain of Admin Command, they are to be considered the go-to people for rules and regulations in game.

Duties

As an Admin, you may be called upon at any time to deal with an issue in game. This is why it is a Responsibility rather than a Right. If you have administration rights, you can be expected to be called upon to utilize them.

Keep calm and in control.

Always stay calm. Administering at times can be hectic, not only will you have the problem player(s) at hand but most of the time you will have public or even Cav members yelling and or trying to tell you to "Just ban him, or just kick him" this will raise your aggravation level, stay calm, ask the members/visitors to let you do the job you need to do. We have a protocol, and that is what makes our servers so good.

Filing a report

To successfully take administrative action means you need to file a report on the administrative actions you have taken to ensure that any and all ban appeals can be dealt with in a timely manner and with appropriate documentation. It is the administrator's responsibility to write this report in the correct forum section. This goes for any and all administrative personnel for any and all bans.

The correct forum sections are:

• Player Hot List : https://7cav.us/forums/player-hot-list.102/
  • Player Hot List Format: https://7cav.us/threads/player-hot-list-posting-format.2225/
• Ban List : https://7cav.us/forums/banned.100/
  • Example of a Ban Report: https://7cav.us/threads/ban-report-example-plus-explanations-do-not-copy-paste.13562/

Responsibilities & Admin Rules

• ALL 7th Cavalry Regiment members, from Private to General, have varying degrees of responsibility when it comes to administrating our servers. This means that regardless of your rank or stature as a 7th Cavalry member, you are to assist at all times necessary [to your ability] in administrating our game servers;

• As a 7th Cavalry Regiment member, you will not ignore or tolerate any rule violations if witnessed while you are in the server;

• All rule violations will be dealt with immediately. This means no waiting until the round is over because you are having a good game. It is your duty as an admin to deal with rule violations as they occur;

• If you do not have admin rights, then you are not to call out any rule violators in a server. You can only state the rules in the game chat or text. At that point, find an admin who does have rights;

It is the duty of the highest-ranking member in server to handle the administrative process. This person can request help from other admins if needed. DO NOT IGNORE A REQUEST TO ADMIN. If you are asked to admin, then you help admin;

• Members that have not completed the Server Admin Course cannot hold a position as an admin;

• Always conduct yourself professionally while in-game and while pulling duty as admin;

• Remember to treat all players in-game like you yourself would like to be treated;

• Admins must follow the rules of each game just like any other 7th Cavalry Regiment member or public (pubber) player without exception.

• If you witness a 7th Cavalry Regiment member breaking rules, you must make note of the event and bring that to the attention of the 7th Cavalry Regiment Military Police.

• If you do not know how to deal with a rulebreaker on the server or the situation needs more than one admin seek help of a MP.

Calling an admin or MP

When calling for help do not only say “we need an admin” but add further information (if possible)...

• Where?
  • TS3, Arma3 Tac1, Post Scriptum, Squad,...
• What?
  • Teamkiller, hacker, pilot not on TS3,...
• Who?
  • “insert player name here”
• When/How long?
  • Currently happening, 5min ago,...

Example: Wrong request for an Admin/MP:

“We need an admin”

Example: Correct request for an Admin / MP:

“We need an admin on Arma 3 Tac2, John is team killing on base ”

or

“We need an MP on Tactical Realism #1, Mr Bravo is setting explosives on friendly vehicles exiting base”

If you do not include any further details the admin/MP will have to ask for them and does not know what to look for once he is on the server.

When looking for an Admin/MP do NOT jump into “knock” offices or named offices (Platoon, Company, Battalion, Regiment, Interview channels), always Privately Message the admin/MP in this case.

Attitude and Dealing with Our Visitors

Of course, we want to maintain a professional and friendly environment for all guests of our community. Refer to the following for some advice on administrative duties, as it can be overwhelming sometimes!

Section 1: Do

Click to view

Follow the SOP Policies and Code of Conduct when admining. These are your tools, those rules and policies are the backbone of the 7th Cavalry Gaming Regiment Be friendly We are not war mongers who come into the games to crack skulls. We are only here to make sure our server rules are followed by everyone. The more they enjoy the atmosphere the more likely they are to join the Cav, which is what our pub servers are for, recruitment. Keep in mind some players are new to the games they are in If Johnny gets Arma 3 for Christmas, and finds our server he is going to break rules. It is our job to notice the difference and treat each player differently, just because the last player you had to warn out purposely did not listen to you does not mean the next one is the same. Always stay calm. Admining at times can be hectic, not only will you have the problem player(s) at hand but a lot of time you will have public or even Cav members yelling and or trying to tell you to "Just ban him, or just kick him" this will raise your aggravation level, stay calm, ask the members/pubbers to let you do the job you need to do, we have a protocol, that is what makes our servers so good. Ask someone to help if it gets to be too much Sometimes there are too many players breaking rules at once for one admin to handle, just try to handle one at a time, usually the one who is causing the most unrest in the server. Say you are in Arma 3, you have been called in to handle a pilot that is not following the TS3 policy and is not on TS. Then a player starts mowing down players at base, you would then switch your attention to the team killer, then come back to the pilot not in TS. Enter and admin the game servers when needed If you cannot get away from something please get in touch with someone who can help. There is nothing worse than having a problem player in game and no help to take care of it. If you are just doing paperwork or hanging around, and notice a server without an admin, hop in and make your presence known. Let our members and public players alike know that we are admining the servers, keeping them safe and fun.

Section 2: Do Not

Click to view

Under no circumstances do we call out a Cav member in ANY public chat, voice or TS3 If a Cav player is breaking the rules, get an MP or if an MP is not available get an officer from that game to handle it. Do not allow yourself to be trolled Many times players will argue the rules for as long as you allow it, this takes your focus off the job you are in the server to do. Players love to push the limits, do not allow them to. Do not take anyone's word when issuing warnings or bans Always have eyes on when using these commands. Just remember if you didn't see it, it didn't happen. It is your name on the ban report and the COS will ask you first if something is not correct.

Procedures

WARNINGS In order to be effective, you need to witness the violation yourself and you need to communicate. Once you've seen an infraction taking place, you need to identify the player.

There are numerous ways of communicating and you must use all of them: text, audio, warnings, etc. The player might not be aware of our rules and probably doesn't bear any ill will towards our community or its guests.

For that reason, it is our duty to make sure that they are aware of our rules and their violation of said rules before driving them away from the server. You never know when someone might be a valuable asset to the 7th Cavalry and so you should act like anyone on the server is a potential recruit waiting to be swooned by our behavior.

Always communicate by text as this is recorded in the logs, this allows queries to be looked at and transcripts to be read should there be an appeal or complaint. That is why there are certain steps to be followed while administering a server:

1. Send the rules to the player breaking ROE.
2. Ensure the player understands their violation(s).
3. Check to make sure they correct their behavior.
4. If not, follow with the first warning.
5. Send the player the rules again.
6. Ensure the player understands their violation(s) again
7. If not responding, follow with the 2nd warning.
8. Ensure the player is aware of the infraction(s) and understands our ROE.
9. Send the rules one last time and inform the player that they will be removed from the server if they do not follow our ROE.
10. If not responding, follow with the 3rd warning.
11. If the issue persists, manually remove player with a temp ban. 1 hour duration.

Note:

• If the player doesn't get it after your third attempt, he/she gets tempbanned and it is on them, not on us. There is also no specific timing to respect between the steps. Be reasonable and communicate with the player.
• If the same player comes in after an hour temp ban and continues his disregard for our rules, on their next warning, remove said player for temp ban of 2 hours.
• This cycle continues until the operating admin thinks that this player is unwilling to follow the SOP’s.

Kicking players is only allowed under following circumstances:

• Player is afk and blocking an important role (i.e. Squad Leader, AT) -> check if the player is reacting before kicking (i.e. “Sloth, are you afk?”)
• Player is active and refusing to use an important slot (i.e. Squad Leader using his Squad's Marksman kit) -> warn him to use his role first
• Player is acting SL and is not communicating on voice communications channels (No Microphone)
• Player is spamming the microphone in game and was asked to stop beforehand
• Player has an offensive or derogatory username (Make sure to let them know they're more than welcome to return after changing their name!)

There are ONLY 3 Reasons to ban a player WITHOUT using the above SOP:

1. Racism or sexual discrimination (Gender or homophobic)
2. Disrespect of the 7th Cavalry, the operating admin or our Fallen
3. Intentional team killing of a 7th Cavalry admin (the player has to know you an admin)

• While in the course of doing their duty admins must have made themselves known by first making contact with the player and the team kill must be directed at the admin. All other issues fall under our admining SOP and are not to be deviated from for any reason. Permanently banning someone is a last resort. If you ever need to permanently ban someone, you must fill out a Ban Report form immediately after issuing the ban.

You can ban a player for mass teamkilling if the following requirements are fulfilled:

• you witnessed the incidents yourself
• the player received a warning to stop prior to the ban (!warn command)

The incidents must be witnessed to avoid false bans for pilots being shot down or in-game bugs. Bans for these reasons must be marked with “mass tk” as reason.