Counter-Strike has a long tradition of community tournaments, and Counter-Strike 2 keeps most of that structure. The competitive conventions are well established, which helps, because players arrive expecting them. This guide covers the decisions an organiser needs to make for a CS2 event: match settings, map vetoes, format, servers and rules.
Match settings
Publish your match settings explicitly, even if you think everyone knows them. The most common competitive setup in CS2 is:
- MR12: 24 regulation rounds, 12 per half. The first team to 13 wins.
- Overtime: if the score reaches 12–12, overtime is played in sets of six rounds (three per side) with money reset for overtime. The first team to win four rounds of an overtime set wins the map; if a set ends 3–3, another set is played.
- Knife round or coin flip for starting side on a decider map, as stated in your rules.
If your time window is tight, you can shorten overtime rules, but state the exact alternative in advance. Never change settings once the event has started.
Choosing a format
A CS2 map typically lasts 40 to 60 minutes including overtime, so formats need to be planned around rounds carefully. Our tournament maths guide shows how to estimate total length.
- Small field, one evening: 8 teams, single elimination, best-of-one with a best-of-three final.
- 16 teams, one day: single elimination with best-of-three semi-finals and final.
- Large field, weekend: a Swiss stage to cut to 8 teams, then single elimination playoffs.
The Major-style Swiss stage
Valve’s Majors popularised a 16-team Swiss stage in which teams play until they reach three wins (advance) or three losses (eliminated). Matches that decide advancement or elimination are commonly best-of-three, while other rounds are best-of-one. It is an excellent format for community events with 16 teams and a full day or two: everyone gets at least three matches, every match has stakes, and the stage produces exactly eight playoff teams. Our Swiss system guide explains the pairings and the Buchholz tiebreak.
Map veto
Use the current Active Duty map pool of seven maps.
Best-of-one
Teams alternate bans until one map remains: six bans, higher seed first. The team that did not make the final ban chooses its starting side, or the teams play a knife round, according to your rules.
Best-of-three
- Team A bans.
- Team B bans.
- Team A picks map one; Team B chooses its starting side.
- Team B picks map two; Team A chooses its starting side.
- Team A bans.
- Team B bans.
- The remaining map is the decider, with a knife round for side.
Team A is the higher seed. In a Swiss stage, it is usually the team with the higher seed or better tiebreak going into that round.
Servers
You have three realistic options:
- Rented or community dedicated servers with a match plugin that loads your config, handles warmup, pauses and knife rounds, and records demos. This is the most reliable option if you can arrange it.
- A third-party match platform that creates servers on demand. Convenient, but check their region coverage and any fees.
- Player-hosted lobbies for casual events. Cheapest, but least consistent and hardest to police.
Whichever you use, test your match configuration before the event with a full practice map, including a pause, an overtime and a demo recording.
Check-in and match flow
- Open check-in 45 to 60 minutes before the first match. Remove teams that do not check in, then regenerate and share the bracket.
- Post connection details for each match in a private channel or thread for the two teams and the admin.
- Run the veto in writing (a Discord thread is fine) so there is a record.
- After the match, the winning captain posts the score and a scoreboard screenshot; the losing captain confirms.
- Admins update the bracket; the shared link updates automatically.
Rules to publish
- Roster: five players and up to two substitutes, registered by a lock time. Substitutions between maps only.
- Late teams: a grace period (for example 10 minutes), after which the missing team forfeits the first map, then the match.
- Technical pauses: allowed at any time, announced in chat, with a total limit per map. Tactical timeouts as per game settings.
- Disconnects: the match pauses at the end of the current round or immediately if a technical pause is called; a registered substitute may replace a player who cannot return.
- Round restarts: only if a disconnect happens before any damage is dealt in the round, and only by admin decision.
- Exploits and bugs: known exploits, such as pixel-walking positions that the organiser lists, are banned. Admins may award rounds or replay them.
- Anti-cheat: state the minimum requirement (for example, VAC-secured servers plus demo review) and the penalty for cheating.
- Demos: recorded for every match and kept for at least a week after the event, for dispute resolution.
Tiebreakers
For group or Swiss stages, publish the tiebreak order. A common CS2 order is: match record, head-to-head, Buchholz (for Swiss), round difference, rounds won, and a deciding map. Round difference is particularly useful in CS2 because it reflects how convincing wins were. See tiebreakers explained for how to handle three-way ties.
Sample day: 16 teams, Swiss into playoffs
| Time | Stage |
|---|---|
| 10:00 | Check-in closes, Swiss round one (BO1) |
| 11:00 | Swiss round two (BO1) |
| 12:00 | Swiss round three (BO1 for 2–0 and 0–2 matches; BO1 for 1–1) |
| 13:00 | Break |
| 13:30 | Swiss round four (BO3 for advancement and elimination matches) |
| 16:00 | Swiss round five (BO3, 2–2 teams) |
| Day 2 | 8-team single elimination playoffs, BO3 |
After the event
Share the final bracket image and standings. Keep the demos and the veto records until any disputes are settled. Then note what ran long for next time.
To set up your bracket, open the Swiss generator for the group stage and the single elimination generator for playoffs, and choose “Counter-Strike 2” in the Customize panel.