World of Tanks CORSAIR Community League

Hello, Tankers!

CORSAIR will run its "Spring Season" with Wargaming support! The format will be:

5v5 with 2 Reserves Tier X Attack/Defense Two Caps

Calendar

The next season is right around the corner with registration for the open qualifier beginning on March 27 and the qualifier starts on April 8. The qualifier reduces the number of teams down to 10 for this season with the regular season being round robin for a total of 25 match days. Playoffs will consist of 6 teams with 1st and 2nd getting a bye to the semi-finals. You can see the full calendar in the spoiler below. Please note: The calendar is subject to change and is not final.

Calendar of Events

Expand
Friday, March 27 Registration opens
Monday, April 6 Registration closes at 11:59 p.m. ET
Wednesday, April 8 First qualifier day begins at 8:30 p.m. ET
Friday, April 10 Second qualifier day begins at 8:30 p.m. ET
Monday, April 13 Third qualifier day begins at 8:30 p.m. ET
Wednesday, April 15 Fourth qualifier day begins at 8:30 p.m. ET
Friday, April 17 Fifth qualifier day begins at 8:30 p.m. ET
Monday, April 20–Saturday, April 25 Paperwork Week
Tuesday, April 21 Mandatory League meeting begins at 9 p.m. ET
Saturday, April 25 Paperwork submission deadline 3 a.m. ET
Monday, April 27 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Wednesday, April 29 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Friday, May 1 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Monday, May 4 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Wednesday, May 6 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Friday, May 8 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Saturday, May 9 Roster change period: 3 a.m. ET through Sunday, May 10 at 10 p.m. ET 
Monday, May 11 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Wednesday, May 13 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Friday, May 15 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Monday, May 18 Match day, pick/ban at 7:30 p.m. ET, game at 8:30 p.m. ET
Wednesday, May 20 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Friday, May 22 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Saturday, May 23 Roster change period: 3 a.m. ET through Sunday, May 24 at 10 p.m. ET
Monday, May 25 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Wednesday, May 27 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Friday, May 29 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Monday, June 1 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Wednesday, June 3 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Friday, June 5 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Saturday, June 6 Roster change period: 3 a.m. ET through Sunday, June 7 at 10 p.m. ET 
Monday, June 8 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Wednesday, June 10 Match day, pick/ban st 7:30 p.m. ET, game at 8:30 p.m. ET
Friday, June 12 Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Monday, June 15 Match day, pick/ban at 7:30 p.m. ET; game 8:30 p.m. ET
Thursday, June 18 Mandatory League meeting for playoff teams at 9 p.m. ET
Friday, June 19 Playoff Quarter-finals Match day, pick/ban at 7:30 p.m. ET; game 8:30 p.m. ET
Saturday, June 20 Playoff Semi-finals Match day, pick/ban at 7:30 p.m. ET; game 8:30 p.m. ET
Sunday, June 21 Playoff Finals Match day, pick/ban at 7:30 p.m. ET; game at 8:30 p.m. ET
Collapse

Prizes

In the "Prizing" spoiler you can see the different rewards you can earn depending on how your team finishes. Every match your team wins will reward your team with a prize pool of 2,500 Gold and 1,500 Bonds that will be split between the players who participated in that specific match. This includes the regular season and the playoffs.

Note:
• In-game prizes payout can take up to two (2) weeks; physical prizes shipping can take up to three (3) months.
• Physical Prizing will only be shipped to Canada, U.S.A., and Mexico.
• Prizing is per player.

CORSAIR Headset & Type 59 Lottery

Qualify for our Lottery by playing in the qualifier and showing up to every battle. If your entire team fails to show up to a game, you are no longer eligible for the draw. After the qualifier playoffs, two are selected at random from the list of eligible players:

Streams

The Community League will stream six (6) matches every week during the season, starting April 27. Hosts for this season are:

Coverage in English:

TheLoveHitman and Haglar

Coverage in Spanish:

Zotz

Coverage in Portuguese:

WorldOfHueOficial

If you are looking to create a team for the upcoming season, join the Community League Discord!

