Vercetti
2012-03-17, 01:26
Admin Rules and Server Behavior
Table of Contents
1. Introduction
2. Server Rules, definitions and punishments:
2.1 Cheating
2.2 Suspected hacker
2.3 (MAV) Glitching
2.4 Swearing
2.6 Baserape
2.7 Statpadding
3. Starting servers
4. Balancing servers
5. Action if OG members are breaking server/community rules
1. Introduction
As you all might know, we try to provide members of our community, as well as for the entire gaming community, a nice and pleasant environment to play games. We do this by providing servers for our members, on which they are granted admin rights, to keep the servers clean from unwanted guests.
We like to offer quality over quantity. We have quite a few servers, in order to try to accommodate every member’s wishes regarding to map rotation and settings. Of course we would like our members to be able to play on full servers when they come home from work/ school or have a day off. Therefore we also have to make a combined effort to fill up our servers with players. If we do this every day, servers will fill up easier and easier every time we try. Who doesn’t like to play a round on a full server, clean from cheaters, glitchers, whiners and other unwanted guests?In order to achieve our goals, we have created a rulebook for Old Guys members regarding the rules on the server, and how to react when a rule is being breached, We ask all Old Guys members to follow the rules, and warn players who are not.
2. Server Rules, definitions and punishments:
2.1 Cheating
Obvious Aimbotter
Example
People who achieve kills of 30+ in 2 minutes. Â*Use your commonsense however you must have no doubt in your mind that the player is hacking. Â*If you only suspect him then please refer to section ‘Suspected Hacker’
Action
1. Ban without warning.
2. Name should be posted on OG Forums for perm ban.
In-game Command
Temp ban - !tban 60 playername Aimbot
2.2 Suspected hacker
Suspected Aimbotter
Example
Unfortunately there are people who are good at the game under normal circumstances and use cheats to give them that extra edge. Â*These people are generally referred to as ‘togglers’ meaning they switch their cheat on and off and actually have a skill for hiding the use of it.
Action
1. Observe score.
2. Note play style.
3. Check Battlelog (http://battlelog.battlefield.com), pbscreens.com (http://pbscreens.com/database.php), Metabans (http://metabans.com). and BF3 Stats (http://bf3stats.com). Â*
4. Look for suspicious stats. Â*
5. Ask a staff member to jump on the server. Â*
6. Post proof or suspicion on OG bans/complaints forum section for Staff and fellow members to deal with retrospectively.
Note
If the player is not obvious please do not ban the player without taking the steps detailed above.
2.3 (MAV) Glitching
Example
(Using an MAV to) reach a normally inaccessible position.
Action
1. Identify the culprit by hovering aim over spawn beacon to show player name.
2. Join snipers squad to 3rd person view sniper.
3. Once identified kick player who is MAV glitching.
4. If they return and repeats the offence, tban the player.
5. Kill people who spawn on beacon stating the reason.
In-game Command
To kick - !kick playername MAV GLITCHING
To Temp Ban - !tban 60 playername MAV GLITCHING
To Kill - !kill playername DO NOT SPAWN ON MAV GLITCHED BEACON
Note
Spam bot already warns people therefore you are free to kick MAV glitches without chat warning.
We expect DICE to address MAV glitching in upcoming game patch.
2.3.1 M26 Glitching
Example
Abusing the M26 heavy barrel glitch
Action
1. Kill the offending player with message No M26
2. If continued abuse, kick player
3. Re-joined and continued abuse then ban the offending player.
In-game Command
To kick - !kick playername NO M26
To Temp Ban - !tban 60 playername NO M26
To Kill - !kill playername DO NOT USE THE M26
2.4 Swearing
Example
A player is directly abusive or verbally attacks another player using offensive language. Â*Please use your judgment here, you are over 18 and know what right and wrong is. Â*OG servers are not a nanny state and the game is 18+. Â*Non excessive impersonal swearing can be overlooked and so can friendly banter.
Action
1. Warn the player who is being abusive.
2. Kick the player if they do not immediately stop abuse.
3. If they rejoin server and continue abuse, temporarily ban the player.
In-game Commands
To warn - !say warning text
To kick - !kick playername reason
Temp ban - !tban 60 playername reason
2.5 Racism
Example
Any racist or derogatory comments about another person’s religion or ethnic background.
Action
Instant temp ban without warning or reprieve. Â*Player name must be posted on OG Bans/complaints forum for perm ban to be given.
In-game Command
To temp ban - !tban 60 playername Racism
2.6 Baserape
Example
To kill a player within their fixed spawn area. Â*Metro is a good example where if a Russian team member kills US team members beyond the C lockers into the US spawn.
Action
1. Kill the offending player stating the reason.
2. If the same player continues to break the rules, kick him stating the reason.
3. If the same player re-joins the server and continues to break the rules, issue a permanent ban stating the reason.
2.7 Statpadding
Example
1. Players who buff their stats in an artificial manner such as resupplying a friend without engaging the enemy.
2. Joining empty OG server just to take flags and agreeing not to kill one another.
3. Arm and disarm bombs without killing one another.
Action
1. Temp ban
2. Post offenders name in Bans/Complains forum section for perm ban.
In-game Commands
4. To Temp ban - !tban 60 playername reason
3. Starting servers
Example
If you’re on a full server please look to see what other OG servers you could start, it only takes 6 members on the same server to really get it going.
Considerations
1. Try to move yourself to the opposing team if it’s unbalanced.
2. Warn players not to use vehicles at all under 10 players, if ignored kill the offending player stating reason.
3. Do not take the last remaining flag if server is less than 50% full.
4. Don’t play ‘hardcore’. If you play rush, let the attackers also blow up a MCOM , hold them at the last ones. If attacking, don’t role-over the defenders if your team is better.
5. Try to have some fun while filling up, train yourself using for example only pistols. Agree this with other people on the server.
In-game Commands
To forcibly switch teams (does not count as death) - !fmove playername
To warn - !say NO VEHICLES UNDER 10 PLAYERS
To Kill - !kill playername NO VEHICLES UNDER 10 PLAYERS
4. Balancing servers
Example
One team is continually pinning the enemy into their fixed spawn round after round.
Actions
1. Before forcibly moving others please try to move yourself.
2. If you are more than 4 OG members on the same side please try to split onto the different teams. This means that you would have to play against other OG members/ friends from time to time.
3. Nuke the aggressive team.
4. Force move top players using Procon, those not in a squad should be moved first.
5. OG members are expected not to move up to the furthest flag, giving the enemy a fair chance.
Considerations
1. Never forcibly move a fellow admin without prior consent.
2. Use nukes sparingly and to give the team the best opportunity to get a flag double nuke.
3. If persistent baseraping is taken place refer to the baserape guidelines.
4. The use of nukes is limited to Metro and Bazaar.
In-game Commands
To forcibly switch teams (does not count as death) - !fmove playername (NOTE: Does NOT work on full servers. There needs to be a free slot, to move a player to)
To nuke US team - !nuke us army
To nuke Russian team - !nuke russian army
5. Action if OG members are breaking server/community rules
Trials
1. Notify staff with trial members name and incident.
2. One verbal warning in separate TS channel.
3. Incident posted in Mod forums.
4. Repeated incident will result in removal from trial status.
Members
1. Notify staff with members name and incident.
2. One verbal warning.
3. Posted in mod section for review.
4. Second verbal warning.
5. Final warning from Community leaders.
6. Continued breaking of rules the member will be removed from OG forfeiting any paid membership fees.
Table of Contents
1. Introduction
2. Server Rules, definitions and punishments:
2.1 Cheating
2.2 Suspected hacker
2.3 (MAV) Glitching
2.4 Swearing
2.6 Baserape
2.7 Statpadding
3. Starting servers
4. Balancing servers
5. Action if OG members are breaking server/community rules
1. Introduction
As you all might know, we try to provide members of our community, as well as for the entire gaming community, a nice and pleasant environment to play games. We do this by providing servers for our members, on which they are granted admin rights, to keep the servers clean from unwanted guests.
We like to offer quality over quantity. We have quite a few servers, in order to try to accommodate every member’s wishes regarding to map rotation and settings. Of course we would like our members to be able to play on full servers when they come home from work/ school or have a day off. Therefore we also have to make a combined effort to fill up our servers with players. If we do this every day, servers will fill up easier and easier every time we try. Who doesn’t like to play a round on a full server, clean from cheaters, glitchers, whiners and other unwanted guests?In order to achieve our goals, we have created a rulebook for Old Guys members regarding the rules on the server, and how to react when a rule is being breached, We ask all Old Guys members to follow the rules, and warn players who are not.
2. Server Rules, definitions and punishments:
2.1 Cheating
Obvious Aimbotter
Example
People who achieve kills of 30+ in 2 minutes. Â*Use your commonsense however you must have no doubt in your mind that the player is hacking. Â*If you only suspect him then please refer to section ‘Suspected Hacker’
Action
1. Ban without warning.
2. Name should be posted on OG Forums for perm ban.
In-game Command
Temp ban - !tban 60 playername Aimbot
2.2 Suspected hacker
Suspected Aimbotter
Example
Unfortunately there are people who are good at the game under normal circumstances and use cheats to give them that extra edge. Â*These people are generally referred to as ‘togglers’ meaning they switch their cheat on and off and actually have a skill for hiding the use of it.
Action
1. Observe score.
2. Note play style.
3. Check Battlelog (http://battlelog.battlefield.com), pbscreens.com (http://pbscreens.com/database.php), Metabans (http://metabans.com). and BF3 Stats (http://bf3stats.com). Â*
4. Look for suspicious stats. Â*
5. Ask a staff member to jump on the server. Â*
6. Post proof or suspicion on OG bans/complaints forum section for Staff and fellow members to deal with retrospectively.
Note
If the player is not obvious please do not ban the player without taking the steps detailed above.
2.3 (MAV) Glitching
Example
(Using an MAV to) reach a normally inaccessible position.
Action
1. Identify the culprit by hovering aim over spawn beacon to show player name.
2. Join snipers squad to 3rd person view sniper.
3. Once identified kick player who is MAV glitching.
4. If they return and repeats the offence, tban the player.
5. Kill people who spawn on beacon stating the reason.
In-game Command
To kick - !kick playername MAV GLITCHING
To Temp Ban - !tban 60 playername MAV GLITCHING
To Kill - !kill playername DO NOT SPAWN ON MAV GLITCHED BEACON
Note
Spam bot already warns people therefore you are free to kick MAV glitches without chat warning.
We expect DICE to address MAV glitching in upcoming game patch.
2.3.1 M26 Glitching
Example
Abusing the M26 heavy barrel glitch
Action
1. Kill the offending player with message No M26
2. If continued abuse, kick player
3. Re-joined and continued abuse then ban the offending player.
In-game Command
To kick - !kick playername NO M26
To Temp Ban - !tban 60 playername NO M26
To Kill - !kill playername DO NOT USE THE M26
2.4 Swearing
Example
A player is directly abusive or verbally attacks another player using offensive language. Â*Please use your judgment here, you are over 18 and know what right and wrong is. Â*OG servers are not a nanny state and the game is 18+. Â*Non excessive impersonal swearing can be overlooked and so can friendly banter.
Action
1. Warn the player who is being abusive.
2. Kick the player if they do not immediately stop abuse.
3. If they rejoin server and continue abuse, temporarily ban the player.
In-game Commands
To warn - !say warning text
To kick - !kick playername reason
Temp ban - !tban 60 playername reason
2.5 Racism
Example
Any racist or derogatory comments about another person’s religion or ethnic background.
Action
Instant temp ban without warning or reprieve. Â*Player name must be posted on OG Bans/complaints forum for perm ban to be given.
In-game Command
To temp ban - !tban 60 playername Racism
2.6 Baserape
Example
To kill a player within their fixed spawn area. Â*Metro is a good example where if a Russian team member kills US team members beyond the C lockers into the US spawn.
Action
1. Kill the offending player stating the reason.
2. If the same player continues to break the rules, kick him stating the reason.
3. If the same player re-joins the server and continues to break the rules, issue a permanent ban stating the reason.
2.7 Statpadding
Example
1. Players who buff their stats in an artificial manner such as resupplying a friend without engaging the enemy.
2. Joining empty OG server just to take flags and agreeing not to kill one another.
3. Arm and disarm bombs without killing one another.
Action
1. Temp ban
2. Post offenders name in Bans/Complains forum section for perm ban.
In-game Commands
4. To Temp ban - !tban 60 playername reason
3. Starting servers
Example
If you’re on a full server please look to see what other OG servers you could start, it only takes 6 members on the same server to really get it going.
Considerations
1. Try to move yourself to the opposing team if it’s unbalanced.
2. Warn players not to use vehicles at all under 10 players, if ignored kill the offending player stating reason.
3. Do not take the last remaining flag if server is less than 50% full.
4. Don’t play ‘hardcore’. If you play rush, let the attackers also blow up a MCOM , hold them at the last ones. If attacking, don’t role-over the defenders if your team is better.
5. Try to have some fun while filling up, train yourself using for example only pistols. Agree this with other people on the server.
In-game Commands
To forcibly switch teams (does not count as death) - !fmove playername
To warn - !say NO VEHICLES UNDER 10 PLAYERS
To Kill - !kill playername NO VEHICLES UNDER 10 PLAYERS
4. Balancing servers
Example
One team is continually pinning the enemy into their fixed spawn round after round.
Actions
1. Before forcibly moving others please try to move yourself.
2. If you are more than 4 OG members on the same side please try to split onto the different teams. This means that you would have to play against other OG members/ friends from time to time.
3. Nuke the aggressive team.
4. Force move top players using Procon, those not in a squad should be moved first.
5. OG members are expected not to move up to the furthest flag, giving the enemy a fair chance.
Considerations
1. Never forcibly move a fellow admin without prior consent.
2. Use nukes sparingly and to give the team the best opportunity to get a flag double nuke.
3. If persistent baseraping is taken place refer to the baserape guidelines.
4. The use of nukes is limited to Metro and Bazaar.
In-game Commands
To forcibly switch teams (does not count as death) - !fmove playername (NOTE: Does NOT work on full servers. There needs to be a free slot, to move a player to)
To nuke US team - !nuke us army
To nuke Russian team - !nuke russian army
5. Action if OG members are breaking server/community rules
Trials
1. Notify staff with trial members name and incident.
2. One verbal warning in separate TS channel.
3. Incident posted in Mod forums.
4. Repeated incident will result in removal from trial status.
Members
1. Notify staff with members name and incident.
2. One verbal warning.
3. Posted in mod section for review.
4. Second verbal warning.
5. Final warning from Community leaders.
6. Continued breaking of rules the member will be removed from OG forfeiting any paid membership fees.