General

1. Rules are subject to change at any time, so please check them often.
   
   
2. It is the responsibility of all the users of this ladder to know and understand the rules.
   
   
3. 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.
   
   
4. 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.
   
   
5. 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.
   
   
6. 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.
   
   
7. Team members are not able to change the name of their team. Only the leader of the team can submit a ticket to request a team name change. Names must be appropriate and cannot be taken by another team on the same ladder.
   
   
8. Team names, blast messages, logos, avatars, and website links are subject to the Forum Rules.
   
   
9. 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.
   
   
10. 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.
    
    
11. 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.
    
    
12. 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.
    
    
13. Users are prohibited from sharing account information stored on 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 · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Rosters

1. 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.
   
   
2. 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.
     
     
   • 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.
     
     
   • Tickets submitted after the match is completed are not valid. You must submit a ticket immediately when the issue arises as stated above.
     
     
   • All gamertags on a team’s roster must be valid. The gamertag must be legitimately owned by the user on the roster. If the team cannot access the gamertag or has an invalid gamertag on the roster, the team is subject to being locked.
     
     
3. The rules below outline our policies on rostered players. Please see rule number 2 if the following rules are broken:
   
   
   • 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.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Challenges

1. Should a team need to cancel an already accepted match, they must submit a ticket requesting to do so at least 24 hours before the scheduled start time of the match. The match can also be removed at any time if both teams submit tickets agreeing to have it removed. Both teams are also recommended to post feedback stating they wish to cancel the match. If both teams do not agree to have the match removed, both teams are required to play the match.
   
   
2. A team cannot play the same team more than once within a 12 hour period.
   

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

No-Shows

1. A team has 15 minutes to show-up with the proper number of eligible players indicated in the match details (i.e. 3v3 would be 3 players), and be ready to start the match. Failure to do so will result in a forfeit. Teams are responsible for all scheduled matches.
   
   
2. To receive a no-show win, you must submit a ticket within 30 minutes of the scheduled match time. You must also report the match as a win for your team.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Reporting

1. 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. Teams can also resolve their own disputes by changing the scores they reported for the match. To do this, teams must go into the match report screen for the disputed match and change the scores within 24 hours of the scheduled start time.
    
2. Teams that have 3 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 3 disputed matches. To resolve disputes, please see rule number 1 above.
   
   
3. 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.
   
   
4. Any team found to report as the winning team before the match is played or completed will be subject to penalties.
   
   
5. All matches need to be reported correctly by both teams. If there is an issue with a match, the match must first be reported accurately and then a ticket containing your valid proof can be submitted afterwards. Do not dispute the match on purpose. Please see the proof section below for more information. If your claims are found to be valid with proof, an Admin has the ability to revert the match.
   
   
6. Disputing a match on purpose will result in penalties for your team.
   
   
   • The first time a team disputes on purpose without valid proof, the team is locked for 6 days and the team warning level is increased to level 1.
     
     
   • The second time a team disputes on purpose without valid proof, the team is disbanded and the member that disputed is banned as well as the leader of the team.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Crown

1. Crown holders must play at least 2 matches every week. If 2 matches are not played in a week, the crown will be returned to the previous crown holder or will be given back to the Staff of GameBattles to be redistributed.
   
   
2. Crown holders must report their loss prior to playing any other matches to make sure the crown is granted to the correct team.
   
   
3. If the crown holder is caught giving a win to another team before reporting to a team that rightfully won the crown, they are subject to being locked.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Tickets

1. Do not contact staff inquiring about the status of a ticket or you and/or your team are subject to penalties.  We receive many tickets from our users, and they are handled in the order they are received.
   
   
2. 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.
   
   
3. All admin decisions are final. If you would like your case looked into again due to new evidence, feel free to submit a new ticket. Submitting a ticket without additional evidence is argumentative and you risk your team being locked. Do not post in the forums regarding a ticket issue.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Cheating

1. 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. The only exception to this rule is for games that give you no advantage by using outside communication.
   
   
2. 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.
   
   
3. If your team receives a win that was not earned or played, you must submit a ticket to have it removed. Failure to do so will result in your team being removed from GameBattles.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Referees

1. If you have any problems during a match, you may contact a Staff member over Live Support to answer any questions you may have. Please contact the Referees first as this is their job. To find the list of Staff members, click on the “Support” tab located within each ladder. 
   
   
2. If a Staff member is called into a match for any reason, all players must comply with the Staff member’s instructions. Failure to do so will result in penalties for your team.
   
   
3. 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.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Proof