REGISTER FOR THE TOURNAMENT


CORSAIR © PRIZES

Prizes for the top teams are provided by CORSAIR

Founded in 1994, CORSAIR has grown from pioneering the high-performance DRAM market into one of the world’s leading providers of high-performance gaming and streaming products. CORSAIR offers a complete range of products to equip gamers, enthusiasts, and esports athletes, including mechanical keyboards, precision gaming mice, wireless headsets, premium PC components, and the CORSAIR ONE fully-integrated gaming PC. With a company-wide commitment to quality, innovative design, advanced features and high-performance, CORSAIR products have won thousands of media and industry awards, earning their place in gamers’ hands and PCs following years of development and engineering by a team dedicated to building great products that they themselves would want to use.

Official Rulebook

Expand

World of Tanks CORSAIR Community League
Spring 2020 Season
Official Rulebook

Last updated March 17, 2020

Any amendments will be documented and listed at the end of this document.

1. Description

1.1. The following document contains rules and regulations for fair and competitive play, the responsibilities of the league and its participants, and guidelines for the World of Tanks CORSAIR Community League.

2. Agreement

2.1. All players who register for the CORSAIR Community League - qualifier agree that they have read and will abide by all rules and regulations listed in this document, which may be amended when necessary by the admin team.

3. In Good Standing

3.1. All players who register for the CORSAIR Community League season must be in good standing with Wargaming.

3.11. If a player has an account that is permanently banned by Wargaming, they will not be permitted to participate in the CORSAIR Community League season.

3.12. If the admins of CORSAIR Community League become aware of a player that does have an account that is permanently banned, they will be removed from the league after confirmation with Wargaming.

3.13. If a player receives a permanent ban from Wargaming during the duration of the season, the player will be removed from the league.

3.14. If a player receives a temporary ban from Wargaming, CORSAIR Community League may enforce their own temporary ban on the player in question.

3.2. Players who lose good standing will be banned for the remainder of the season which will result in their removal from the league.

3.3. Teams who lose good standing will be removed from the league for the remainder of the season.

3.3.1. If a team is removed, all their games for the season will be turned into technical victories for all of their opponents. They will be placed at the bottom of the standings with 0 points. They will not be eligible for any prizing.

3.4 If a team or player falls out of good standing with CORSAIR Community League and actions are taken against a team or player(s), either by a player(s) being removed or a team being removed, Wargaming will be notified and we will forward all evidence regarding the situation. Wargaming reserves the right to take further action against the player(s) in question.

4. Code of conduct

4.1 All players, coaches, and anyone involved in the league will be held to our Code of conduct rules as follows.

4.2. Behavior - Players are required to behave in a sportsmanlike manner towards other competitors, members of the administration team, media, and fans. Do not be toxic to other members of the community. Toxicity is hard to define, but in general, do not personally attack anyone else. No flame, avoid passive aggressive comments. In the end, it will be the discretion of the admin staff what constitutes poor sportsmanship and toxic behavior. We simply suggest that all players be nice and helpful to each other.

4.3. Cheating - Any form of cheating will not be tolerated. If the admin team determines that a participant or team is cheating, the participant or team will be immediately disqualified from participating in the Tournament. This includes the use of any illegal mods as defined by Wargaming.

4.4. Software Exploitation - Any intentional use of any bugs or exploits in the game may result in a forfeit of the match and/or disqualification from the tournament. This does not include “boosts” or “climbs”.

4.5. Collusion and Match Fixing - Players are not allowed to intentionally alter the results of any match. If the admins determine that a player or team is colluding or match fixing, the player or team will be immediately disqualified and removed from the tournament.

4.6. Gambling - All players, casters, and admin staff associated with the World of Tanks CORSAIR Community League are forbidden from placing wagers on any matches.

4.7. DDOSing - If we find proof that a team or player DDOSed another team or paid for someone to DDOS another team during a match. We will immediately ban the player or team from the league.

4.8. Reporting - Reporting a team or player is always helpful and we will try and follow up. To do this though, we need evidence. Screenshots, voice clips, however it happened, if we can’t see it, we can’t punish it.

