Captain’s Handbook

This guide provides comprehensive information for team captains participating in the MAP Tournament. As a captain, you are responsible for team management, match coordination, and maintaining communication with tournament staff. All tournament matches take place between Friday 23:59 UTC and Monday 23:59 UTC on their designated weekends. For a complete overview of the tournament, see the Tournament Overview.

Table of Contents

Quick Reference

Bookmark these important resources:

Support Resources

Getting Help

  1. Support Tickets
    • Create in #open-ticket channel
    • Provide detailed information
    • Keep all communication in ticket
  2. General Help
    • Use #questions-suggestions
    • Check pinned messages
    • Be patient for responses
  3. Direct Staff Contact
    • Check Staff List for department heads
    • Contact RaiRei for general inquiries
    • Tag @Referee in #general for urgent match issues
  4. Emergency Protocol

    For urgent match-day issues, follow this order:

    1. Contact assigned referee
    2. If unavailable, ping @Referee in #general
    3. For serious issues, contact:

Core Responsibilities

Primary Duties

Responsibility Details
Communication Team coordination and Discord presence
Scheduling Arranging match times and confirming with staff
Roster Managing team lineup and substitutions
Contact Primary point of contact for tournament staff

Team Management

Team Requirements

Teams must maintain these requirements throughout the tournament. For complete registration requirements, see the Registration page.

  • Team Size: 4-8 players total
  • Match Participation: Minimum 4 players per map
  • Player Requirements:
    • Rank between 75,000 and 999,999
    • Active Discord participation
    • No restricted accounts

Team Documentation

Using the RussianVaxei Team Sheet

  1. Initial Setup

Copying the RussianVaxei sheet

  1. Sheet Configuration
    • Add the names of your team members (1) onto the settings page
    • Insert the links to the tournament mainsheet (2)
    • After that, once the mappool is publicly available:
      • Open the mainsheet and copy the exact name of the mappool tab into the sheet (3)
      • Insert the value of the first and last row of maps (4) as seen on the mappool sheet

RussianVaxei sheet configuration sections

  1. Managing Team Availability
    • Organizing a schedule through this sheet is possible and required during scheduling conflicts
    • Use the availability tab to visualize when your team members can play
    • This helps coordinate team schedules and resolve conflicts

RussianVaxei sheet availability setup

Team sheets are required documentation. In scheduling conflicts, staff will request your team’s availability sheet.

  1. Using the Sheet
    • Input player scores and map preferences
    • Organize team lineups
    • Take map notes
    • Track team availability
    • Use for scheduling conflict resolution

Match Format

Tournament Structure

The tournament uses a double elimination bracket structure. For complete format details, see the Tournament Format page. The pick/ban sequence and rules for all match types are illustrated below:

Pick/Ban Format

  • Teams need two losses to be eliminated
  • One loss moves a team to the losers’ bracket
  • Teams in losers’ bracket must win to continue
  • Teams in losers’ bracket must play two matches per week after Round of 16
  • Grand Finals features winners’ bracket champion vs losers’ bracket champion

Stage Requirements

Stage SR Protects Bans Best of NM HD HR DT FM TB Async Available*
Qualifiers ★5.30 NA NA NA 4 2 2 2 0 0 NA
Round of 32 ★4.90 1 2 9 4 2 2 2 2 1 Yes
Round of 16 ★5.10 1 2 9 5 2 2 2 2 1 Yes
Quarterfinals ★5.30 1 2 11 5 3 3 3 3 1 LB*
Semifinals ★5.50 1 2 11 6 3 3 3 3 1 No
Finals ★5.70 1 3 13 6 3 3 4 3 1 No
Grand Finals ★5.90 1 3 13 6 3 3 4 3 1 No

*LB = Losers Bracket only

Prize Structure

Tournament Prizes

Make sure your team knows what they’re competing for. For complete prize information and bounty rules, see the Prizes page.

Placement Reward
1st Place • 6 months osu!supporter per player
• Custom Profile Banner
2nd Place • 4 months osu!supporter per player
• Custom Profile Banner
3rd Place • 2 months osu!supporter per player
• Custom Profile Banner
4th Place • 1 month osu!supporter per player

