** 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.
** 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.
** Users are prohibited from sharing account information stored on GamerBattles 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
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.
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 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.
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
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.
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
A team has 15 minutes to show-up with the number of eligible players indicated in the match details, and be ready to start the match. Failure to do so will result in a forfeit. Teams are responsible for all scheduled matches.
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
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.
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.
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 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.
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
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.
Crown holders must report their loss prior to playing any other matches to make sure the crown is granted to the correct team.
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
Do not contact staff inquiring about the status of a ticket or your team is subject to penalties. We receive many tickets from our users, and they are handled in the order they are received.
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.
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
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.
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.
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
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.
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.
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
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.
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.
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 Ladder
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.
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.
General · Rosters · Challenges · No-Shows · Reporting · Crown
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. The staff will support no other agreements, (i.e. verbal, AIM, email). So unless specified otherwise in the match details, these default rules will be followed.
General Settings
Game Name: Challenge Details
Max players: The max number of players in the match. (ie: A 4v4 would be a max of 8.)
Password: Challenge Details
Faction Balancing: Off
My Rank Range: Off
Friendly Fire: On
Enemies on radar: When Firing
Spectators: On
Spectator Password: Challenge Details
Add AI Bots: 0
Restrictions - If an item below is restricted via the match details, it is not allowed for use. If a team is found using a restricted item they will lose the map in which the item was used on. Valid proof will need to be provided.
Assault Class: Challenge Option
The following settings are set for each game mode.
Body Count
Mission Time: 10 Minutes
Maximum Kills: 50
Capture and Hold
Point Maximum: 500
Minimum Capture Time: 10 Seconds
Mission Time: 10 Minutes
Search and Retrieve
Flag Maximum: 3
Mission Time: 10 Minutes
Search and Destroy
Explosive Detonation Time: 45 Seconds
Mission Time: 3 Minutes
