Requested page is not yet translated to the selected language (português brasileiro). Showing English version.
The Yuyuko's Hidden Cup Season 3 (YHC S3) was a team-based 4v4 double-elimination osu! tournament hosted by SIyuyuko. It was the 3rd instalment of the Yuyuko's Hidden Cup.
Registration phase |
2023-06-01/2023-06-15 |
Drawings |
2023-06-16 (20:00 UTC+8) |
Elimination stage 1 |
2023-06-16/2023-06-25 |
Elimination stage 2 |
2023-06-26/2023-07-09 |
Elimination stage 3 |
2023-07-10/2023-07-29 |
|
USD 4.8 per player, an unofficial badge |
|
USD 3.4 per player |
|
USD 2 per player |
the most valuable person of the tournament (MVP) |
1 month of osu!supporter |
the coach of winner team |
1 month of osu!supporter |
the MVP of the tournament (under 3200 pp) |
1 month of osu!supporter |
YHCS3 badge
The Yuyuko's Hidden Cup Season 3 was run by various community members.
Manager |
SIyuyuko |
Mappool selector |
SIyuyuko, Muziyami |
Mappool playtester |
SIyuyuko, Muziyami |
Showcaser |
Hakumo Shiro, Hakumo Ai, VialVistas, Sayori_yui, Senbe1, carrywind |
Streamer |
SIyuyuko, Muziyami |
Commentator |
SIyuyuko, Muziyami |
Designer |
Muziyami |
Referee |
SIyuyuko, Muziyami |
Statistician |
Muziyami |
A |
null |
Arca Lunar, mura sama, Pcioafk, yukko233, wjs255, qimengxunkong, Endless fare |
B |
我倒杯水 |
n0000000000o, yukishize, cd20200816, EYii, FiresunX, Aokreti, akuya |
C |
6A级景点 |
FlyingYellow, goyhan, Avogadoll, -aLIEz-, YamadaJ, ArleneRain_, [Alex] |
D |
鲭西何时无缘进路 |
innnnovation, Natsukaze, Refu3, eric1388, TomCh, ElectroTD, Kallen0401 |
E |
天使纷扰 |
7R1N1TY, SouJuku, Asp1er, zhuiyi_crane, MizukiQwQ, Fungus OVO, Lfruin |
F |
遇到HD睡大觉 |
fate80016, rtconsuming, MAPSILL, FeD4kTo, SansX, iz6, Dawintch |
G |
笔不飞 不会打 |
Kieost, sion22, Zxian, xxbg, chana, Lemen, K_vAE |
H |
孤儿收容所 |
Niumaokun, Alymetic, LingYuanOvO, 1224192602, lizhanyiawa, CyberBunnyGirl, magic__sunny |
YHCS3 bracket
This competition has come to an end and resulted in the following podium:
Download the mappack here! (167.2 MB)
Download the mappack here! (99.6 MB)
Download the mappack here! (94.6 MB)
鲭西何时无缘进路 |
7 |
0 |
天使纷扰 |
#1 |
我倒杯水 |
2 |
7 |
天使纷扰 |
#1 |
孤儿收容所 |
4 |
7 |
天使纷扰 |
#1 |
鲭西何时无缘进路 |
7 |
0 |
我倒杯水 |
#1 |
天使纷扰 |
6 |
3 |
笔不飞 不会打 |
#1 |
遇到HD睡大觉 |
3 |
6 |
孤儿收容所 |
#1 |
笔不飞 不会打 |
6 |
5 |
null |
#1 |
6A级景点 |
2 |
6 |
孤儿收容所 |
#1 |
我倒杯水 |
6 |
5 |
遇到HD睡大觉 |
#1 |
天使纷扰 |
-1 |
0 |
鲭西何时无缘进路 |
win by default |
遇到HD睡大觉 |
5 |
0 |
null |
#1 |
我倒杯水 |
5 |
1 |
笔不飞 不会打 |
#1 |
孤儿收容所 |
4 |
5 |
鲭西何时无缘进路 |
#1 |
6A级景点 |
1 |
5 |
天使纷扰 |
#1 |
The Yuyuko's Hidden Cup Season 3 is a entertainment-oriented double elimination 4v4 team tournament, played on the osu! game mode.
Beatmap scoring is based on ScoreV2.
Based on the number of registration, the size for a team is 7 players.
The beatmap list for each next round will be announced by the mappool selectors on the official live stream, on the weekend (Friday 12:00 UTC+8 - Monday 23:00 UTC+8) after the matches take place.
The default match schedules for each round will be announced by the tournament managers in the information (main) sheet, on Sunday before the last matches take place. The captain may have a discussion with the opponent and confirm the match time before Saturday 00:00 on the same week.
Use of the Visual Settings panel to alter background dim or disable beatmap elements like storyboards and skins is 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.
Replacing 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, at their discretion, veto this request.
"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 abide by 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 reserve the right to modify these rules at any moment. Any such changes will be announced in advance.
A player who meets the registration conditions can register through the
Registration Form. Registration will close on 2023-06-16.
If a player registered successfully, a cost will be calculated and will affect the team-up stage.
Each team will have 7 players (including the captain).
The sum of player cost should be 6.7 - 7.3 (including boundary values).
Please try to keep the cost within a reasonable threshold. If out of limit, staff will take action.
If a team formed successfully, the captain could send the team name and team flag to the staff.
The staff will intervene and complete the team formation task of the players who fail to form a team before the group match pool showcase.
In general, the player with the highest cost in the team should hold the position of captain. If other players in the team want to be the captain, they need to obtain the consent of the captain to be replaced and the staff.
The captain shall be responsible for his team. If a captain neglects his duty, the staff may impose punishment and notify other domestic staff of relevant tournaments.
During all the matches, 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.
No team will be eliminated in the eliminating stage 1, the result of the group stage will only affect the position of the team in the eliminating stage 2/3.
In the Elimination Stage 1, teams need to win 5 maps to win a match (best of 9).
In the Elimination Stage 2, teams need to win 6 maps to win a match (best of 11).
In the Elimination Stage 3, teams need to win 7 maps to win a match (best of 13).
Note: different from the OWC tournament rules, for the Grand Finals match, the team coming from the losers' bracket, the same as the last one of the winners' bracket team, just needs to win 1 match.
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!"
, Team mode: "Team Vs"
and Score mode: "ScoreV2"
. The room name must follow the pattern of YHCS3: ({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 team may ban one beatmap to be selected from the pool In all stages of the tournament. These beatmaps may not be picked by any team for the entire duration of the match.
Each captain must use
!roll
once in the match's chatroom.
The winner of the !roll
, the team captain would decide if their team picks first or bans first.
Teams may "double pick" (i.e. pick two or more maps from the same mod pool in sequence) without limitations.
The loser of the !roll
's ban/pick depends on the winner of the !roll
.
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:
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.
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.
Every stage will have its own mappool.
The mappool sizes are as follows:
Elimination Stage 1 and Elimination Stage 2: 14 beatmaps: 6 HD, 2 NM, 2 DT, 3 FM, 1 TB
Elimination Stage 3: 16 beatmaps: 7 HD, 2 NM, 3 DT, 3 FM, 1 TB
The Hidden and Double Time brackets will be played with the respective mods enabled for all players.
The No Fail mod will be enforced on every beatmap.
The FreeMod bracket will have "Free Mods" enabled, that is, players will be able to select what mods they use.
Possible mod choices are Hidden, Hard Rock, and Hidden + Hard Rock.
When playing a FreeMod beatmap, there must be 1 player with Hidden ONLY and at least 3 players with a Mod. For the remaining player, enabling mods is optional.
The tiebreaker will be played under FreeMod conditions, but the mod requirement is not enforced.
Each stage will be held on a single or double weekend.
All bracket stages will be held between Wednesday 00:00 UTC+8 and Sunday 22:00 UTC+8.
Match scheduling will be handled by the tournament managers. Schedules will be released on the Sunday after the last matches of the stage. The tournament managers will try to create the schedule to respect the participants' time zones and time favors.
Reschedules will only be considered if both teams agree to a time and communicate it to the tournament managers, before Friday 23:59 UTC+8 of the week the match is to take place on.
Matches may not be scheduled to any time beyond Sunday, 22:00 UTC+8 of the week they are to be played at.
Do not ask for a reschedule unless it is absolutely needed. The tournament managers reserve the right to deny any rescheduling request.
Late reschedule requests will not be accepted under any circumstances.
Captains and coaches are responsible for their team's availability.