Requested page is not yet translated to the selected language (српски). Showing English version.
The Touhou Project Mania Cup 4th (THMC 4th) is a team-based 2v2 osu!mania 4K tournament hosted by [GB]Sanae. The main theme of this tournament is the Touhou Project. The pool used for THMC 4th is 100% based on original and fan-made Touhou music. It is the fourth instalment of the Touhou Project Mania Cup.
Registration phase |
2024-12-22 (00:00 UTC) / 2025-01-12 (24:00 UTC) |
Qualifier showcase |
2025-01-19 (12:00 UTC) |
Qualifier stage |
2025-01-20/2025-01-28 |
Qualifier results |
2025-01-28 (04:00 UTC) |
Group stage week 1 |
2025-01-28/2025-02-09 |
Group stage week 2 |
2025-02-14/2025-02-16 |
Round of 32 |
2025-02-21/2025-02-23 |
Round of 16 |
2025-02-28/2025-03-02 |
Quarterfinals |
2025-03-07/2025-03-09 |
Semifinals |
2025-03-14/2025-03-16 |
Finals |
2025-03-21/2025-03-23 |
Grand Finals |
2025-03-28/2025-03-30 |
|
TBD, profile badge (pending) |
|
TBD |
|
TBD |
The Touhou Project Mania Cup 4th is run by various community members.
Coordinator |
[GB]Sanae, YuEast 2018 |
Consultant |
akace100, cdwcgt, EpsilonMaiagare, ERA trooperr |
Referee |
[GB]ChickenGold, [GB]GanyuAngel, [GB]Sanae, [LS]Sagirium, affirmedcheese, akace100, Dynascape, ERA trooperr, ILUVPUERTORICO, Isita, Iskas, Konohana Lucia, Logg45vs, MidRed, normanzerga, normiplier, Pilot_BFFRI, Rush_FTK, YuEast 2018 |
Streamer |
[GB]ChickenGold, affirmedcheese, Iskas, Logg45vs, MidRed, Rush_FTK, YuEast 2018 |
Commentator |
Dynascape, epic man 2, Rush_FTK |
Mappool selector |
TBA |
Mappool playtester |
11Bit, [Crz]raber, [Crz]Reimu, [GB]r3uz, [GB]Reisen, [GB]Sanae, Hidden is fun, Kiraz, Koishi Komeijie, Micleak, MidRed, Oceanus, Paturages, xc165543337, Xu seventeen, YuEast 2018 |
Mapper |
-mint-, 0DZ0, [Crz]Crysarlene, [Crz]FolAH1217, [Crz]Reimu, [GB]Azukisan, [GB]Reisen, [GB]Sanae, [GB]sherweifa, [GB]V1do, [GS]hina, AelSan, Alptraum, AutotelicBrown, Blue_Potion, Castella, cherrychou, Critical_Star, elexire, epic man 2, ERA trooperr, ExNeko, eZmmR, fvrex, :gzdongsheng, Hidden is fun, Hylotl, Hytex, ImperialTrinity, KimMui, Kiraz, Miaurichesu, Micleak, MyZterioN-, Nicknem_, PORTTAYER, RiceSS, Saemitsu, ScoliosisET, Xinhong1003, Xu seventeen, Xzzj, Ycloki, YuEast 2018 |
Statistician |
EpsilonMaiagare, Rush_FTK, YuEast 2018 |
Wiki editor |
akace100, Rush_FTK, YuEast 2018 |
Designer |
[GB]ChickenGold, lous, lovely_hyahya, Sakura006, YuEast 2018 |
The ruleset is primarily based on rulesets used in the osu!mania 4K World Cup 2024 and 4 Digit osu!mania World Cup 2024.
The Touhou Project Mania Cup 4th (THMC 4th) is a 2 versus 2 double-elimination team tournament played on the osu!mania game mode (4K variant).
If no referee is available at match time, the match will be postponed to a later time.
Players' scores will still count toward the team score, even if they fail.
Use of visual settings to alter background dim or disable beatmap elements like storyboards and skins is allowed.
If a game ends in a draw, it will be nullified and the beatmap replayed. This is called a rematch.
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 acceptable proof:
Livestream clips or VODs from the player's point of view. The entirety of the play and 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 in the multiplayer match history).
Screenshots showing the affected player's score must be taken directly from within the game.
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 determine the player's score.
All screenshots MUST be taken using the game itself; that is, they must be hosted on the https://osu.ppy.sh/
domain (using Shift
+ F12
). 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 number of players required is defined as the number needed to play a beatmap without any empty spots in the lobby (e.g., at least two participants must be present for the match to start).
In the off chance that both teams have the same amount of players (i.e., each team with 1 player present) but not enough to start the match, the match may be rescheduled to a different time. Otherwise, a win by default will be declared to the team with the highest seed.
Players are expected to keep the match running fluently and without delays. Disrupting the match by foul play, insulting and provoking other players or staff, delaying the match, and other deliberate inappropriate misbehaviour are strictly prohibited and will be punished accordingly.
The multiplayer chatrooms underlie the
osu! community rules. All chat rules apply to the multiplayer chatrooms where the matches will take place.
Referees may allow, at their discretion, lower or higher tolerances for timers.
Tournament coordinators may request liveplays or recordings of individual players or teams at any point in the tournament without prior warning.
Tournament coordinators will be responsible for receiving and investigating any tournament-related complaints.
Tournament coordinators reserve the right to modify these rules at any moment. Any such changes will be announced in advance.
Penalties for violating the tournament rules include, but are not limited to:
Specific players will be excluded for one beatmap.
Specific players will be excluded for an entire match.
The match will be declared as forfeited or as a win by default for the other team.
Disqualification from the entire tournament.
A report will be submitted to the
Tournament Committee, which will result in disqualification from the current and future official tournaments until an appeal is made.
A team must have a minimum of 2 and a maximum of 4 players.
To ensure valid registrations, every prospective player will be manually checked via
tournament screening.
All successfully formed teams will be published after the registration phase.
Tournament staff members are
not allowed to play in the tournament, with the exception of commentators, statisticians, and streamers.
All information about the tournament will ONLY be available on the
Discord server. All captains are asked to join the server in the case of any issues that may arise.
The Qualifier Stage will happen in the first week of the tournament play. All registered players who were not screened out during screening are eligible to participate in the Qualifiers.
During Qualifiers, all teams will play the Qualifier pool in sequential order up to 2 times. The pool will have 6 stages, and they are as follows:
Stage 1: Early mid-game rice technical
Stage 2: Early mid-game LN coordination
Stage 3: Mid-game LN density
Stage 4: Mid-game rice jumpstream
Stage 5: Mid late-game rice technical
Stage 6: Mid late-game hybrid
Each team must have 2 players participate in each map. They may be exchanged freely after a map has concluded.
Teams can skip any map in the second playthrough. An optional 5-minute break will be offered between the first and second playthrough of the mappool.
The following methods will be used in order for seeding, sorting through each criterion in the case of equal rank:
Lower-weighted rank sum: The following formula will be used for each map:
Map rank = RANK(Team score) * Map weight
, where:
RANK
is the function that ranks the current Team score
against all team scores for the current map.
Map weight
is the weight for the current map, as defined by the table below.
Team score
is the highest of the team total scores they get in all tries.
Then the following formula will be used to calculate Final rank = SUM(Map rank)
, where a lower Final rank
will have higher ranks.
Higher total score: An exact formula will be used:
Total score = SUM(Team score)
, where:
Higher map score: Higher team scores will receive higher ranks. Comparisons will be done from the last stage to the first stage in order until ties are broken.
Fewer total tries: Teams that play fewer maps in the Qualifier lobby will receive higher ranks.
Dice rolls: If still tied, all tied team captains will gather in a multiplayer room, using !roll
; higher results will get higher ranks. Roll again until all ties are broken.
The top 64 seeded teams will advance to the Group Stage.
The weights for the Qualifiers are as follows:
Weight |
1 |
1.01 |
1.2 |
1.21 |
1.4 |
1.41 |
Below are the win conditions and mappool format for each of the bracket stages:
Group Stage |
7 |
13 |
6 rice, 3 LN, 3 hybrid, 1 tiebreaker |
Round of 32 |
9 |
13 |
6 rice, 4 LN, 2 hybrid, 1 tiebreaker |
Round of 16 |
9 |
13 |
6 rice, 4 LN, 2 hybrid, 1 tiebreaker |
Quarterfinals |
11 |
15 |
7 rice, 4 LN, 3 hybrid, 1 tiebreaker |
Semifinals |
11 |
15 |
7 rice, 4 LN, 3 hybrid, 1 tiebreaker |
Finals |
13 |
17 |
8 rice, 5 LN, 3 hybrid, 1 tiebreaker |
Grand Finals |
13 |
17 |
8 rice, 5 LN, 3 hybrid, 1 tiebreaker |
Each round will have its own mappool, where the match format will be determined by the mappool that each stage uses.
2 RC maps, 1 LN map, and 1 of the HB maps in the Group Stage mappool will be made as classic picks; picks which have been reused from previous or other tournaments.
1 RC map and 1 LN map in the other bracket stage mappools will be made as X picks; picks that are more difficult than usual in the mappool.
The Group Stage format will be determined by the amount of teams who play in the Qualifier stage. Each group will contain a team from the top seeds (#1 – #16), high seeds (#17 – #32), mid seeds (#33 – #48) and low seeds (#49 – #64), where each group will play a mini double-elimination bracket.
If 140+ teams play in the Qualifier stage, the format will be TBD (a future announcement will be made regarding this circumstance).
If 70–140 teams play in the Qualifier stage, a split double-elimination format will be used in the Group Stage, where 64 teams will split into 16 groups. In each group, the top and high seeds will start in the upper bracket while the mid and low seeds will start in the lower bracket.
If 32–70 teams play in the Qualifier stage, the Group Stage will use a standard double-elimination format, where 32 teams split into 8 groups. All teams will start in the upper bracket.
In the Winners' Semifinals of the Group Stage, the Group Stage mappool will be used.
In the Winners' Finals, Losers' Semifinals and Losers' Finals of the Group Stage, the Round of 32 mappool will be used.
If fewer than 32 teams play in the Qualifier stage, the Group Stage will be cancelled and all teams will automatically advance into the Playoff bracket.
The 2 teams (from the upper and lower bracket) that win their Group Stage Finals will advance to the Playoffs bracket; a standard double-elimination bracket stage.
Teams that lose a match in the upper bracket move to the lower bracket; losing a match in the lower bracket will eliminate the team. This continues until the final winner is determined.
Possible mod choices for all maps are Hidden, Fade In, Flashlight, and Mirror.
Group Stage bracket
A referee will create a multiplayer room 10 minutes before the scheduled match time.
If less than 2 players from a team are present at match time, the match can be postponed for up to
10 minutes. If there are still less than 2 players from a team, a
win by default will be declared for the side with the most members present.
If both teams do not have enough players to present, there is still available staff, and the match is not influenced by other match processes, the match can be rescheduled.
If a match cannot be rescheduled, the higher-seeded team will win by default.
Each captain must use
!roll
once in the match's chatroom.
After the order is determined, the pick and ban phase will have the following steps:
The team that wins the !roll
protects a beatmap, followed by another team. They may not protect the same beatmap. Protected beatmaps may not be banned.
The team that loses the !roll
bans a map, and then the other team bans a map.
If it is during the Group Stage, the team that loses the !roll
bans the second map; after that, the winning team then bans a map.
The team that wins the !roll
picks the first map, followed by alternating picks for the remaining maps.
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, who may also choose to use the team's tactical timeout to allow them to make their 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 coordinator.
Each team will receive only one timeout of 3 minutes, to be used as extra time to pick or ban a beatmap (tactical) or if a technical issue occurs (technical).
The timeout is optional.
This timeout is automatically consumed when regular picking time runs out.
The tactical timeout may be called on a tiebreaker, provided that both teams' captains agree to it.
If players are unavailable for a rematch (e.g., technical issue or unavoidable player absence), the influenced team may replace those players while keeping the remaining players the same.
Teams need to pick an available lobby to play a Qualifier match.
Teams may request an extra lobby before January 16, 23:59 UTC.
A team that does not pick a lobby after the last lobby starts will be considered disqualified.
All bracket stages will be held between Saturday 00:00 and Sunday 23:59 (UTC).
Reschedules will only be considered if both teams agree to a time and communicate it to the coordinator before Thursday at 23:59 UTC of the week the match is to take place.
If a team needs to reschedule, the captain must submit their request in the reschedule channel at least 24 hours (48 hours recommended) before the match.
Do not ask for a reschedule unless it is absolutely needed. The coordinator reserves the right to deny any rescheduling request.
Late reschedule requests will not be accepted under any circumstances.
For emergency reschedules due to the unavailability of both teams, they may be handled on a case-by-case basis. Rescheduling approval is not guaranteed.
Captains are responsible for their team's availability.