GAMEBATTLE RULES

For my team


General Ladder
This ladder is limited to 16 players per team.
 
Every team is required to have a minimum of 4 players on their roster prior to accepting a match.
 
Players and/or teams are not allowed to participate on a ladder that is not within the region in which they live. If any team or player is found to be violating this rule, the team will receive the loss regardless of the result of the match.
General · Rosters · Challenges · No-Shows · Reporting · Tickets
Cheating · Referees · Proof · General Ladder · Settings · Matches

Settings
The default settings specified in these rules can be changed, but only if an option is available in the challenge. Unless specified otherwise in the match details, these default rules will be followed.

The following settings apply to all GameBattles matches, regardless of the Game Mode.
Spectating: Disabled (Does not apply for Search and Destroy). Spectating is to be Enabled when a Staff Member is present to spectate the match.
Friendly Fire: Enabled
Forced Respawn: Enabled
Wave Spawn Delay: None
Respawn Delay: None (Does not apply to Sabotage, Capture the Flag, Domination, and Demolition)
Radar Always On: Challenge Option
Max Health: Normal
Health Regeneration: Normal
Kill Cam: Enabled
Headshots Only: Disabled
Third Person View: Challenge Option
Allow Perks: Challenge Option
Killstreak Rewards: Challenge Option
Number of Lives: Unlimited (Does not apply to Search and Destroy.)
Join-In-Progress: Not Allowed
Hardcore Mode: Disabled
 
The following settings are specific to each Game Mode, so please read them carefully before setting up the server.
Team Deathmatch
Points to Win: 7500
Round Timer: 10 Minutes
 
Search and Destroy
Round Length: 3 Minutes
Bomb Timer: 45 Seconds
Number of lives: 1 Life
Plant Time: 7.5 Seconds
Defuse Time: 7.5 Seconds
Multi Bomb: Disabled
Score Limit: 4 Points
Round Switch: Every Round
Spectator: Team Only
 
Sabotage
Time Limit: 10 Minutes
Bomb Timer: 45 Seconds
Plant Time: 5 Seconds
Defuse Time: 5 Seconds
Respawn Delay: 7.5
Shared Bomb Timer: Disabled
Note: In the event of a tie, the game will go into Overtime to determine the winner. If the Overtime results in a Draw, the map must be replayed until a winner is decided.
 
Domination
Round Length: 10 Minutes
Score Limit: Unlimited
Respawn Delay: 5 Seconds
 
Capture The Flag
Round Length: 5 Minutes
Score Limit: Unlimited
Respawn Delay: 5 Seconds
Note: In the event of a tie, the game will go into Overtime to determine the winner. If the Overtime results in a Draw, the map must be replayed until a winner is decided.
 
Demolition
Time Limit: 3 Minutes
Round Switch: Every Round
Bomb Timer: 30 Seconds
Plant Time: 5 Seconds
Defuse Time: 5 Seconds
Extra Time: 2 Minutes
Respawn Delay: 5 Seconds
 
Headquarters
Time Limit: 10 Minutes
Score Limit: Unlimited
HQ Lifetime: 1 Minute
HQ Activate Delay: 30 Seconds
 
Kill Confirmed
Time Limit: 10 Minutes
Score Limit: 65 Points
 
If any of the above settings are incorrect, the hosting team forfeits that map. The team hosting is responsible to ensure all setting are correct prior to beginning any map. If the settings are incorrect, the map needs to end and the next map needs to be played. The team that was not hosting is responsible for obtaining valid proof to show that the hosting team did not have the settings correct. A ticket with valid proof must be submitted immediately after the match has been completed.
GameBattles (GB) Variant Settings
All of the Settings changes that were made to the default Game Modes (Search and Destroy, Capture the Flag, Demolition, and Kill Confirmed) are listed below.  Settings that are not listed below should not be changed from their default state.

Maps and Modes
Arkaden - Capture the Flag
Arkaden - Search & Destroy
Bootleg - Capture the Flag
Bootleg - Search & Destroy
Carbon - Search & Destroy
Dome - Capture the Flag
Dome - Search & Destroy
Hardhat - Search & Destroy
Lockdown - Capture the Flag
Lockdown Search & Destroy
Seatown - Capture the Flag
Seatown - Search & Destroy
Underground - Search & Destroy
 
