Squad Server Administration

From 7th Cavalry Wiki
Jump to navigation Jump to search
This is the Document Release Information
Article Number: 7CAV-R-XXX
Scope: In Game Administrator Procedures for Squad/PS AOs
Version: Version 0.1
Effective Date: NA
Last Modified Date: DDMMMYYYY
Approving Authority: Regimental Commander
Point of Contact: Chief of Staff



Squad and Post Scriptum Game Administration

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:

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 Squad Tac1, John is teamkilling on base ”

or

“We need an MP on Tactical Realism #1, one team has completely back-capped the other and is spawn camping”

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.

Squad and Post Scriptum Rules of Engagement (ROE)

Click right 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)

  1. No team killing.
  2. Do not intentionally waste assets.
  3. No offensive behavior.
  4. No camping the main base.
  5. All Squad Leaders must have a microphone and utilize an SL kit and communicate in English.
  6. Do not play unassigned.
  7. No soloing vehicles
  8. Vehicle claims are by squad name
  9. No Squad baiting.
  10. No locked public infantry Squads
  11. 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.

  1. All Squad leaders must have a Microphone and use the SL role.
  2. Squad Leaders are to communicate and lead their section using tactical gameplay.
  3. Keep combat centered on the objectives.
  4. 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 right to show full Post Scriptum ROE

Post Scriptum – Rules of Engagement (ROE)

  1. No fratricide.
  2. No destruction of friendly equipment.
  3. No offensive behavior.
  4. Weapons safe on base.
  5. No spawn camping
  6. No blind usage of explosives
  7. Play the objectives.
  8. All Squad Leaders must have a microphone.
  9. You must join a squad and follow your Squad Leader's order.

Specific definitions of Post Scriptum – Team vs. Team Server Rules The following numbered list of all server rules are in accordance with the list above. Each rule has a subsection explaining the intent of the rule.

1.No fratricide or friendly fire


  • 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
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. No destruction of friendly equipment.


  • This includes purposeful and accidental occurrences;
  • This includes all actions other than enemy fire: crashing, using explosives and shooting;
Spirit of the rule - This rule is similar in spirit to the first rule. There's already enough concern with the enemy trying to wax that armor or aviation asset.

3. No offensive behavior.


  • No racism of any kind. any racist 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 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.

4. Weapons safe on base.


  • Discharge or firing of any weapon on base is strictly prohibited;
Spirit of the rule - This rule is meant to underline rules 1 and 2. There's no reason to fire on base.

5.No camping the uncapturable bases


  • Intentionally choking an uncapturable spawn area, blocking all areas off from escape;
  • Do not fire into or out of uncaps, unless you are getting fired at. Retaliate and move away;
  • You must be actively trying to move forward, and leave your base;
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.

6.No blind usage of explosives


  • Visual or verbal (in-game or TS3) confirmation of target is needed;
  • Tracers fired at you or teammates can be considered hostile and reacted upon;
  • Footsteps and hostile verbal communication are considered valid indicators and can be reacted upon;
  • Clearing explosives is allowed as long as you follow through;
  • Call out explosives so your teammates know what's going on to make sure you do not hurt friendlies
Spirit of the rule - These rules are designed to promote a tactical experience and prevent team kills by grenade spamming.

7.Play the objectives


  • Work with the members of your squad toward the objectives based on the current game mode;
  • Avoid merely running through the maps wildly firing at the opposing team
Spirit of the rule - This rule is designed to encourage players to work together in tactical movements to accomplish an objective. Soldiers work together as units to complete assigned missions.

8.All Squad Leaders must have a microphone


  • Squad Leaders must have a microphone to communicate with their squad and other Squad Leaders.
  • Using text chat only is not acceptable.
  • Failing to do so will result in being kicked from the server.
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.

9.You must join a Squad and follow your Squad Leader's orders


  • Commonly called "lone-wolfing".
  • You must join a Squad, if they are full start a new one.
  • Staying unassigned doesn't contribute to the team.
  • Follow you Squad Leaders orders.
  • Helps identify AFK players.
  • Failing to do so will result in a kicked from the server.
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.

Server Administration SOP

Chapter 1: 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.

Chapter 2: 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:

  • Send the rules to the player breaking ROE.
  • Communicate with that player in Global Chat their violation(s).
  • Check to make sure they understand our ROE.
  • If not responding then follow with the 1st. Warning.
  • Send the player the rules again
  • Communicate the ROE infraction(s) to them again, using Global texting.
  • If not responding follow with the 2nd. Warning.
  • Communicate the ROE infraction(s) to them again, Global texting.
  • Send the rules one last time, and tell them they are on their last warning, and that they need to follow the rules or they will be removed from the server.
  • If not responding follow with the 3rd. Warning.
  • If the issue persists, manually remove player with a temp ban. 1 hour duration.

Note:

  • 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 1 day.

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!)

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.

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

  • Racism or sexual discrimination (Gender or homophobic)
  • Disrespect of the 7th Cavalry, the operating admin or our Fallen
  • 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 inGame bugS. Bans for these reasons must be marked with “mass tk” as reason.

In Game Procedures

BattleMetrics / RCON

Of course, to use this tool you will need an account synchronized to our BattleMetrics profile. If you do not yet have access to this tool, and you qualify for having access, reach out to your Chain of Command for more help. Once you have followed the above Server Administration SOP, it may be time to take action in removing the problematic person, given you have the ability to do so.

Click to view Step by Step BattleMetrics Guide


Step One: Select The Offending Player

  • The simplest step, select the offending player




Off1.png


Step Two: Verify and Select Punitive Measure

  • During this step, it is imperative you ensure you've selected the right person. Double check their name and activity log. After you've verified the identity, select "Ban Player" or "Kick Player". "Kick Player" will only be visible if the player is currently connected to the server.




Off2.png


Step Three: Punishment Duration and Details

  • An important step - Do not forget to add as many details as possible to your BatlleMetrics Ban Report. Your Ban "Reason" should be concise, and you can add as many details as you want (Screenshot/Vid links, log snips, etc) in the "Note" subsection.




Off3.png


Step Four: Final Identity Check and BattleMetrics Submission

  • When selecting Identifiers for player bans, be sure to select unique Identifiers (Such as BattleEyeGUID, or Steam ID). This prevents wrongful kicks and bans, as often times players may have common names, or intentionally change theirs to that of another innocent person actively connected to the server. When you have done your final checks and are satisfied with your completion of the above steps, select "Save Ban".




Off4.png


Step Five: Reporting Your Actions

  • To remain transparent and keep everyone in the loop, it is up to you (the admin) to submit your ban/hot list report. Refer to the above section, "Filing A Report" for more on this.