4.9. Violations of any of these rules will be reviewed by the admins and any punishment will be handled on a case by case basis.

5. Schedule

5.1. Written Dates and Times

  • Friday, March 27 - Registration opens
  • Monday, April 6 - Registration closes at 11:59pm EST
  • Wednesday, April 8 - First qualifier day begins at 8:30pm EST
  • Friday, April 10 - Second qualifier day begins at 8:30pm EST
  • Monday, April 13 - Third qualifier day begins at 8:30pm EST
  • Wednesday, April 15 - Fourth qualifier day begins at 8:30pm EST
  • Friday, April 17 - Fifth qualifier day begins at 8:30pm EST
  • Tuesday, April 21 - Mandatory League meeting begins at 9pm EST
  • Saturday, April 25 - Paperwork submission deadline 3am EST
  • Monday, April 27 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Wednesday, April 29 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Friday, May 1 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Monday, May 4 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Wednesday, May 6 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Friday, May 8 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Saturday, May 9 3am EST through Sunday, May 10 10pm EST - Roster change period
  • Monday, May 11 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Wednesday, May 13 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Friday, May 15 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Monday, May 18 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Wednesday, May 20 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Friday, May 22 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Saturday, May 23 3am EST through Sunday, May 24 10pm EST - Roster change period
  • Monday, May 25 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Wednesday, May 27 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Friday, May 29 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Monday, June 1 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Wednesday, June 3 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Friday, June 5 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Saturday, June 6 3am EST through Sunday, June 7 10pm EST - Roster change period
  • Monday, June 8 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Wednesday, June 10 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Friday, June 12 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Monday, June 15 - Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Thursday, June 18th - Mandatory League meeting for playoff teams at 9pm EST
  • Friday, June 19th - Playoff Quarter-finals Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Saturday, June 20th - Playoff Semi-finals Match day, pick/ban 7:30pm EST, game 8:30pm EST
  • Sunday, June 21th - Playoff Finals Match day, pick/ban 7:30pm EST, game 8:30pm EST

6. Qualifier Information

6.1. All qualifier details, scheduling, rules, and regulations are subject to change without notice.

6.2. All teams will start their registration for the CORSAIR Community League Season by participating in the CORSAIR Community League Qualifier found on the Wargaming website under the tournaments section.

6.3. After the qualifier, all 10 qualified team captains will receive a private message on the World of Tanks NA Forums with a list of documents to complete their registration that they must fill out by Saturday, April 25 3am EST. All 10 team captains must join the CORSAIR Community League Discord as that will be the program used for communication between league admins and teams.

6.4. All 10 teams that qualify must have at least 1 player represent their respective teams at the league meeting on April 21 which starts at 9pm EST.

6.5. If a team fails to reply to the message on the forums or fails to have a representative at the league meeting, a major strike will be issued. If a team fails to do either, it will be taken that they do not wish to participate in the rest of the CORSAIR Community League Season. We will then look for a suitable replacement team from the qualifier to fill their spot.

6.6. If teams are caught using illegal mods as defined by Wargaming during the qualifier, they will be immediately removed and we will attempt to find a suitable replacement team from the qualifier.

6.7. For a team to qualify as a suitable replacement, they must not break any rules in this document during the qualifier.

6.8. If we fail to find a suitable replacement, we may start the season with less than 10 teams.

6.9. Qualifier Format

6.9.1. The 5/50 format (5 tanks and 50 total tier points) will be the official format of play for the CORSAIR Community League Qualifier.

6.9.2. Minimum number of players on a team is 5, max 7.

6.9.3. Minimum number of players to start a battle to avoid a technical defeat is 4.

6.9.4. There will be no tank restrictions during the qualifier.

6.9.5. Battle format will be two cap attack/defense.

6.9.6. Official battle time will be 8 minutes.

6.9.7. Cap timer will be 120 cap points.

6.9.8. The map pool for the qualifier will be as follows:

Round 1: Prokhorovka
Round 2: Himmelsdorf
Round 3: Murovanka
Round 4: Sand River
Round 5: Cliff