Mapper’s Choice Bounty System

Each round features additional prize opportunities through the “Mapper’s Favourite” bounty system. For complete bounty rules and prize information, see the Prizes page.

Overview

  • Special map selected by mapping board each round
  • Two winners per round receive 1 month supporter
  • Total prize pool distribution:
    • Round of 32: 2 winners × 1 month
    • Round of 16: 2 winners × 1 month
    • Quarter Finals: 2 winners × 1 month
    • Semi Finals: 2 winners × 1 month
    • Finals: 2 winners × 1 month
    • Grand Finals: 2 winners × 1 month
  • Total bounty prize pool: 14 months supporter across tournament

How to Participate

  1. Map Selection
    • Mapper’s Favourite announced in mappool showcase
    • Required score threshold specified
    • Teams must meet or exceed threshold to qualify
  2. Attempt Rules
    • Attempts during official matches only
    • Can attempt after match winner decided (same lobby)
    • One attempt per team per bounty map
    • Maximum 4 players per attempt
    • All participating players attempt simultaneously
    • For multiple match opportunities, only first attempt counts
  3. Prize Distribution
    • Raffles during next round’s mappool showcase
    • Two winners randomly selected from qualifying attempts
    • Players can only win one bounty per round
    • Does not affect tournament placement prizes

Match Coordination

Match Scheduling

All scheduling must be done in #scheduling channel using the proper format.

Basic Requirements

  • All times in UTC
  • Between Friday 23:59 UTC and Monday 23:59 UTC
  • Both teams must confirm
  • Wait for referee confirmation

Scheduling Format Examples

Teams must provide:

  • Match ID
  • Time (in UTC)
  • Warmup Gimmick participation
  • Confirmation from both teams
  • Warmup maps (if participating in gimmick)
Example 1: Standard Reschedule (No Warmup Gimmick)

Format:

Match ID: 69
Time: 15:30utc sunday
Warmup Gimmick: No

Example of scheduling without warmup gimmick

Notice in this example:

  • Clear match identification
  • Time specified in UTC
  • Explicit mention of not using warmup gimmick
  • Confirmation from opponent included
  • Referee acknowledgment
Example 2: Default Time with Warmup Gimmick

Format:

Match ID: 69
Time: Default (12utc)
Warmup Gimmick: Yes
Our team: https://osu.ppy.sh/beatmapsets/406217#osu/882812
Their Team: https://osu.ppy.sh/beatmapsets/914754#osu/1910547

Example of scheduling with warmup gimmick

In this example:

  • Using default match time
  • Both teams participating in warmup gimmick
  • Warmup maps provided by both teams
  • Confirmation from opponent included
  • Referee acknowledgment
  • Mapping board member confirmation

Qualifier Match Scheduling

Check “Qualifiers Lobbies” tab on main sheet for available slots:

Team Name: [your team]
Lobby ID: [desired lobby]

For custom qualifier times:

Team Name: [your team]
EX_[number]: [UTC time]

Async Match Procedures

Available only as last resort for:

  • Round of 32 (all matches)
  • Round of 16 (all matches)
  • Quarter Finals (Losers’ Bracket only)

To request:

  1. Show scheduling attempt evidence
  2. Contact Internal Affairs (@RaiRei)
  3. Receive explicit approval
  4. Complete pick/ban by Friday 23:59 UTC

Discord Channel Setup

Three private channels will be created. For complete async match procedures, see the Async Matches page.

  • Pick/Ban Channel (async-pickban-team1-team2): Both captains + staff
  • Team 1 Channel (async-team1): Team 1 + staff
  • Team 2 Channel (async-team2): Team 2 + staff

Match Privacy Rules

  • Teams play independently
  • Match timing kept private
  • Scores remain secret
  • Results announced only after both matches
  • No inter-team communication until results posted

Match Procedures

Pre-Match Requirements

Time Action
15 minutes before Be available for referee contact
5 minutes before Join match lobby
Until start Invite team members

Late Penalties

Time Late Penalty
2 minutes Forfeit warmup
5 minutes Forfeit protect/bans
10 minutes Match forfeit