Game Settings
Spectating: Team Only
Killcam: Enabled
Radar Always On: No
Wave Spawn Delay: No
Force Respawn: Enabled
Friendly Fire: Enabled
Max Health: Normal
Health Regeneration: Normal
Perks and Proficiencies: Enabled
Hardcore Mode: Disabled
3rd Person: Disabled
Headshots Only: Disabled
Killstreaks: Disabled
Custom Classes: Enabled
Join-In-Progress: Not Allowed

The following settings are specific to each Game Mode, so please read them carefully before setting up the server.

Search and Destroy
Round Length: 2.5 Minutes
Bomb Timer: 45 Seconds
Plant Time: 7.5 Seconds
Defuse Time: 7.5 Seconds
Score Limit: 4 Points
Round Switch: Every Round
 
Capture the Flag
Round length: 5 minutes
Score Limit: Unlimited
Respawn delay: 7.5 seconds
Note: The winner is determined by the flag count. In the event of a tie, the Overtime tie-breaker will not be used, the map must be replayed until a winner is found.
 
Banned Weapons
All Launchers
All Shotguns
Riot Shield
 
Banned Lethals
Bouncing Betty
Claymore
C4
 
Banned Tacticals
Scrambler
Trophy System
Tactical Insertion
Portable Radar
 
Banned Attachments
Heartbeat Sensor
Grenade Launcher
Shotgun
Akimbo
Rapid Fire
 
Banned Proficiencies
Attachments (Double Attachments are not Allowed)
 
Banned Perks
Blast Shield
Overkill
Recon
 
Note: All players Death Streak must be set to Hollow Points.
 
To play a match using the GameBattles (GB) Variant Gameplay, you must first select the "GB Variant Gameplay" custom mapset from the drop-down. If this is not selected, maps that are not included in the GB Variant Gameplay may be randomized and cannot be played. Both teams should select to cancel the match on the Match Report screen if the correct options and mapset are not selected.
 
Second, you must select the "Yes - Use GB Variant Gameplay" option from the GB Variant Gameplay section. If this was not selected, the match will not be played with GB Variant Gameplay and would use the settings found under "Settings" in the Settings section above.
 
Your selection for all options below the GB Variant Gameplay section will not matter. All required settings for GB Variant Gameplay are listed above in the "Settings" section and must be used.
General · Rosters · Challenges · No-Shows · Reporting · Tickets
Cheating · Referees · Proof · General Ladder · Settings · Matches

Matches
All matches must be played in their entirety unless both teams agree to postpone or cancel the match. Teams can play a best of 3 (first team to win 2 maps wins the match) or a best of 5 (first team to win 3 maps wins the match). If no selection is made, a Standard Ladder Match will be played best of 3 maps.

Randomized maps MUST be used. Users cannot pick maps or change options selected in the challenge details. Unless specified otherwise in the challenge details, these default rules will be followed.

The higher ranked team at match time will host the first map. The higher ranked team is the team ranked closer to “1” on the ladder. If there is a tie in rank (i.e. both are unranked), the Team ID closest to 0 will host first. The lower ranked team at match time will host the second map. This will alternate for each map until/if a tie breaker map is needed. If a tie breaker map is needed, the lower ranked team will host the final map.

The team that is not hosting will pick which side to play on.

A "Lag Test" must be completed prior to starting the match. This is a test round that does not count and uses the standard game settings that will be used during the match. For the lag test, a map that is not scheduled for play must be used. If the game lags during this test, a new host must be chosen. If both teams cannot find or agree upon an acceptable host, the match needs to be removed. To have the match removed, both teams need to go to the Match Report tab and click on the Request Cancellation button.

Teams may not delay the match for more than 5 minutes between each map. If a team delays the start for longer than 5 minutes between maps, they will forfeit that map. The team that did not delay must submit a ticket with valid proof showing that this delay did occur. Complete the match and then report the outcome. You can select the Match Status that says: “I’m reporting: I had an issue and want to dispute”. Then, submit your ticket containing valid proof.

