Requested page is not yet translated to the selected language (bahasa Indonesia). Showing English version.

GB Cup 2022 Spring

GBC 2022 Spring banner

The GB Cup 2022 Spring (GBC 2022 Spring) was a 3v3 captain draft-based osu!mania 4-key tournament hosted by [GB]yobrevelc.

Tournament schedule

Event Timestamp
Registration phase 2022-03-26/2022-04-02 (23:59 UTC+8)
Drafting phase 2022-04-03 (19:30 UTC+8)
Regular stage week 1 2022-04-09/2022-04-10
Regular stage week 2 2022-04-16/2022-04-17
Regular stage week 3 2022-04-23/2022-04-24
Quarterfinals 2022-04-30/2022-05-01
Semifinals 2022-05-07/2022-05-08
Finals 2022-05-14/2022-05-15


Placing Prizes
Gold crown Profile badge, KanonBot profile badge, ¥250 CNY
Silver crown KanonBot profile badge, ¥200 CNY
Bronze crown KanonBot profile badge, ¥150 CNY
4th place ¥125 CNY
5-8th place ¥75 CNY

Teams were also awarded a ¥25 CNY bonus for each regular stage win.


The GB Cup 2022 Spring was run by the GB Team and various community members.


# Teams Members
1 金戈铁马的鲜丰水果摊 [GB]Luoxuan0327, WLYMinato, King Fish, tangul, [GB]hej_067
2 你没对象对不队 YyottaCat, [Arkona], miserable neet, Llkkm
3 涩涩不队 JJFLy, Hylotl, rizazyh, Kos-, fangruyan1013
4 Yzhhのqlll森林汪酱不会大叠 Qz501kn, [RT]Alleyne, R u m i a, qiaolilailai, QAQlingjiu
5 可爱的hyahya酱上线啦!! lovely_hyahya, -[Ulazis]-, tito31158, _Kokodayo, AkalinT
6 货拉拉拉不拉拉布拉多队 crazybrother, abbikly, Zyuuu, majesticlegend, TkskKurumi
7 bikabika Ranm, Littlesheep37, DJ Sharpnel, woshiji, UnnamedOrange
8 MyAngel Koishi Koishi-0514, [ Classic ], shiki natsume, Mito Van, Ez2dance
9 大怨种被迫当队长 My Angel Yukee7, [Crz]Yukikaze-, Rync_, Sakurada Shiro, [GB]voidmoyu
10 青叶摩卡的百合后花园 - Ran Mitake -, Molli, [GB]Foxy1459, sherweifa, Chelly-
11 啊不对不队 Vlf, - Xiaoluoli -, [GB]a_hisa, Takahashi_Yuki, Horizon5
12 啊对对队 Carpihat, -Chen-, for need, PORTTAYER, SY-COCO
13 太美丽了理塘 gluefly, EurusY, [GB]Tyris, fishbone2445, biubiutu
14 皮蛋蛋吸手手俱乐部 [Crz]Nickname, Ubiquity, MkoTenshi, Alptraum, dreamwy
15 GBC最强阵容9个Miyes Miyes, alivn, ZOM148, ChiralSS, 1atk
16 头号倒霉蛋 StarTemplar, 9961, 1145810, lochid, OTruthO


GBC 2022 Spring podium


Semifinals & Finals

Download the mappack here (130.7 MB)

Regular stage week 3 & Quarterfinals

Download the mappack here (116.38 MB)

Regular stage week 1 & 2

Download the mappack here (160.84 MB)

Match results

Play-offs summary

GBC 2022 Spring play-offs summary


Saturday, May 14, 2022:

Team A Team B Match link Note
金戈铁马的鲜丰水果摊 7 6 太美丽了理塘 #1 Finals

Sunday, May 15, 2022:

Team A Team B Match link
GBC最强阵容9个Miyes 7 3 货拉拉拉不拉拉布拉多 #1 Bronze match


Saturday, May 7, 2022:

Team A Team B Match link
货拉拉拉不拉拉布拉多 3 7 太美丽了理塘 #1

Sunday, May 8, 2022:

Team A Team B Match link
GBC最强阵容9个Miyes 3 7 金戈铁马的鲜丰水果摊 #1


Sunday, May 1, 2022:

Team A Team B Match link
大怨种被迫当队长 3 6 GBC最强阵容9个Miyes #1
太美丽了理塘 6 2 可爱的hyahya酱上线啦!! #1

Monday, May 2, 2022:

Team A Team B Match link
货拉拉拉不拉拉布拉多 6 5 涩涩不队 #1
金戈铁马的鲜丰水果摊 6 4 皮蛋蛋吸手手俱乐部 #1

