- Event
-
Tournaments
GRAND TOURNAMENT
SATURDAY ARENA
SOLO TOURNAMENT
TEAM TOURNAMENT
- Rocket League (3v3)
- Rocket League (2v2)
- ARAM League of Legends (5v5) powered by Be Quiet!
- Valorant (5v5)
FUN TOURNAMENT
- Partners
- Shop
ALL PLAYER MODELS (CT & T) SHOULD BE SET TO DEFEAULT!
Introduction
This is the official rulebook for the Frag-o-Matic 27.0 CS2 competition, that will take place from the 13th february until the 15th of february 2026. These rules apply to the players throughout all stages of the CS2 competition.
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.
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 #CS2 channel on the FoM discord, or at the Compo Desk. The CS2 admin team will consist of:
We will be available as much as possible in the #CS2 channel. We will use this as a channel to remind everyone to play, of scheduling or changes. Important server-info will also be communicated in the #CS2 channel.
Communication before and after the LAN for providing feedback, or regarding question can be done using the following email:
Discord will be our main communication channel.
the link to discord is always available through the FOM-website!
https://www.fom.be/discord
Due to lack of time, we have a tight schedule. Therefore we can make the decision to force teams to only participate in 1 grand compo! We will contact the teams who are signed in for 2 grand compo’s at the moment and they will need to make a choice. When a team refuses, we will remove them from the competition to make room for other teams.
As teams may be required to compete on the stage, it is required that all teams remove any offensive material from their desktops. A rule violation by any player in a team may lead the tournament admins to sanction the entire team, even if the rest of the team was not aware of the violation.
The admins reserve the right to ban teams from the compo if they find teamnames too offensive or inappropriate. A team name change might be a solution to prevent the ban.
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.
During a match, the coach may only communicate with the players during warm up, half-time, or during timeouts.
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
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.
All players must read and understand the CS2 rulebook.
Any player in violation of a rule, will be sanctioned as described in this rulebook.
Each team must have five players on the match server at the match start time as indicated by the schedule, unless permission has been granted by the tournament admins to play with less than five players.
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.
People participating in the CS2 tournament are expected to normal grooming standards.
You may be asked to take action if you or your clothing have a look or odor that’s offensive to other players.
At Frag-o-Matic, we will not investigate cheaters from an external event. If we catch someone cheating during our LAN, both the player and their team will be banned from the competition, and the player will also be banned from the next Frag-o-Matic event. Additionally, we will look into reports of players cheating in other tournaments up to 2 weeks before our LAN. If a player is found cheating in another tournament or platform within 12 months before our event, they will not be permitted to participate in that edition of Frag-o-Matic in the CS2 competition or the one following it. If a player is caught cheating in a tournament or platform within 12 months of our event's start date, they will be disqualified from competing in our tournament. There must be sufficient evidence to prove that a player was cheating, and the tournament administrators will determine the validity of the evidence.
All hardware or software that has an influence on the game in such a way that the essence of the game is affected are banned from this tournament. Any use of this kind of hardware will result in a disqualification of the tournament as it will be recognized as cheating.
When proven that a player is not cooperating in his own ban research or is lying on purpose. He will get banned for 1 edition.
You can find our banlist at http://www.fom.be/contents/view/cs-go-banlist The mentioned people in our ban list are not allowed in the CS2 tournaments at Frag-O-Matic until the edition that’s stated there. When these people compete under a false name nonetheless or try to circumvent the rules then they will receive an extended or permanent ban.
Here are some of the other examples of ways to gain advantages, this list may not be the full list but if players are unsure of certain things, they should seek to ask the tournament admins first:
Wall Hacking.
Aimbotting.
Trigger Botting.
Radar Hacks or Modifications on the client or pushed externally over the web or to other devices.
Hardware based cheats.
FOV/HUD modifications.
Economy modifications.
Inflicting damage, any modifications or inducing crashing to the Game Server.
Modified versions of CS2’s .pak or .exe files or any other protected or unprotected client files.
Screen watching and / or Stream Sniping.
Knowingly gathering game information that provides an unfair competitive advantage.
Any programs or files, that change CS2 or augment its functionality or which may interact with CS2 in any way that gains a competitive advantage.
Bringing the competitive integrity of the tournament into question.
Tampering with other participant’s personal equipment / BYOC setups.
โIf any player or team feels unsure of a new advantage they have found through their practice sessions, they are welcome to show this specific spot to the tournament team to review. Any player or team that does this will be treated to the strictest confidence as not to jeopardize your strategic advantage, however we can rule on whether it is a legal move. We strongly advise teams to give us plenty of time ahead of an event so we can review it in good time and make good judgement on it.
The game admins may inspect your machine at any time throughout the event to inspect for cheats or hacks within your game files, steam cloud and anywhere on your PC or memory sticks.
During the lan, to prevent cheating by using external devices or items, the following items are forbidden:
Any other electronic devices (like smartphones) that are used during a match will be considered suspicious and we’ll ask that they’re not used. If, during a match, the suspicious device is still in use; the team of the player using the device will receive a warning. After 3 warnings the team will receive a disqualification from the tournament.
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.
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 parameters include, but are not limited to:
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.
Frag-o-Matic Counter strike 2 (CS2) 5v5 tournament is a local area network (LAN) tournament. By competing in this tournament, teams and players accept these rules in full.
Teams which violate these rules will be sanctioned, and may be removed from the tournament without compensation.
In the beginning of the LAN the team captains can sit together with the admin to discuss the rules and to make adjustments if needed.
The decisions are made by the admin. If you have any issues with the rules, you can explain this by sending an email to compo@fom.be up to one week before the start of the event.
Clarification of any point in the rules is available from the tournament admins at any time during the tournament.
Sanctions and disputes will be resolved by the main tournament admin.
The admin’s decision on any sanction or dispute is final.
Abusive behavior towards the Frag-o-Matic staff, tournament admins or opponents at any time during the tournament is unacceptable and will be punished with warnings. 3 warnings are equal to a forfeit in 1 match.
The content of protests, support communication, discussions or any other correspondence with tournament officials and administrators are considered as strictly confidential. The publication of such material is prohibited. If the contents has been shared without consent then this could lead to a team’s disqualification.
Any form of aggression* (both verbally and physically) will not be tolerated.
Any and all physical aggression will be sanctioned with an immediate disqualification by that person or team performing the physical act (both actioned and reactioned).
Any verbal aggression will be sanctioned by a time-out for that person or team.
A time-out is either set in time (hours/day) or in amount of matches when a player or team is not allowed to participate in the CS2 competition.
Any situation that is about to escalate should be dealt with in a calm and diplomatic manner.
An audience with any Frag-o-Matic crew member (CS2 admin or Frag-o-Matic team leaders) can always be called for at any time during the event.
Keep in mind that this audience can not be used to waste time or get a time advantage.
At any point, the CS2 tournament admins can decide to continue with the competition with or without consent from either players or other Frag-o-Matic staff.
In the event when a single player or more are accused of cheating, the event will continue nonetheless.
Evidence will be presented to the tournament admins and a call will be made at a later stage of the event.
This rule is set to not cause any delays and have the situation under control.
Any player(s) or team(s) ignoring this rule will receive a forfeit.
Any player or team ignoring a CS2 admin will be sanctioned with a warning.
3 warnings are equal to a forfeit of 1 match.
*A form of aggression is described as:
To play a match under the influence of any drugs or performance enhancers is strictly prohibited, and may be punished with exclusion from the tournament.
If an admin finds that a player is not capable of competing in the competition because of intoxication, the admin can exclude that person from the entire tournament.
Betting on any match in the CS2 tournament is strictly forbidden.
Teams may be required to play any match on the stage. If so, teams will be notified at least 20 minutes prior to the start time of that match.
Frag-o-Matic reserves the right to broadcast any match or demo, teams may not refuse such broadcasts.
All forms of client side game broadcasting are NOT allowed.
Frag-o-Matic participants are not allowed to watch a local GOTV if a CS2 server broadcasts a game.
Players must always be available for interviews on the official CS2 stream. At least one of the five team members must be prepared to participate if requested. A team manager is also permitted to participate in the interview.
All match media (screenshots, demos, etc.) must be kept until the end of the event. Faking or manipulating match media is forbidden and will result in exclusion from the tournament.
Match media should be named clearly based on what it is. It is not possible to file a protest to complain about bad match media naming.
However if a tournament admin is hindered in their work because of bad match media naming, then a tournament admin will give a warning.
3 warnings are equal to a forfeit in 1 match.
The admin can ask for screenshots of every game on any moment during the event. When he does this, the team leader has 15 minutes time to deliver the screenshot to the admin.
A screenshot of the scoreboard at the end of each map must be taken. When this is not done by a team it can result in a lost match when one of the other teams complains about a score.
Teams are permitted to substitute players (only with another player not active in the CS2 competition) during pauses and between rounds, if they have permission from the tournament admin.
Consent for substitutions must be obtained from the tournament admins, and substitute players must be registered for that team in the tournament. You can make this clear to the admin by using the contact information in section ‘Admins and communication’.
When you subscribe to this competition you agree to our prize money policy: http://www.fom.be/contents/view/prizemoney-policy
You can find the current tournament schedule on the schedule tab of the compo page.
The schedule may change depending on what happens before and during the tournament. CS2 compo admins can modify the schedule at any time if needed to keep the event running properly.
When possible, admins will notify affected teams at least 30 minutes before a rescheduled match. If a match gets cancelled, admins will notify teams as soon as they can.
FoM CS2 tournaments run on a fixed schedule. Players are not allowed to start matches early without admin permission. Keep in mind that your next opponents don't have to play their match early just because you did, which can lead to longer waits between matches.
During the group stage, you cannot choose which order to play your matches. Teams must follow the order shown on the FoM tournament website.
If there isn't enough time to finish a match, admins may declare a winner if one team has a clear advantage. Admins decide what counts as a clear advantage. This rule is only used in emergencies when running out of time becomes a problem.
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 10 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: 10 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:
All sign-ups happen on the fom.be website. Some rules are already covered in the general rulebook. Any team without at least 5 players will be removed from the sign-up one hour before the competition starts.
We allow a maximum of 64 teams to register for the CS2 competition.
The CS2 tournament has a round-robin group stage followed by one double elimination bracket.
Each group has 3-4 teams who compete to determine playoff seeding. Every team in a group plays every other team in that group. After the group stage, all teams advance to the playoffs bracket and are seeded based on their group results.
Match formats:
Tournament admins can change matches from BO3 to BO1 or vice versa when necessary (for example, when there isn't time for a BO3).
If two or more teams have the same number of points during the group stage, the following tiebreakers determine placement (in order):
Matches are played 5v5. Playing with fewer than five players requires tournament admin permission.
Before a match starts, both teams must confirm they're ready by having one team member type '!ready' in server chat.
If a player or team has temporary problems, inform your opponent and restart the ready process.
Map loading bugs (missing boxes, ladders, etc.) can happen after any round. If you don't check the map before the round starts, you cannot complain about these bugs after the round/map ends.
Match setup process:
`.map [mapname]`. See section 4.1.8 for the veto processAll weapons and grenades are allowed. You can use everything implemented in CS2.
For this edition of the FoM CS2 tournament, Matchzy will be used to handle the veto-process during all group stage and playoffs matches. The map(s) chosen to be played in each BO1 and BO3 are done via elimination (i.e. veto), where ‘team 1 = A’ and ‘team 2 = B’, with team A being decided by the highest seeded team that matchup. All the match results of your group will also have impact in the seeding of the bracket.
The maps you don’t want to play as a team, should be the maps that you veto during this process. The veto process needs to be done in server chat.
VETO rules best-of-1: ABABAB veto.
The map pool exists out of 7 maps.
6 maps are vetoed during this process, 3 maps for each team.
The remaining map is the map played in the best-of-1 match.
VETO rules best-of-3: A/B veto, A/B play and A/B veto.
The map pool exists out of 7 maps. 4 maps are eliminated, and 3 maps are selected to play.
Each team needs to veto a map, followed by each team choosing a map and again each team vetoing a map. The remaining map is the third map that needs to be played if both teams win a map.
All matches in the group stage are played MR12. All matches in the brackets are played MR12.
In the group stage, matches are played best of one (BO1) on a map decided by veto (as described above). All games in the upper-bracket are best of three (BO3) , 3 maps are decided by veto. Lower-bracket will be BO1.The grand final is a best of three (or best of 5 depending on time) Admins will change the lowerbracket BO1 to BO3 if time schedule allows.
When in the brackets a game is tied an overtime needs to be played. โThe overtime will be played MR3 with 10.000$ start money. For the start of the overtime teams will stay on the side which they played the previous half on, during halftime sites will be swapped. Teams will continue to play overtimes until a winner has been found.
We have our own special breed of bracket seeding. For more information please contact us in advance. This bracket seeding is law. Obey it.
All CS2 players can only use our ts.fom.lan (local) teamspeak for voice communication or the fom provided discord.
If the choice is made to use a discord server that is not linked to the available discord the tournament admin reserves the right to join and/or investigate the used discord server.
Teams are only allowed to have 5 players + 1 coach in their teamspeak/discord channel whilst in a competition match.
Pauses may be taken for any reason.
Teams are permitted 4 pauses per map
Each pause having a maximum duration of 2 minutes, unless authorised by an admin to take a longer pause (in case of technical difficulties, for example).
After a “pause”-event, an “unpause“-command needs to be done.
Teams can’t unpause without the consent of the other team.
Pauses may only be activated at the start of the next round during freeze time.
So make sure you tell the other team before round end (in all-chat), that your team will take a pause in the next freeze time.
Usage:
Type the following commands in the chat, to activate and deactivate the pause event.
Pause = .pause or .tac
Unpause = .unpause
Tech pause = .tech
It is also possible to call a timeout through the cs2 menu.
GoTV demos must be active for each match to be recorded. It’s the responsibility of (both) team captains to ensure that GoTV is recording. If this isn’t the case, the tournament admins will be forced to make calls without a recording when a dispute occurs.
It’s recommended for all players to record point of view (POV) demos for the full duration of all matches without exception. A knife round is part of a match and should be recorded. At least one of the players must be able to upload the knife round on admin request. Protests regarding missing knife rounds are not valid.
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.
Recording demos is recommended. Our servers will likely record demos for every match but these are only used when there is doubt about a decision the admin has to make.
It is strictly forbidden to edit demos. If a demo is manipulated, it will be treated as missing demo.
The FoM CS2 tournament will following 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 admin is allowed to take over your computer before, during and after a game and have a look. Without the pc’s owner in question nearby, the person in question can appoint someone to stay with the admin to make sure no privacy issues are violated. Any trace evidence of cheats found on a player’s computer – even if such discovery took place outside of a game – can lead to exclusion from any competition.
In your game client cfg-folder you’re only allowed to have config files.
Pictures, demos, screenshots and zipped files are forbidden.
All other configuration changes are allowed as long as they do not give an unfair edge or advantage comparable to cheating.
The using of bugs is not allowed. Should a bug that is not listed be used, an admin will decide if a penalty is necessary.
To plant the bomb in a way that it cannot be reached is forbidden. Places that can be reached with help of a team mate are allowed as long as they are visible. Violating this rule will result in tournament administrators intervention.
Changing graphic settings to irregular values can be punished.
In general, all scripts are illegal except for buy, toggle & demo scripts. Some examples of illegal scripts:
If there are more than one player who used a wrong client setting, the match will be deleted.
Using illegal scripts will be penalized if the script could lead to a game advantage. This depends on the script concerned and it is up to the responsible admin to decide about this. It does not matter whether the script has been used or not. If the config files of a user contain illegal scripts or parts of illegal scripts, he will be penalized.
The use of No-Flash and No-Recoil bindings/scripts in any and all forms will be punished.
The HUD can be changed as long as no information are deleted or falsified which are available in the standard HUD. If the HUD is changed it has to be readable. If an admin is hindered in his work due to an unreadable HUD, penalty points may be assigned. Protests or supports which adhere to this rule will not be admitted and are rejected directly. Apart from the HUD and the GUI no custom files are allowed. This also includes custom models, changed textures or sounds (volume, soundscapes) are forbidden.
The usage of external programsare not allowed to enhance vision.
Changing the game graphics or textures with the help of video card drivers or similar tools is illegal. Furthermore any kind of overlay that displays the system performance while playing is illegal. Failure to comply with this rule will result in a punishment for the player and the team. Tools that only display the FPS are legal.
Regardless of being actively used, if these scripts are found in part or in full in your config files, you will be penalized.
Punishment will be given regardless of whether the script/binding is executed via external hardware or software.
Also binding any snd_ command is forbidden.
All In-Game overlays provided by the game itself are allowed:
If a disconnection occurs the game should automatically reconnect. When this doesn’t work, a tournament admin will decide what to do.
The tournament admin will make a call in every possible scenario regarding the severity of the problem and how to deal with it.
But, the following guidelines are in place in the event of a disconnect:
Frag-o-Matic will supply hardware for all servers. All games related to the tournament must be played on these servers.
All matches will be played using the latest version of CS2 and the official Frag-o-Matic CS2 server config. All matches have to be played on an official Frag-o-Matic CS2 tournament server and on the provided server number (as listed on our fom.be website, in the CS2 compo section).
We’ll use a standard ESL 5v5 pro league tournament config:
In the event of a server crash, after notifying a tournament admin and having them restart the the server, both teams have to re-join the same server, and wait for the admins to restore and unpause the match on the correct match.
Teams are given the time to play a warm-up match on their server before every compo match if they wish to do so. It’s not allowed to switch to another server once the compo match has been started. Test the server before the match starts.
Any server problems should be reported to a tournament admin by going to the compo desk after sending an email with the information below.
In the event that you experience any lag during or before a match, please note the time(s) and contact us via Discord or the Compo Desk.
We'll escalate this information and, if possible, provide a solution for upcoming matches.
The statement or report of (possible) lag in a match is a not valid argument in a protest.
However, sending us the data above will give your team the time necessary to avoid any possible forfeits when you notify us at the compo desk after sending your email.
Failure in providing us this data will not allow your team to deviate from our time schedule.
We strive to provide all our servers lag free.
We would like to thank you in helping us improve our servers.
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.
Subject to availability, we will provide warmup servers. The settings will mirror our war servers as close as possible, but won’t be managed by the CS2 team.
Participants in our competition are allowed to use our warmup servers as such, to warm up, practice nade throws, practice aim,etc…
We will not guarantee availability of those servers, since they will depend on the overall capacity.
If warmup servers are available, they cannot ever be used for playing matches. If a match has been played on one of those servers though, the end-scores will still count. It is the responsibility of both teams the correct (assigned) server is joined.
At any time, we can convert one of those servers to an official war server (In cases of need). It will at that point no longer show up as a warmup server.
Copyright © 2005-2025 by E-EVENTS VZW
All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law. For permission requests, write to the publisher, addressed at compo@fom.be
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.0
Schedule
Counter-Strike 2
BEFORE THE GROUPS STARTS WE EXPECT ALL THE TEAM CAPTAINS
AT THE STAGE AT 21u30 FOR A SMALL INFO TALK!
| Match | Time |
|---|---|
| Team Captain Talk 21u30 | |
| Group Match 1 | Friday, 22u – 23u |
| Group Match 2 | Friday, 23u – 00u |
| Group Match 3 | Saturday, 00u – 01u |
| Match | Time |
|---|---|
| UB Match 1 (BO3) | Saturday, 10u00 – 13u00 |
| UB Match 2 (BO3) | Saturday, 13u00 – 16u00 |
| - BREAK 16u00 – 17u00 - | |
| UB Match 3 (B03) | Saturday, 17u00 – 20u00 |
| - BREAK 20u00 – 21u00 - | |
| Semifinals (BO3) | Saturday, 21u00 – 00u00 |
| Match | Time |
|---|---|
| LB Match 1 (BO1) | Saturday, 13u00 – 14u00 |
| LB Match 2 (BO1) | Saturday, 14u00 – 15u00 |
| - BREAK 16u00 – 17u00 - | |
| LB Match 3 (BO1) | Saturday, 17u00 – 18u00 |
| LB Match 4 (BO1) | Saturday, 18u00 – 19u00 |
| - BREAK 20u00 – 21u00 - | |
| LB Match 5 (BO1) | Saturday, 21u00 – 22u00 |
| LB Match 6 (BO1) | Saturday, 22u00 – 23u00 |
| Match | Time |
|---|---|
| LB Final | Sunday, 09u00 – 12u00 |
| Grand Final | Sunday, 13u00 – 16u00 |
