1 Player Eligiblity

1. General Requirements
1.1 The CTL week is from 00:00 Pacific Time Monday to 23:59:59 Pacific Time Sunday. A player’s eligibility is determined at the start of the CTL week.
1.2 CTL players must play 20 (+10 every 2 weeks) 1v1 ranked ladder matches in the current Blizzard ladder season as whichever race they intend to play (IE you need 20 + 10 every 2 weeks as Zerg if you intend to play zerg). Admins may require a player to play additional games if there is question about their league (IE: new account, hasn't played in several seasons, etc.)
1.3 If a CTL season spans two Blizzard Ladder seasons, players will be required to have the total required games across the two ladder seasons. Players must complete their placement match in the second season to retain eligibility. A player's rank will be their highest achieved 1v1 rank among both seasons.
1.4 If you were ranked one or more leagues higher than your current league within the previous 3 Blizzard ladder seasons (excluding the current season), you must complete 10 extra ranked ladder games in addition to the minimum in order to be eligible to play CTL matches at the lower league. You may only play one league lower than the highest league attained in the past three seasons.
1.4.1 Previous seasons will only include the current Starcraft Expansion.
1.4.2 A former Masters 1 player may play no lower than the Master 2/3 set. A former Master 2/3 player may play no lower than the Diamond set. These players will not be allowed to play in the Diamond 2/3 set.
1.5 In order to participate in the playoffs, a player must have played at least one regular season match for his current team. Receiving a walkover victory counts as playing a match.
1.7 Players must be listed properly on the roster page of their respective team to be eligible to play; if not, they will be forcibly substituted. "Listed properly" will be defined as:
- Having a hyperlink to the player’s Enjin profile
- Having the correct SC2 name and battletag (i.e Siegfried | Siegfried#11760)
- Having the correct main race attributed.

2. League Classification
2.1 Your league classification is generally your current 1v1 ladder league.
2.1.1 Leaving Blizzard Ladder League
Players are strongly encouraged to never leave their ladder league. If a player does leave their league, however, they may regain their eligibility.
With Admin Approval
If a player believes they have been placed too high in a season, they may petition the admins to leave league and play at a lower level. Admins will vote to allow this based on a number of items; including, but not limited to: Current ladder win percentage, recent win percentage, CTL participation and record, and recent ladder replay review. If allowed, a player previously eligible to play will need to complete 10 additional ladder games after placing to regain eligibility. These players will still be subject to any bi-weekly, increasing requirement as dictated by Rule 1.2 as the season progresses. (i.e. If a player was eligible in Week 3 with 40 games played but was approved to leave their league, they would need 20 games in Week 5 to be eligible)
Players who want to leave their ladder league to place back into the same league may also petition the admins to do so. The same games requirement following leaving their league will be placed upon those players.
A player who is currently ineligible will not be allowed to leave their league.

Without Admin Approval
A player leaving their league without admin approval will be locked to the highest league attained during that Blizzard Season for the remainder of the CTL Season.
A previously eligible player will need to complete 20 games and will still be subject to the bi-weekly, increasing requirement of Rule 1.2.
A previously ineligible player will need to complete all games required by Rule 1.2. These players may also have further constraints placed upon them for eligibility as deemed necessary by the admins.

Leaving your Ladder League twice in a single Blizzard Season will make you ineligible for the remainder of a CTL Season under all circumstances.
2.1.2 Players are allowed to play at higher leagues if there are roster limitations or their captain gives it the OK (ex: Plat playing in Diamond matches). Playing up does not forfeit a player's right to play in their own league if they should so choose later.
2.1.3 Players who play on the KR or CN servers as their primary server will be approached in a case-by-case basis to determine eligibility. Generally, those players will be asked to complete their required games on the NA or EU server, depending on which is a better fit for their location.
2.2. Promotions
2.2.1 If an eligible Player is promoted during the CTL season they may play in their previous league for one additional week after the promotion. After this period, the player will play at their newly promoted league This will apply only to promotions earned during the CTL season and will not be retroactive to promotions earned prior to the start of a season Rule 2.2.1 will not apply to the Diamond 2/3 slot. If a Diamond 2/3 player promotes to Diamond 1 they will not be given the grace period. A player receiving a promotion in accordance to 2.2.1 will not be allowed to play at the lower league if they promote a second time. That player will then play matches at their current league. I.e. A player promoting from Gold to Diamond in a single CTL season will play at Diamond regardless of the number of weeks passed.
2.2.2 If a player is promoted after the line-up submission deadline for a week that player is allowed to play in their former league for the current week and afterwards must participate in their new league for the purpose of the CTL if the player does not meet the requirements of 2.2.1

3. Race
3.1 The race you play for CTL matches must have the minimum number of games played, and is played at your highest current 1v1 rank. For the purposes of the CTL, there shall be four races: Terran, Zerg, Protoss, and Random.
3.1.1 Players competing as Random may have additional constraints to gain eligibility. This could come in the form of additional matches required, completing placement matches in some or all other races, and any other requirements as determined by the admins.
3.2 A player may not change their race after the line-up submission deadline.

2 Line-Ups

2.1 Line-Up Submission

Every team submits their weeky line-up by filling out the appropriate form before 3:59pm Pacific Time Sunday. Each team will submit the players for each set and the correct Starcraft 2 ladder league for each week as defined by Rule 2.2. This line-up must come in the following format:
Week #
Team Name
Set 1: Player1.### (Race)
Set 2: Player2.### (Race)
Set 3: Player3.### (Race)
Set 4: Player4.### (Race)
Set 5: Player5.### (Race)
Set 6: Player6.### (Race)
Ace Set: Player7.### (Race)

2.2 Set and League Distribution
The CTL comprises ladder divisions from Gold to Master league. The current set and league distribution for weekly matches is as follows and is subject to change at admin discretion. This change can come between seasons or during a season if necessary.

Set 1 - <3114 MMR
Set 2 - Platinum
Set 3 - <3654 MMR
Set 4 - Diamond 2/3
Set 5 - Diamond 2/3
Set 6 - Diamond
Ace Set - Masters 2/3

2.2.1 Sets 1 through 6 will be best-of-ones.

2.2.2 Set 1 and Set 3 Additional Guidelines
These 2 sets are fluid sets based on a player's MMR at the start of a week. Players who exceed the boundary after the deadline are allowed to play for the current week. If they stay above the boundary, they will not be able to play in the following week. If a player falls below the boundary during a week. they may play in the set the following week. A player that reaches Plat 2 (for set 1) or Diamond 2 (for set 3) during a ladder season will not be able to play the set, no matter their MMR.

Players who were above the boundary at the beginning of the week may not be subbed into the set, regardless of their current MMR. Similarly, if a player was below the boundary at the deadline, but surpassed it during the week, they may be subbed into this set.

2.2.3 Current Masters players may play the ace set provided they have not reached Grand Master in any of the previous three ladder seasons or the current ladder season.

2.2.4 The final set of a series will be the ace set. This will be a Best of 3 series. The starting map will always be given weekly by the CTL admins. Subsequent maps will be chosen through a veto and loser pick.

(1) The winner of the previous game in a set will veto one map.
(2) The loser of the previous game will then choose a map remaining the CTL Map pool.
(2a) The CTL Map Pool will generally use the current Blizzard ladder maps but is subject to change by admins at any time during the season.
(2b) The current map pool is as follows:
Automaton LE (2)
Cyber Forest LE (2)
Kairos Junction LE (2)
King's Cove LE (2)
New Repugnancy LE (2)
Port Aleksander LE (2)
Year Zero LE (2)
(3) Maps are not repeatable in the ace series and any vetoed map cannot be chosen for the duration of the series.

2.2.4 Deviation from the Default Distribution
Teams will not be permitted to replace sets with a league other than the default. If a team does not have a player at the league needed for any set, they may use a player in a lower league or forfeit the set for that week.

2.3 Late Line-Up Submission

If a team fails to submit their weekly line-up by 3:59pm Pacific Time Sunday, that team will be forced to use their line-up from the previous week. The offending team will also only be able to make two substitutions for the week. If sets were played by leagues other than the default in the prior week’s line-up, the offending team will either use one of their two available substitutions for the week or forfeit the set.

2.4 If a team doesn't have the 8 minimum players defined by By-Law 1.2 to play all the sets of a match throughout the week they will receive a walkover loss for each set that cannot be played because of the absence of a player.

2.5 Forced Substitution of Ineligible Players

If a player submitted to the weekly lineup is ineligible based on the Player Eligibility guidelines, the opposing captain has until Tuesday at 23:59 Pacific Time to force a substitution. The opposing captain is also welcome to allow the ineligible player to remain in the lineup, but may not contest the set due to eligibility after this deadline. Any substitution must follow the Substitution guidelines. Captains will have until the substitution deadline (5.1) to find an eligible sub or the set will be forfeited.

3 Match-Up Contact

3.1 Players must contact their opponent via the Enjin messaging system to arrange a time-to-play. If contact is made through a third-party system, screenshot proof should be taken showing an agreed upon time to play. If no proof is given but a walkover is requested from either team, the match will be a double-forfeit.
3.2 Both players must attempt to contact their opponent prior to Wednesday 23:59 pm Pacific for each week. If neither player attempts contact, the match will be a double-forfeit.
3.3 If one player attempts to initiate contact but receives no messages from the opponent prior to 23:59 PM Pacific on Wednesday, the match will be a forfeit in favor of the player who attempted contact.
3.4 If players make contact, but one player puts forward considerably less effort towards setting up a time than the other, the admins may deem a walkover against him.
3.5 If both players are unable to reach an agreeable time to play, they must contact their captains to find substitutions prior to Friday. Their captains may either agree to play substitutes or take the matter to the Admins, who will determine how to score the match fairly under the circumstances.*

*Admin decisions will be recorded and archived to guide future disputes. Admins will generally endeavor to decide disputes consistently so that players and captains can fairly predict the outcome in advance (and thus avoid mass repetition of essentially identical disputes).

4 Match Reports

4.1 Match Report Submission
At the conclusion of each CTL week, teams must submit their results for the week by filling out the appropriate form before 11:59pm Pacific Time Monday. The match report must come in this format:
Week X
[team1] [score] [team 2]
Set 1: [player] [score] [player] ([map])
Set 2: [player] [score] [player] ([map])
Set 3: [player] [score] [player] ([map])
Set 4: [player] [score] [player] ([map])
Set 5: [player] [score] [player] ([map])
Set 6: [player] [score] [player] ([map])
Set 7: [player] [score] [player] ([maps])

4.1.1 If a team fails to submit a match report by 11:59pm Pacific Time Monday, that team will lose one map score in the overall standings. This will not affect the score of that week's match-up.

4.2 Walkovers

4.2.1 No walkovers will be granted without either proof in the form of message and in game screenshots or concession of the set by the other team captain. Every set or match can be forfeited by a team without any justification needed. However, the power to forfeit a set or a match resides entirely on the team's captain.
4.2.2 If a set isn't played for whatever reason except the one listed in 3.2.3, the set result is registered as 0-0, and both teams get a set loss. Each weekly match-up must have at least 1/2 (rounded up) of the sets played in order to be valid. If a match has less than 1/2 (rounded up) of sets played, both teams get a match loss, pending admin approval. Any sets played will be taken into account for overall standing map score.
4.2.3 If one player (Player A) is not in the SC2 client or responding to personal messages in the SC2 client at the agreed upon match time that player will be considered unavailable and will be given a 30 minute grace period. If at the end of said grace period Player A is still unavailable to play their match a walkover may be claimed by the opposing player (Player B). Player B may choose, but is not obligated, to play the match at a later time. If the match is played the result of the match will be used and no walkover will be issued. If Player B becomes unavailable during Player A's grace period then a second 30 minute grace period will be given to Player B starting at the time Player A become available. No walkovers will be granted until both team captains are notified of the situation. Screenshots should be taken showing the player being offline at the match time and at the end of the wait period to be provided with the weekly match report.
4.2.4 If a player disconnects during a CTL match the players must attempt to use the “Recover from Replay” option to resume the game. If the disconnect occurs in the first two minutes of the game then the match may be restarted if both players agree. If the disconnected player is offline for a period of more than 10 minutes that player will forfeit the set.

4.3 Replay Submission
In addition the text based report, teams must submit all replays for played games. These must be uploaded to the Google Drive folder for the corresponding week and match-up By the winning team. The match replays must come with both players identified in the name file. (e.g. Set3_Player1_Player2_MapName.SC2REPLAY)

4.3.1 Failure to Submit Replays
If a team fails to submit their replays for the week, they will not receive map score credit in the overall standings for any won set that is missing a replay. Teams will have a full week to supply any missing replays to recoup their lost map score. Captains are expected to notify the Admins to recoup any map score.

4.3.2 Admin Responsiblity
The admins will be responsible for notating any missing replays and map points at the time standings are posted Admins may not penalize teams for missing replays which were not noted in this window of time any later than Tuesday at 23:59 Pacific Time.

5 Substitutions
Each team will be allowed a maximum of two substitutions per week. Additionally, teams will be capped at a total number of subs per season, equal to half the number of weeks of the season, playoffs included (this will round up). Substitutions after this cap is reached will not be allowed unless the opposing captain allows the substitution.

If you must substitute a player in for a match there are two types of substitutions: normal substitutions and emergency substitutions. Both Captains and the admins must be notified of the substitution before any substitutions are acceptable.

5.1 A normal substitution must occur prior to the end of Wednesday Pacific time and more than 24 hours before an already scheduled match. Normal substitutions may be of any race regardless of the initial player's race
5.2 An emergency substitution can be done at any time after Wednesday. This substitute must be of the same race as the initial player.
5.2.1 An emergency substitution occurring within 24 hours of a scheduled match time must be approved by the opponent. The players may also attempt to find a new time if the player not subbed is able, but the originally scheduled match time will stand if they are not able to find a new time to play.
5.3 A player is not a valid substitution if any or all of the following conditions are met:
- The player was not present on the team's roster before that week's lineups were submitted
- The player was already placed into the lineup for that week
5.4 Any violation of any substitution rules will result in a forfeiture of the set.

6 Miscellaneous

6.1 Observing and Streaming Live CTL Matches

Observers or streamers are allowed in a game unless anyone involved in the game has an objection to it. Any player is free to stream their own CTL matches. Any allegations of ‘stream cheating’ will be disregarded as the streamer has taken on this risk himself.

6.2 Server Selection

In certain situations, a specific server must be chosen. These situations are:
NA vs EU - NA East
NA vs AU/SEA - NA West
AU/SEA vs EU - NA West
In these situations, both players are responsible for ensuring the correct server is chosen. If the wrong server is chosen, either player has until 1:00 into the game to request a remake on the correct server. Leaving at any time after that will be viewed as a concession of the current game.

6.3 Voice Chat

Players are not to be in any voice call during a CTL match. Captains are expected to police their own teams in ensuring fair play across the entire league. Breaking this rule will forfeit the match played and may result in suspension or other actions against the player, captain, and/or team.

7 Harassment
For purposes of the Chobo Team League there will be three types of harassment considered. These three are; CTL Event Harassment, General Harassment, and Probation Harassment.

CTL Event Harassment - This will include any harassment that occurs during a sanctioned CTL event.

General Harassment - This will include any harassment that occurs outside of a sanctioned CTL event. This includes but is not limited to ladder games, game lobbies, and harassment outside of the SC2 client. This will also include public accusations of cheating in any form coming without substantial proof.

Probation Harassment - This includes ANY harassment by a player in probationary status. Once a player is placed on probation, probation cannot be removed.

7.1 Any violation of any harassment rule will count as an offense against that player. Depending on which offense it is the punishment shall increase in severity. Offenses do not have a harassment type associated with them. This means a player that has incurred one general offense, and is found to have harassed during a CTL Event, the punishment shall be the CTL Event 2nd offense

7.2.1 1st Offense - Player shall be banned for 1 quarter of the season. This ban can span multiple seasons. (carry over from one season to the next)
7.2.2 2nd Offense - Player shall be banned for one half of the season. This ban can span multiple seasons. Player also forfeits the game in which the harassment occurred. Player is placed on probation.

7.3.1 1st offense - Player shall be warned, and a harassment offense is noted.
7.3.2 2nd offense - Player is banned for 1 quarter of the season. This ban can span multiple seasons.
7.3.3 3rd offense - Player is banned for 1 half of the season. This ban can span multiple seasons. Player is placed on probation.

If a player harassment occurs from a player in probationary status, the player shall be banned from the Chobo Team League.

7.5.1 One quarter of a season will be calculated by the following method.
(Total number of regular season weeks + Total number of Playoff weeks) / 4. This number will then be rounded up if it is not an integer.
7.5.2 One half of a season will be the number for One Quarter of a season doubled.

7.6 Vulgarity Assessment
In the event harassment occurs and is of a vulgar nature in regards to someone's real or perceived race, gender identity, ethnicity, sexual orientation, and/or disability, the offense will immediately move up the scale of offenses. Admins will use their own discretion to determine if it will move a single or multiple offenses up in the scale depending on the severity of the offense.

i.e. If a player with no prior harassment offenses BM's another player outside of a CTL match and disparages their ethnicity in the BM, the player will be punished according to the 2nd offense definition rather than 1st if the admins deem it to be of a vulgar nature.

8 Cheating

Any form of cheating is strictly forbidden. Cheating can come in various forms: Smurfing, hacking, account sharing, or other means of gaining an improper advantage in the CTL. Players suspected of cheating will be investigated by the admins through any means available. Players under suspicion of cheating will have their captains informed. If the admins deem that a player has cheated or is cheating that player will face punishments deemed fitting. Punishments can range from permanent removal from the CTL, varying lengths of suspensions, and/or match forfeiture.

8.1 Smurfing will be defined as a player purposefully playing matches at a league lower than they are currently ranked. The player can accomplish this by playing games on an account not their own, having a second account which is ranked higher than their main account, or purposefully or intentionally losing games on ladder to remain in a specific league or degrade their MMR to a point where they are no longer playing at their true skill level.

8.2 Hacking will be defined as a player using third-party programs Blizzard deems hacking programs. This can be in the form of map hacks, production tab hacks, drop hacks, etc. A player found to be hacking, whether in the CTL, ladder, or any Starcraft match, will be permanently banned from the CTL.

8.3 Account Sharing will be defined as a player allowing their account to be used by a second player. This can be through paid or unpaid boosting services, allowing a higher level player to compete in the CTL on their account, and/or allowing a second person to ladder on their account to keep their MMR artificially low.

9 Tiebreakers

9.1 Weekly Matches
During a weekly matchup if for some reason a tie occurs the following will be used as tiebreakers:
1. Winner of the 'Ace' Best of 3 match-up.
2. Team that won the most Diamond matches
3. Team that won the most Platinum Matches
4. Team that won the most Gold Matches
5. Team with the fewest forfeits
6. Team that won the match played the earliest, based on replay creation date

9.2 Overall Standings
If two or more teams are tied at the end of the season for playoff spots, the following will be used as tiebreakers:
1. Team with the highest +/- map score
2. Head-to-head result
3. Best winning percentage vs division teams
4. Most ace sets won
5. Coin-flip