If a player/host disconnects during the initial launch of a map, the map will be restarted. The initial launch is defined as within the first 30 seconds or before the first kill. If both teams disagree over when the disconnection took place, video proof must be provided. Complete the match and then report the outcome. You can select the Match Status that says: “I’m reporting: I had an issue and want to dispute”. Then, submit your ticket containing valid proof.

If the host disconnects after the map has started, the host's team forfeits that map. After the map has started is after 30 seconds or after the first kill. If both teams disagree over when the disconnection took place, video proof must be provided. Complete the match and then report the outcome. You can select the Match Status that says: “I’m reporting: I had an issue and want to dispute”. Then, submit your ticket containing valid proof.

If a player disconnects after the game has started, the game will continue and a player may be re-invited. The re-invited player may be the player that dropped or a new eligible player that was selected as a substitute when setting up the match. The only exception to this rule is for a "Kill Dependent Game Mode". Please see the rule below regarding "Kill Dependent Game Mode".

A "Kill Dependent Game Mode," often referred to as Deathmatch, Sharpshooter or Slayer, is a game mode whose winner is decided by the overall number of kills, or points gained from kills. Because this mode relies on the number of players present, a team can never play shorthanded when playing this mode. A Team that loses a player during this game mode, after the first kill has occurred, forfeits that map.
 
A team can start a map shorthanded unless it is for a "Kill Dependent Game Mode" (for a description of what a "Kill Dependent Game Mode" is, please see above). You can only be shorthanded by one player. For example, in a 4v4, a team can start a map with 3 players. If you are missing more than one player, you cannot start a map. This rule applies to all matches except for 1v1s.
We highly recommend that all players appear offline during their match. Users are not to dispute a match on purpose if the other team did not appear offline. If random players enter the room, ask them to leave. If they leave immediately without disrupting the match, the match can continue. If the player disrupts the match, the match is to resume from the score at which the player(s) entered.

We strongly recommend that you set your Friends List to "Private".
If a map results in a tie, the map will be replayed with the same sides and settings.

Deliberate and repeated team-killing or committing suicide on purpose during Team Deathmatch will  result in a forfeit of the map. If a team is accused of violating this rule, the accuser must provide valid video proof. Complete the match and then report the outcome. If it is a Premium Match, report the scores correctly and then submit a ticket. If it is a Non-Premium Match, you can select the Match Status that says: “I’m reporting: I had an issue and want to dispute”. Then, submit your ticket containing valid proof.

Using disabled equipment/weapons/secondarys during a game will result in a forfeit of that map. Using the equipment includes holding it while running or walking and/or placing it on the ground.

Planting a bomb in a place that cannot be defused by standing next to it on the ground will result in a forfeit of the map.

Using the Proficiency Gun Glitch during a match will result in a forfeit of the match and a ban from the MLG websites.

Teams are allowed to utilize Party Chat during matches.

General
Rules are subject to change at any time, so please check them often.
 
Rules are customized for either MLG League Member Match (Premium Matches) or Non-Premium Matches. Many rules are universal, but some rules will specify instructions for Premium or Non-Premium Matches. Premium Matches utilize the ticket system and GameBattles Staff to resolve match issues. The Non-Premium Matches use the Community Match Resolution System (CMRS) to resolve match issues. 
 
It is the responsibility of all the users of this ladder to know and understand the rules.
 
By sending or accepting a challenge in the challenge system, you acknowledge that you have read, understand, and agree to abide by the rules posted here. This includes posting or accepting challenges on the Match Finder.
 
Our goal here at GameBattles is to provide gamers with a place to find fair and competitive matches. In order to accomplish this goal, we will not tolerate players or teams that cause problems or attempt to undermine the positive atmosphere on GameBattles. This includes teams that cheat, dispute on purpose, or repeatedly abuse players. Violators will be dealt with accordingly including possible removal from GameBattles. As with all accusations, valid proof must be provided. Please see the proof section below.
 