6.9.9. All remaining qualifier information for the qualifier will be released at a later date prior to the start of the qualifier.

7. Completing Registration

7.1. The following documents will only be given to the team captains and players that qualify for the season by coming in the top 10 of the CORSAIR Community League Qualifier.

7.2. All teams and players must fill out any documents and provide any information requested of them by the CORSAIR Community League Head Admin.

7.3. All players must fill out the Registration Google form page.

7.4. During the paperwork week, teams may change their name for the season pending approval from the Head Admin.

7.5. During the paperwork week, players will be asked to submit a preferred name for their event account. All account names must be approved by the head admin.

7.6. Any team that qualifies for the season with only 5 players on their roster must add 1 additional player to their roster during the paperwork week.

7.7. The paperwork submission deadline is Saturday April 24 3am EST.

7.8. Any player caught submitting false information may be subject to punishment at the discretion of the CORSAIR Community League admin staff.

7.9. Any team that fails to submit the required paperwork by the deadline will be given a major strike and the team captain will receive a strike.

7.9.1. The Head Admin may decide to start the league with less than 10 teams if a team fails to submit all required paperwork.

8. League Meetings

8.1. There will be 2 league meetings all season long, 1 during the paperwork week that every team is required to have a representative at and 1 prior to the playoffs that all playoff teams must have a representative at.

9. Captain and Player Responsibilities

9.1. Captains

9.1.1. All captains must be a part of the CORSAIR Community League Discord for the duration of the season as this will be the main program for communication. Messages sent through any other means may be disregarded.

9.1.2. The captain has the most responsibility placed upon him. He will be held responsible for the paperwork and all formal communication between the team and the league admins. He is responsible for any and all players actions and may be held accountable for them.

9.1.3. The team captain should be the representative at the league meetings but it is not required. If the team captain plans for another player from their team to represent them at the meeting, the captain is still responsible if that player doesn’t show up to the meeting.

9.1.4. The captain is also counted as a player.

9.1.5. The position of team captain may be changed if the team reaches a supermajority vote, which is 66% or more. For a 7 person team, this requires 5 players to vote in favor of the change. For a 6 player team, this requires 4 players to vote in favor of the change.

9.1.6. The admin team has the right to revoke or transfer the title of captain based on but not limited to: lack of communication, inappropriate behavior, or illegal activity.

9.2. Players

9.2.1. Players are responsible for their own internet connection and electrical power.

9.2.2. Players are responsible for informing their team captain and the head admin if they wish to leave their team on the Saturday of any roster period.

9.2.3. We highly recommend that all players for the season join the CORSAIR Community League Discord Server. This will help the admin staff get in contact with your team if your captain is not responding.

9.2.4. Follow the code of conduct and the other rules listed in this document, don’t break the World of Tanks End User License Agreement and Game Rules.

10. Roster information

10.1. Teams must consist of a minimum of 6 players, maximum of 7 players.

10.2. Teams are not allowed to have less than 4 players from the original qualifying roster at any point in the season.

10.3. Teams may only consist of less than 6 players if a player(s) is removed from the league.

10.3.1. Players can be removed from the league either by being banned or by being ejected from the team.

10.3.2. If a player(s) is removed from the league, teams will either have to wait for the roster change period or apply for an emergency roster change to add another player to their roster.

10.3.4. Each team will be allowed 1 emergency roster change throughout the season. Any additional emergency roster changes will only be allowed at the discretion of the Head Admin.

11. Roster Changes

11.1. With Covid-19, the CORSAIR Community League reserves the right to change all information regarding roster changes at any point in the season.

11.2. Roster Change Period

11.2.1. There will be 3 roster change periods all season.

Saturday, May 9 3am EST through Sunday, May 10 10pm EST
Saturday, May 23 3am EST through Sunday, May 24 10pm EST
Saturday, June 6 3am EST through Sunday, June 7 10pm EST

11.2.2. Teams will be allowed to remove up to 2 players from their roster during each roster change period.

