Requested page is not yet translated to the selected language (slovenščina). Showing English version.
![CWC 2024 banner](https://i.ppy.sh/c3abfcbac2828418cf94c9f0a180465d8edd6b96/68747470733a2f2f6f73752e7070792e73682f77696b692f696d616765732f546f75726e616d656e74732f4357432f323032342f696d672f637763323032342d62616e6e65722e6a7067)
The osu!catch World Cup 2024 (CWC 2024) was a country-based osu!catch tournament hosted by the osu! team. It was the thirteenth instalment of the osu!catch World Cup.
Registration phase |
2024-04-18/2024-05-02 (23:59 UTC) |
Qualifier showcase |
2024-05-12 (14:00 UTC) |
Qualifier stage |
2024-05-18/2024-05-19 |
Round of 32 |
2024-05-25/2024-05-26 |
Round of 16 |
2024-06-01/2024-06-02 |
Quarterfinals |
2024-06-08/2024-06-09 |
Semifinals |
2024-06-15/2024-06-16 |
Finals |
2024-06-22/2024-06-23 |
Grand Finals |
2024-06-29/2024-06-30 |
The osu!catch World Cup 2024 offered a $2,534.24 cash prize pool and limited-edition merch.
![1st place Gold crown](https://i.ppy.sh/c8447c5ce37eaa34ed393f537dda8099a4c5e161/68747470733a2f2f6f73752e7070792e73682f77696b692f696d616765732f7368617265642f63726f776e2d676f6c642e706e67) |
50% of the prize pool, single-run merch, profile badge, osu!catch Champion user title for one year |
![2nd place Silver crown](https://i.ppy.sh/d076465cfe8cbc9a6911417496c8a21efa7838c3/68747470733a2f2f6f73752e7070792e73682f77696b692f696d616765732f7368617265642f63726f776e2d73696c7665722e706e67) |
30% of the prize pool, single-run merch, profile badge |
![3rd place Bronze crown](https://i.ppy.sh/b582c7211024aa1bbd35b1d75e4778b0bdf08836/68747470733a2f2f6f73752e7070792e73682f77696b692f696d616765732f7368617265642f63726f776e2d62726f6e7a652e706e67) |
20% of the prize pool, single-run merch, profile badge |
![CWC 2024 3rd-place badge](https://i.ppy.sh/b9788f1be2144e8f8970417b3f759d253495583e/68747470733a2f2f6f73752e7070792e73682f77696b692f696d616765732f546f75726e616d656e74732f4357432f323032342f696d672f637763323032342d62616467652d3372642e706e67)
The osu!catch World Cup 2024 was run by various community members.
Manager |
Azer, ChillierPear, LeoFLT, mangomizer |
Mappool selector |
wwwww, Yoshi_green, autofanboy, Bunnrei, Spectator |
Mappool quality assurance |
autofanboy, Bunnrei, ExGon, Jemzuu, Spectator, wwwww, Yoshi_green, ZiRoX |
Mappool playtester |
Aryssiel, Blushing, DreStar, JISAN, Motion , Roido, Urabe Mikoto |
Mapper |
-Ken, -Luminate, -Rustyy, 4rcheR-, Ascendance, autofanboy, BlackBN, Bunnrei, Crowley, Daletto, Dapulezatos, Deif, Dika312, ExGon, F D Flourite, fayew, GiGas, Greaper, JBHyperion, Jemzuu, Lacrima, Liyac, Malai, midorijeon, Mniam, Mochi -, Morusya, Mrbinking, Nidoking, Nosuri, rinkiha, Sololiquy, Spectator, wwwww, Yoshi_green, yuinn, Yumeno Himiko, ZiRoX, Zyzyx |
Commentator |
Ash Ketchum, Dohland, e wong, ElSkeffe, Elux, hypnoSpirA, KWYJIBO, Maitoo, Realmas, Sartan, Secre, Snowleopard, Toaph Daddy |
Referee |
[K], Aidown, Albionthegreat, LeoFLT, nik, Speshimen, tigereyes144, Yazzehh |
Statistician |
shdewz, LeoFLT |
Design coordinator |
Sakura006, kaetwo |
|
Argentina |
-Story-, VelperK, SirGonzaxz, [225]Zeus, [225]nullCat, Ambition- |
|
Australia |
chickennando, KWYJIBO, CrimsonPleaseee, Beerus, TheTixTop, Talicrons |
|
Austria |
Pepti, Jinhwan, qzoomee, Volki |
|
Belgium |
ElSkeffe, Jezse, Emmenez moi, [ Zhiend ], my cutie, Cakenoob |
|
Bulgaria |
Dekyoura, Azakriel, ss033, Deadlest33 |
|
Canada |
Katsuragi, fuhie, sularis, Unlucky_w, Dea ex machina, RedcXca |
|
Chile |
Lechu FAQ 35P, Aryssiel, Pekorrat, Smukur, Stark, Thaemine |
|
China |
Nene Sakura, Eta UMa, -Yui, Shiina Minatsu, [Paw]Just_MLN, Seira-Nanamori |
|
Denmark |
Kaare, Captain, Noemark, tjukas |
|
Estonia |
TuuGamer, Sadu, Dianthus, -Nyaro, TkonicRabid |
|
Finland |
YERTI, Veeti, -Kaguya, Leinou, Tohtori G-piste, JonZku |
|
France |
Electr0o, Zelepha, Holloh, Noctalium, Gwelawyr, dotCore |
|
Germany |
Marvmallow, Ginoshi, Yuno4life, Inryoku, GinIkari, - B e a t e r - |
|
Hong Kong |
my angel auto, I CAN FC, fua, Black Spot |
|
Iceland |
Ash Ketchum, kiriwi, birkir, Teini |
|
Indonesia |
Zvenx, Chroneko, Serestia, Chiya--, EpanPan, Renessia |
|
Japan |
Molqus, -Rindou-, eisuke0530, hiroshiki, Melu, S B K |
|
Latvia |
AnApple7, Soruki, Xeltusha, Voxargenteae, Joyy |
|
Malaysia |
kokomi on osu, Moeruattack, HyPerNekoChan, Kagari, Evirir, Summerleopard |
|
Mexico |
Firu, Cxlucha, ArLuxZerRay, ExGunt, Astrea, Agamalpa |
|
Netherlands |
Dutchman, b-a-d-s123, woodpamp, Roasted Chicken, Sartan, Selo |
|
New Zealand |
Kasumizawa-Miyu, Starwide, Nashiro, Wettham77, Cipse, Trumpet |
|
Norway |
CyCeph, Cameragod, Azeidith, Vikki, Benita, Lanki |
|
Peru |
islux, Lunati1kid, Boltico, MauriciOSU, Anthonyvfxfx, GZone |
|
Philippines |
- Kielzu -, liamggss, [ Potemkin ], Mawile, -Isla-, Chrisuly |
|
Poland |
BoberOfDarkness, trig0n, Phob, madcin, Jakkubon, -Filow- |
|
Russian Federation |
Kimitakari, KitsunIvy, Segmentum, ArthurEdikovich, Nerris, _Rama |
|
Singapore |
Ekseff, Setsuen, uniqly, Yiihao, NoBudgetGuy |
|
Spain |
Eyminz, Alepe, MusicDropZ, [Ajoduro], skyres00 |
|
Sweden |
Aceon, Shameimaru, Setomi, nc enjoyer, DataPata, Eps |
|
Taiwan |
DoDoEbi, _Nanami, Shimoe Koharu, Happiness Fish, Psc_IceRain, Minato Yukina |
|
Thailand |
EzyS, N3Marry, G1ilbert, -TANAKITO-, Bigkung2006, ZeroKungz |
|
Turkey |
lorem ipsum, shimu, Teoman, Yasi6n, 1Haruki, Reha |
|
United Kingdom |
Withered Lotus, Matt_H, Eliminate, DarnedUrchin, Stats-Kun, Olib |
|
United States |
Secre, Dahcreeper, Lexii, Colin, rostld, Trent |
|
Vietnam |
Stardust Prism, Shu, NamSPro, -Linglan Lily-, _Fubucky_, Beubaby |
Captains are listed in bold.
The complete sign-up list can be found here.
CWC 2024 podium
Grand Finals
Download the mappack here (195 MB)
View the showcase VOD here
Download the mappack here (199 MB)
View the showcase VOD here
Download the mappack here (154 MB)
View the showcase VOD here
Download the mappack here (149 MB)
View the showcase VOD here
Download the mappack here (109 MB)
View the showcase VOD here
Download the mappack here (99 MB)
View the showcase VOD here
Download the mappack here (80 MB)
View the showcase VOD here
Grand Finals
Detailed statistics for this round can be found here.
Saturday, 29 June 2024:
All-stars Red |
6 |
7 |
All-stars Blue |
#1 |
#1 |
Grand Finals Showmatch |
Argentina |
7 |
4 |
Poland |
#1 |
#1 |
|
Saturday, 29 June 2024:
United States |
7 |
4 |
Argentina |
#1 |
#1 |
Detailed statistics for this round can be found here.
Saturday, 22 June 2024:
Rookies |
3 |
7 |
Veterans |
#1 |
#1 |
Finals Showmatch |
Chile |
6 |
7 |
Poland |
#1 |
#1 |
|
Finland |
1 |
7 |
Canada |
#1 |
#1 |
|
Sunday, 23 June 2024:
United States |
7 |
1 |
Argentina |
#1 |
#1 |
Canada |
5 |
7 |
Poland |
#1 |
#1 |
Detailed statistics for this round can be found here.
Saturday, 15 June 2024:
Canada |
7 |
1 |
Australia |
#1 |
#1 |
France |
7 |
2 |
Indonesia |
#1 |
#1 |
Poland |
7 |
0 |
Japan |
#1 |
#1 |
Russian Federation |
3 |
7 |
Peru |
#1 |
#1 |
Argentina |
7 |
2 |
Finland |
#1 |
#1 |
Sunday, 16 June 2024:
Staff Red |
7 |
6 |
Staff Blue |
#1 |
#1 |
Showmatch featuring CWC staff |
France |
0 |
7 |
Poland |
#1 |
#1 |
|
Canada |
7 |
1 |
Peru |
#1 |
#1 |
|
United States |
7 |
1 |
Chile |
#1 |
#1 |
|
Detailed statistics for this round can be found here.
Friday, 7 June 2024:
Saturday, 8 June 2024:
Australia |
0 |
-1 |
Thailand |
win by default |
|
Japan |
6 |
1 |
Sweden |
#1 |
#1 |
Taiwan |
6 |
0 |
Philippines |
#1 |
#1 |
United Kingdom |
6 |
0 |
Netherlands |
#1 |
#1 |
China |
0 |
-1 |
Mexico |
win by default |
#1 |
Poland |
5 |
6 |
Argentina |
#1 |
#1 |
Indonesia |
6 |
0 |
Spain |
#1 |
#1 |
Belgium |
6 |
4 |
Germany |
#1 |
#1 |
Peru |
6 |
1 |
Taiwan |
#1 |
#1 |
Canada |
4 |
6 |
Chile |
#1 |
#1 |
Sunday, 9 June 2024:
China |
1 |
6 |
Australia |
#1 |
#1 |
Japan |
6 |
4 |
United Kingdom |
#1 |
#1 |
Belgium |
2 |
6 |
Indonesia |
#1 |
#1 |
United States |
6 |
0 |
Russian Federation |
#1 |
#1 |
Finland |
6 |
3 |
France |
#1 |
#1 |
Detailed statistics for this round can be found here.
Friday, 31 May 2024:
France |
6 |
4 |
China |
#1 |
#1 |
Malaysia |
0 |
6 |
Germany |
#1 |
#1 |
Saturday, 1 June 2024:
New Zealand |
1 |
6 |
Philippines |
#1 |
#1 |
Thailand |
6 |
3 |
Vietnam |
#1 |
#1 |
Canada |
6 |
4 |
Indonesia |
#1 |
#1 |
Latvia |
4 |
6 |
Norway |
#1 |
#1 |
Iceland |
0 |
6 |
Sweden |
#1 |
#1 |
Estonia |
0 |
6 |
Mexico |
#1 |
#1 |
Chile |
6 |
0 |
Belgium |
#1 |
#1 |
Sunday, 2 June 2024:
Finland |
6 |
1 |
Australia |
#1 |
#1 |
Japan |
4 |
6 |
Russian Federation |
#1 |
#1 |
Poland |
6 |
0 |
Taiwan |
#1 |
#1 |
Denmark |
1 |
6 |
Spain |
#1 |
#1 |
United States |
6 |
0 |
United Kingdom |
#1 |
#1 |
Turkey |
3 |
6 |
Netherlands |
#1 |
#1 |
Argentina |
6 |
3 |
Peru |
#1 |
#1 |
Detailed statistics for this round can be found here.
Saturday, 25 May 2024:
Chile |
5 |
0 |
New Zealand |
#1 |
#1 |
Sweden |
1 |
5 |
Australia |
#1 |
#1 |
Russian Federation |
5 |
0 |
Vietnam |
#1 |
#1 |
Indonesia |
5 |
1 |
Norway |
#1 |
#1 |
China |
5 |
3 |
Netherlands |
#1 |
#1 |
France |
5 |
0 |
Turkey |
#1 |
#1 |
Canada |
5 |
1 |
Latvia |
#1 |
#1 |
United Kingdom |
5 |
0 |
Mexico |
#1 |
#1 |
Sunday, 26 May 2024:
Belgium |
5 |
2 |
Philippines |
#1 |
#1 |
Taiwan |
5 |
2 |
Germany |
#1 |
#1 |
Japan |
5 |
0 |
Thailand |
#1 |
#1 |
Poland |
5 |
0 |
Malaysia |
#1 |
#1 |
Finland |
5 |
0 |
Iceland |
#1 |
#1 |
Argentina |
5 |
2 |
Denmark |
#1 |
#1 |
United States |
5 |
0 |
Estonia |
#1 |
#1 |
Peru |
5 |
0 |
Spain |
#1 |
#1 |
The final standings for the Qualifier stage can be found in the following spreadsheet.
View the Qualifier seed reveal VOD here
#1 |
United States |
8.966 |
2,939,752 |
#2 |
Poland |
8.775 |
2,877,531 |
#3 |
Finland |
8.749 |
2,868,272 |
#4 |
Canada |
8.717 |
2,859,477 |
#5 |
Chile |
8.667 |
2,842,008 |
#6 |
France |
8.635 |
2,831,886 |
#7 |
Argentina |
8.616 |
2,825,710 |
#8 |
Japan |
8.408 |
2,758,068 |
#9 |
Russian Federation |
8.379 |
2,748,316 |
#10 |
Peru |
8.367 |
2,745,095 |
#11 |
China |
8.347 |
2,737,890 |
#12 |
Belgium |
8.332 |
2,732,675 |
#13 |
Indonesia |
8.322 |
2,728,902 |
#14 |
Sweden |
8.282 |
2,716,302 |
#15 |
Taiwan |
8.200 |
2,689,500 |
#16 |
United Kingdom |
8.143 |
2,671,665 |
#17 |
Mexico |
8.041 |
2,637,777 |
#18 |
Germany |
8.020 |
2,631,226 |
#19 |
Australia |
7.871 |
2,582,154 |
#20 |
Norway |
7.814 |
2,563,246 |
#21 |
Philippines |
7.79 |
2,555,711 |
#22 |
Netherlands |
7.745 |
2,541,554 |
#23 |
Spain |
7.408 |
2,430,075 |
#24 |
Vietnam |
7.331 |
2,405,819 |
#25 |
Thailand |
6.940 |
2,277,007 |
#26 |
Denmark |
6.754 |
2,215,590 |
#27 |
Turkey |
6.588 |
2,162,663 |
#28 |
New Zealand |
6.483 |
2,126,254 |
#29 |
Latvia |
6.465 |
2,120,394 |
#30 |
Iceland |
6.436 |
2,109,321 |
#31 |
Malaysia |
6.215 |
2,039,032 |
#32 |
Estonia |
5.972 |
1,959,411 |
#33 |
Singapore |
5.852 |
1,918,407 |
#34 |
Austria |
5.699 |
1,869,718 |
#35 |
Bulgaria |
4.484 |
1,469,144 |
#36 |
Hong Kong |
DNP |
DNP |
The osu!catch World Cup is a country-based 3 versus 3 double-elimination team tournament, played on the osu!catch game mode.
Players from countries or territories (as seen on their profile flag) that are under a protectorate or sovereign state may choose to play for that country
if the country listed on their profile is unable to field enough players to form a valid team. Refer to
this article for an overview of the criteria that is adopted. Players that have participated under another country previously may continue to do so.
Beatmap scoring is based on ScoreV2.
The minimum size for a team is 4 players, and the maximum is 6.
The beatmap list for each round will be announced by the mappool selectors on the official stream, on the Sunday before the matches take place.
The match schedules for each round will be announced by the tournament managers on this page, as well as the information sheet, on the Sunday before the matches take place.
Use of the Visual Settings to alter background dim or disable beatmap elements like storyboards and skins are allowed.
If less than the minimum amount of required players are present at match time, the match can be postponed for up to 10 minutes. If after this period there are still not enough players for either team, a
win by default will be declared for the side with the most members present.
Exchanging players between games is allowed without limitations.
If a game ends in a draw, it will be nullified and the beatmap will be replayed.
Teams may ask for a rematch if a team member encounters technical issues while playing within 30 seconds or 25% of the beatmap drain length (whichever happens first) of the game's start. Referees may do rematch independently of either team if reasonable evidence of a disconnect/tech issue exists. Referees may veto any rematch requests at their discretion.
"Lag spikes" are not considered a valid reason to rematch a beatmap.
The roster for each team during a rematch must remain the same as the original run. If that is not possible, e.g. by virtue of a technical issue that prevents a player from entering the lobby, both teams will be allowed to swap rosters.
This rule is not to be abused. Referees may veto a rematch request if they find that this is the case.
If a player disconnects mid-game, their scores will not be counted towards their team's total, unless adequate proof of said score is provided. The following are considered as acceptable proof:
Player point-of-view live stream snippets (commonly referred to as "clips" or "VODs"). The entirety of the play, along with the results screen must be clearly visible along with the affected player's score.
Replay files of the play, taken directly from the "Local scores" tab on the affected player's client (the timestamps must exactly match the time at which the game took place, as seen on the multiplayer lobby link).
Screenshots from other players taken directly in-game that show the affected player's score.
Screenshots from the results screen must clearly show the affected player's score. This is the preferred method.
Screenshots taken in-game at the time of disconnection may be accepted. Note that this method does not provide a one-to-one representation of that player's score. Using this method is not encouraged and it may be denied at the referee's discretion if the information provided is not sufficient to identify the player/score.
All screenshots MUST be taken using the game itself (using Shift
+ F12
), that is, they must be hosted on the https://osu.ppy.sh/
domain. Any other form of screenshot will be denied.
Player scores may be derived from the official stream as a last resort, in cases where the match is streamed.
Players are expected to keep the match running fluently and without delays. Excessive match delays from the players' side may result in penalties being applied by the tournament managers. Disrupting the match by foul play, insulting or provoking other players or staff, delaying the match, or other deliberate inappropriate misbehaviour are strictly prohibited, and will be punished accordingly.
All players and staff must be treated with respect. Instructions from the referees and the tournament managers are to be followed. Decisions labelled as final are not to be objected.
The multiplayer chatrooms underlie the
osu! community rules. All chat rules apply to the multiplayer chatrooms where the matches will take place.
Penalties for violating the tournament rules include, but are not limited to:
Exclusion of specific players for one beatmap.
Exclusion of specific players for an entire match.
Declaring the match as forfeited, or as a win by default for the other team.
Disqualification from the entire tournament.
Disqualification from the current and future official tournaments, until appealed.
Referees may allow, at their discretion, lower or higher tolerances for timers.
The tournament managers may request liveplays or recordings of individual players or teams at any point in the tournament without prior warning.
The tournament managers will be responsible for receiving and investigating any tournament-related complaints.
The tournament managers reserve the right to modify these rules at any moment. Any such changes will be announced in advance.
Every user interested in joining their country's team signs up individually.
The tournament managers will create a list of potential candidates for a country's team.
The tournament managers will declare one candidate captain of their country's team.
The provisional captain will receive a private message on the osu! website containing further instructions, via the announcement feature, titled "osu!catch World Cup 2024 - Team {Country Name}".
The provisional captain will then form their team by selecting players from the candidate pool for their country.
Captains are expected to choose team members with honesty and good will, with the aim of fielding the strongest team possible.
Captains are expected to submit their finalised team list before the deadline.
Captains are allowed to exclude themselves from the team list.
Captains are allowed to conduct and coordinate "tryouts", tests to gauge player aptitude, on their own terms.
Captains are allowed, at any time, to transfer their role to other prospective team members. Once given, only the new captain may assign the captaincy to another player.
Teams that do not send their team list by May 10, 23:59 UTC will be disqualified from the competition.
To ensure valid registrations, every prospective participant will be manually checked by the
account support team, in a manner similar to the
tournament screening that is offered to community tournaments.
All successfully formed teams will be published after the registration phase on this page.
Tournament staff members are not allowed to play in the tournament, with the exception of commentators and streamers.
In the Qualifier stage, all teams will play a specific pool designed by the mappool selectors.
The Qualifier pool will consist of 9 maps. There will be 3 maps under the No Mod bracket, and 2 maps for the Hidden, Hard Rock, and Double Time brackets.
Teams will be asked to play the mappool twice at a designated time. The team's best playthrough will be used for seeding.
The mappool is to be played according to the order listed on this page.
Each team must have 3 members play each map. They may be exchanged freely after a map is concluded.
An optional 3-minute break will be offered between the first and second playthrough of the mappool.
All teams will play their qualifiers in separate rooms. It is
suggested that teams do not broadcast or share their results publicly to avoid seed manipulation.
The seeding method used for Qualifiers will be %MAX — the highest combined team score for each map will receive 100% of the points, and every other team will be awarded a percentage of that top score.
The exact formula that will be used for all teams (and for each map) is
Final Score = Team Score / MAX Score
, where:
Final Score
is the percentage awarded to the current team
Team Score
is the score the current team achieved on the current map
MAX Score
is the highest score achieved for the current map
Only the top 32 seeded teams will advance to the Round of 32.
Following the Qualifiers, a double-elimination bracket will be played — for teams in the winners bracket, the winning team continues in the same bracket, while the losing team gets moved to the losers bracket, where any further defeats will eliminate the team from the competition.
Teams in the losers bracket must play up to 2 matches each weekend, starting from the Quarterfinals.
In the Qualifiers, teams need to place in the top 32 seeded teams in order to advance to the double-elimination stage.
In the Round of 32, teams need to win 5 maps to win a match (best of 9).
In the Round of 16 and Quarterfinals, teams need to win 6 maps to win a match (best of 11).
In the Semifinals, Finals and Grand Finals, teams need to win 7 maps to win the match (best of 13).
Note: for the Grand Finals match, the team that is coming from the winners bracket is required to win one "set", that is, one best of 13, to win the tournament. The team coming from the losers bracket, however, needs to win 2 sets.
A referee will create a multiplayer room 10 minutes before the scheduled match time. Teams must join the lobby in that period.
The room settings are Game mode: "osu!catch"
, Team mode: "Team Vs"
and Score mode: "ScoreV2"
. The room name must follow the pattern of CWC2024: ({Red Team}) VS ({Blue Team})
. The team mentioned first in the room name must be the red team, the team mentioned second in the room name must be the blue team.
Each captain must use
!roll
once in the match's chatroom. After the rolls are set, the pick and ban phase will have the following steps:
The winner of the !roll
may choose to either pick first and ban second, or pick second and ban first.
The loser of the !roll
will follow the remaining pick order.
After bans are decided, both teams will take turns in picking a beatmap from the mappool.
Teams will be allowed 2 minutes to pick a beatmap and 2 minutes to press the
Ready
button on their client. If a team takes more time than allotted for either action, the procedures adopted will be as follows:
For the first occurrence:
The team will receive a verbal warning from the referee; in addition, the referee may opt to forcefully use the team's tactical timeout to allow for the team to pick.
If the team does not pick a map within 15 seconds from when the timer expires, the referee will apply the procedure for subsequent occurrences listed below, i.e. a random pick will be used for a pick timer, and the match will be forcefully started for a ready timer.
On subsequent occurrences:
For a pick timer: a random map will be chosen from the mappool using !roll X
, where X is the number of beatmaps that were neither picked nor banned, excluding the tiebreaker.
For a ready timer: the referee will issue the !mp start 10
command, regardless of how many players from each team are present in the lobby, using !mp kick
on any extra players for each team, starting from the top (i.e. the first valid player combination for each team will be forced to play the pick). The results for such games are to be taken as is.
Repeat offenders may receive further sanctions from the tournament managers.
In the case of a team starting a map with less than the optimal number of players on their roster due to an unforeseen circumstance (e.g. a technical issue or unavoidable player absence), the team in question will be granted the right to fill their roster before play commences. The remainder of the original roster must stay the same, i.e. only player additions are allowed.
Each team will receive one "tactical timeout" of 2 minutes, to be used as extra time to ban, pick, or ready for a beatmap.
The tactical timeout is optional.
Every stage will have its own mappool.
The mappool sizes are as follows:
Qualifiers: 9 beatmaps
Round of 32: 14 beatmaps
Round of 16 and Quarterfinals: 16 beatmaps
Semifinals, Finals, and Grand Finals: 18 beatmaps
Each mappool has one tiebreaker, except for the Qualifiers.
The No Mod bracket will be played with the
No Fail mod activated.
The Mixed Mod bracket will be played with FreeMod activated. Each player will be forced to choose one mod each, from a selection of
NoMod,
Hidden, and
Hard Rock. Each mod must be played by exactly one player (i.e. one player MUST pick NoMod, another player MUST pick Hidden, and the remaining player MUST pick Hard Rock).
Failed scores will be counted. To that end, the
No Fail mod will be enforced on every beatmap.
The tiebreaker will be played under FreeMod conditions, but players are exempt from the mod requirement.
Each stage will be held on a single weekend.
Matches in Qualifiers will be held during specific time slots proposed by the tournament managers. Each team may to choose a time slot in which they want to play.
All bracket stage matches will be held between Saturday 00:00 and Sunday 19:00 UTC.
Match scheduling will be handled by the tournament managers. Schedules will be released on the Sunday before the first matches of the stage. The tournament managers will try to create the schedule to respect the participants' time zones.
Reschedules will only be considered if both teams agree to a time and communicate it to the tournament managers, before Wednesday 23:59 UTC of the week the match is to take place on.
Matches may not be scheduled to any time beyond Sunday, 19:00 UTC of the week they are to be played at.
Do not ask for a reschedule unless it is absolutely necessary. The tournament managers reserve the right to deny any rescheduling request.
Late reschedule requests will not be accepted under any circumstances.
Captains are responsible for managing their team's availability.