Users that are found to be participating on a team with a user that is evading a ban will be subject to penalties including removal from the site. We advise you to report the evading user immediately by utilizing our ticket support system. 
 
If a user is found to be evading a ban, the original account that was banned will be disabled permanently.
 
GameBattles prohibits members from creating or managing more than one team on a ladder from the same household as well as competing against each other. Multiple people from the same household may compete on GameBattles; however, only one username can be in a management position on a team. For example, only one username can be a Co-Leader or Leader on a team. All other usernames from the same household cannot be anything higher than member on any team.
 
Abuse of our volunteer Staff will not be tolerated in any form. This includes written messages or verbal comments. Violators will be removed from GameBattles.
 
The Leader of a team can change the team name. The name must be appropriate and cannot violate our Forum Rules. Attempting to bypass the automatic censor by misspelling, inserting spaces or symbols, transposing letters, using look-alike symbols, or any other method is not allowed. Teams that attempt to bypass the censor will be subject to penalties.
 
Team names, blast messages, logos, avatars, and website links are subject to the Forum Rules.
 
Teams on a ladder must contain the minimum number of eligible players to remain active on a ladder. Teams without the minimum number of eligible players - especially teams that are "abandoned" - are subject to removal at the Staff's discretion.
 
All MLG/GameBattles accounts are property of Major League Gaming Inc.  Any advertising of, or attempts to buy, sell, trade, or exchange an account by any means, is strictly prohibited.  Violators will be banned from all MLG/GameBattles websites and all related accounts terminated.
 
Users must utilize their own unique username for competing on GameBattles. This unique username must have been registered on GameBattles personally by the user. The registered username must contain the correct and complete Name, Address, and Email of the user. If a false Name, Address, or Email was entered, the user voids the privilege to participate in the Ladder/Tournament and receive any prizes.
 
Users are permitted to have two gamertags per console on their profile. For example, you may have two gamertags for the Xbox 360, two PSNs, and two Wii codes. Also, "stealing" gamertags by placing gamertags that belong to someone else on your profile will result in you being banned.   
 
As a user, you are personally responsible for accepting an invitation to a team. Someone else cannot accept a team invitation for you. If you do not personally accept a team invitation, you may be disqualified from competing. You also forfeit the ability to receive prizes.
 
Roster spots on public ladder teams are for free entry. Any users found to be selling or buying a spot on a roster will be banned from MLG/GameBattles websites and all related accounts terminated.
 
Users are prohibited from sharing account information stored on MLG/GameBattles with another person for any reason. This includes, but is not limited to, the following: usernames, passwords, gamertags, email accounts, etc. If another person accesses your account, you may be disqualified from the Ladder/Tournament and removed from GameBattles.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Staff Support · CMRS · Proof · General Ladder · Settings · Matches

Rosters
When you are added to a roster, it may take up to 6 hours before you will be eligible. A green eligibility icon will be displayed once you are eligible.
 
It is both teams responsibility to verify the eligibility of all players playing in the match prior to starting or continuing any match play. A team playing with an ineligible player will forfeit the match.
 
The only players eligible to play in the match are the players who were selected when the challenge was sent/accepted. Once a match is confirmed, the eligible players from both Teams will be displayed on the Match page. See the Challenges section for more information.
 
All gamertags on a team’s roster must be valid. The gamertag must be legitimately owned by the user on the roster.
 
The rules below outline our policies on rostered players:
Users are permitted to be listed on only one team on each ladder at any given time. Users are only permitted one gamertag per ladder.
 
All roster spots must be comprised of only one valid gamertag. Spelling and spaces must be exact, but does not need to be case sensitive.
 
Gamertags may not contain foul language, disparaging remarks, hateful or racist names.
 
Players must have a green eligibility icon  next to their name to participate in matches.
 
If the opponent team has an ineligible player present, ask the team to replace that player. You must have given the team the required 15 minutes from match start time to substitute their ineligible players. If the ineligible player shows up between maps/rounds, you must give the team the required 5 minutes to replace their ineligible player. If the team does not substitute their ineligible player and allows that player to compete in the match, follow these steps:
Immediately submit a ticket stating an ineligible player was present. This ticket must be submitted before starting or continuing to play the match.
 