Regular stage summary

#1 Team Matches Beatmaps BD2 BU3 Round 1 Round 2 Round 3
1 金戈铁马的鲜丰水果摊 3-0 18-4 +14 +1 6-1 倒霉蛋 6-2 hya酱 6-1 货拉拉
2 太美丽了理塘 3-0 18-3 +15 -3 6-1 Yzh 6-1 摩卡 6-1 大怨种
3 货拉拉拉不拉拉布拉多队 2-1 13-13 0 +3 6-4 啊不对 6-3 涩涩 1-6 水果摊
4 大怨种被迫当队长 2-1 13-13 0 +3 6-3 MK 6-4 最强阵 1-6 理塘
5 可爱的hyahya酱上线啦!! 2-1 14-9 +5 +1 6-1 啊对对 2-6 水果摊 6-2 MK
6 涩涩不队 2-1 15-11 +4 +1 6-5 吸手手 3-6 货拉拉 6-0 bika
7 皮蛋蛋吸手手俱乐部 2-1 17-12 +5 -1 5-6 涩涩 6-3 啊不对 6-3 摩卡
8 GBC最强阵容9个Miyes 2-1 16-12 +4 -3 6-2 没对象 4-6 大怨种 6-4 倒霉蛋
9 青叶摩卡的百合后花园 1-2 10-13 -3 +3 6-1 bika 1-6 理塘 3-6 吸手手
10 头号倒霉蛋 1-2 11-17 -6 +3 1-6 水果摊 6-5 啊对对 4-6 最强阵
12 啊不对不队 1-2 13-12 +1 -1 4-6 货拉拉 3-6 吸手手 6-0 没对象
11 MyAngel Koishi 1-2 11-13 -2 -1 3-6 大怨种 6-1 没对象 2-6 hya酱
13 啊对对队 1-2 12-12 0 -3 1-6 hya酱 5-6 倒霉蛋 6-0 Yzh
14 bikabika 1-2 7-17 -10 -3 1-6 摩卡 6-5 Yzh 0-6 涩涩
15 Yzhhのqlll森林汪酱不会大叠 0-3 6-18 -6 +1 1-6 理塘 5-6 bika 0-6 啊对对
16 你没对象对不队 0-3 3-18 -9 -1 2-6 最强阵 1-6 MK 0-6 啊不对

Regular stage tiebreaker

Sunday, April 24, 2022:

Team A Team B Match link
大怨种被迫当队长 18 71 货拉拉拉不拉拉布拉多队 dice roll

Regular stage week 3

Friday, April 22, 2022:

Team A Team B Match link
大怨种被迫当队长 1 6 太美丽了理塘 #1

Saturday, April 23, 2022:

Team A Team B Match link
青叶摩卡的百合后花园 3 6 皮蛋蛋吸手手俱乐部 #1
涩涩不队 6 0 bikabika #1
可爱的hyahya酱上线啦!! 6 2 MyAngel Koishi #1

Sunday, April 24, 2022:

Team A Team B Match link
Yzhhのqlll森林汪酱不会大叠 -1 0 啊对对队 win by default
GBC最强阵容9个Miyes 6 4 头号倒霉蛋 #1
啊不对不队 0 -1 你没对象对不队 win by default
金戈铁马的鲜丰水果摊 6 1 货拉拉拉不拉拉布拉多 #1

Regular stage week 2

Saturday, April 16, 2022:

Team A Team B Match link
Yzhhのqlll森林汪酱不会大叠 5 6 bikabika #1
啊对对队 5 6 头号倒霉蛋 #1
金戈铁马的鲜丰水果摊 6 2 可爱的hyahya酱上线啦!! #1
啊不对不队 3 6 皮蛋蛋吸手手俱乐部 #1

Sunday, April 17, 2022:

Team A Team B Match link
太美丽了理塘 6 1 青叶摩卡的百合后花园 #1
MyAngel Koishi 6 1 你没对象对不队 #1
货拉拉拉不拉拉布拉多 6 3 涩涩不队 #1
大怨种被迫当队长 6 4 GBC最强阵容9个Miyes #1

Regular stage week 1

Saturday, April 9, 2022:

Team A Team B Match link
bikabika 1 6 青叶摩卡的百合后花园 #1
可爱的hyahya酱上线啦!! 6 1 啊对对队 #1
金戈铁马的鲜丰水果摊 6 1 头号倒霉蛋 #1
涩涩不队 6 5 皮蛋蛋吸手手俱乐部 #1

