3v3 Online Cup #2 Tournament

Status: Completed
Size: 64 teams

Connect with MLG

World of Warcraft Online Tournament

Quick Links
Settings
Bracket Play
Games in a Series
Hosting
Support
Penalties
General

Settings


  • The higher seeded team is responsible for challenging their opponent to a Wargame at the match's scheduled start time. The process for doing so is detailed in the Games in a Series section.
  • Tournament officials may require screenshots or video (proof) of any maps played in order to solve disputes. Proof must follow specific guidelines in order to be considered valid. For more information on how to properly provide proof, please review Rule #5 in the Reporting section.
  • Admins will be adding competing players to BattleTag. Please make sure you have room on your friend’s list to accept BattleTag requests. A list of verified admin Battle Tags are here
  • Players will be competing on their own characters on live servers. Players are required to be able to form an eligible 3v3 team, meaning they each need a character on the same faction.
  • No matches will be started after 11:30 PM ET Thursday. Matches will resume at 7:00 PM ET Friday and play to Winners Bracket Round 4 and Losers Bracket Round of 4.

General

Tournament Rules
  • Teams must have Tournament Rules checked. 
Gear and Settings
  • The “Busy” setting in Battle.net is required to be active.
  • Tournament Gear shall be used for all matches.
  • Tournament Gear may be Enchanted and Gemmed if applicable.
  • Players are advised not to transmogrify Tournament gear. Transmogrification will not result in action being taken, but Tournament Admins can ask players to remove Transmogrifications at their discretion.
  • The Tournament Gear requirement shall be active for all matches.

Map Pool

Wargame
  • Nagrand Arena
    • Note: Nagrand Arena will always be the first map of any series, and will also be used for game 7 if the final goes to a 7th game.
  • Blade’s Edge Arena 
  • Ruins of Lordaeron 
  • Dalaran Arena 
  • Tol’viron Arena 
  • Tiger’s Peak

Restrictions

Team Compositions
  • Team compositions must not have:
    • More than one healer
    • More than one tank
  • With the exception of the above, there are no other restrictions to team compositions.
  • Starting Comps can be altered between rounds, using the method outlined in the Games in a Series section.

Bracket Play


  1. Double Elimination: After losing in the winner's bracket, the losing team will be moved into the loser's bracket. After losing a match in the loser's bracket, teams will be eliminated from the tournament.
     
  2. Default Start Time: All Round 1 Matches have the same default start time. After Round 1, all Matches have a unique default start time that is dependent upon the time at which the Teams’ previous Round results were submitted. Matches must be started by their default start time and played until completion. Postponing matches is only at the discretion of Online Tournament staff.
     
  3. Double Forfeit: If a Match is not played and neither Team submits a Ticket requesting the Forfeit win, or both Teams otherwise Forfeit a Game/Match, the Game/Match win will be awarded to the higher seeded Team.
     
  4. Seeding: Teams will be seeded according to the 3v3 Ladder Ratings of the characters listed during registration. Seeds are done in ascending order. Seed one is the highest seed.

Games in a Series


  1. First Game in a Series: If an admin is available, they will handle setting up the lobby for a match. In the event that an admin is not available, teams will need to handle getting themselves into a Wargame. Wargames must be hosted using the settings found here, it is imperative that the "Tournament Rules" box is checked.
    • Each team will declare a team captain. The captain should preferably hold the Leader position on the Gamebattles team.
    • The first map will always be Nagrand Arena.
    • If teams are teams are competing on different servers, the team leaders/captains will need to add each other's Battletag.
    • Once each captain is added, the higher seeded team will then challenge the opposing team to a Wargame by typing this command in chat: /wg GroupleaderBattletag Mapname 5
      • Note: Both the challenging and receiving player must have party lead for this command to work. If teams are not receiving a wargame request, all players from each team should completely exit the game and reform each party. If the issue persists, get in contact with an admin.
         
  2. Second and Subsequent Games of a Series: After the end of each game, chat shall be set to show timestamps and the below conversation must be screenshotted in game for potential dispute resolution. Chat logs WILL NOT be accepted. The following order of events will occur in the in-game chat and must take no more than five minutes.
    • The losing team of each game will select the next map from the Map Pool of non-played maps. Maps in a match series cannot be played twice until every map has been played once.
    • The winning team will then declare and lock in their composition.
    • After the winning team's lock in, the losing team will declare their and lock in their composition.
      • This process must be performed as detailed below:
        1. Losing Team Captain: "[Losing Team Name]'s map selection is [map]"
        2. Winning Team Captain: "[Map] confirmed"
        3. Winning Team Captain: "[Winning Team Name]'s comp is [class/spec, class/spec, class/spec]"
        4. Losing Team Captain: "[Class/spec, class/spec, class/spec] confirmed"
        5. Losing Team Captain: "[Losing Team Name]'s comp is [class/spec, class/spec, class/spec]"
        6. Winning Team Captain: "[Class/Spec, class/spec, class/spec] confirmed"
    • Following this conversation the next match must be started within 5 minutes.