11.2.3. If a team has less than 6 players on their roster during each roster change period, they will be required to add players to their roster until they reach the minimum of 6 players during the roster change period.

11.2.4. If a team wishes to remove a player during a roster change period, they must submit that player’s name to the head admin on the Saturday of any roster change period. A team then has until the end of the roster change period on Sunday to submit to the head admin the name of any player they wish to add to their roster. Any player removed from a roster by a team can join any other team in the league during that same roster change period.

11.2.5. If a player decides to leave a team, they must inform their team captain and the head admin on the Saturday of any roster change period. They can then join any other team in the league on the Sunday of that same roster change period. If a player fails to inform their team captain and the head admin that they intend to leave a team on the Saturday of any roster change period, they may not be allowed to join another team in the league until the next roster changer period.

11.2.6. All roster changes must be submitted to the Head Admin before the end of each roster change period

11.2.7. A player joining the league must be in good standing and have all the registration information submitted to the Head Admin by the end of each roster change period to be eligible to play in the league. The player will not be allowed to play in any match until all required information is submitted.

11.2.7.1.1. Failure to have this information submitted by the deadline will be a strike for the player joining the league, a strike for the captain of the team and a minor strike to the team.

11.3. Player Ejections

11.3.1. Teams may vote to eject a player from their team.

11.3.1.1. Ejection of a team member, including team captain, requires a supermajority vote, which is 66%. For a 7 person team, this requires 5 players to vote in favor of the ejection. For a 6 player team, this requires 4 players to vote in favor of the change.

11.3.1.2. Ejection of a team member must be communicated to the Head Admin immediately.

11.3.1.3. A team that ejects a player cannot replace them until the next roster change period.

11.3.1.4. If a player is ejected from a team, that player is still eligible to participate in the league if another team wants to add them to their roster either through the roster change period or through an emergency roster change.

11.3.1.5. A team may not eject a player if they have less than 6 players on the roster.

11.4. Emergency Roster Changes

11.4.1. Emergency roster changes will only be allowed at the discretion of the Head Admin.

11.4.2. They are only intended to be used in case a player ends up in the hospital, has a family emergency, is dealing with a natural disaster or in other rare cases.

11.4.3. If an emergency roster change is allowed, the joining player will be given 48 hours to complete all registration documents. They will be allowed to play any matches during that time.

11.4.4. If a team uses an emergency roster change then that team loses one of the available roster changes available to them during the next roster change period.

11.5. During the paperwork week, any team that is found to have a player that is not in good standing with Wargaming will be removed and those teams will be allowed to replace them with another player who is in good standing.

12. Mods

12.1. All modifications are strictly prohibited for the duration of the CORSAIR Community League Season.

12.1.1. The only exception to this rule is during the qualifier where Wargaming approved mods will be allowed.

12.2. Every player must play with a vanilla client (no mods allowed, not even Wargaming approved mods)

12.3. Failure to abide by this rule may result in forfeiture of a match, ejection of a player, disqualification of a team, or a suitable punishment determined by the admin team.

13. Strike System and Bans

13.1. Strikes are permanent and will not be removed.

13.2. Strikes are broken up into team strikes and player strikes

13.3. Players

13.3.1. Players may not have more than 2 strikes against them. A 3rd strike will remove the player from good standing status for the remainder of the season.

13.3.2. Violations of this document by a player will earn the player a strike at the discretion of the admins.

13.3.3. The player and the team captain will be notified when a strike is given.

13.4. Teams

13.4.1. Teams may not have more than 4 strikes against them. A 5th strike will remove the team from good standing status for the remainder of the season.

13.4.2. Teams can earn minor strikes which are worth 1 strike and major strikes which are worth 2 strikes. This allows for more flexibility with punishing a team. Teams can earn any combination of minor and major strikes as long as the total value of the strikes does not exceed 4.

13.4.3. Violations of this document by a team will earn that team a strike at the discretion of the admins.

13.4.4. The team captain will be notified when the strike is given.

13.5. Bans

13.5.1. A player may receive a suspension/temporary ban from all matches within the defined amount of time as punishment for breaking the rules listed in this document or by receiving a temporary ban from Wargaming.