Sunday, April 10, 2022:

Team A Team B Match link
Team MyAngel Koishi 3 6 大怨种被迫当队长 #1
货拉拉拉不拉拉布拉多队 6 4 啊不对不队 #1
Yzhhのqlll森林汪酱不会大叠 1 6 太美丽了理塘 #1, screenshot
你没对象对不队 2 6 GBC最强阵容9个Miyes #1


Tournament rules

  1. The GB Cup 2022 Spring is a captain draft-based team tournament, played on the osu!mania game mode.
    • While this competition is planned as a 3 versus 3 setup, this might change depending on the number of incoming registrations.
  2. Beatmap scoring is based on Score V2.
  3. The maps for each round will be announced by the mappool selectors on the Sunday before the actual matches take place.
    • Each mappool 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. if the scoreline is 4-4 and the match is best of 9, the tiebreaker shall be played.
  4. Match scheduling will be handled by the host.
  5. If no referee is available at match time, the match will be postponed.
  6. Failed players' scores do not get added to the team score.
    • Reviving and surviving during a beatmap is considered as passing it.
  7. Use of the Visual Settings to alter background dim or disable beatmap elements like storyboards and skins is allowed.
    • Custom skin elements must not be used to alter core gameplay mechanics.
  8. If a game ends in a draw, it will be nullified and the map will be replayed.
  9. 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.
  10. The size for a team is 5.
    • This might change depending on the amount of registrations.
  11. 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 the 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. If less than the minimum amount of required players are present at match time, it can be postponed for up to 10 minutes. If, after this period, there are still not enough players for either, a win by default will be declared for the team with the most members present.
    • The minimum amount of required players is defined as the amount of players needed to play a beatmap.
  13. Exchanging players during games is allowed without limitations, except tournament-specific rules. See the match instructions for details.
  14. 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.
  15. 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).
  16. All players and staff must be treated with respect. Instructions of the referees and the host are to be followed. Decisions labelled as final are not to be objected.
  17. Disrupting the match by foul play, insulting and provoking other players or staff, delaying the match, and other deliberate inappropriate misbehaviour are strictly prohibited.
  18. The multiplayer chatrooms underlie the osu! community rules. All chat rules apply to the multiplayer chatrooms, too.
    • Breaking the chat rules results in a silence. Silenced players cannot participate in multiplayer matches and must be exchanged for the time being.
  19. Unexpected incidences will be handled by the host. Referees may allow higher tolerance depending on the given circumstances. This is up to their discretion.
  20. 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 current and future GBC series.
    • Disqualification from current and future official and community tournaments, until appealed.
  21. The host reserves the right to modify these rules at any moment. Any such changes will be announced in advance.

Tournament registration

  1. Please send the host a private message and fill this form to register.
  2. To ensure valid and serious registrations, every registered user will be manually checked by the host.
    • To be successfully registered, a player must not have violated the osu! community rules within the last 12 months.
    • There are no rank limitations for this tournament. If there are too many registrants, some of the high-level registrants may be removed from the main tournament and be invited to participate in the showmatch instead.
  3. A list of all successfully registered players will be published after the registration phase, and will then participate in the drafting phase.
  4. Organisers, mappool selectors, and referees must not participate as players in the tournament.
  5. Organisers reserve the right to decline restricted players from participating in the tournament.

Drafting phase instructions

  1. The host will declare one captain for each team 24 hours before the drafting phase.
    • Drafting order will also be declared by the host.
    • Captains are selected by performance and preference.
    • Non-captains will join a group of players waiting to join a team, herein called a "player pool".
  2. Captains decide their team members during the drafting phase.
    • Captains are allowed to conduct and coordinate "tryouts", tests to gauge player aptitude, on their own terms.
  3. There will be a 120-second planning phase before the picking phase starts.
  4. During the picking phase, picks start in increasing order, from the 1st to the 16th captain. The picks repeat four times, such that every captain gets to choose 4 players.
  5. Each captain has 60 seconds to pick one player from the player pool on their turn.
    • If the captain does not pick an player within 60 seconds, a random player from the remaining player pool will be assigned to their team.
  6. If the captain picks a player, the pick time still has to elapse before the next captain's turn starts, meaning each phase will take 16 minutes.
  7. After each phase, there is a 60-second break before the next phase starts.
  8. At all times, the captains may communicate with each other via multiplayer chatrooms or voice chat.
    • Other players will be muted during the drafting phase.
  9. After the drafting phase, captains may choose, with the approval of the host, to delegate their role to other prospective team members.
  10. Bad behaviour during the drafting phase will be seen as disrupting the match by foul play.

