wiki
Requested page is not yet translated to the selected language (한국어). Showing English version.
osu!catch World Cup 2022
The osu!catch World Cup 2022 (CWC 2022) was a country-based osu!catch tournament hosted by the osu! team. It was the eleventh instalment of the osu!catch World Cup.
Tournament schedule
| Event | Timestamp |
|---|---|
| Registration phase | 2022-04-21/2022-05-05 |
| Qualifier showcase | 2022-05-14 (14:00 UTC) |
| Qualifiers | 2022-05-21/2022-05-22 |
| Round of 32 | 2022-05-28/2022-05-29 |
| Round of 16 | 2022-06-04/2022-06-05 |
| Quarterfinals | 2022-06-11/2022-06-12 |
| Semifinals | 2022-06-18/2022-06-19 |
| Finals | 2022-06-25/2022-06-26 |
| Grand Finals | 2022-07-02/2022-07-03 |
Prizes
The osu!catch World Cup 2022 offered a $2,000 cash prize pool and limited edition merch.
| Placing | Prizes |
|---|---|
| 48% of the prize pool, single-run merch, profile badge, osu!catch Champion user title for one year | |
| 32% of the prize pool, single-run merch, profile badge | |
| 20% of the prize pool, single-run merch, profile badge |
Organisation
The osu!catch World Cup 2022 was run by the osu! team and various community members.
| Position | Member(s) |
|---|---|
| Manager | Azer, ChillierPear, F D Flourite, LeoFLT |
| Mappool selector | autofanboy, ekr, F D Flourite, wwwww, -Ken |
| Mappool quality assurance | Bunnrei, Deif, JBHyperion, Jemzuu, Sanyi |
| Mapper | Ascendance, autofanboy, Bunnrei, Daletto, Dapulezatos, Deif, Emiru, F D Flourite, Greaper, JBHyperion, Jemzuu, JierYagtama, Mniam, Nosuri, Sanyi, Souvenir, Verti, wwwww, Yumeno Himiko, -Ken, -Rustyy |
| Commentator | Dohland, Elux, JBHyperion, KWYJIBO, Lumenite-, Maitoo, Nelly, Sartan, Secre, Snowleopard, Zak, [ Quinten ] |
| Referee | Albionthegreat, Fairy Bread, LeoFLT, Speshimen, tigereyes144, Yazzehh, [K] |
| Statistician | shdewz |
Links
- Pick'ems page hosted by hallowatcher
Participants
Podium
CWC 2022 podium
Mappools
Download the mappack here (145 MB)
Grand Finals
Finals
Download the mappack here (119 MB)
Semifinals
Download the mappack here (144 MB)
Quarterfinals
Download the mappack here (138 MB)
Round of 16
Download the mappack here (104 MB)
Round of 32
Download the mappack here (82 MB)
Qualifiers
Download the mappack here (93 MB)
Match results
Grand Finals
Sunday, 3 July 2022:
Finals
Detailed statistics for this round can be found here.
Saturday, 25 June 2022:
| Team A | Team B | Match link | ||
|---|---|---|---|---|
| Indonesia | 7 | 5 | Canada | #1 |
Sunday, 26 June 2022:
| Team A | Team B | Match link | ||
|---|---|---|---|---|
| China | 2 | 7 | South Korea | #1 |
| United States | 7 | 2 | France | #1 |
| United States | 7 | 4 | Indonesia | #1 |
Semifinals
Detailed statistics for this round can be found here.
Saturday, 18 June 2022:
| Team A | Team B | Match link | ||
|---|---|---|---|---|
| France | 7 | 0 | Germany | #1 |
| Mexico | 2 | 7 | Italy | #1 |
| Chile | 7 | 1 | Russian Federation | #1 |
| Chile | 6 | 7 | France | #1 |
| Canada | 7 | 2 | Australia | #1 |
Sunday, 19 June 2022:
| Team A | Team B | Match link | ||
|---|---|---|---|---|
| China | 7 | 4 | Indonesia | #1 |
| South Korea | 7 | 4 | United States | #1 |
| Canada | 7 | 6 | Italy | #1 |
Quarterfinals
Detailed statistics for this round can be found here.
Saturday, 11 June 2022:
| Team A | Team B | Match link | ||
|---|---|---|---|---|
| Russian Federation | 6 | 0 | Japan | #1 |
| Italy | 6 | 3 | Belgium | #1 |
| Taiwan | 6 | 0 | Argentina | #1 |
| Australia | 6 | 2 | Finland | #1 |
| Poland | 6 | 1 | Netherlands | #1 |
| Brazil | 6 | 1 | Norway | #1 |
| Russian Federation | 6 | 4 | Poland | #1 |
Sunday, 12 June 2022:
| Team A | Team B | Match link | ||
|---|---|---|---|---|
| South Korea | 6 | 0 | Mexico | #1 |
| Germany | 6 | 2 | Vietnam | #1 |
| Singapore | 6 | 2 | Sweden | #1 |
| Taiwan | 4 | 6 | Germany | #1 |
| Australia | 6 | 0 | Singapore | #1 |
| China | 6 | 1 | France | #1 |
| Indonesia | 6 | 2 | Chile | #1 |
| Italy | 6 | 0 | Brazil | #1 |
| United States | 6 | 5 | Canada | #1 |
Round of 16
Detailed statistics for this round can be found here.
Saturday, 4 June 2022:
| Team A | Team B | Match link | ||
|---|---|---|---|---|
| China | 6 | 0 | Brazil | #1 |
| Ukraine | -1 | 0 | Belgium | win by default |
| Portugal | 1 | 6 | Finland | #1 |
| Malaysia | 0 | 6 | Argentina | #1 |
| France | 6 | 5 | Italy | #1 |
| Canada | 6 | 5 | Russian Federation | #1 |
Sunday, 5 June 2022:
| Team A | Team B | Match link | ||
|---|---|---|---|---|
| Taiwan | 2 | 6 | Mexico | #1 |
| South Korea | 6 | 1 | Germany | #1 |
| Thailand | 1 | 6 | Netherlands | #1 |
| Israel | 0 | 6 | Japan | #1 |
| Chile | 6 | 3 | Australia | #1 |
| Indonesia | 6 | 1 | Singapore | #1 |
| Colombia | 2 | 6 | Vietnam | #1 |
| United States | 6 | 1 | Poland | #1 |
| Turkey | 5 | 6 | Sweden | #1 |
| United Kingdom | 0 | 6 | Norway | #1 |
Round of 32
Detailed statistics for this round can be found here.
Saturday, 28 May 2022:
| Team A | Team B | Match link | ||
|---|---|---|---|---|
| China | 5 | 0 | Israel | #1 |
| France | 5 | 0 | Thailand | #1 |
| Singapore | 5 | 1 | Argentina | #1 |
| Canada | 5 | 0 | United Kingdom | #1 |
Sunday, 29 May 2022:
| Team A | Team B | Match link | ||
|---|---|---|---|---|
| Brazil | 5 | 1 | Japan | #1 |
| Chile | 5 | 0 | Colombia | #1 |
| Belgium | 2 | 5 | Poland | #1 |
| South Korea | 5 | 0 | Portugal | #1 |
| Italy | 5 | 1 | Netherlands | #1 |
| Indonesia | 5 | 0 | Malaysia | #1 |
| Australia | 5 | 1 | Vietnam | #1 |
| Taiwan | 5 | 1 | Turkey | #1 |
| Russian Federation | 5 | 1 | Norway | #1 |
| United States | 5 | 0 | Ukraine | #1 |
| Germany | 5 | 4 | Finland | #1 |
| Mexico | 5 | 0 | Sweden | #1 |
Qualifiers
The final standings for the Qualifier stage can be found in the following spreadsheet. Detailed statistics for this round can be found here.
| Seed | Country | MAX% sum |
|---|---|---|
| #1 | China | 8.888 |
| #2 | South Korea | 8.795 |
| #3 | United States | 8.787 |
| #4 | Indonesia | 8.755 |
| #5 | Chile | 8.69 |
| #6 | Canada | 8.688 |
| #7 | Taiwan | 8.629 |
| #8 | France | 8.608 |
| #9 | Italy | 8.556 |
| #10 | Mexico | 8.494 |
| #11 | Russian Federation | 8.478 |
| #12 | Australia | 8.261 |
| #13 | Singapore | 8.253 |
| #14 | Belgium | 8.222 |
| #15 | Germany | 8.189 |
| #16 | Brazil | 8.059 |
| #17 | Japan | 7.934 |
| #18 | Finland | 7.882 |
| #19 | Poland | 7.847 |
| #20 | Argentina | 7.648 |
| #21 | Vietnam | 7.574 |
| #22 | Norway | 7.538 |
| #23 | Sweden | 7.372 |
| #24 | Netherlands | 7.302 |
| #25 | Thailand | 7.285 |
| #26 | Turkey | 7.274 |
| #27 | United Kingdom | 7.199 |
| #28 | Colombia | 7.011 |
| #29 | Malaysia | 6.779 |
| #30 | Ukraine | 6.588 |
| #31 | Portugal | 6.445 |
| #32 | Israel | 6.173 |
| #33 | Spain | 5.982 |
| #34 | New Zealand | 5.584 |
| #35 | Philippines | 5.286 |
| #36 | Algeria | 4.722 |
| #37 | Switzerland | 4.452 |
Ruleset
Tournament rules
- The osu!catch World Cup is a country-based 3 versus 3 team tournament, played on the osu!catch game mode.
- Beatmap scoring is based on ScoreV2.
- The maps for each round will be announced by the mappool selectors on the Sunday before the actual matches take place.
- The match schedule will be settled by the Tournament Management (see above).
- If no referee is available at match time, the match will be postponed.
- Use of the Visual Settings to alter background dim or disable beatmap elements like storyboards and skins are allowed.
- Custom skin elements must not be used to alter core gameplay elements or mechanics in unintended ways.
- If a game ends in a draw, it will be nullified and the map will be replayed.
- Teams may ask for a rematch if a team member encounters technical difficulties while playing.
- "Lag spikes" are not considered a valid reason to nullify a beatmap.
- If a rematch happens, the original roster for each team during that particular beatmap must remain the same. If that is not possible, e.g. by virtue of a technical issue, 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.
- Disconnects within 30 seconds or 25% of the beatmap length (whichever happens first) can be rematched, at the referee's discretion, as long as it is clearly communicated in the chatroom.
- If a player disconnects, 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 thehttps://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.
- 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.
- The minimum amount of required players is the amount of players needed to play a beatmap without any vacant spots in the lobby (i.e. 3 participants must be present for the match to begin).
- If a player disconnects between beatmaps and the team cannot provide a substitute, the match can be delayed for up to 10 minutes (limited to once per team, per match).
- Exchanging players between games is allowed without limitations.
- The minimum size for a team is 4 players, and the maximum is 6.
- 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 at the referee's discretion. 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 Management 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, too.
- Breaking the chat rules may result in a silence. Silenced players cannot participate in multiplayer matches and must be exchanged for the duration of the punishment.
- 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 Management may request liveplays or recordings of individual players or teams at any point.
- The Tournament Management reserves the right to modify these rules at any moment. Any such changes will be announced in advance.
Tournament registration
- Every user interested in joining their country's team signs up individually.
- Tournament Management will create a list of potential candidates for a country's team.
- Tournament Management will declare one candidate captain of their country's team.
- The declared captain will then form their team from the candidate list of 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 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 may choose, with the approval of the Tournament Management, 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.
- 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.
- Every registered user will be assigned to their respective country's candidate list.
- To be successfully accepted on the list, players are required to be placed #5000 or higher on the osu!catch global ranking, and not have violated the osu! community rules within the last 12 months.
- All successfully formed teams will be published after the Registration Phase.
- A team should have at least 4 players registered to have the chance to play the Qualifier stage. This limitation may be change depending on the amount of signups.
- The top 32 seeded teams will qualify to the Round of 32.
- Tournament staff members are not allowed to play in the tournament, with the exception of commentators and streamers.
Qualifier instructions
- In the Qualifier stage, all teams will play a specific pool designed by the mappool selectors.
- The mappool will contain 4 brackets: NoMod, Hidden, Hard Rock, and Double Time. There will be no tiebreakers for this stage.
- The Qualifier pool will contain 9 maps. There will be 3 maps under the NoMod bracket, and 2 maps for the Hidden, Hard Rock, and Double Time brackets each.
- Teams will play the mappool in two runs at a designated time.
- Teams may skip individual maps or the second run altogether if they so desire.
- The mappool must be played in the following order: NM1, NM2, NM3, HD1, HD2, HR1, HR2, DT1, DT2.
- Each team must have 3 players for each map. They can be exchanged freely after each map is concluded.
- A team's final score for a map is considered as the highest combined team score for that map (i.e. the sum of each individual player's score). Only the highest score out of the two runs will be used for seeding.
- 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(Map Score), where:Final Scoreis the percentage awarded to the current teamTeam Scoreis the score the current team achieved on the current mapMAX(Map Score)is the highest score achieved for the current map
- 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.
- Only the top 32 seeded teams will advance to the Round of 32.
- The Qualifier stage results will be published in this wiki article after all teams have played.
Stage instructions
- Following the Qualifier stage, a double elimination bracket will be played. This means that the winning team moves to the next stage while the loser gets moved to the losers bracket.
- Teams in the losers bracket must play 2 matches each weekend starting from the Quarterfinals.
- Teams that lose a match in the losers bracket are eliminated from the tournament.
Win conditions
- In the Qualifier stage, teams need to place in the top 32 seeded teams in order to advance to the following double elimination stages.
- 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 a match (best of 13).
Match instructions
- A referee will create a multiplayer room 15 minutes before the scheduled match time. Players must join the lobby in that period.
- The room settings are
Game mode: "osu!catch",Team mode: "Team Vs"andScore mode: "ScoreV2". The room name must follow the pattern ofCWC2022: ({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 can ban one beatmap from the pool. These beatmaps can not be picked by any team for the entire duration of the match.
- Both captains will alternate picking a beatmap from the mappool.
- Each captain must use
!rollonce in#multiplayer.- The winner of the
!rollstarts picking the first beatmap of the match. - The loser of the
!rollstarts banning one beatmap, followed by the winner of the!rollto ban a beatmap.
- Teams will have 2 minutes to pick a beatmap and 2 minutes to get ready. If a team takes more time than allotted, the procedures adopted will be as follows:
- For the first occurrence:
- The team will receive a verbal warning from the referee
- 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 maps that were neither picked nor banned, excluding the tiebreaker. - For a ready timer: the referee will issue the
!mp start 10command, regardless of how many players from each team are present in the lobby, using!mp kickon 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 Management.
- Each team will receive one "tactical timeout" of 2 minutes, to be used as extra time to pick or ban a beatmap. The tactical timeout is optional.
- The tactical timeout may be called on a tiebreaker, provided that both teams' captains agree to it.
Mappool instructions
- There will be one mappool for each round of play.
- The Qualifier stage mappool will consist of 9 maps, Round of 32 will consist of 14 maps, Round of 16 and Quarterfinals will consist of 17 maps, Semifinals, Finals and Grand Finals will consist of 18 maps.
- Every mappool, except for the Qualifier stage, will contain a tiebreaker beatmap. It will only be played in case of a tie in the scoreline in the best of system, e.g. the scoreline is 4-4 and the match is best of 9, the tiebreaker shall be played.
- The No Fail mod will be enabled on all maps.
- When playing a map from the Hard Rock or Double Time pool, Hidden can be used optionally by any player.
- 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).
- The player using Hard Rock may choose to use Hidden and Hard Rock or just Hard Rock.
- The tiebreaker can be played with no mods selected or with the Hidden mod.
Scheduling instructions
- Each stage will be held on a single weekend.
- Matches in Qualifiers will be held during specific time slots proposed by the tournament staff. Each team is free to choose a time slot in which they want to play.
- A team that doesn't pick a time slot by Wednesday, 18 May 23:59 UTC will be considered disqualified.
- All Bracket Stages will be held between Saturday 0:00 and Sunday 23:59 UTC+0.
- Scheduling will be handled by the Tournament Management. Schedules will be released on the Sunday before the first matches of the stage. Tournament Management will try to create the schedule to respect the participants' time zones.
- In the Semifinals and subsequent stages, team captains may inform Tournament Management if they expect a specific time slot to be unavailable in the following week. Schedule updates will be granted to the best of Management's abilities.
- Reschedules will only be considered if both teams agree to a time and communicate it to the Tournament Management, before Wednesday 23:59 UTC+0 of the week the match is to take place on.
- Reschedules may only be requested by a team captain.
- Matches may not be scheduled to any time beyond Sunday, 19:00 UTC+0 of the week they are to be played at.
- Do not ask for a reschedule unless it is absolutely needed. The Tournament Management reserves the right to deny any rescheduling request.
- Captains are responsible for their team's availability. Any mishaps resulting from a lack of transparency from a team are to be resolved internally, the Tournament Management will not intervene.