Hosting


  1. Definition: The Host is the Player who must create the Wargame and ensure that the proper Settings and Map are used. The Host should set the player limit to match the number of players for the specified match.
     
  2. Host and Side Choice for each Game: The higher seeded team at match time must host the first game. The lower seeded team will host the second game. This will alternate until a tie breaker game is required.
     
  3. Procedure: Hosting Players should create the Wargame. As the hosting Team changes over the course of a Match, the new hosting Player should leave the Game and create a new one. 
     
  4. Finish Games: If a player’s connection to the server becomes unreasonable during a game, the Game must still be played. The lag incident should be reported to tournament support immediately following that game.
     
  5. Incorrect Ending: If either team leaves after the gates open, they may forfeit the game at the discretion of the admin.

All Matches


    Match Rules: 
    • Players may only play on the battle.net account they signed up with.
    • Players are required to be online and ready to compete at the start of the specified time. Once prepared, the Team Captain must notify the opposing team leader.
    • In the event that a team cannot compete at within 30 minutes of the scheduled time they will forfeit the first game.
      • If the team is still unable to compete, the admin will commence a 5-minute waiting period. If, after that 5-minute waiting period, the team is still unavailable they will forfeit the second map.
      • Should the series be a Best of 3, forfeiting the second match will forfeit the series.
      • Should the series be a Best of 5 or Best of 7, the admin will commence subsequent 5-minute waiting periods until matches have been forfeited that would forfeit the series.
    • All matches will be played on the World of Warcraft: Warlords of Draenor server determined by the tournament organizer.
    • During the game, players may not use chat except for the required announcements, a greeting, closing, and disconnects or other issues.
    • Players who intentionally quit a Game after the doors have opened will concede the Game.
    • If players enter a match and notice that the Tournament Gear Required buff is not present, they can immediately leave the match. Players may be required to provide a screenshot to prove the absence of the tournament mode buff, and should note in chat the reason for their leaving the match. Should teams leave in error (i.e. if the tournament mode buff was in fact present), they will forfeit the match.
    • Players experiencing connection or other issues should leave before the doors open. Players should announce this in chat if possible.
    • In the case of a technical issue, the tournament organizer administrator may restart the game from the beginning at their discretion. 
       
  1. Match Length: All Matches will be the best of 5 games. The team that reaches 3 game wins first wins the match.
     
  2. Warm-up: No warm-up or practice Games are permitted once the Tournament has begun. If a Match is played before the scheduled time, it will not be considered a warm-up and will count as the official results.
     
  3. Delays: Once a series has commenced, the total allowed delay for a Best of 5 is 15 minutes of allowed delay, and a best of 7 will have 20 minutes of allowed delay. This delay is additional to the 5 minutes allocated for comp and map picks. 
     
  4. Minimum Required Players: Teams may not play shorthanded. Teams without the required number of players will be considered unable to compete and are subject to map and match forfeits as detailed in All Matches Rule #1.
     
  5. Disconnections: If a player disconnects from the match before the starting gates have opened then all affected players must leeave the arena immediately in order to void the match. Any matches that have disconnects or lag issues that occur after the starting gates have opened must be played out. If a team leaves the arena after the gates have opened and the map is in play then they may be subject to a map forfeit. If a disconnect or drop occurs and the wargame must be remade, players are required to use the same team compositions they had before the drop occurred (this includes map one). 
     
  6. Normal Boundaries: Players who move their Character outside of the normal boundaries of a Map may Forfeit the Game at the discretion of tournament staff. Moving outside of the normal boundaries of a Map includes but is not limited to part of the Character’s body passing through what should be a non-permeable surface or object, and moving into any area from which your Character registers damage on an opponent who is not able to register damage on your Character.
     
  7. Outside Players/Spectators: After a game has been created, only eligible Players on the two Teams and Staff members may be invited/join. If an ineligible Player joins a Game, the Game must be ended if the player affects the game and/or doesn't leave within 30 seconds of joining. If a Player is found to have invited an ineligible Player to a Game, they will Forfeit the Game.
     
  8. Game Length: All games will last a maximum of twenty-five (25) minutes.
    • If no team has a clear lead after twenty-five (25) minutes, as determined by an admin (i.e. three players vs two players), the winner of that game in the series will be determined by total damage done as displayed on the Tournament Commentator User Interface.