Regular stage instructions

  1. Following the drafting phase, a 3-round Swiss stage will be played. This means teams with same record will face each other.
  2. The final ranking of the Swiss round will be determined by the following criteria in order:
    • Most matches won
    • Head-to-head result (if possible)
    • Highest Buchholz score
    • Highest beatmap difference (beatmap wins - beatmap losses)
    • Most beatmaps won
    • Fewest beatmaps lost
    • Dice roll
  3. The top 8 teams will advanced to the Playoff stage, while the remaining players get eliminated from the tournament.
    • This means that teams with a record of 2-X or better will advance to the next stage.
    • All teams will finish all 3 rounds, even when they have a record of 0-2.
  4. In the Regular stage, all teams will play in the same mappool.
  5. The results from the Regular stage will also be used for seeding teams.

Playoff stage instructions

  1. Following the Regular stage, a single elimination stage will be played. This means that the winner continues with their runs, and the losing team will be eliminated from the tournament, except in the bronze match.

Win conditions

  • In the Regular stage and Quarterfinals, teams need to win 6 maps to win a match (best of 11).
  • In Semifinals and Finals, teams need to win 7 maps to win a match (best of 13).

Match instructions

  1. A referee will create a multiplayer room 15 minutes in advance. Players must gather during this period.
    • Room settings are osu!mania, Team VS, Win Condition: Score v2. Room name must be GBC2 Spr: ({TeamRed}) vs ({TeamBlue}).
    • The team mentioned first in the room name must be the red team, and the team mentioned second in the room name must be the blue team.
  2. Each captain can ban one beatmap from the pool. These beatmaps cannot be picked by any team during the entire match.
  3. Beatmap selection will alternate between each captain selecting a beatmap out of the mappool.
  4. Each captain must use !roll once in #multiplayer.
    • The winner of the !roll starts picking the first beatmap of the match.
    • The loser of the !roll starts banning one beatmap, followed by the winner of the !roll to ban a beatmap.
  5. After each pick, the captain may ban one player of the opposing team from playing that beatmap in the match, except in a tiebreaker.
    • Any player can only be banned like this once per match.
    • Banning players is optional.
  6. Teams will have 2 minutes to pick or ban a beatmap, 1 minutes to ban an opposing player, 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 bans of opposing players, the captain forfeits the ban.
      • For map bans, the captain forfeits the ban.
      • For map picks, a random map will be chosen using the !roll command from the remaining mappool, excluding the tiebreaker map.
      • 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 host.
    • Each team will receive one "tactical timeout" of two minutes, to be used as extra time to pick or ban a beatmap. The tactical timeout is optional.
  7. The referee reserves the right to modify these rules or decide if a team has violated these rules in matches they are responsible for, if absolutely necessary.

Mappool instructions

  1. There will be three separate mappools.
    • Regular stage Round 1 and Round 2 use mappool #1.
    • Regular stage Round 3 and Quarterfinals use mappool #2.
    • Semifinals and Finals use mappool #3.
  2. Each mappool consists of a fixed amount of maps each stage which will all be played under FreeMod conditions. This means that there is a unique FreeMod bracket.
  3. Mappools #1 & #2 contain 13 beatmaps, and mappool #3 contains 15 beatmaps.
  4. Each mappool has one tiebreaker.
  5. Possible mod choices for all maps are Hidden, FadeIn, Flashlight, and Mirror.
  6. The tiebreaker will be played under FreeMod conditions.

Scheduling instructions

  1. Each stage will be held on a single weekend.
  2. All matches will be held on either a Saturday or Sunday (UTC+8).
    • Rescheduling a match to a weekday is only permitted if both teams request and agree to it.
  3. Scheduling will be handled by the host, and will be released on the Sunday before the first match of the stage. The host will try to create a schedule that respects all participants' preferences.
    • Please inform the host before Sunday if you expect a specific time slot to be unavailable in the following week. The host will try to accommodate all wishes, but makes no promises.
  4. Reschedules will only be considered if both teams agree to a time. This needs to be done and notified to the tournament staff before Wednesday (23:59 UTC) of that particular week when your match takes place.
  5. Reschedules may only be requested by a team captain.
    • Do not ask for reschedule unless it is absolutely needed. The host reserves the right to decline any reschedule requests.
  6. Captains are responsible for their teams' availability. The current team size exists to ensure every team can provide at least three players for each match. If teams cannot provide three players for a match, the match will be considered forfeited.


  1. Seed: the top 8 advance to the next round. 

  2. Beatmap difference. 

  3. Buchholz score.