Match Flow Responsibilities

  1. Preparation Phase
    • Submit protect/ban decisions
    • Manage team picks
    • Can override team member picks before map set
  2. During Match
    • Ensure correct mod combinations
    • Manage timeouts (one 120-second timeout per match)
    • Handle technical issues
    • Coordinate player substitutions if needed

Here’s the revised section that clarifies the specific mod combinations for FreeMod maps, incorporating your requested adjustments:

Freemod Rules

Teams must follow these specific mod combinations for FreeMod maps:

Position Requirement
Player 1 True Freemod: Any mod combination (e.g., NM, HD, HR, HDHR)
Player 2 Hidden mod required
Player 3 HardRock mod required
Player 4 Must use either:
  • A difficulty-increasing mod/combination, or
  • EZ mod/combination (1.8x base score multiplier)

Additional Notes

  • Difficulty-increasing mods may include Hidden, HardRock, DoubleTime, Flashlight, Easy, or any combination.
  • The EZ mod applies a 1.8x base score multiplier to balance its difficulty.

Pick/Ban Process

Initial Phase

  1. Captains use !roll when prompted
  2. Highest roll winner will:
    • Protect second
    • Ban second
    • Pick first
  3. Equal rolls: Repeat until winner determined

Protection and Pick Order

  1. Roll loser protects first map
  2. Roll winner protects their map
  3. Roll loser bans their map
  4. Roll winner bans their map
  5. Teams alternate picks, starting with roll winner

Pick Rules

  • Double picks (selecting two maps from the same mod pool consecutively) are allowed
  • Triple picks (selecting three maps from the same mod pool consecutively) are not allowed

Ban Phases

  • Second Ban Phase:
    • Occurs after first 4 maps
    • Leading team bans first
    • If tied (2-2), winner of 4th map bans first
    • Each team bans 1 map

Finals Special Rules

  • Third ban phase after next 4 maps
  • Same ban order rules apply
  • Each team bans 1 additional map

Tiebreaker

If both teams are one point from winning, designated Tiebreaker (TB) map is played.

Warmup Gimmick Management

Optional feature that can earn your team a free point.

Requirements

  • Advance notice in scheduling
  • Both teams must agree to participate
  • Exactly 4 players must participate
  • Map must not be previously seen by mapping board
  • Map must thoroughly impress mapping board member

Scheduling Requirements

When participating in warmup gimmick:

  • Include warmup map links in schedule post
  • Wait for mapping board member confirmation
  • Both teams must agree to participate
  • Exactly 4 players required

Warmup gimmick requests without proper format or missing information will be ignored.

Issue Resolution

Technical Support

Score Verification

Acceptable proof of score includes:

  1. Official Stream Footage
    • Last visible score will be used
  2. Player POV Recording
    • Must show entire play including results screen
    • E.g., Twitch stream VOD
  3. Screenshots
    • Must use osu!’s screenshot function (Shift + F12)
    • Must be hosted on osu.ppy.sh
  4. Phone Recording
    • Must show the play/score
    • Must show current date/time (via alt-tab or Windows key + D)

Staff reserve the right to reject any proof deemed illegitimate.

During Maps

  • First 30 seconds: Can request referee abort
    • Same players must replay
    • Substitutions allowed only for connection issues
  • After 30 seconds: Player gets 0 score
    • Unless acceptable proof provided
    • 30-second rule flexible based on referee discretion

Abort Rules

  • One abort allowed per team per match
  • Additional disconnections won’t trigger aborts

Fair Play Guidelines

The following are considered unfair:

  • Misrepresenting team availability
  • Pressuring teams into disadvantageous times
  • Using forfeit threats
  • Making unreasonable demands
  • Showing unwillingness to compromise

Reporting Issues

  1. Create Support Ticket
    • Use #open-ticket channel
    • Provide evidence (screenshots, logs)
    • Include clear description
  2. Direct Contact
    • Find appropriate staff member
    • Contact Internal Affairs for general issues

Consequences

Teams found violating fair play guidelines may face:

  • Forfeiture
  • Tournament disqualification
  • Ban from future tournaments