Reporting


  1. No Shows: The No Show grace period time is 30 minutes after the match's original start time. For example, if a match is scheduled for 10:00 PM, the no show time for this match would be 10:30 PM. No Shows must be verified by a Tournament Official. In order to contact a Tournament Official use Live Support. If a Tournament Official isn’t immediately available, a Ticket must be submitted within 30 minutes of the scheduled match time. The Ticket must include proof that their opponent did not show. Select "I'm reporting: my opponent did not show" under “Report Problem” on the Match page. Please see the All Matches section for details about the no show forfeit process.
     
  2. Time Limit: Both teams must report the Match results within 10 minutes of its completion. Failure to report the Match results on time may result in a Forfeit.
     
  3. Report Match Score: To report the Match results, Teams must report the Match Score accurately, with overall Games won being reported. For example, the Match Score can be reported as 2-0, 2-1, 3-0, 3-1, or 3-2 depending upon the Match length. Reporting the individual points for each Game is optional.
     
  4. Cheating: Breaking any rule and any form of cheating, glitching, abusing in-game mechanics, or unsportsmanlike behavior may result in a Forfeit of a Game, Match, or Ban from GameBattles. Cheating, glitching, and abusing in-game mechanics accusations must be verified by a Tournament Official. In order to contact a Tournament Official use Live Support. If a Tournament Official isn’t immediately available, a Ticket must be submitted immediately, along with proof, screenshot or video, of the cheating. Punishable unsportsmanlike behavior includes, but is not limited to, excessive use of foul or degrading language. For all cheating claims, the burden of proof is on the accuser. Players may not use known bugs in the tournament matches, as determined by the tournament administration. A few known bugs are listed below, but MLG/Blizzard reserve to the right to pass judgement over any other in game actions that could be deemed a bug or an abuse of in-game mechanics.
    • Rain of Frogs use is not permitted.
    • Lightwells in pillars are not permitted.
       
  5. Screenshots: Teams may be required to provide screenshots of each game to prove the results of any series and Map and composition selections by each team.
    • Players are required to turn their in-game timestamps on (Option “15:27:32”) to be capable of providing accurate proof when taking screenshots of Game results as well as Map and Composition selections.
    • To turn Timestamps on, first go to the Game Menu, Interface, Social and click on the Chat Timestamps drop down box. Choose the option “15:27:32”.
    • The background of the chatbox of each screenshot must be completely transparent.
    • To make your chatbox transparent, right click on the chat channel and click on background. Then drag the opacity dial all the way down.
    • The team not starting the match can check that Tournament Gear is active by equipping a piece of gear that is not Tournament Gear and verifying that it is red on their character sheet. This should be screenshotted in-game for potential dispute resolution. 
    • Screenshots of game results must include a chat log of the following information
      • “X team vs Y team - Game Z - [DATE]”  
      • X=Team 1 name, Y=Team 2 name, and Z=the game played.
         
  6. Dispute Evidence: If a Screenshot(s) is needed in order to resolve a dispute, it should be transferred to the user’s computer and uploaded an image hosting website. Videos may also be uploaded to a website such as YouTube. The URL for the image(s)/video must be attached to the dispute Ticket(s) or provided to a Tournament Official via Live Support
     
  7. Disputes: In order to dispute Game results, Players/Teams must notify a Tournament Official, via Live Support or Ticket submission, that they would like to Protest the Game before a new Game has begun. Once the next game has started, players may not protest results. In order to dispute Match results, Players/Teams must notify a Tournament Official, via Live Support or Ticket submission, that they would like to Protest the Match. The tournament administration may investigate past results at their discretion
    .
  8. Concessions: Teams may request that they be allowed to concede victory of a Game. Teams may request that their opponent not receive a Forfeit penalty. A Tournament Official must be contacted with these requests. In order to contact a Tournament Official use Live Support.