13.5.2. If a player or team falls out of good standing, they will be banned from the current season of CORSAIR Community League.

13.5.3. The CORSAIR Community League admin staff reserves the right to bypass the strike system and ban a team or player if we feel that the actions of the team or player deserve such a punishment.

13.5.3.1. Any decisions of this level will be discussed with Wargaming prior to being handed out.

14. Regular Season Information

14.1. Round Robin Format

14.1.1. Round Robin format will be used for the regular season.

14.1.2. During the regular season each team will face every team once.

14.1.3. CORSAIR Community League reserves the right to extend the regular season if problems with the World of Tanks servers prevent matches from being played.

14.1.3.1. This decision will be made by the head admin and Wargaming.

15. Playoffs Information

15.1. The Playoffs start after the season’s regular games are finished.

15.2. The 6 teams who ranked 1st through 6th in the regular season will play in a single elimination bracket.

15.3. The 4th and 5th place teams will be seeded against each other.

15.4. The 3rd and 6th place teams will be seeded against each other.

15.5. The 1st place team will be seeded against the lowest ranked team after quarter finals. The 2nd place team will be seeded against the remaining team after the quarter finals.
Example: 6th wins 3rd vs 6th and 4th wins 4th vs 5th, then 1st will fight 6th and 2nd will face 4th.

15.6. The game deciding 3rd and 4th will be played between the two team who lost in the semi-finals.

15.7. Match rules for playoffs are the same as the regular season.

16. Season Format

16.1. The 5/50 format (5 tanks and 50 total tier points) will be the official format of play for the CORSAIR Community League.

16.2. A team must have at least 5 vehicles with 48 tier points to compete in a battle during the regular season and playoffs.

16.3. Teams are allowed to bring tier 8-10 tanks except for clan wars reward vehicles and personal rewards vehicles.

16.4. Both teams are allowed to make changes in their tank roster and vehicle setup after each battle.

16.5. Battle format will be two cap attack/defense.

16.6. Official battle time will be 8 minutes.

16.7. Cap timer will be 120 cap points.

16.8. Regular season matches will be held in training rooms.

16.9. Teams will only play on any of the 8 official maps.

16.9.1. Sand River, Cliff, Himmelsdorf, Ruinberg, Prokhorovka, Steppes, Ghost Town and Murovanka

16.10. Tank Selection

16.10.1. A 60 second timer will be used for tank selection.

16.10.2. Teams will receive three messages in the training room chat window. One being a 60 second timer starting now, a 30 second warning and a 15 second warnings.

16.10.3. At the end of the 60 second timer the battle will start.

16.10.4. Each team is responsible for making sure their players are ready by the end of the 60 second countdown timer.

16.11. The order of battles within a match is as follows.

16.11.1. Regulation

16.11.1.1. Map 1: Battle 1, Battle 2

16.11.1.2. Map 2: Battle 3, Battle 4

16.11.1.3. Map 3: Battle 5, Battle 6

16.11.1.4. Map 4: Battle 7, Battle 8

16.11.2. Overtime

16.11.2.1. Map 1: Battle 1

16.11.2.1.1. Over time for this season will be a best of 1

16.11.2.1.2. Side choice for the overtime battle will be given to the team with (in this order) fastest attack, most kills in total across all attacking battles (Kills will be counted as any vehicle destroyed on the defensive side), and then most damage done in total across all attacking battles.

17. Map Pick/Ban

17.1. The Map Pick/Ban process will start one hour prior to the start of matches at 7:30pm EST.

17.2. It will be held on CORSAIR Community League Discord server.

17.3. Teams are required to have a representative present at the time of pick and ban. The representative is not required to be the Team Captain. Failure to have a Player represent your team will result in a minor strike. After 7:40pm EST, if a representative does not show up to your scheduled Pick/Ban, the admins will randomly pick and ban maps for your match.

17.4. Map Pick/Ban Process

17.4.1. Map Pick/Ban Process is split between Regulation and Overtime.

17.4.2. The Map Pick/Ban Process will proceed in order of the steps listed below. Regulation:

