- Event
-
Tournaments
PRO TOURNAMENT
CHALLENGER TOURNAMENT
FUN TOURNAMENT
- Partners
- Shop
Welcome to the Counter-Strike 2 competition at Frag-o-Matic!
Frag-o-Matic 27.1 – Official Prize Pool Announcement The prize money for Frag-o-Matic 27.1 has been confirmed! Both Pro and Challenger tournaments will feature ...
The prize pool depends on the final number of participating teams.
ALL PLAYER MODELS (CT & T) SHOULD BE SET TO DEFAULT!
Introduction
This is the official rulebook for the Frag-o-Matic 27.1 CS2 competition. These rules apply to the players throughout all stages of the tournament.
Failure to adhere to these rules may be penalized as outlined. It should be noted that the tournament administrators have the final word, and have the power to decide on any circumstances that are not outlined by this document, and in extreme cases may overrule the rulebook in order to preserve fair play and sportsmanship.
Frag-o-Matic reserves the right to change these rules at any time without any notification.
The CS2 admin team wishes you good luck in the tournament and hopes that you have an enjoyable competition. We’ll do our utmost best to make it fair, fun and exciting for everyone involved.
Communication during the LAN will be through the #counter-strike-2 channel on the FoM Discord, or at the Compo Desk.
Registration opens: TBD
Registration closes: 4-9-2026 21:00
To submit a valid registration, each team must register a minimum roster of 5 players.
During registration, the following information must be provided for every player:
Additionally, at least 1 player from each team must join the Discord server. This player is responsible for following all official announcements and communication from the tournament admins.
All players must read and understand the CS2 rulebook.
Any player in violation of a rule, will be sanctioned as described in this rulebook.
Only players registered for a team in the tournament may play for that team unless otherwise discussed with the tournament admin.
All players must play at their designated seats for all tournament games unless otherwise instructed by the tournament admins.
Players registered for a team in the tournament may not play for any other team in the same tournament.
Each player has to use their nickname that is similar to the nickname he/she has entered on their fom.be account.
Players may not significantly change their nickname during the tournament. Any nickname they use during the tournament must always obviously visibly correspond to their original nickname. You are not allowed to change your nickname in-game.
If an admin’s job is hindered because of wrong or difficult nicknames or clan tags, the team will get a warning. 3 warnings are equal to a forfeit in 1 match.
Player nicknames may not be offensive. Tournament admins reserve the right to reject any tag or nickname they deem inappropriate.
Make sure your steam account is linked with your fom.be account corresponding to your nickname.
Players are strictly prohibited from using any other person’s steam account for any reason whatsoever during the CS2 competition.
We consider the one who registered the team into the compo on the Frag-o-Matic website as captain!
The clan leader or team captain is responsible for his team and all the players in that team. It is recommended that the team captain is fluent in English or Dutch, as he will be required to communicate with the tournament admins.
The team captain must read and understand the rulebook.
The team captain is responsible for ensuring his team and players adhere to the rules.
Ignorance of the rules is not an excuse for rule violations.
The team captain may choose at any time to nominate another player in or manager of his team as team captain for any reason. Such nominations must be reported by the team captain, either in person or in writing, to the admins before the game starts.
All official communication between a competing team and the tournament admins must be conducted by the team captain.
The team manager does not have any responsibilities. The team manager is eligible to play for his team in matches, providing he’s indicated as a “Player” on the team in the team sheet. The communication with the team will not go via the team manager, all communication will go via the team captain!
Spectators are not allowed on our servers. Only tournament admins and On-site Casters may be in spectator mode during a match.
Coaches are permitted to communicate with their players through third-party applications such as TeamSpeak or Discord. However, they are not allowed to have any presence within a match server as a spectator. Since Counter-Strike 2 does not currently support coach slots, Frag-o-Matic does not provide a third-party alternative. Teams are fully responsible for managing communication between their coach and players.
Frag-o-Matic does not restrict coach communication until the Grand Final.
Coaches may stand behind their players within the BYOC area. However, if you are a coach or affiliated with a team, you must not position yourself in a way that allows you to see or hear opponents, thereby gaining a tactical advantage. Frag-o-Matic may provide barriers on site to restrict visibility for coaches standing in the LAN area during matches
A protest is a raised issue for problems that affect the match outcome; a protest may even be filed during a match for things like incorrect server settings and other related issues. A protest is the official communication between a team captain and a tournament admin.
A forfeit is a lose or surrender.
Participants are only allowed to issue a match protest before the beginning of their next match.
The protest must contain detailed info about why the protest was filed, how the discrepancy came to be and when the discrepancy occurred. A protest may be declined if proper documentation is not presented. A simple “they are cheaters” will not be enough.
Insults and flaming are strictly prohibited in a protest, and may result in the protest being ruled against the insulting party.
A forfeit can be called for a single match or the entire competition from a competing team for their team. Only the team captain can raise a forfeit for their team.
A forfeit can also be raised by an admin as a penalty for wrongdoing.
For example, in most cases where a competing team doesn’t follow the time schedule.
The tournament admins can always force a forfeit.
The current tournament schedule can be found on the schedule tab of the competition page.
Please note that the schedule is subject to change. Tournament administrators reserve the right to modify the schedule at any time to accommodate delays, technical issues, or other circumstances necessary to ensure the smooth operation of the tournament.
All participating teams will begin in a Round-Robin Group Stage. Based on the final group standings, teams will qualify for one of two playoff brackets:
The match formats are as follows:
Tournament admins can change matches from BO3 to BO1 and vice versa when necessary (for example, when there isn’t enough time for a BO3)
The exact tournament structure depends on the total number of registered teams.
| Teams | Group Stage | Pro Playoffs | Semi-Pro Playoffs |
|---|---|---|---|
| 8-15 | 3-5 team round-robin groups | Double Elimination | None |
| 16 | 5-6 team round-robin groups | 8-team Double Elimination | 8-team Single Elimination |
| 17-23 | 4-6 team round-robin groups | 8-team Double Elimination | 9–15 team Single Elimination |
| 24-32 | 3-4 team round-robin groups | 16-team Double Elimination | 8–16 team Single Elimination |
Players need to know when their matches are scheduled and be ready on time.
All players must be ready (present in the game server) at least 5 minutes before the scheduled start time.
If a team isn't ready within 10 minutes after the scheduled start time, they risk:
Since admins can't watch all matches at once, the opposing team needs to report when someone is late. Report this through any of the communication channels mentioned in section 1.
This keeps games starting on time and the tournament running smoothly.
Teams with fewer than 4 players in the server cannot use Technical Pauses to delay match start times.
FoM tries to give players enough break time between matches. If a game runs late and cuts into the scheduled break, the break won't be extended to make up the difference. However, teams will still get a reasonable amount of time to rest.
Between matches: minimum 15 minutes, or until the next tournament round is scheduled to start (whichever gives you more time). Teams must be ready (!ready in the game server) by then.
Between maps in a series: 15 minutes before teams need to be ready for the next map (!ready in the game server). Admins can adjust this timeframe to keep the tournament on schedule.
Teams cannot skip a match or refuse to play for strategic or tactical reasons. Teams that miss a match or forfeit must give a valid explanation.
Valid reasons for missing a scheduled start or entire match include:
Tournament seeding is determined exclusively through objective parameters established by the administration team. Participating teams may be required to provide statistical information for all team members to support the seeding process. Teams of which no data is present or which fail to submit complete data for all five members will automatically be seeded outside the top 16 positions.
Seeding is done in the following order:
The admin team does not include subjective opinions into seeding decisions. If there are ever any questions regarding seeding before or during the event, admins can share the seeding tables to show how placements were determined.
The admin team reserves the right to adjust the playoff bracket format depending on the number of participating teams and the tournament structure.
For the group stage, teams are distributed into groups using a snake (serpentine) seeding system. This ensures that each group receives a balanced distribution of seeded teams.
The allocation follows the order below: (example given with 3 groups)
Seed 1 → Group A
Seed 2 → Group B
Seed 3 → Group C
Seed 4 → Group C
Seed 5 → Group B
Seed 6 → Group A
Seed 7 → Group A
Seed 8 → Group B
Seed 9 → Group C
etc.
Teams advancing from the group stage are placed into the playoff bracket based on their final group standings. For a four-group format where the top two teams from each group advance, the playoff bracket is seeded as follows:
A1 vs D2
B1 vs C2
C1 vs B2
D1 vs A2
The higher-ranked team from each group is rewarded with a first-place group finish and is matched against a second-place finisher from another group. Teams from the same group cannot face each other in the first playoff round.
If two or more teams have the same number of points during the group stage, the following tiebreakers determine placement (in order):
The tournament will use the latest available version of the game client. If the tournament admins deem the current version unplayable due to bugs or extreme balance changes close to the start of or during the event, an older version might be used if it's available for rollback. Any update during the event may result in a rollback to the initial version due to problems that might arise with the plugins.
All servers will use the standard Valve Anti-Cheat (VAC)
Teams are seeded at the start of the tournament in accordance with section 2.4. The highest seeded team (lowest seed number) is allowed to choose if they want to be Team A or Team B in the veto process.
The FoM CS2 tournament will follow the official Valve Active-Duty Map Pool. Admins reserve the right to modify this map pool in case of for example an update to the map pool right before, or during the event, in which competitive play is severely altered.
Only the following maps are allowed to be played on during the competition:
The map veto during the group-stage and the playoffs on saturday will be done using an in-game veto system.
The map veto for the Lower Bracket Final and Grand Final will be conducted in person by a tournament administrator.
The veto will take place 30 minutes before the scheduled match start time. At that time, a tournament administrator will personally invite one representative from each team to the veto location.
Teams are responsible for ensuring that their representative is available when requested. Failure to attend the veto on time may result in the veto being conducted at the tournament administrators' discretion.
The higher-seeded team (lower seed number) chooses to be Team A or Team B.
The highter-seeded team (lower seed number) chooses to be Team A or Team B.
The following match settings will be used for tournament matches:
In case of a draw after all 24 regulation rounds have been played, overtime will be played in
best out of 6 mode (mp_maxrounds 6) and with $12,500 start money (mp_startmoney
12500). At the start of each overtime, teams will stay on the side from which they played the
previous half - during half-time sides will be swapped. Teams will continue to play overtimes
until a winner has been found.
Frag-o-Matic provides all official match servers for the tournament.
Matches are normally played on locally hosted servers. However, if issues arise with the local infrastructure, tournament administrators may move matches to online-hosted servers when deemed necessary.
The pause function can be used at any time, but it will only come into effect during freezetime.
Technical timeouts are intended to be used when a player experiences a technical issue that cannot be resolved while the match is live.
Each team is allocated a total of 10 minutes of technical timeout time per map. This time may be used all at once or divided across multiple technical timeouts during the match. Once a team has exhausted its allotted timeout time, the match will automatically resume.
If a technical issue cannot be resolved within the allocated timeout period, or it is clear that the issue cannot be resolved in a reasonable amount of time, the team must immediately contact a tournament administrator to determine how the match will proceed.
Technical timeouts may only be used for legitimate technical issues. Abuse of technical timeouts for unrelated purposes will not be tolerated. The opposing team may report suspected abuse to the tournament administrators. If the tournament administration determines that a technical timeout was used without valid reason, the offending team may receive a warning or other appropriate penalty.
Each player is allowed to invoke a timeout of 30 seconds up to 3 times in regulation rounds per map. Tactical timeouts can be called through the in-game menu (ESC → Call Vote → Call Tactical Timeout) or by typing !tac in the chat.
If a match reaches overtime, all remaining timeouts will be removed and each team will receive one timeout to be used during that overtime. If the map progresses to another overtime, the same process will happen again.
A tournament admin can pause the game from the compo area, or from a players PC when it is required.
All matches must start with 5 players per team (5v5). No other team sizes are permitted.
If a team is unable to field five players at the scheduled start of a match or map, the team will be considered a no-show, and the relevant match or map will be forfeited.
In the event of a map forfeit due to a no-show, the scheduled start time for the next map will be considered to be 1 hour after the scheduled start time of the forfeited map.
If a player disconnects during a live round, that round must be completed before play is paused. If the map has not concluded, the match must be paused to allow the player to reconnect or to be replaced by an eligible substitute.
If the disconnected player is unable to return and no substitute is available, the affected team may either forfeit the match or continue playing with 4 players.
If, at any point, a team is unable to field at least 4 players, the opposing team will be awarded a default win.
If a match is interrupted due to circumstances beyond the players' control (such as a server crash or technical failure), the tournament administration will, where possible, restore the match using Counter-Strike's backup and restore feature.
Depending on the circumstances, tournament administrators may instead decide to replay a round, restore a round, or, in exceptional cases, replay the entire match. The following guidelines apply:
After damage has occurred and the round can continue
If damage has already been dealt but the outcome of the round can still reasonably be determined (for example, a single player disconnects while the remaining players continue), the round will not be restored or replayed. Play will continue as normal.
Tournament administrators may make exceptions if the damage is considered insignificant, such as accidental team damage at the start of the round or damage dealt by the team affected by the interruption.
Tournament administrators reserve the right to make the final decision in any interruption scenario that is not explicitly covered by these rules.
Rounds will not be restored or replayed when the interruption or issue is clearly the result of player error, such as forgetting to purchase equipment or other mistakes made during normal gameplay.
MatchZy will automatically record a GOTV demo for each game.
It’s recommended for all players to record point of view (POV) demos for the full duration of all matches without exception.
In general, defective or manipulated demos will be treated as missing demos. If the demo is incomplete, as decided by the admin, it also will be treated as missing demo.
If a protest is opened for a match, all match media need to be kept until the end of the event.
Demos can only be requested up to a maximum of 30 minutes after a match via the admin.
A demo request must state which teams were playing, the name(s) of the map(s) the match(es) was/were played on, the time of the match(es) and the server IP address(es).
If a player or a team illegally aborts the match, they lose their right to demand demos.
It is strictly forbidden to edit demos. If a demo is manipulated, it will be treated as missing demo.
Any form of cheating, exploitation, or modification that provides an unfair competitive advantage is strictly prohibited.
This includes, but is not limited to, any hardware, software, configuration, modification, or external tool that affects gameplay in a way that compromises competitive integrity.
If a player is found cheating during Frag-o-Matic, both the player and their team will be disqualified from the competition. The player will additionally receive a ban from the following Frag-o-Matic edition.
Tournament administrators have the right to investigate suspected cheating cases. Sufficient evidence must be provided before a player is considered to have violated this rule. The tournament administration has the final decision regarding the validity of evidence.
Players are required to cooperate fully with any investigation. Players who intentionally provide false information or refuse to cooperate during an investigation may receive additional penalties.
Frag-o-Matic does not investigate or enforce bans for cheating incidents from unrelated external events unless they fall within the defined review period.
Tournament administrators may review reports of cheating from tournaments or platforms occurring before the event.
A player who has been confirmed to have cheated within 12 months before the start of Frag-o-Matic will not be allowed to participate in the CS2 competition for that edition or the following edition.
A player who is caught cheating in another tournament or platform within 12 months after the start of Frag-o-Matic may also receive penalties for future Frag-o-Matic events.
The Frag-o-Matic banlist remains applicable. Players attempting to circumvent bans by using false identities or other methods may receive an extended or permanent ban.
The following are prohibited:
Frag-o-Matic Discord 
twitch.tv/fomlan 
Signups & Seeding 
Bracket .pak, .exe, or other game filesThis list is not exhaustive. Any action that compromises competitive integrity may be considered cheating.
Only standard CS2 scripts and bindings that do not provide a gameplay advantage are permitted.
Allowed examples:
The following are prohibited:
The following commands are also prohibited:
+weapon_recoil_model 0snd_* bindingsUsing illegal scripts is punishable regardless of whether they were actively used during the match. If prohibited scripts or bindings are found in configuration files, penalties may still be applied.
Penalties may apply to both software and hardware-based execution of illegal scripts.
Only official CS2 files and approved modifications are allowed.
Allowed:
Forbidden:
Tournament administrators may inspect player files at any time during the event.
External programs that provide gameplay advantages are prohibited.
This includes, but is not limited to:
Simple FPS counters are permitted.
Tournament administrators may inspect player computers, game files, Steam Cloud files, storage devices, and running processes during the event to verify compliance.
If a player or team discovers a new mechanic, setup, configuration, or strategy that may provide an advantage and they are unsure whether it is allowed, they are encouraged to contact the tournament administration before using it.
Teams may submit examples privately for review. Frag-o-Matic will keep such submissions confidential and provide a ruling before the event whenever possible.
RCON will not be allowed by any participating player during this tournament. If there are any issues that cannot be solved by the provided command of MatchZy, please contact one of the admins.
Disclaimer
De cash prijzen kunnen altijd wijzigen naarmate het aantal team dat zich inschrijft en de compo effectief speelt.
Cash prizes can be altered till the last minute, depending on how many teams register and play the compo.
Frag-o-Matic 27.1
Schedule
Counter-Strike 2
BEFORE THE GROUPS STARTS WE EXPECT ALL THE TEAM CAPTAINS
AT THE STAGE AT 21u30 FOR A SMALL INFO TALK!
Assuming 17-23 teams. Subject to change:
| Match | Time |
|---|---|
| Team Captain Talk 21u30 | |
| Group Match 1 | Friday, 22u – 23u |
| Group Match 2 | Friday, 23u – 00u |
| Group Match 3 | Saturday, 00u – 01u |
| Group Match 4 | Saturday, 11u00 – 12u00 |
| Group Match 5 | Saturday, 12u00 – 13u00 |
| Match | Time |
|---|---|
| - BREAK 13u00 – 14u00 - | |
| UB Match 1 (BO3) | Saturday, 14u00 – 17u00 |
| - BREAK 17u00 – 18u00 - | |
| UB Semi (BO3) | Saturday, 19u00 – 21u00 |
| UB Final (BO3) | Saturday, 21u00 – 00u00 |
| Match | Time |
|---|---|
| LB Match 1 (BO1) | Saturday, 18u00 – 19u00 |
| LB Match 2 (BO1) | Saturday, 21u00 – 22u00 |
| LB Match 3 (BO1) | Saturday, 22u00 – 23u00 |
| Match | Time |
|---|---|
| LB Final | Sunday, 10u00 – 13u00 |
| Grand Final | Sunday, 13u00 – 16u00 |