Support


  1. Tickets & Live Support: Tournament support can be requested by creating a Support Ticket or Live Support. For issues with registration, missing tournament achievements, and general tournament questions, a “Tournament Question/Issues” Ticket should be created. For all tournament match issues, a “Solve My Dispute” Ticket should be created.
     
  2. Live Support Limit: Only 1 Player per Team should use Live Support for in-game issues and that Player should stay on Live Support until a Tournament Official answers their call.
     
  3. Listen for Instructions: If a Tournament Official is called into a Custom Game or party, Players must keep the Tournament Official un-muted at all times.
     
  4. Abuse: Verbal and/or written abuse of a Tournament Official will not be tolerated through any medium. This includes, but is not limited to, voice communications in game, voice messages, live support chats, written messages on GameBattles, Twitter, Facebook, etc. Violators of this rule may be disqualified from the Tournament.
     
  5. Technical Issues: If you are having technical issues, please contact support@mlg.tv and Live Support.
     
  6. Decisions Are Final: Tournament Staff have the final decision in all matters related to this competition. If a player feels the decision is unjust and/or goes against the rules listed for this competition, an Arena: Staff Report Ticket should be submitted for review. Please include any information and proof pertinent to the issue.

Penalties


  1. Settings: The hosting team will forfeit all maps where the incorrect setting(s) affected the game. If a game is hosted out of order, the hosting team will forfeit that game that was played out of order. 
     
  2. Restricted Items: Use of any restricted item(s) or gear will result in the loss of the map(s) the item(s) were used in if it affected game play.
     
  3. Premature Game Ending: Teams that force the game to end prematurely by having player(s) leave the game may be subject to a forfeit of that map.
     
  4. IP Flooding (DDoS Attacks): Performing or assisting with a DDoS attack of your opponent will result in immediate disqualification of that team. All players on that team will be suspended from GameBattles for up to seven hundred and thirty (730) days.
     
  5. Evading a Tournament or Servere Site Ban: Any player found evading a severe site ban or one related to Online Tournaments will be disqualified from this competition. If that player participates in any part of the match during the first tournament round, that team will forfeit the games that were played. If that player participates in any part of a match after the first tournament round, that team will be disqualified from the competition. The offending player(s) will be suspended from GameBattles for up to ninety (90) days.
     
  6. Piloting Battle.net Accounts: Tournament participants are forbidden to allow others to play in this competition in place of them by sharing Battle.net accounts. The offending the team will forfeit the entire match. The offending players will be suspended from the site for up to thirty (30) days.
     
  7. Hacks/Illegal Macros: Use of in game hacks and/or illegal macros will result in the immediate disqualification of that team. The player(s) using the hacks and/or illegal macros will be suspended from GameBattles for up to seven hundred and thirty (730) days and disqualified from the tournament. The rest of the team will be suspended for up to ninety (90) days and disqualified from the tournament.
     
  8. Evading a Ban: If a player is found evading a ban the team will be disqualified from this competition. The offending player(s) will be suspended from GameBattles for up to ninety (90) days.
     
  9. Lack of Cooperation: Failing to comply with Support Staff's directions and/or requests may result in the forfeit of a map or the entire match as detailed below in the Match Offenses rule.  Verbal or written abuse of a staff member will result in a suspension from GameBattles for up to twenty (20) days.
     
  10. Match Offenses: If a Player does not follow any of the rules listed on this rules page, the player may receive a warning at the discretion of the tournament organizer.
    • If a Player causes a delay beyond the designated exceptions, the player will receive a warning. (warnings persist for the duration of the tournament)
    • Player misconduct as defined in the player responsibilities will receive a warning at the discretion of the organizer.
    • The first misconduct warning will carry over throughout the current season.
    • In a single competition day, if a Player receives:
      • Two (2) warnings they will forfeit the next Game
      • Three (3) warnings they will forfeit the next match
      • Four (4) warnings will cause a disqualification from the current tournament
    • Players may request the status of their total warnings from the organizer.
       
  11. Disqualification: Some infractions may result in warnings and penalties being bypassed with immediate disqualification from the remainder of the Tournament being enforced. Examples of behavior or actions that could result in this are physical acts violence, cheating, collusion/manipulating the bracket, drug/substance abuse on-site, any illegal activities, betting or gambling on a tournament or match results, hate speech, and harassment.

