Skip to content

Map Selection

If your match is configured to include a veto-phase (setting skip_veto to false), each team's captain will ban or pick maps from your configured map pool.

Team Captains

Get5 will give map pick/ban and side choices to a player on each team. The player it gives it to will be the first player listed in the players section of a match configuration, or a random player on the away-team when in scrim mode. Except for the team captains, players can only talk in team chat during map selection. This is to reduce clutter, as a lot of text is already printed during this phase.

Side Selection

When a team picks a map, the other team gets to choose the side to start on for that map. If a map is selected by default by being the last map standing, a knife round is used. This behavior is determined by the side_type parameter of your match configuration. Sides may also be predetermined using the map_sides parameter.

Default Flow

If you don't provide a custom veto_mode, Get5 will create a suitable map selection flow depending on your series length (num_maps) and map list (maplist). In all cases, the map list must be at least one larger than the number of maps to play. If not, the veto system is automatically disabled, and the maps are played in the order they appear in the map list.

Legend

To make the table easier to read, we'll use icons instead of strings to illustrate.

1⃣ ✅ team1_pick

2⃣ ✅ team2_pick

1⃣ ⛔ team1_ban

2⃣ ⛔ team2_ban

🇽 ✅ played by default

Note that these examples assume that veto_first is set to team1, which starts by default. You can invert or randomize the default flow by setting veto_first to team2 or random, respectively.

Teams alternate banning maps until only one map remains.

5 is used as at the map pool size example here, but the flow is identical for any pool size.

Map Pool Size Flow
5 1⃣ ⛔ 2⃣ ⛔ 1⃣ ⛔ 2⃣ ⛔ 🇽 ✅

When less than 5 maps are in the pool, each team simply picks one map. At 5 or more maps, each team bans one map and then picks one map, regardless of map pool size.

Map Pool Size Flow
3-4 1⃣ ✅ 2⃣ ✅
5+ 1⃣ ⛔ 2⃣ ⛔ 1⃣ ✅ 2⃣ ✅

If the map pool size is at least 2 larger than the number of maps to play (num_maps), teams alternate banning until there are num_maps + 2 (i.e. 5) maps left, at which point teams alternate picking num_maps - 1 (i.e. 2), then alternate banning until only one map remains. The remaining map is played last by default.

If the map pool is only 1 larger than the number of maps to play (num_maps), teams simply alternate picking until all maps are decided. The remaining map is ignored.

Map Pool Size Maps Flow
4 3 1⃣ ✅ 2⃣ ✅ 1⃣ ✅
5 3 1⃣ ✅ 2⃣ ✅ 1⃣ ⛔ 2⃣ ⛔ 🇽 ✅
6 3 1⃣ ⛔ 2⃣ ✅ 1⃣ ✅ 2⃣ ⛔ 1⃣ ⛔ 🇽 ✅
7 3 1⃣ ⛔ 2⃣ ⛔ 1⃣ ✅ 2⃣ ✅ 1⃣ ⛔ 2⃣ ⛔ 🇽 ✅
8 3 1⃣ ⛔ 2⃣ ⛔ 1⃣ ⛔ 2⃣ ✅ 1⃣ ✅ 2⃣ ⛔ 1⃣ ⛔ 🇽 ✅
5 4 1⃣ ✅ 2⃣ ✅ 1⃣ ✅ 2⃣ ✅
6 4 1⃣ ✅ 2⃣ ✅ 1⃣ ⛔ 2⃣ ⛔ 1⃣ ✅ 🇽 ✅
7 4 1⃣ ⛔ 2⃣ ⛔ 1⃣ ✅ 2⃣ ✅ 1⃣ ✅ 1⃣ ⛔ 🇽 ✅
8 4 1⃣ ⛔ 2⃣ ⛔ 1⃣ ✅ 2⃣ ✅ 1⃣ ✅ 1⃣ ⛔ 2⃣ ⛔ 🇽 ✅

Life ain't fair

When the the numbers don't add up, one team may ban or pick one more time than the other. This is simply a best-effort by Get5 to make any combination work without producing errors. It's up to you to provide reasonable combinations of maps to play and map pool sizes.

Custom Flow

You may provide a custom ban/pick order using the veto_mode property of a match configuration. If you do this, any logically possible combination of picks/bans, number of maps to play (num_maps) and map pool size (maplist) is allowed.

The veto_mode parameter accepts an array of strings:

team1_pick, team1_ban, team2_pick and team2_ban.

When using a custom veto flow, veto_first is ignored.

Rules

Your array of picks and bans must comply with these rules, or your match configuration will fail to load:

  1. If your series consists of more than one map, the number of picks must be no less than the number of maps to play minus one. This ensures there is no ambiguity in the order of maps, even if the number of maps remaining after bans is correct. I.e. in a Bo3, you must have at least 2 picks.
  2. If you provide more options (picks or bans) than required, extra options are ignored. I.e. with a map pool of 7, only the first 6 options would be evaluated and used.
  3. If you provide more picks than required, extra options are ignored. I.e. with a map pool of 7 and 6 picks in a Bo3, only the first 3 picks would be evaluated and used.
  4. Which team you assign to pick or ban does not matter. If you wanted, you could have one team pick all the maps.
  5. Either:
    1. If the number of picks is less than the series length, you must provide at least "map pool size minus 1" number of options, i.e. no less than 6 options for a pool of 7 maps.
    2. If the number of picks is equal to (or per rule 3, exceed) the series length, the picks can be positioned before the map pool has been exhausted, and the total number of options can be less than the "map pool size minus 1".