[CTWL] Changelog

[chris]

The purpose of this thread is to log every change made to CTWL's ruleset, so everyone can clearly see what has been updated.
Said updates will always be announced by the Staff of Wiimmfi League on the Wiimmfi League's Discord Server.

Discord Server Link

It was also made in order to comply with this rule:

e. Rule changes made mid-season will apply for all matches played after the change has been made with the
exception of reschedules (at the staff's discretion). An announcement thread or post will be made for any and all rule changes.

The CTWL Ruleset can be found here.

 

[Niko]

Update

Edit of section VI. CTGP Revolution Channel Settings

Spoiler: Old VI. CTGP Revolution Channel Settings

b. If a host uses any different setting(s) than the ones listed in VI. a. (video proof required), his/her team will receive a penalty based on how severely the game modification may have affected the match.

b.i. Unless it is mutually agreed on between both teams, a host caught with Host Always Wins Vote set to "ON" must reset the room at the cost of one of his/her team's resets (see rule IV. c. for more information) and correct the setting. If the host refuses to reset, his/her team will receive a penalty of 150 points.​

b.ii. A host caught with Track Availability set to "Nintendo Tracks" or "All Tracks", Thundercloud Effect set to "Mega", Item Rain set to "ON", All Items Can Land set to "ON", and/or Item Boxes set to "OFF" must reset the room at the cost of one of his/her team's resets (see rule VIII. c. for more information) and correct the setting(s). Races played with any of these settings will not count toward the final score. If the host refuses to reset, his/her team will forfeit the match.​

b.iii. If a host is caught with Vehicle Availability set to anything but "All Vehicles", the match may proceed unless a reset is requested. If requested, the host must reset the room at the cost of one of his/her team's resets (see rule VIII. c. for more information) and correct the setting. If the host refuses to reset, his/her team will receive a 150 point penalty.​

b.iv. Unless a different setting is mutually agreed upon by both teams, a host caught with Specific Engine Class set to anything but "Normal" must reset the room at the cost of one of his/her team's resets (see rule VIII. c. for more information) and correct the setting. The same must be done if the setting is different than the one mutually agreed upon. If the host refuses to reset, his/her team will receive a penalty of 8 points per race until the setting is corrected.​

b.v. Unless a different setting is mutually agreed upon by both teams, a host caught with Race Count set to above 4 must reset the room at any point before race 5, at the cost of one of his/her team's resets (see rule VIII. c. for more information), and correct the setting. If the host refuses to reset before race 5, his/her team will receive a penalty of 30 points for each additional race played.​

b.vi. If a host is caught with Race Count set to below 4, his/her team will lose a reset (see rule VIII. c. for more information) each time a Grand Prix ends (showing the final results screen with the Engine Class) without 4 races being completed.​

b.vii. A host caught with Room Encryption set to "OFF" must reset the room at the cost of one of his/her team's resets (see rule IV. c. for more information) and correct the setting. Races played with this setting will not count toward the final score. If the host refuses to reset, his/her team will forfeit the match.​

b.viii. Unless a different setting is mutually agreed upon by both teams, a host caught with Network Data Rate set to anything but "Normal" must reset the room at the cost of one of his/her team's resets (see rule VIII. c. for more information) and correct the setting. If the host refuses to reset, his/her team will forfeit the match.​

Spoiler: New CTGP Revolution Channel Settings

b. If a CTGP-R player uses any prohibited game modification(s) (video proof required), a penalty will be given based on how severely the game modification may have affected the match.

*b.i. A host caught with Track Availability set to "Nintendo Tracks" or "All Tracks", Thundercloud Autofire set to "OFF", Thundercloud Effect set to "Mega", Room Encryption set to "OFF", Item Rain set to "ON", All Items Can Land set to "ON", and/or Item Boxes set to "OFF" must reset the room at the cost of one of his/her team's resets (see rule VIII. c. for more information) and correct the setting(s). Races played with any of these settings will not count toward the final score. If the host refuses to reset, his/her team will forfeit the match.​

b.ii. A host caught with Host Always Wins Vote set to "ON" must reset the room at the cost of one of his/her team's resets (see rule VIII. c. for more information) and correct the setting(s). If the host refuses to reset, his/her team will receive a 150 point penalty.​

b.iii. If a host is caught with Vehicle Availability set to anything but "All Vehicles", the match may proceed unless a reset is requested. If requested, the host must reset the room at the cost of one of his/her team's resets (see rule VIII. c. for more information) and correct the setting. If the host refuses to reset, his/her team will receive a 150 point penalty.​

b.iv. A host caught with Specific Engine Class set to anything but "150cc" must reset the room at the cost of one of his/her team's resets (see rule VIII. c. for more information) and correct the setting. The same must be done if the setting is different than the one mutually agreed upon. If the host refuses to reset, his/her team will receive a penalty of 8 points per race (96 point cap).​

b.v. A host caught with Race Count set to above 4 must reset the room at any point before race 5, at the cost of one of his/her team's resets (see rule VIII. c. for more information), and correct the setting. If the host refuses to reset before race 5, his/her team will receive a penalty of 30 points for each additional race played (240 point cap).​

b.vi. If a host is caught with Race Count set to below 4, his/her team will lose a reset (see rule VIII. c. for more information) each time a Grand Prix ends (showing the final results screen with the Engine Class) without 4 races being completed.​

b.vii. A host caught with Network Data Rate set to anything but "Normal" must reset the room at the cost of one of his/her team's resets (see rule VIII. c. for more information) and correct the setting. If the host refuses to reset, his/her team will forfeit the match.​

- uniform rules with RTWL Ruleset excluding:
-> My Stuff rule because that's only relevant on RTs
-> "150cc only" as default on CTs because "All ccs" is the default on RTs instead

________________


Addition of rule c.ii. for VII Hosting

Spoiler

c.ii. Teams can mutually agree on joining the room in a "a-b-a-b" pattern (Team A joins first, Team B joins second, Team A joins third,...).

Reason: We're fine with letting teams do this as long as they can manage this on their own.

 

[Niko]

Changes to VIII. g. Match Structure

Spoiler: Old

*g. Certain custom tracks have been banned from league matches. If they are selected, the race will not count at the cost of a reset to the team that picked the banned track (see rule VII. c. for more information). The banned tracks are as follows:
- Hell Pyramid (6vs6 matches only)
- Lava Road (6vs6 matches only)
- Rockside River (6vs6 matches only)
- Snowy Circuit 1 (6vs6 matches only)
- Undiscovered Offlimit (6vs6 matches only)
- Yellow Loop

Spoiler: New

g. Track picks are limited to 20 tracks per match week, which are announced in the #ctwl-random-only-lists channel (no wild card picks are allowed). Any team that is responsible for picking a track not in the list of 20 for that week will receive a 20 point penalty.

g.i. Certain custom tracks have been banned entirely, so they won't be featured on any of the lists of 20 tracks. If they are selected, the race will not count at the cost of a reset to the team that picked the banned track (see rule VII. c. for more information). The banned tracks are as follows:​

- Disco Fever​

- Hell Pyramid (6vs6 matches only)​

- Lava Road (6vs6 matches only)​

- Rockside River (6vs6 matches only)​

- Snowy Circuit 1 (6vs6 matches only)​

- Undiscovered Offlimit (6vs6 matches only)​

Reason: needed a rule to reflect this Season being a CTWL-random-only Season as well as Disco Fever being officially re-banned again along with the removals of tracks like Yellow Loops as they're not in the pack anymore.

^small edit. BassBasher City has also been removed from a list that entailed banned shortcuts/glitches as it has been removed from the pack as well

 

[Niko]

Fixing of rule VI. a.i. CTGP Revolution Settings

*a.i. All hosts have to show their conditionals to their opponent in order to prove they have the right settings for 'Room Encryption'. The person responsible for checking a host's conditionals has to make sure the host has the correct settings.
Should a host fail to use the correct settings for a match, they will be host banned.
The person responsible for checking a host's conditionals will also be striked in addition if a host is seen to be using wrong settings.

Changes in italics

Reason: many matches have turned out to have been played with wrong settings even in CTWL (Strikes will also be given).

 

[Niko]

some more rule edits/additions/removals!
Edits in the new rules will be highlighted like this
__________________________________________________________________

Spoiler: Old IV.g.

g. If approved by council beforehand, players registered for a lower-division subset of a team may play a match for a higher-division subset of that same Team.

Spoiler: New IV.g.

g. If the opposing team and Council are notified beforehand in the discord team representative chat, players registered for a lower-division subset of a team may play a match for a higher-division subset of that same Team.

Reasoning: Council may be busy playing their own Matches + a quick tagging of Council as well as notifying the opponent shouldn't harm anyone.

__________________________________________________________________

Spoiler: Old IV.*h.i.

*h.i. If, during the time period of the match, an unregistered FC is proven to belong to a player registered for the correct team, no penalty will be given.

Spoiler: New IV.*h.i.

*h.i. If, during the time period of the match, an unregistered FC is proven to belong to a player registered for the correct team, a strike will be given instead.

Reasoning: clarifying the rule just in case.

__________________________________________________________________

Spoiler: Old V.f.

f. If and only if two teams from the same team are playing each other, the team which is officially registered as Team 2 must put the character "2" after its tag (ex: If two teams from Charged Brigade played each other, Charged Brigade 1 would use the tag "¢β" and Charged Brigade 2 would use the tag "¢β2").

Spoiler: New V.f.

f. If and only if two sister teams are playing each other (ex: Charged Brigade and Charged Brigade 2), the teams may choose to use an alternative tag to play with as long as Council, the Division Admin and the opposing team are all notified in the discord chat before the opening of the room.

Reasoning: The old rule implies that both teams have to use i.e. cB and cB2. There is no harm in making both sister teams use completely different appropriate tags if they want.

________________________________________________________________

Addition of V.a.ii. (will be put in a spoiler on the ruleset) - separators

Spoiler

a.ii. The following symbols are considered a separator:
- [ ] \ / ‘ # ! “ % ^ & * ( ) _ | ` { } ? @ ~ ; , . = < > + : ¿ ¡ « » · - × ÷ = ± ∞ ™ º ª ♭ ♪ * ← → ↑ ↓ ΄ ΅ ☆ ★ ○ ● ◎ ◇ ◆ □ ■ © △ ▲ ▽ ▼ ¦ ∴ 、 。 ？ ！ ー 「 」' ※ 〒 • … (space)

Reasoning: People always ask which symbols are considered separators, this makes it easy for people to tell and they don’t need to ask.

_______________________________________________________________

Removal of VI.a.i - host conditionals

Spoiler

a.i. All hosts have to show their conditionals to their opponent in order to prove they have the right settings for 'My Stuff' Folder and 'Allow My Stuff users?'. Settings for 'Room Encryption' as well as 'Only allow CTGP users?' have to be enabled correctly as well.
The person responsible for checking a host's conditionals has to make sure the host has the correct settings.
Should a host fail to use the correct settings for a match, they will be host banned.
The person responsible for checking a host's conditionals will also be striked in addition if a host is seen to be using wrong Settings.

Reasoning: we no longer require them anymore.

______________________________________________________________

Spoiler: Old VI.b.v.

b.vi. A host caught with Race Count set to above 4 must reset the room at any point before race 5, at the cost of one of his/her team's resets (see rule VIII. c. for more information), and correct the setting. If the host refuses to reset before race 5, his/her team will receive a penalty of 30 points for each additional race played (240 point cap).

Spoiler: New VI.b.v.

b.vi. A host caught with Race Count set to above 4 must reset the room at any point before race 5, at the cost of one of his/her team's resets (see rule VIII. c. for more information), and correct the setting. If the host refuses to reset before race 5, his/her team will receive a penalty of 30 points for each additional race played (240 point cap). This rule does not apply if the Race Count is mutually agreed to be either 6 or 12 races. If the setting is mutually agreed to 6 races, the rule is altered to fit the agreed Race Count.

Reasoning: In case people use 6 or 12 races.

____________________________________________________________

Spoiler: Old VII.b.

*b. Hosts must reset the room if requested.

Spoiler: New VII.b.

*b. Hosts must reset the room when requested and if the requesting team has resets remaining.

Reasoning: Clarity, the old rule may make people think the host has to reset the room regardless if the opposing team does not have any resets left.

___________________________________________________________

Spoiler: Old VII.c.

*c. Before opening the room, the hosting team must provide the opposing team with a host friend code and wait for the opposing team to give permission to open the room. If no confirmation to open the room has been given 5 minutes after the scheduled match time, the room may be opened.

Spoiler: New VII.c.

*c. Before opening the room, the hosting team must provide the opposing team with a host friend Code and the format 10 minutes prior to the start time. They have to wait for the opposing team to give permission to open the room. If no confirmation to open the room has been given 5 minutes after the scheduled match time, the room may be opened.

Reasoning: Teams were technically able to give the opposing team host at 2:04.59 and then open at 2:05 and get top 4 in room. The newly added part makes it so teams aren’t being stupid to each other.

_________________________________________________________

Spoiler: Old VII.g.v.

g.v. If a player on the opposing team is kicked from the room during a kickstart or when kicking a player not participating in the war, rule g.i. is nullified. If this happens after the room starts, however, the host must immediately reset the room at the cost of one of the hosting team's resets (see rule VIII. c. for more information).

Spoiler: New VII.g.v.

g.v. If a player on the opposing team is kicked from the room during a kickstart or when kicking a player not participating in the war, rule g.i. is nullified. If a host kicks a player that is supposed to participate, the host must immediately reset the room at the cost of one of the hosting team's resets (see rule VIII. c. for more information).

Reasoning: Old rule was a bit confusing, new rule makes it more clear for people to read.

________________________________________________________

Spoiler: Old VIII.f.i

f.i. If a player provides video evidence that the CTGP randomizer was responsible for selecting a track that has already been played (without having a cup pre-selected), then no penalty will be given for the repick.

Spoiler: New VIII.f.i.

f.i. If a player provides video evidence of their screen that the CTGP randomizer was responsible for selecting a track that has already been played (without having a cup pre-selected), then no penalty will be given for the repick.

Reasoning: Teams can abuse this to get tracks they like to be repeated. They can wait until the 30 seconds hit, pick the track and play an audio clip of the randomizer in call and they can get a track they want and use the call as evidence.

________________________________________________________

Spoiler: Old VII.h.

*h. After a reset, the host will wait for a maximum of 15 minutes to let players join the room. If stalling is evident after all the players are in and room stability is good enough, a strike will be given to the current lineup of the hosting team. If a second offense occurs (in the same match or a different one), then a host ban will ensue for the said lineup and any remaining home matches will be hosted by the away team (the host-banned team will still be allowed to determine ruleset and engine class).

Spoiler: New VII.h

*h. After a reset, the host will wait for a maximum of 10 minutes to let players join the room. If stalling is evident after all the players are in and room stability is good enough, a strike will be given to the current lineup of the hosting team. If a second offence occurs (in the same match or a different one), then a host ban will ensue for the said lineup and any remaining home matches will be hosted by the away team (the host-banned team will still be allowed to determine ruleset and engine class).

Reasoning: 10 minutes should be still sufficient enough for players to rejoin.

______________________________________________________

Addition of XV.c.

Spoiler

c. Any matches in playoffs that consist of one 12 race match is to be played at default time of the respective week unless mutually agreed. Any match-up that is more than 12 races must be mutually agreed. Any match-up that consists of either team needing to win 2 matches must be mutually agreed.

Reasoning: No scheduled time for playoffs in the ruleset, gives more teams clarity.

 

[Niko]

Edits in green and bold

Edit of VIII.g. and Addition of a New VIII. g.i and g.ii.

Spoiler: Old

*g. Track picks are limited to 20 tracks per match week, which are announced in the #ctwl-random-only-lists channel (no wild card picks are allowed). Any team that is responsible for picking a track not in the list of 20 for that week will receive a 20 point Penalty.

Spoiler: New

*g. Track picks are limited to 26 tracks per match week, which are announced in the #ctwl-random-only-lists channel (no wild card picks are allowed). Any team that is responsible for picking a track not in the list of 26 for that week will receive a 20 point penalty.
g.i. Should the CTGP-randomizer be responsible for repicking a track on the respective week's list and sufficient proof is given, then no penalty will be applied. If no proof is provided, a penalty of 20 is given.
g.ii. A track that appeared once in a list may only re-appear in another list once 3 weeks have passed. Example: if Hell Pyramid was part of week 1's list, it will not appear in weeks 2, 3 and 4; it can re-appear in week 5.

Reasoning: We wanted the generic information we put in the #ctwl-random-only-lists to be in the ruleset as well + a small expansion of the track lists themselves.

__________________________________________________

Spoiler: Old XV. Playoffs a.

a. Six-Team-Divisions

a.i. Before the start of the season, Team Representatives will be voting for their teams in order to choose between having playoffs or no playoffs. There are 2 choices to pick from this:​

- No Playoffs (in this case, a 10 week season will take place)​

- Playoffs (needs a 4-2 vote in favor for this)​

a.ii. Playoffs will include 3 more weeks to the season with top 4 teams making it and the weeks will be performed in the following manner:​

Spoiler

- [W11] 3rd seed vs 4th seed (Bo1), 3rd seed determines ruleset​

- [W12] 2nd seed vs winner of [W11] (Bo1), 2nd seed determines ruleset​

- [W13] 1st seed vs winner of [W12] but 1st only needs to win once while opponent needs to win twice: 1st seed determines ruleset first and then opponent in the next match if necessary​

Spoiler: New XV. Playoffs a.

a. Six-Team-Divisions

a.i. No Playoffs will be performed; a main Season consisting of 10 weeks will be played.​

a.ii. Should two teams tie for first place on the final standings, a Best-of-3 series will take place. ​

Reasoning: Either format didn't really work out for a smaller pool of teams (6-team-divisions); one would disregard the main season for first place especially, one would ultimately buff first place's advantages. Hence the very old traditional format (10 weeks) being a thing again.

_____________________________

River of Dreams has been removed from the Banned glitches/shortcuts list as it no longer is available in the latest CTGP-R Version.

 

[Niko]

Update

The following tracks will be moved to the banned tracks list:

- Kartwood Creek

Reason: infamous for its harsh position glitches/similarities to Disco Fever which is also already banned.

The following shortcuts will be added to the banned shortcuts/glitches list as we consider these worthy of a ban:

- Autumn Leavesway Respawn

Spoiler

- Flowery Greenhouse, Slow Wheelie
- GCN Rainbow Road, Slow Wheelie
- Jungle Cliff, Cliff

 

[Niko]

Update

In addition to the most recently banned shortcuts, the following shortcut will be added to the banned shortcuts/glitches list:

- Hell Pyramid, Respawn

Spoiler

https://puu.sh/CCwVx/2ad38d067f.mp4

 

[Niko]

Update

The shortcut on Snowy Circuit 2 will no longer be permitted in this league's environment -- therefore, it will be added to the banned shortcuts/glitches list.

 

[Niko]

Update

The shortcut on Dragon Burial Grounds will no longer be permitted in this league's environment -- therefore, it will be added to the banned shortcuts/glitches list.

 

[Niko]

Update

As this post Pretty much covers the gist for the CTWL Ruleset, we will drop a reference here.

 

[~Maidvelia❤︎~]

Update

This post pretty much covers the gist for the CTWL Ruleset.

 

[Niko]

Update

The shortcut on Forest Creek will no longer be permitted in this league's environment -- therefore, it will be added to the banned shortcuts/glitches list.

Crossingville and Disco Fever have been removed from the list as they no longer are in CTGP.

 

[~Maidvelia❤︎~]

Update

Change: Modification of rule VIII. g., removal of rule VIII. i., rule VIII. g.iii. is now rule VIII. h., and rule VIII. h. is now rule VIII. i.

Spoiler: Old

*g. Track picks are limited to 26 tracks per match week, which are announced in the #ctwl-random-only-lists channel (no wild card picks are allowed). Any team that is responsible for picking a track not in the list of 26 for that week will receive a 20 point penalty.

g.i. Should the CTGP-randomizer be responsible for repicking a track on the respective week's list and sufficient proof is given, then no penalty will be applied. If no proof is provided, then a penalty of 20 is given.
g.ii. A track that appeared once in a list may only re-appear in another list once 3 weeks have passed.
Example: If Hell Pyramid was part of week 1's list, it will not appear in weeks 2, 3 and 4; it can reappear in week 5.
g.iii.. Certain custom tracks have been banned entirely, so they won't be featured on any of the lists of 26 tracks. If they are selected, the race will not count at the cost of a reset to the team that picked the banned track (see rule VII. c. for more information). The banned tracks are as follows:
- Cave Island
- Disco Fever
- Hell Pyramid (6vs6 matches only)
- Kartwood Creek
- Lava Road (6vs6 matches only)
- Rockside River (6vs6 matches only)
- Snowy Circuit (6vs6 matches only)
- Undiscovered Offlimit (6vs6 matches only)​

h. All players must have at least 5000 VR on the license they chose to use for a match. If the first race of the in-game GP is completed with a player's VR not meeting this requirement, their team will receive a penalty of 30 points (90 point cap).
i. The random-only/drafting hybrid format will proceed as follows:
- Start with 36 tracks total available each week, each week 36 new tracks will be rolled, and each week will not contain tracks from the past 2 weeks. (i.e. if something is rolled W1, it will not see play until at least W4).
- The away team has until Tuesday at 11:59 PM EST to post their protects, and then 24 hours pass for each stage, and so on. If teams don't respond or do not wish to participate in a particular ban phase, that phase will be omitted. Drafting phases must be done in division rep chats. Gentleman's agreements can be met upon if teams wish to not omit a phase.
- 1st phase: Away team: Protects 2 courses from the track pool.
- 2nd phase: Home team: Bans 5 courses, protects 2 courses from the track pool.
- 3rd phase: Away team: Bans 5 courses from the track pool.
- All tracks that were not banned in the track pool are available for selection in the upcoming week's home vs away match.

Spoiler: New

g. Track Selection Format

g.i. Prior to the start of the season, teams will draft 20 tracks that they will use as their track pool for the season.
g.ii. After the draft, each team will declare a global protect.
*g.iii. After each team has claimed their global protect, each team will globally ban 2 tracks. Teams may not use the globally banned tracks against a team where the global ban applies, as doing so will result in a 20 point penalty.
*g.iv. A week prior to the following week, a list of 12 randomized tracks will be posted in #ctwl-random-lists. Any team that is responsible for picking a track that is both not in the randomized list of 12 for that week will receive a 20 point penalty.
*g.v. Midway through each week, each team will bring select 4 tracks from their track pool that will be used during that week. Any team that is responsible for picking a track not in their selection of 4 and not in the randomized list of 12 for that week will receive a 20 point penalty.
g.vi. A total of 20 tracks will be playable for that week: 12 randomized tracks, 4 from team A, 4 from team B.
g.vii. Should the CTGP-randomizer be responsible for repicking a track in either of the teams' pools or the randomized list for that week and sufficient video proof is given, then no penalty will be applied. If no proof is provided, then a penalty of 20 is given.
g.viii. Teams may not use the same tracks they used the 2nd time they play an opposing team that they used the first time playing them. (Example: XK vs Special K`s, XK uses Colour Wonderland, Yoshi Lagoon, SNES Mario Circuit 1, Halogen Highway; they may not use any of the 4 tracks the next time they face Special K`s).
g.ix. In playoffs, every match each team will ban 1 track each, in addition to the already existing 2 global bans for the season (ex: XK bans Final Grounds and their global bans are Abyssal Ruins and Candy Coaster, Special K`s bans Mushroom Peaks and their global bans are Colour Wonderland and Forest Creek--Final Grounds and Mushroom Peaks are out of play and the others are out of play based on global ban rules).​

h. Certain custom tracks have been banned entirely, so they won't be featured on any of the lists of 26 tracks. If they are selected, the race will not count at the cost of a reset to the team that picked the banned track (see rule VII. c. for more information). The banned tracks are as follows:
- Cave Island
- Disco Fever
- Hell Pyramid (6vs6 matches only)
- Kartwood Creek
- Lava Road (6vs6 matches only)
- Rockside River (6vs6 matches only)
- Snowy Circuit (6vs6 matches only)
- Undiscovered Offlimit (6vs6 matches only)
i. All players must have at least 5000 VR on the license they chose to use for a match. If the first race of the in-game GP is completed with a player's VR not meeting this requirement, their team will receive a penalty of 30 points (90 point cap).

Reason: Addition of the new Track Selection Format.

 

[~Maidvelia❤︎~]

Update

Change: Modification of rule VIII. g.vi.

Spoiler: Old

g.vi. A total of 20 tracks will be playable for that week: 12 randomized tracks, 4 from team A, 4 from team B.​

Spoiler: New

g.vi. A total of 20 tracks will be playable for that week: 12 randomized tracks, 4 from the home team, and 4 from the away team. During a match, up to 4 randomized tracks can be picked but no more than 4. This means that all home team tracks are played, all away team tracks are played, and 4 random tracks are played (4 Home-4 Away-4 Random). If 5 randomized tracks are picked during a match, the team who picked the 5th track will be forced to use a reset. Not resetting will result in a forfeit.​

Reason: More clarity on the 4-4-4 spread.

 

[~Maidvelia❤︎~]

Update

Change: Modification of several parts of rule VIII. g. (Track Selection Format).

Spoiler: Old

*g.iii. After each team has claimed their global protect, each team will globally ban 2 tracks. Teams may not use the globally banned tracks against a team where the global ban applies, as doing so will result in a 20 point penalty.​

*g.iv. A week prior to the following week, a list of 12 randomized tracks will be posted in #ctwl-random-lists. Any team that is responsible for picking a track that is both not in the randomized list of 12 for that week will receive a 20 point penalty.​

*g.v. Midway through each week, each team will select 4 tracks from their track pool that will be used during that week. Any team that is responsible for picking a track not in their selection of 4 and not in the randomized list of 12 for that week will receive a 20 point penalty.​

g.vi. A total of 20 tracks will be playable for that week: 12 randomized tracks, 4 from the home team, and 4 from the away team. During a match, up to 4 randomized tracks can be picked but no more than 4. This means that all home team tracks are played, all away team tracks are played, and 4 random tracks are played (4 Home-4 Away-4 Random). If 5 randomized tracks are picked during a match, the team who picked the 5th track will be forced to use a reset. Not resetting will result in a forfeit.​

g.vii. Should the CTGP-randomizer be responsible for repicking a track in either of the teams' pools or the randomized list for that week and sufficient video proof is given, then no penalty will be applied. If no proof is provided, then a penalty of 20 is given.​

g.viii. Teams may not use the same tracks they used the 2nd time they play an opposing team that they used the first time playing them. (Example: XK vs Special Ks, XK uses Colour Wonderland, Yoshi Lagoon, SNES Mario Circuit 1, Halogen Highway; they may not use any of the 4 tracks the next time they face Special Ks).​

g.ix. In playoffs, every match each team will ban 1 track each, in addition to the already existing 2 global bans for the season (ex: XK bans Final Grounds and their global bans are Abyssal Ruins and Candy Coaster, Special K`s bans Mushroom Peaks and their global bans are Colour Wonderland and Forest Creek--Final Grounds and Mushroom Peaks are out of play and the others are out of play based on global ban rules).​

Spoiler: New

*g.iii. A week prior to the following week, a list of 12 randomized tracks will be posted in #ctwl-random-lists. Any team that is responsible for picking a track that is both not in the randomized list of 12 for that week will receive a 20 point penalty.​

*g.iv. Midway through each week, each team will select 2 tracks to ban from their opponent's pool of 20 tracks or the list of 12 randomized tracks. These bans should be posted at the same time, without changes allowed, and must be completed before the process in rule VIII. g.v. Any team responsible for picking a banned track will receive a 20 point penalty.​

*g.v. Midway through each week, after the 2 bans, each team will select 4 tracks from their pool of 20 tracks that will be used during that week. Any team that is responsible for picking a track not in their selection of 4 and not in the randomized list of 12 for that week will receive a 20 point penalty.​

g.vi. Not submitting the 2 bans on time will result in losing the opportunity to ban 2 tracks. Not submitting the 4 picks on time will result in council randomizing 4 tracks from the team's pool of 20 tracks.​

g.vii. A total of 20 tracks will be playable for that week: 12 randomized tracks (includes insurance tracks if necessary), 4 from the home team, and 4 from the away team. During a match, up to 4 randomized tracks can be picked but no more than 4. This means that all home team tracks are played, all away team tracks are played, and 4 random tracks are played (4 Home-4 Away-4 Random).​

g.viii. If 5 randomized tracks are picked during a match, the team who picked the 5th track will be forced to use a reset and receive a 20 point penalty. Not resetting will result in a forfeit. If it is race 4 of the GP, a reset is not required, but the race will not count.​

g.ix. Should the CTGP-randomizer be responsible for repicking a track in either of the teams' pools or the randomized list for that week and sufficient video proof is given, then no penalty will be applied. If no proof is provided, then a penalty of 20 is given.​

g.x. Teams may not use the same tracks they used the 2nd time they play an opposing team that they used the first time playing them. (Example: XK vs Special Ks, XK uses Colour Wonderland, Yoshi Lagoon, SNES Mario Circuit 1, Halogen Highway; they may not use any of the 4 tracks the next time they face Special Ks).​

g.xi. In playoff matches, each team will select 12 tracks from their pool of 20 tracks before the entire set of 3 wars. In between each war, each team will decide on 2 tracks to ban from the opponent's pool of 20 or the randomized list for the week of that playoff match.​

Reason: Global Bans changed to Weekly Bans by team representative majority vote. Global Bans were incompatible with the drafted track format. In addition to that, a 20 point penalty is now issued for violation of rule VIII. g.viii. to deter cases of teams trying to force a reset to cancel out an opponent team's starting spots. Lastly, playoffs rules have been changed to coincide with the new Weekly Bans.