osu!catch World Cup 2025 1ju1y

3p5i3m

The osu!catch World Cup 2025 (CWC 2025) is a country-based osu!catch tournament hosted by the osu! team. It is the fourteenth instalment of the osu!catch World Cup.

Tournament schedule 2r3s6r

Prizes 5r3n2j

The osu!catch World Cup 2025 offers a $2,000 cash prize pool and limited-edition merch.

Placing	Prizes
	50% of the prize pool, single-run merch, profile badge, osu!catch Champion title for one year
	30% of the prize pool, single-run merch, profile badge
	20% of the prize pool, single-run merch, profile badge

Organisation 3g3j71

The osu!catch World Cup 2025 is run by various community .

Links 1s5k29

• Livestream
• Discussion thread
• Tournament listing

Participants 1d4w2a

Captains are listed in bold. Individual team compositions subject to change until Saturday, May 31 23:59 UTC. This list was last updated on May 30.

The complete list can be found here.

Ruleset m83o

Tournament rules w523q

1. 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.
2. Beatmap scoring is based on ScoreV2.
3. The minimum size for a team is 4 players, and the maximum is 6.
4. 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.
5. 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.
6. 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.
7. 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 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. at least 3 participants from each team must be present for the match to begin).
8. Exchanging players between games is allowed without limitations.
9. If a game ends in a draw, it will be nullified and the beatmap will be replayed.
10. 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.
11. 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.jeuxcrack.net/ 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.
12. 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.
13. 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.
14. The multiplayer chatrooms underlie the osu! community rules. All chat rules apply to the multiplayer chatrooms where the matches will take place.

    • 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.
15. 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.
16. Referees may allow, at their discretion, lower or higher tolerances for timers.
17. The tournament managers may request liveplays or recordings of individual players or teams at any point in the tournament without prior warning.
18. The tournament managers will be responsible for receiving and investigating any tournament-related complaints.
19. The tournament managers reserve the right to modify these rules at any moment. Any such changes will be announced in advance.

Tournament registration 4z5y5y

1. Every interested in ing 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 2025 - Team {Country Name}".
2. The provisional captain will then form their team by selecting players from the candidate pool for their country.

   • Captains are expected to choose team 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 .
   • Captains are allowed, at any time, to transfer their role to other prospective team . Once given, only the new captain may assign the captaincy to another player.
   • Teams that do not send their team list by May 31, 23:59 UTC will be disqualified from the competition.
3. To ensure valid registrations, every prospective participant will be manually checked by the team, in a manner similar to the tournament screening that is offered to community tournaments.

   • Every ed 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.
4. All successfully formed teams will be published after the registration phase on this page.

   • A team should have at least 4 players ed to have the chance to play the Qualifier stage.
5. Tournament staff are not allowed to play in the tournament, with the exception of commentators and streamers.

Qualifier instructions 71k51

1. In the Qualifier stage, all teams will play a specific pool designed by the mappool selectors.
2. The mappool will contain 4 brackets: NoMod, Hidden, Hard Rock, and Double Time. There will be no tiebreakers for this stage.
3. 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.
4. Teams will be asked to play the mappool twice at a designated time. The team's best playthrough will be used for seeding.
5. The mappool is to be played according to the order listed on this page.

   • Teams may skip playing any beatmap on their second run.
6. Each team must have 3 play each map. They may be exchanged freely after a map is concluded.
7. An optional 3-minute break will be offered between the first and second playthrough of the mappool.
8. 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.

   • Teams may be grouped into a singular room if there are not enough referees available at match time.
9. The seeding method used for Qualifiers will be %MAX — the highest combined team score for each map will receive 100% of the points (i.e. a numerical value of 1), and every other team will be awarded a percentage of that top score. The individual map percentages will be added together to compose that team's final score, which is then sorted from highest to lowest, highest being seed #1.

   • The exact formula that will be used for all teams (and for each map) is Map percentage = Team score / MAX score, where:

     • Map percentage 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
   • The final team score to be sorted is defined as Final score = SUM(Map percentage), i.e. the sum of each map's Map percentage.
10. Only the top 32 seeded teams will advance to the Round of 32.

Stage instructions 523l6o

1. 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.
2. Teams in the losers bracket must play up to 2 matches each weekend, starting from the Quarterfinals.

Win conditions 52546d

• 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.

Match instructions 5t5g2r

1. A referee will create a multiplayer room 10 minutes before the scheduled match time. Teams must 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 CWC2025: ({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.
2. 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.
3. After bans are decided, both teams will take turns in picking a beatmap from the mappool.
4. 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.
5. 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.
6. 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.

   • The tactical timeout may be called on a tiebreaker, provided that both teams' captains agree to it.

Mappool instructions 6e252u

1. Every stage will have its own mappool.
2. Each mappool consists of 5 brackets: NoMod, Hidden, Hard Rock, Double Time and Mixed Mod.
3. 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
4. Each mappool has one tiebreaker, except for the Qualifiers.
5. The No Mod bracket will be played with the No Fail mod activated.
6. The Hidden, Hard Rock and Double Time brackets will be played with the respective mods activated along with the No Fail mod.
7. When playing a map from the Hard Rock or Double Time pool, the Hidden modification may be optionally used by any player.
8. 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.
9. Failed scores will be counted. To that end, the No Fail mod will be enforced on every beatmap.

   • Teams that purposefully disregard this instruction and team fail as a result will lose said game.
10. The tiebreaker will be played under Free Mod conditions, but players are exempt from the mod requirement.

Scheduling instructions 5w5o63

1. Each stage will be held on a single weekend.
2. Matches in Qualifiers will be held during specific time slots proposed by the tournament managers. Each team may choose a time slot in which they want to play.

   • A team that does not pick a time slot by Thursday, June 5 23:59 UTC will be considered disqualified.
3. All bracket stage matches will be held between Saturday 00:00 and Sunday 19:00 UTC.

   • Other times may be available upon request, consult with the tournament managers for more information.
4. 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.

   • In the Quarterfinals and subsequent stages, team captains may inform tournament managers if they expect a specific time slot to be unavailable in the following week.
5. 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.
6. Captains are responsible for managing their team's availability.