http://www.avforums.com/forums/blogs/tg-v1p3r-152499/ Home Entertainment and Audio Visual Home Consumer Electronics Forums en Tue, 24 Nov 2009 00:19:11 GMT vBulletin 60 http://www.avforums.com/forums/images/misc/rss.jpg http://www.avforums.com/forums/blogs/tg-v1p3r-152499/ http://www.avforums.com/forums/blogs/tg-v1p3r-152499/1397-mlg-gamebattles-match-rules.html Wed, 10 Jun 2009 07:29:04 GMT _*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... 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.

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.

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 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.

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

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 map, they must find eligible substitutes prior to beginning the next map. A team is not allowed to start a map 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 maps as per rule number 6. Please follow the steps in rule number 6 if the match is delayed longer than 5 minutes between maps.

12. Only one player per console is permitted.

13. All players must use the Spartan character model[:grin:]. Any team found using an Elite character model will forfeit all maps that the character was found on. ]]> TG V1P3R http://www.avforums.com/forums/blogs/tg-v1p3r-152499/1397-mlg-gamebattles-match-rules.html