Be sure to gather proof of the ineligible player actively playing in the match. Then, upload the proof to a website. For more information regarding proof, please see the Proof section below.
 
When the match is completed, you must go back to your ticket and submit the URL link containing valid proof showing the ineligible player playing in the match. Without valid proof, no win can be awarded.
 
After completing the match, select the Match Status of “They are using an ineligible player”.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Staff Support · CMRS · Proof · General Ladder · Settings · Matches

Challenges
When sending and accepting challenges, you MUST select the players who will actually be playing in the match. You will be prompted to do this before sending and accepting any challenges. The number of players you must select is determined by both the match size and the ladder. Therefore, if the match is a 2v2, you will need to select two (2) people. On Team ladders, however, you will have the ability to select up to one (1) additional player. This player may serve as a substitute during the match.

These players you select when sending and accepting any challenges are the ONLY players that are allowed to play in the match. Players who enter the room, but whom were not selected to play beforehand, will be considered ineligible players.
 
If you need to cancel an already accepted match, you must first select the match you wish to cancel and hit the "Request Cancellation" button. Fill out the required field to notify your opponent that you wish to cancel, and then submit the request. Your opponent will then either accept or decline the request. If the cancellation request is not accepted by your opponent, you will be required to play the match.
 
A team cannot play the same team more than once within a 12 hour period.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Staff Support · CMRS · Proof · General Ladder · Settings · Matches

No Shows
A team has 15 minutes to show-up with the proper number of eligible players and be ready to start the match. Failure to do so will result in a forfeit. Teams are responsible for all scheduled matches.
 
If you have a No Show issue, you must select to Report Problem: “I'm reporting: my opponent did not show up” when you go to report the match. Do not report scores of winning the match. Since the match was not played, you should not report scores that you won.
 
To receive a no show win, you must submit a ticket within 30 minutes of the scheduled match time. You must also select the No Show option for Report Problem when you go to report the match.
 
If you have any proof, be sure to submit it in your ticket.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Staff Support · CMRS · Proof · General Ladder · Settings · Matches

Reporting
Both teams are responsible for reporting the match within 30 minutes of its completion. If teams do not report matching results, the match will result in a ‘dispute’. Both teams are then required to submit a ticket regarding the dispute and include any valid proof they have. If you had a problem with the match, please select the Report Problem option and pick the one that best fits the outcome of your match. Then, you can submit a ticket containing your valid proof.
 
Premium Matches: If you encountered an issue and there is no Report Problem that applies, report the match as a win for the team that won the number of rounds/maps needed to win a match. Then, you can submit a ticket containing your valid proof. If your claims are found to be valid with proof, an Admin has the ability to finalize the outcome of the match. 
 
Non-Premium Matches: Select the appropriate option under Report Problem and follow the instructions on the Match Report screen. 
 
Do not dispute on purpose or you risk being punished. Disputing on purpose is defined as knowingly reporting that you won a match despite the outcome of the match resulting in a loss for your team.  
 
Teams that have 5 or more disputed matches will be automatically locked and unable to play additional matches. The team will not be unlocked until they have less than 5 disputed matches. To resolve disputes, please see rule number 1 above.
 
Matches that go unreported by one team will be reported automatically for the team that did report. Matches that go unreported by both teams will be deleted automatically.
 
Any team found to report as the winning team before the match is played or completed will be subject to penalties.
 
All matches must be reported correctly. If you had an issue with a match such as a No Show, Wrong Settings, etc., you must report the correct problem on the Match Report screen via the Report Problem section at the top. You can then submit a ticket containing your valid proof.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Staff Support · CMRS · Proof · General Ladder · Settings · Matches

Tickets
Premium Matches: Your ticket will be handled by Staff. Submitting an incomplete or incorrect ticket will be closed without being processed. All Admin decisions are final.
 
Non-Premium Matches: Tickets submitted regarding match issues will be displayed to the community via the Community Match Resolution System (CMRS). The community will vote for which team should receive the win. It is very important that your ticket contain all the proof that you have to support your case. The community’s decision is final.
 