General


  1. Rules: The rules may be updated and modified at any time, for any reason. Rulings may be made outside the scope of these Rules in order to preserve fair play and tournament integrity. Participation in this Tournament constitutes entrant’s full and unconditional agreement to these Rules, the Official Rules on the Prize tab, and Tournament Official decisions, which are final and binding in all matters related to this tournament. Winning a prize is contingent upon fulfilling all requirements set forth herein.
     
  2. Eligibility: United States, Canada, Mexico, and Central America Residents only. Not valid in Arizona, Connecticut, Maryland, and Quebec. Employees of MLG, the Tournament's participating sponsors and their advertising agencies, and members of the immediate family of any such persons, are not eligible to participate and win. For the complete list of restrictions/limitations, please visit the prize tab. Any team found using a restricted player may be disqualified from the tournament without a refund of credits.
     
  3. Players: Players 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 this Tournament and/or receive any prizes. As a user, you are personally responsible for accepting any invitation to a Team. If you receive a paid invite to a team, you accept the credits used for entry as your own in order to participate in this competition. If you do not personally accept a Team invitation, you may be disqualified from the Tournament and Forfeit any prize. All players must have an Battle.net account in good standing and be signed into Battle.net for all Games. All MLG/GameBattles accounts, teams, roster spots and crowns are property of Major League Gaming Inc. Any advertising of, or attempts to buy, sell, trade, or exchange any aforementioned item is strictly prohibited. This also includes offering to forfeit matches in exchange for any item or service. Violators will be removed from all MLG/GameBattles online properties and all related accounts terminated. Furthermore, MLG reserves the right to deactivate, reset or temporarily suspend any account or team, without notice, that violates our Terms of Use.
     
  4. Team Management: If leadership of a tournament team is transferred to another member of that team, that person gives up all team editing privileges(adding/removing players, disbanding team, ect.). This includes any player/team "credit sponsors". As a warning, credits will not be refunded for any players the "credit sponsor" pays for if he/she is removed from the roster after leadership is transferred.
     
  5. Valid Battletags: All battletags on a team’s roster must be valid. Each user on the Roster must legitimately own their battletag. A battletag’s spelling and spaces must be exact, but the correct case is not necessary. Battletags may not contain foul language, disparaging remarks, hateful or racist names. Any changes to a team roster after the tournament has been seeded is at the discretion of tournament staff. This includes changes to Battle.net IDs, etc. Battletags must be linked to a player's GB/MLG Account before the start of the tournament bracket play.
     
  6. Privacy & Impersonation: Individuals 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, battletags, email accounts, etc. Individuals may not use another Player’s Battle.net Account in a Game. Individuals may not allow another Player to use their Battle.net Account in a Game. Players who break this rule may be disqualified from the Tournament. In game IP checks will be administered at the discretion of the Online Tournament Staff. This will ensure no one is account recovering and attempting to play on another person's account. However, IP checks will not be be given after the match has been completed.
     
  7. Broadcast: MLG reserves the right to broadcast any Match. If MLG chooses to broadcast a Match, MLG Staff members must be allowed into each Game.
     
  8. Third Party Communication: Third party communication is allowed for this tournament. (i.e. skype, TeamSpeak, Party Chat, etc.). However, players must be able to communicate with any staff member that joins the Custom Game.
     
  9. Check In: Teams must use the Check In system on the day of the Tournament in order to acknowledge that they are ready to play in the Tournament. Teams that do not go through the Check In procedure will not be eligible for the Tournament and will not be placed into the Bracket. Anyone on a Team can check the whole Team in. For a detailed explanation on how to check in, Please review this support article.
     
  10. Team and Character Names:
    • Team names must not be longer than 15 characters, spaces included.
    • Team names must not contain profanity, the names of people not on the team, or the names of any group at odds with Blizzard/MLG.
    • Blizzard/MLG may reject team names and request renames for any reason. If renames are not acceptable, Blizzard/MLG may assign a team name to the team. 
    • Character names must not contain profanity, the names of people not on the team, or the names of any group at odds with Blizzard/MLG.
    • Blizzard/MLG may flag characters for a free rename for any reason. If renames are not acceptable, Blizzard/MLG  may assign new character names to characters.  
       
  11. WoW and Battle.net Accounts:
    • Players must have authorized access to a World of Warcraft account that is in good standing and has been upgraded with the “The Burning Crusade,” “Wrath of the Lich King,” “Cataclysm,” “Mists of Pandaria” and “Warlords of Draenor” expansions to World of Warcraft upon the commencement date of the tournament, and which remains in good standing throughout the tournament.
    • All players must meet the stated rating requirement to be eligible to participate, and ensure their battle.net contact information is accurate and up-todate. 
       
  12. Legal Macros: Players may use any addon or macro they wish as long as:
    • For all actions it is required to push a button.
    • No timers, actions, scripts, or macros automatically activate or trigger in response to opponent’s or ally’s actions (no automatic cooldown trackers).
       
  13. Team Content: The Leader of a team can change the team name, blast message, logos, avatars and website links. The images/information submitted 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.
     
  14. Prizing and Bracket Size: Tournament bracket size and prize are subject to change based on the total number of eligible teams at the end of registration.