Ok guys here are the GB rules for GOW3: If you're participating in clan matches with us please at least read what is in bold red so you know what to expect when we run a game. If you have the time scroll through the rest too, it's best when everyone knows all the rules so we don't end up getting a loss for a stupid reason unbeknownst to us thanks.
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 16 players per team.
3. 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 · Tickets
Cheating · Referees · Proof · General Ladder · Settings · Matches
Settings
1.
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.
◦Starting Weapon: Challenge Option
◦Team Deathmatch Settings:■ Respawns Allocated - 15
■ Rounds to Win - 2
■ Number of Bots - 0
■ Bleed-Out Time - 15
■ Friendly Fire - On
■ Weapon Respawn - After Pickup
◦Execution Settings■ Rounds to Win - 4
■ Round Time Limit - 4
■ Number of Bots - 0
■ Bleed-Out Time - 15
■ Friendly Fire - On
■ Weapon Respawn - After Pickup
◦King of the Hill Settings■ Round Score Limit - 150
■ Rounds to Win - 2
■ Number of Bots - 0
■ Bleed-Out Time - 15
■ Friendly Fire - On
■ Weapon Respawn - After Pickup
◦Game Types■
Execution – Checkout
■
Execution – Drydock
■
Execution – Gridlock
■
Execution – Hotel
■
Execution – Mercy
■
Execution – Old Town
■
Execution – Overpass
■
Execution – Sandbar
■
Execution – Thrashball
■
Execution – Trenches
■
Team Deathmatch – Checkout
■
Team Deathmatch – Drydock
■
Team Deathmatch – Gridlock
■
Team Deathmatch – Hotel
■
Team Deathmatch – Mercy
■
Team Deathmatch – Old Town
■
Team Deathmatch – Overpass
■
Team Deathmatch – Sandbar
■
Team Deathmatch – Thrashball
■
Team Deathmatch – Trenches
■
King of the Hill – Checkout
■
King of the Hill – Drydock
■
King of the Hill – Gridlock
■
King of the Hill – Hotel
■
King of the Hill – Mercy
■
King of the Hill – Old Town
■
King of the Hill – Overpass
■
King of the Hill – Sandbar
■
King of the Hill – Thrashball
■
King of the Hill – Trenches
General · Rosters · Challenges · No-Shows · Reporting · 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).
2. Randomized Game Types 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 team ranked closest to 1 at the time of the match will host the first map. The team ranked furthest from 1 at the time of the match will host the second map. If there is a tie in rank (i.e. both teams are unranked), the Team ID closest to 0 will host first. This will alternate for each map if/until a tie breaker map is needed. The team that has won the most overall rounds from all maps played will host the final map. If there is a tie in round count, the lower ranked (furthest from 1, or if unranked, team ID closest to 0) team will host the tie breaker map.
4. The hosting team is not required to give you a new host on the tie breaker map. Once you have played a full map on the opposing team's host, you have accepted that host and must use that host for the remainder of the match. It is imperative that both teams conduct a lag test prior to beginning the match as a lag test cannot be performed before the tie breaker map.
5. The team that is not hosting will pick which side to play on.
6. Teams may request a Lag Test before the start of the Game. A Lag Test is a test round that does not count. A Map that is not scheduled to be played must be used. If a Lag Test is given on a map that is scheduled to be played, the hosting team forfeits the map the Lag Test is being given for, not the map that it was played on. 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.
7. Teams may not delay the match for more than 5 minutes between each Game. If a Team delays the start for longer than 5 minutes between Games, they will forfeit that Game. 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.
8. If a Player/host disconnects during the initial launch of a Game, the Game 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.
9. If the host disconnects after the Game has started, the host's team forfeits that Game. After the Game 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.
10. 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 Team Deathmatch. Please see the rule below.
11. A Team that loses a player during Team Deathmatch, after the first kill or 30 seconds has occurred that Team will forfeit the Game.
12. A Team can start an Execution or King of the Hill Game shorthanded by one Player. For example, in a 4v4, a Team can start a Game with 3 Players. If you are missing more than one player, you cannot start a Game. This rule applies to all Matches except for 1v1s.
13. Teams cannot start a Team Deathmatch Game shorthanded. All Players must be present for the Game to begin.
14. We highly recommend that all Players appear offline at all times during their Match. Players may not dispute a Match 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 Game, the Game can continue. If the Player disrupts the Game, the Game is to resume from the score at which the player(s) entered.
15. Pausing the Game will result in a forfeit of the Game for the hosting Team.
General
1. Rules are subject to change at any time, so please check them often.
2.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.
3. It is the responsibility of all the users of this ladder to know and understand the rules.
4. 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.
5. 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.
6. 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.
7. If a user is found to be evading a ban, the original account that was banned will be disabled permanently.
8. 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.
9. 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.
10. 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.
11. Team names, blast messages, logos, avatars, and website links are subject to the Forum Rules.
12. 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.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. 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 · Referees · CMRS · 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. 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.
3. All gamertags on a team’s roster must be valid. The gamertag must be legitimately owned by the user on the roster.
4. 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.
5. 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 · Referees · CMRS · Proof · General Ladder · Settings · Matches
Challenges
1. 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.
2. 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.
3. A team cannot play the same team more than once within a 12 hour period.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Referees · CMRS · Proof · General Ladder · Settings · Matches
No Shows
1. 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.
2. If you have a No Show issue, you must select the Match Status of: “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.
3. 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 Match Status 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.
4. If you have any proof, be sure to submit it in your ticket.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Referees · CMRS · 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. Please select the Match Status that best fits the outcome of your match. Then, you can submit a ticket containing your valid proof.
2.
Premium Matches: If you encountered an issue and there is no Match Status 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 Match Status and follow the instructions on the Match Report screen.
3.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.
4. 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.
5. 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.
6. Any team found to report as the winning team before the match is played or completed will be subject to penalties.
7. 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 Match Status on the Match Report screen. You can then submit a ticket containing your valid proof.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Referees · CMRS · Proof · General Ladder · Settings · Matches
Tickets
1.
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.
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.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Referees · CMRS · 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 or games that do not have an in-game voice option.
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.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Referees · CMRS · Proof · General Ladder · Settings · Matches
Referees for Premium Matches
1. If you have any problems during a match, you need to update your Match Status in order for a Referee to come help you with an in-game issue. To find the list of Staff members, click on the “Support” tab located within each ladder.
2. 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.
3. 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 · Referees · CMRS · Proof · General Ladder · Settings · Matches
Community Match Resolution System
1. The Community Match Resolution System (CMRS) is the system that will be used for Non-Premium Matches (Non-League Member Matches).
2. 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).
3. 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.
4. 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.
5. Be sure to evaluate the matches carefully. Always examine the Team Stats, Team Information, Match Details, and any information provided in the Tickets section.
6. 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.
7. 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 · Referees · CMRS · Proof · General Ladder · Settings · Matches
Proof
1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. All conversations between users are not considered proof. This includes AIMs, emails, PMs, etc.
General · Rosters · Challenges · No-Shows · Reporting
Tickets · Cheating · Referees · CMRS · Proof · General Ladder · Settings · Matches
Calendar