Difference between revisions of "Squad Server Administration"
| Line 176: | Line 176: | ||
* Intentional team killing of a 7th Cavalry admin (the player has to know you an admin) | * 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. | * 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== | ==In Game Procedures== | ||
Revision as of 21:26, 20 October 2018
| 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:
- 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 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 EngagementThis 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)
Specific definitions of Squad Server Rules 1. No Team Killing.----
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.
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.----
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----
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.----
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.----
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----
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.----
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.----
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.----
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).----
Seeding Rules of Engagement (RoE)Until 20 v 20 players, the following rules apply.
Company SOP/REG/POL/DOC
|
| Click right to show full Post Scriptum ROE |
|---|
Post Scriptum – Rules of Engagement (ROE)
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
2. No destruction of friendly equipment.
3. No offensive behavior.
4. Weapons safe on base.
5.No camping the uncapturable bases
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 orders
|
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 |
|---|
|
|
Section 2: Do Not
| Click to view |
|---|
|
|
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 Two: Verify and Select Punitive Measure
Step Three: Punishment Duration and Details
Step Four: Final Identity Check and BattleMetrics Submission
Step Five: Reporting Your Actions
|