1. 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 all clearly show both team's players to be considered valid.
   
   
2. We recommend all video proof should be uploaded to the GB Game Room. Picture proof can be uploaded to your GB profile. The URL link to the individual pictures/proof must be placed in a ticket.
   
   
3. 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.
   
   
4. All conversations between users are not considered proof. This includes AIMs, emails, PMs, etc.

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

General Ladder

1. All players participating in a match must be on the roster for at least 12 hours and can not be updated within the past 12 hours prior to the match start time indicated in the accepted match details.

2. This ladder is limited to 24 players per team.
   
   
3. Every team is required to have a minimum of 4 players on their roster prior to accepting a match.
   
   
4. 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 · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Settings

1. Global Match Settings:
   
   • Item Restrictions : XM-26 LSS, C4, GPS Device, Motion Sensor
     
   • Team Respawn: Off
   • Friendly Fire : Yes
   • Punish Team Killers : No
   • Max Players : 12
   • Private Slots : 12
   • Join in Progress : No
   • Kill Camera: Disabled
   • Voice Chat : Alive Only
   • Random Respawns : Off
     
     
2. Team Conquest Settings:
   
   • Time Limit : 5 Minutes
   • Respawns : Unlimited
     
     
3. Team Leader Settings: This mode is objective based; the objective must be completed before the time runs out. There are two ways to win. Either extract your team's leader, or kill the opposing team's leader AND eliminate the entire opposing team.
   
   • Time Limit : 5  Minutes
   • Respawns : Per Game Settings
     
     
4. Attack & Defend Settings:
   
   • Time Limit : 3 Minutes
   • Respawns : None
     
     
5. Team Deathmatch Settings:
   
   • Time Limit : 5 Minutes
   • Game Point Limit : None
   • Respawns : Unlimited
   • Random Respawns : Off 
     
     
6. Team Survival (GB) Settings: This game mode is not available as an independent game mode in Vegas 2. However, we would like to bring this mode back to offer to the community. To create this game mode, a Team Deathmatch server will be setup, with respawns OFF. To win a round of Team Survival, you must have the most surviving players alive at the end of the round, or eliminate the entire opposing team.
   
   • Time Limit : 5 Minutes
   • Respawns : None
     
     
7. Team Elimination (GB) Settings: This game mode is not available as an independent game mode in Vegas 2. However, this mode is now offered in addition to Team Survival. To create this game mode, a Team Deathmatch server will be setup, with respawns OFF. To win a round of Team Elimination, you must eliminate the entire opposing team before the time ends, otherwise the round ends in a draw.
   
   • Time Limit : 5 Minutes
   • Respawns : None
     
8. 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.
   

General · Rosters · Challenges · No-Shows · Reporting · Crown
Tickets · Cheating · Referees · Proof · General Ladder · Settings · Matches

Matches

1. All matches must be played in their entirety unless both teams agree to postpone or cancel the match. A Standard Ladder Match will be played best of 3 maps (first to 2), and best of 3 rounds per map (first to 2).

2. Randomized maps MUST be used. Verbal agreements will not receive staff support via Referees or Support Tickets. The only exception is the use of an Overriding Game Mode in the challenge, which changes all of the generated maps to the selected Game Mode.
   
   
3. The higher ranked team at match time will host the first map. The lower ranked team at match time will host the second map. This will alternate for each map if/until a tie breaker map is needed, when the team that has won the most combined rounds will host the final map. If there is a tie in rank (i.e. both are unranked), the Team ID closest to 0 will host first. If there is a tie in round count, the lower ranked team will host the tie breaker map. The host may not force launch the game.
   
   
4. The team that is not hosting will pick which Alpha or Bravo for the first round. After each completed round of play, teams must switch sides.
   

5. A "Lag Test" must be completed prior to starting the match. This is a test round that doesn't 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 agree on an acceptable host, a ticket must be submitted by both teams to cancel the match.

6. 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. First, the match must be completed and the scores must be reported correctly. Do not dispute the match on purpose. After the match is complete, submit a ticket containing the URL link of the proof.
   
   
7. 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. First, the match must be completed and the scores must be reported correctly. The URL link of the proof must be submitted in a ticket once the match is completed.
   
   
8. 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. First, the match must be completed and the scores must be reported correctly. The URL link of the proof must be submitted in a ticket once the match is completed.
   
   
9. 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. The only exception to this rule is for a "Kill Dependent Game Mode". Please see rule 10 below.
   
   
10. 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.
    
    
11. If a team loses players during a round, they must find eligible substitutes prior to beginning the next round. A team is not allowed to start a round shorthanded. For a “Kill Dependent Game Mode”, a team can never play shorthanded as stated in rule number 10. Teams are allowed a 5 minute grace period to find eligible substitutes between round as per rule number 6. Please follow the steps in rule number 6 if the match is delayed longer than 5 minutes between round.