When submitting a ticket, fill out all applicable fields. Submitting an incomplete or incorrect ticket will be closed without being processed. You are required to select your team name from the drop-down. If you are submitting a ticket about a match, you must also fill out the match ID or your ticket will not be processed.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Staff Support · CMRS · Proof · General Ladder · Settings · Matches

Cheating
The use of any communications other than what is provided within the game is prohibited. For example, the use of Skype or private chatting during a match is not allowed. There are exceptions to this rule in which outside communication can be utilized, which includes:
Games that give you no advantage by using outside communication
Games that do not have an in-game voice option
Games in which we specifically state in the rules that outside communication is allowed
 
We have a zero tolerance policy for cheating. Teams caught cheating, “glitching”, or abusing in-game mechanics in any way will be removed from GameBattles.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Staff Support · CMRS · Proof · General Ladder · Settings · Matches

Staff Support for Premium Matches
If you have any problems during a match, you need to report the issue via the Report Problem section on the Match Report page. This will inform our Senior Support Supervisors that you have an in-game issue. To find the list of Staff members, click on the “Support” tab located within each ladder. 
 
Verbally abusing Staff members called into a match will not be tolerated. The individual user and/or team violating this rule will be subject to being locked. All team leaders are responsible for the conduct of the players on the team while interacting with Staff and are subject to penalties for abusive team players.
 
Staff members that enter a match have the discretion to make necessary calls to ensure the match is completed successfully. When in a match, the Staff member's call is final and must be followed. Failure to do so will result in penalties for your team. After the match, if you disagree with a call made, first you must accurately report the match and then you can submit a ticket for review by an Admin. Do not dispute the match on purpose.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Staff Support · CMRS · Proof · General Ladder · Settings · Matches

Community Match Resolution System
The Community Match Resolution System (CMRS) is the system that will be used for Non-Premium Matches (Non-League Member Matches).
 
When there is an issue with a match that results in a match dispute, the community will help resolve the issue by evaluating the match through the Community Match Resolution System (CMRS).
 
When you submit a ticket for your match, include as much detail as possible to help the community understand the issue. All proof submitted in your ticket needs to be from the match in question. If you submit proof from the wrong match/game or links to inappropriate material, you risk being punished. 
 
Community members can access the CMRS at the top navigation bar by clicking on “Match Resolution”. Matches will be randomly generated for you to judge.
 
Be sure to evaluate the matches carefully. Always examine the Team Stats, Team Information, Match Details, and any information provided in the Tickets section.
 
If you find that you cannot decide a winner based on the proof provided, you can select the “Skip This Match” option and another match will be generated for you.
 
Members that use the CMRS feature will be placed on the Resolution Leaderboard. The more often that you select the correct team, the more XP that you will gain and the higher you will climb the Leaderboard.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Staff Support · CMRS · Proof · General Ladder · Settings · Matches

Proof
Before submitting any proof, please make sure the match is reported correctly. If you had an issue with a match such as a No Show, Wrong Settings, etc., you must report the correct Match Status on the Match Report screen. Do not dispute the match on purpose.
 
When submitting proof, you must paste the hyperlinks to your proof in the URL boxes located below the “Message Body” box. Be sure to only place one URL link in each box.
 
All proof submitted in your ticket needs to be from the match in question. If you submit proof from the wrong match/game or links to inappropriate material, you risk being punished. 
 
You need to show proof of winning each map/game in a match to be given the win for it. All proof must be clearly visible and show the in-game full scoreboard during the completion of that map/game. The proof must clearly show both team's players to be considered valid. Essentially, proof needs to be large enough in size to clearly read all scores and gamertags.
 
All video proof should be uploaded to a website. Picture proof can be uploaded to your GB profile. The URL link to the individual pictures/proof must be placed in a ticket.
 
For all glitching and cheating claims, the burden of proof is on the accuser. To submit a glitching or cheating claim, you must submit a ticket and include the URL link containing valid proof.
 
All conversations between users are not considered proof. This includes AIMs, emails, PMs, etc.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Staff Support · CMRS · Proof · General Ladder · Settings · Matches