1. The team listed first on the match schedule will call the coin toss
2. Winner of the coin toss will choose to either be Team A or Team B
3. Team A bans a map
4. Team B bans a map
5. Team A picks the first map
6. Team B picks their starting side on the first map
7. Team B picks the second map
8. Team A picks their starting side on the second map
9. Team A bans a map
10. Team B bans a map
11. Team A picks the third map
12. Team B picks their starting side on the third map
13. Team B picks the fourth map
14. Team A picks their starting side on the fourth map

Overtime:

1. A second coin will be tossed and the team listed first on the match schedule will call the coin toss.
2. Winner of the coin toss will choose to either be Team A or Team B
3. Team A bans a map
4. Team B bans a map
5. Team A bans a map
6. Team B bans a map
7. Team A bans a map
8. Team B bans a map
9. Team A picks the map
10. The last map is not played in Overtime

18. Timeouts

18.1. At the conclusion of a battle and before tank selection for the next battle, a captain may declare a timeout.

18.2. A timeout lasts 2 minutes.

18.3. Each team has 1 timeout per match.

19. Training Rooms

19.1. All matches are played using the Training Room system.

19.2. All Training Rooms will be hosted on the US Central server.

19.3. Order of Operations before and between battles will be done in this order:

• Step 1: Before a battle begins, the admin will ask both teams if they wish to make any changes to their roster for the next battle. Teams will be given 20 seconds to indicate any roster changes. If a team wishes to make a roster change they should answer in a similar fashion to these examples.
Example 1: -Vyraall +Hitman.
Example 2: Remove Hitman, Add Vyraall
• Step 2: Both teams will confirm with the admin that their sides, map, and rosters are correct. Teams will be given 20 seconds to answer with “ready”, “yes” or “++”. The admin will then proceed with tank selection.
• Step 3: A 60 second timer will be used for tank selection. Teams will be told in the training room chat, 60 seconds, 30 seconds, 15 seconds, indicating the remaining time on the timer. Teams have until the end of the timer to ready up their tanks. When the timer hits 0, the battle will begin even if one team is short players.

20. Disputes

20.1. For any dispute involving a match, the replays and Python logs may be investigated.

20.2. Only team captains may file for an investigation, and must do so by private message to an admin on the official CORSAIR Community League Discord server. Any requests made using any other method or to any other League personnel will not be considered.

20.3. All disputes must be filed on the same day of the grievance in question.

21. Technical Victories/Defeats

21.1. Technical Victories/Defeats for Battles

21.1.1. Teams failing to field an adequate team (minimum of 5 tanks and 48 tier points) will have the battle declared as a technical victory for the opponent.

21.1.2. If either team has a player enter a battle in spectator, the battle will be declared a technical victory for the opposing team.

21.2. Technical Victories/Defeats for Matches

12.2.1. If a team is short 2 minutes after official match start time, a minor strike is given.

12.2.2. If a team is short 10 minutes after official match start time, a major strike will be given and a technical victory will be declared for the other team.

12.2.3. Technical victories are recorded with a score of 5-0 for the opposing team.

12.2.4. Technical victories are declared at the discretion of the admin team.

22. Streaming

22.1. By participating in the CORSAIR Community League season, all teams agree to have their matches streamed.

22.2. By participating in the CORSAIR Community League season, all teams agree to have their voice communications broadcasted during a listen-in. Teams will be notified prior to the start of a match which battles will be a listen-in.

22.3. 44 out of the 45 matches in the regular season will be on the three mainstreams.

22.4. Teams must be ready to play their match 10 minutes prior to the start time of their match.

22.5. If the first match of the night is declared a technical victory for a team. The second match of the night will begin at 9pm EST.

22.6. POV streams will be permitted. We advise a 8 min delay as CL is not responsible for any stream sniping or position reporting.

22.7. Any additional information and rules will be provided to teams in advance to the start of their match.

23. Accounts

23.1. Each player will be assigned an event account for the season.

23.2. Every player must follow the CORSAIR Community League rulebook, CORSAIR Community League Code of Conduct, Wargaming Een User License Agreement and Game Rules while using the event accounts.

23.3. Players must use the account assigned to them to compete in every match.

23.4. Players must not share event accounts

23.5. Any action that happens on the assigned account is the sole responsibility of the player the account is assigned to.

23.6. Players are not allowed to change any account information on the Wargaming website for the event accounts including the account name and password.

23.7. Players found to be in violation of these rules face potential punishment by the strike system and might be potentially disqualified from the league.

23.8. Players will be provided with their event account for the season once they have completed all required paperwork.

23.8.1. The latest a team may receive their event accounts after submitting all required paperwork is before map pick/bans begin on Monday June 3rd 2020.

24. Disconnects

24.1. No disconnects will be called
After a tank is spotted or
After 30 seconds have been played in the battle

24.1.1. If either of these have happened, the battle will be played out.

24.2. Teams will call a disconnect by typing “disconnect” into the all chat window in the game client.

24.3. If the disconnect is called within the legal timeframe, an admin will reply with “confirm”.

24.4. If a disconnect is called, all tanks in the battle must immediately stop moving and remain where they are. Both teams will then follow any instructions given to them by the admin.

24.5. If the disconnected player cannot reconnect within 2 minutes, the substitute player must be used.

24.6. If the player does not return within the 2-minute window and there is no substitute available, a 3 minute timer will then be set. If either the disconnected player or a substitute are not in the training room after the end of the 3 minute timer, the admins may declare a technical victory for the match in favor of the opposing team .

24.7. If the battle is restarted, player and tank composition for both teams must remain the same as it was for the first battle attempt.

24.7.1. If the substitute player must be used, only the tank composition for both teams must remain the same for both teams.

24.8. If a player disconnects more than 1 time in a match, it is at the admins discretion to force the team to replace the player for future battles in the match.

24.9. During a match, only 1 disconnect may be called by each team.

25. Replays and Python Logs

25.1. Players must set replays to record every battle.

25.2. The team captain is required to submit all Python logs and replays from every player on their respective teams to the head admin within 12 hours of the start of the match. If a team fails to submit them within the 12 hour window, their team will receive a minor strike. If a team fails to submit them within 24 hours of the start of the match, the minor strike will be upgraded to a major strike and the opposing team from that matchday will receive a technical victory for the match in question.

25.3. For Playoffs, all replays and Python logs must be submitted within 2 hours of the end of a match. If a team fails to submit them on time, they will be disqualified from the playoffs.

25.4. Captains can submit the Python logs and replays to the head admin either through a Discord PM or by email to CommunityLeagueWoT@gmail.com

25.5. Please submit them as a Google Drive folder shareable link or as a compressed zip folder and have each player organized into their own folder with their respective replays and Python logs.

25.6. Any replays submitted may be used in the creation of promotional material by the League or by Wargaming.

25.7. All replays will be made publicly available for any other team in the league to watch.

26. League Points System

26.1. Ranking is decided by the number of points a team has acquired.

26.2. A team will earn:

26.2.1. 3 points for a victory.

26.2.2. 2 points for an overtime win.

26.2.3. 1 point for an overtime loss.

26.2.4. 0 points for a loss.

26.3. If teams are tied for points, tiebreakers will be determined by the following parameters in this listed order:

1. Head to head record with the tied team
2. Battle win/loss difference
3. Strength of opponents (This refers to the stats of the teams they have played compared to the team they are tied with.)

27. Prizes

27.1 In-game prizes for this season are supplied by Wargaming. In-game prize payouts can take up to 2 weeks.

27.2. Physical prizes for this season are supplied and shipped by CORSAIR. Players are responsible for any applicable duties or taxes. Physical prizes can take up to 3 months to be shipped out.

27.2.1. Physical Prizing will only be shipped to Canada, USA and Mexico.

27.2.3. All prizing for the season can be seen on the image below:

27.4. If a player/team is removed from the league, they are not eligible for any prizing from the season.

27.5. Only the 7 players on the team roster at the end of the season will receive prizing.

Amendments Section

Collapse
Close