Frag-o-Matic 25.1



6/09 - 8/09



GRAND - CS:GO (5 vs. 5)


Password to join the CS:GO servers: war
Open in-game console and type the following: connect IP:PORT; password war

Best 4 of each poule go on to the brackets to compete for the victory.

Brackets will be played as followed:
1st round upperbracket → BO1 → TODAY (Saturday)
1/4 and ½ final upperbracket → BO3 → TODAY (Saturday)
Lowerbracket → BO1 → TODAY (Saturday)
1/2 Final Lowerbracket → BO3 → TODAY (Saturday)

Final → BO5 (with map advantage) → Tomorrow (Sunday)

Lowerbracket will have to wait on the upperbracket for a bit for 2 rounds, so make use of the time off to do the things you have to do.
The idea is that both 1/4 finals (UB + LB) and after that both 1/2 finals (UB + LB) will be played at the same time 

Tomorrow (Sunday) is the day for the Final... BO5 so we will have to start at 10 o'clock (BE ON TIME !!!)... to be sure to end in time in case the 4 rounds will be needed to play in full... 

CS:GO Tournament powered by Cooler Master

CS:GO Tournament powered by Cooler Master

Initial compo list FoM 21.1

Initial compo list FoM 21.1



CS:GO Tournament powered by Cooler Master

The doors have opened on this 22nd edition of Frag-o-Matic! While people are arriving, it's a good moment to announce the prizes for the CS:GO tournaments provided by our ...

Initial compo list FoM 21.1

We are proud to announce the confirmed compo’s at this time! This list is pretty complete, but can still change of course. These compos will definitely be available on FoM ...


The RIV4L Lan Tour stops at our favourite lan of the Benelux twice. They will return in our September edition! Find out more information about the RIV4L Lan Tour on the ...

CS:GO Gungame by Tech Data

Frag-o-Matic collaborates with Tech Data and organizes a CS: GO Gungame compo! This is a double compo, where you can win a prize on Saturday and Sunday. Games ...

SteelSeries returns to FoM 21.0!

We would like to welcome SteelSeries to the Frag-o-Matic 21.0 race track! SteelSeries will be providing the CS:GO Semi-pro and CS:GO Fun competitions with awesome hardware ...

<< previous next >>


Best 4 teams of each poule will progress to the next round.

w: wars won | l: wars lost | d: draw wars | rw: rounds won | rl: rounds lost

First Place 


  • 1000 € 

Second Place


  • 450 €

Third Place


  • 200 €

Frag-o-Matic 24.0
Counter-Strike:Global Offensive (CS:GO)


This is the official rulebook for the Frag-o-Matic 24.0 CS:GO competition, that will take place from the 17th until the 19th of Februari 2023. These rules apply to the players throughout all stages of CS:GO 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 CS:GO 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.

Table of contents

  1. Admins and communication
  2. Compo overview
    1. Participants
    2. Team sheets
    3. Team names
    4. Team manager / coach
    5. Team captain
    6. Players
      1. Grooming standards
    7. Cheating
      1. Forbidden items
    8. Match protests and forfeit
      1. Definition
      2. Match protest rules
      3. Forfeit rules
    9. Seeding
  3. General
    1. General rules
    2. Sanctions and disputes
    3. Confidentiality
    4. Code of conduct
    5. Drugs and alcohol
    6. Betting
    7. Additional agreements
    8. Streaming, interviews and media
      1. Broadcasting
      2. Match media
      3. Screenshots
    9. Player changes
    10. Prize money
  4. Counter-Strike:Global Offensive rules
    1. Tournament structure and time schedule
      1. Penalties and forfeits during the time schedule
      2. Compo sign-up and max teams
      3. Structure
      4. Game setup
      5. Veto system
      6. Compo specific rules
      7. Usage of pause
      8. Demo files
    2. Match procedure
      1. Map list
      2. Match rules
      3. Client rules
      4. Illegal scripts
      5. Custom files
      6. Color depth and external programs
      7. Illegal programs
      8. In-game overlays
      9. Technical problems and disconnects
    3. CS:GO server
      1. Server settings
      2. Server crash
      3. Server (var) lag
      4. Server plugins
      5. RCON usage
      6. Warmup servers
  5. Copyright Notice

1. Admins and communication


Communication before the LAN:

Please email us any feedback before and after the LAN event.

CS:GO admin team:

Communication during the LAN:

The communication during the LAN will be through Steam, Discord or at the Compo Desk.


We will be available as much as possible in the #csgo channel. We will use this as a second channel to remind everyone to play, of scheduling or changes. Important server-info will also be communicated in the #csgo channel.

Discord will be our main communication channel.

Back to top

2. Compo overview

2.1 Participants

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.

Back to top

2.2 Team sheets

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.

Back to top

2.3 Team names

Back to top

2.4 Team manager / coach

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 may be in spectator mode during a match.

The only exception is: coaches are allowed to spectate a match using the coach's command, only if the tournament admin is notified, and thus to spectate their team only. They are obligated to use the “coach t” or “coach ct” command before the match start and aren’t allowed to join after a match has been started. If noticed that the coach is abusing this rule, the team will get punished for it (e.g. round loss, side loss or match loss).

During a match, the coach may only communicate with the players during freeze-time, warm up, half-time, or during one of the 4 timeouts.

Back to top

2.5 Team captain

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.

Back to top

2.6 Players

All players must read and understand the CSGO 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.

All players for a team must be clearly identifiable in-game with a uniform tag for that team and a separate, noticeably different nickname for each player.

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 CS:GO competition.

Back to top

2.6.1 Grooming standards

People participating in the CS:GO 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.

Back to top

2.7 Cheating

During Frag-o-Matic we won’t investigate cheaters from an external event. When we discover someone cheating during our LAN, that player and his team will be banned from the compo and the player will be also banned for the next Frag-o-Matic edition.

Furthermore we will investigate reports of players cheating during other tournaments until 2 weeks before the LAN. When a player is discovered cheating during another tournament/platform 12 months before the event occurs, then that player will not be allowed to play on that edition of Frag-o-Matic within the CS:GO competition and the edition after that.

If one of the following rules apply, then that player will not be allowed to compete in our tournament:
Caught cheating within a tournament/platform 12 months before the start date of our event.
There needs to be enough evidence for that player, that he/she was cheating and the tournament admins will judge if the evidence is valid OR if he/she was caught cheating on the following platforms:

  • ts.fom.lan - CS:GO admin channel
  • Discord: https://discord.gg/MbPY2ge
    • Teams are only allowed to use a uniform team name for their team.
    • Teams may not change their team name during the tournament.
    • Teams may not change their team in-game tag during the tournament, unless none was set.
    • Duplicating team names of other teams is not allowed.
    • Duplicating (exactly or approximately) the tags used by another team in the tournament is not permitted.
    • Team names are not allowed to be offensive.
    • Please make sure your team name is filled in on your fom.be profile.
    • Faceit
    • Esl
    • Valve (vac ban for any Counter strike: Global Offensive game)
    • ESEA
    • Cevo

  • When a player is caught selling or buying cheats.
    In any case the admin will have the final decision.
    This means that the admin will review the evidence and make the final call.
    If a player shows the intention of coming to our tournament to cheat and we’re provided evidence of this.


    Everyone from the community may send evidence to csgo@fom.be, when they suspect someone participating at Frag-o-Matic of cheating.

    All forms of cheating in matches are forbidden, and will result in an overall forfeit in the tournament. Possibilities for cheating in Counter-Strike:Global Offensive are, for example; all kinds of multi-hacks, wallhack, aimbot, colored models, no-recoil, no-smoke, no-flash and sound changes.

    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 CS:GO 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: Flash Bang, Smoke Grenade, and Hand Grenade Bugs - it is illegal to use any flash bang, smoke grenade, or hand grenade bugs, regardless of intent. Silent Bomb Plants - ALL bomb plants must be done in a position where your opponents can hear you. There should be no rotation in players to gain money advantages throughout a match. The bomb must be planted on solid surfaces on the map, ie where an opponent can defuse from, so not up in the air or floating. Illegal Bomb Defuses - No player can defuse a bomb through any other solid object on the map, it has to be done in clear view. It is also forbidden to try to intentionally distort your hitboxes during a defuse situation to prevent an opponent from killing you in game. Walking/Boosting through walls - No player should walk, boost through walls or roofs. To do so will see your team penalized for that round. Map Exploits - Boosts that include the use of clipping are strictly forbidden. The term “Clipping” defines that when a player is boosted can see through certain parts of the map (ie over/under walls, or through solid objects on the map).

    If any player or team feels unsure on 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.

    Back to top

    2.7.1 Forbidden items

    During the lan, to prevent cheating by using external devices or items, the following items are forbidden:

    • Smartwatches; Having or carrying a smartwatch during the event, when competing in the CS:GO competition, that player will immediately be disqualified from the competition.
    • Alienware Wireless Headset AW988; Visual representation of audio isn’t allowed.
    • AR (augmented reality) glasses
    • Hardware from the brand “Bloody” (these are mice that come with software that reduces recoil on weapons)

    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.

    Back to top

    2.8 Match protests and forfeit

    2.8.1 Definition

    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.

    2.8.2 Match protest rules

    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.

    2.8.3 Forfeit rules

    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.

    Back to top

    2.9 Seeding

    Seeding is done through an objective outlook towards data provided by all participants for every event.
    Every participant is required to provide us their main steam account, ESEA and/or CEVO profile, FACEit level and previous wins/achievements.
    The supplied data is only kept and used for one event to calculate an individual “score” based on reached rank, played time, csgo hours and historical performance/achievements from Frag-o-Matic or other tournaments.
    The team sum of 5 individual scores will show an objective score where the higher the score, the higher the team seeding.
    The tournament admins won’t seed teams higher based on any subjective opinions.
    If no statistical data was provided for all 5 team member, than that team will be seeded beyond top 16.

    3. General


    3.1 General rules

    Frag-o-Matic Counter strike:Global Offensive (CS:GO) 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 csgo@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.

    Back to top

    3.2 Sanctions and disputes

    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.

    Back to top

    3.3 Confidentiality

    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.

    Back to top

    3.4 Code of conduct

    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 CS:GO 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 (CS:GO 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 CS:GO 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 CS:GO admin will be sanctioned with a warning.
    3 warnings are equal to a forfeit of 1 match.

    *A form of aggression is described as:

    • Instrumental aggression -- Aggression aimed at obtaining an object, privilege or space with no deliberate intent to harm another person. Typical of participants wanting to get ahead of the competition with lies, anger, bullying, criticizing other people behind their backs, leaving others out of a group or otherwise ostracizing them, turning people against each other, dismissing the opinions of others (passive aggression).
    • Hostile aggression -- Aggression intended to harm another person, such as hitting/kicking/biting someone (active aggression). Threatening to beat up someone (nonverbal intimidation). Sending threatening messages through emails, phone calls, or social media, or making threats against someone's life, shouting, and swearing (verbal hostility). Breaking someone's computer, destroying someone's cell phone, or other forms of vandalism (destruction of property).
    • Relational aggression -- A form of hostile aggression that does damage to another's peer relationships, as in social exclusion, gossiping or rumor spreading. Examples: Arguments within a team after a lose that lead to a verbal fight.


    Back to top

    3.5 Drugs and alcohol

    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.

    Back to top

    3.6 Betting

    Betting on any match in the CS:GO tournament is strictly forbidden.

    3.7 Additional agreements

    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.

    Back to top

    3.8 Streaming, interviews and media

    3.8.1 Broadcasting

    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 CS:GO server broadcasts a game.

    Back to top

    3.8.2 Match media

    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.

    Back to top

    3.8.3 Screenshots

    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 half 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.

    An RCON status screenshot must be taken:

    • at the beginning of the match
    • in case of a server/player change
    • if a player reconnects


    RCON status screenshots made with the help of programs like HLSW etc. are not sufficient.

    In order to take an RCON status you have to use the console command “rcon status” (don’t forget to enter your RCON password) and take a screenshot of that.

    Back to top

    3.9 Player changes

    Teams are permitted to substitute players (only with another player not active in the CS:GO 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’.

    Back to top

    3.10 Prize money

    When you subscribe to this competition you agree to our prize money policy: http://www.fom.be/contents/view/prizemoney-policy

    Back to top

     4. Counter-Strike:Global Offensive rules

    4.1 Tournament structure and time schedule

    Games will be scheduled to be played between 23:00 on Friday and 18:00 on Sunday. On Saturday and Sunday, teams must be present at 10:00 (AM) and ready to start playing the rest of their scheduled matches. It can be the case that the tournament admins decide to start earlier or end later, but this will be communicated (to all team captains). An exact time schedule will be provided on our fom.be website for all teams to follow.

    Each match will have a start time on which the game needs to be started. The team(s) that are responsible where the start time has not been met will receive a forfeit for that match. Whether or not this rule will be applied, is the decision of a tournament admin.

    The schedule for the tournament may be subject to change at any time. Matches may be rescheduled to a later time, delayed, postponed or cancelled at any time by the tournament admins without prior notice.

    Games will not be rescheduled to an earlier time in the same day if either of the teams have not yet played a game on that day without the consent of both team captains.

    Where possible the tournament admins will notify any teams involved in a rescheduled game of the new match start time at least one hour before the new start time. In the event a match is cancelled, the tournament admins will notify the teams involved as quickly as reasonably possible.

    If there’s insufficient time to complete a match, the tournament admins may at any time declare one team as the winner, if that team holds a clear advantage in that match. It is the responsibility of the tournament admins to decide whether a team holds a clear advantage. This rule will only be used in the emergency when the remaining event time is a factor.

    Back to top

    4.1.1 Penalties and forfeits during the time schedule

    If 1 or more teams are still playing a match in a previous stage or if 1 team is late and doesn’t start playing their match in the stage where they are; Teams are offered 30 minutes of grace time in both circumstances, after 30 minutes warnings are handed out:

    After 30 minutes that team, who’s still not playing their scheduled match, will receive a 1st warning from a tournament admin.
    A notice via our csgo channel on discord and if the team is present and found at their seat they’ll be warned in person as well.

    A second warning is given in the same manner 5 minutes after the first warning.

    A third and final warming is given in the same way 5 minutes after that.

    5 minutes after the final warning the team who received 3 warnings will receive 1 game loss for their match in the next round.

    In case of a bo3 in the next round, a bo2 will be played with one win to the team that was on time.
    If after 15 minutes the team with 3 warnings and one loss in the next round is still not playing, they’ll receive a forfeit from an admin.
    In case of a bo1 (in the lower bracket for example) we won’t lose any more time and a forfeit will be forced.
    The forfeit is applied on our fom.be website and a notice is given on Discord in our csgo channel.

    The tournament admins will keep a record of the warnings and will communicate this to the compo desk.
    As mentioned in our general rulebook; Non-acceptable excuses for a delay: “We want to eat” isn’t a valid excuses for starting an argument at the compo desk.

    As a note, we ask that teams only take a maximum of 15 minute breaks in between games and matches to avoid any penalties.

    Back to top

    4.1.2 Compo sign-up and max teams

    All compo sign-ups are done via our fom.be website. Some rules are already explained in our general rulebook. Any team that is not “full”, meaning the team doesn’t consist of minimum 5 players, will be removed from the compo sign-up one hour before the start of the competition.

    We allow a maximum 64 teams to register to our CS:GO competition.

    Back to top

    4.1.3 Structure

    Our CS:GO tournament will use a poule system and 3 double elimination brackets (pro, semi-pro and fun).

    Each poule will consist out of 3-4 teams who will compete against each other to make it into the brackets. Each team within the poule needs to play against any other team within its poule.

    Following the poule stage, the 2 winners from each poule will advance to a pro bracket, the  last 2 teams from each poule will advance to a semi-pro bracket and other teams will proceed to the fun bracket.

    Our compo structure will use the following setup for pro, semi-pro and fun:

    • Groupstage > BO1 (best of 1)
    • Upper Bracket > BO3 (best of 3)
    • Lower Bracket > BO1 (best of 1)
    • Pro & semi-pro bracket:
      • Semi-final (Finals in lower bracket) > BO3 (best of 3)
      • Final > BO3 (best of 3) with map advantage
    • Fun bracket:
      • Semi-final (Finals in lower bracket) > BO1 (best of 1)
    • Final > BO3 (best of 3) with map advantage

    When 2 teams have the same amount of points after the poules we will look at the following criteria in order:

    • The match between the 2 teams
    • The won rounds total
    • The lost rounds total
    • Seeding

    We can also look at other criteria if we feel that it's necessary (also cooperation). The admin is allowed to overrule these criteria. If there’s not enough data to validate a criteria the admin can chose to ignore it.

    A tournament admin can decide to change some matches from BO3 to BO1 or visa versa when needed. (For example: no time to play a BO3).

    Back to top

    4.1.4 Game setup

    Matches will be played 5on5. Playing with fewer than five players in any match is only allowed with permission from the tournament admins.

    Before a match starts, both teams must state that they are ready to start the match.
    The must do this by having one team member typing ‘ready’ in server chat.
    Should a player or a team have temporary problems, the opponent must be informed and the start must be repeated.

    Bugs due to map loading (e.g. missing boxes, ladders or similar) must be checked before the match starts and if they appear the map must be reloaded. You cannot protest after the match to complain about this type of bug.

    You’ll need to use the following match setup to play every game:


    • 2 teams join the server that is assigned to them on our fom website.
    • The team captains can use the RCON password “godmode” to follow the next steps :
      • Don’t forget to do ‘cl_mute_enemy_team 0’
      • Change the map to de_mirage (rcon changelevel de_mirage)
      • Load the Frag-o-Matic config (rcon exec fom5on5.cfg)
      • Start a knife round on de_mirage (optional). The winner of this knife round can decide who team A is. Start the map veto process (Veto is explained under ‘Veto system’’).
      • After the Veto the team captain needs to change the map to the first map of Team A (in a BO3) or the single map that was chosen (in a BO1) (rcon changelevel ‘mapname’)
      • Load the fom5on5.cfg again on this map. (rcon exec fom5on5.cfg)
      • After this the teams do another knife round to decide which team will start on which side of the map. The winner of the knife round decides which side they want to start on and that team will also start the match. (rcon mp_restartgame 1)

    If a player drops before the first kill has been made in the first round, the match will be restarted. If a player drops after the first kill has been made, the server can be paused at the end of the current round (see rule ‘Usage of pause’ function) by one of the teams.
    The waiting time for a dropped player is 10 minutes. If the player or a substitute rejoins the server and both teams are ready, the game can be resumed.
    If a player/substitute doesn’t connect within that time, then the match is continued 4on5, or 4on4 if the opposing team agrees and the tournament admins are informed.
    There are no forbidden weapons or grenades. Feel free to use all new weapons and grenades implemented in CS:GO.

    Back to top

    4.1.5 Veto system

    Our veto process is the next step after playing a knife round, as described in ‘Game setup’.
    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 A being decided by the winner of the knife round.
    Teams can also decide who team A/B is without playing a knife round.
    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-2: ABAB veto AB play.
    The map pool exists out of 7 maps.
    4 maps are vetoed during this process, 2 maps for each team.
    Out of the 3 remaining maps, 1 team each gets to decide a map to play on.

    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.

    Back to top

    4.1.6 Compo specific rules

    All matches in the group stage are played MR15. All matches in the brackets are played MR15 (meaning, 16 rounds won = game win).

    In the group stage, matches are played best of one (BO1) on a map decided by veto (as described above). All games are best of three (BO3) in the bracket, 3 maps are decided by veto. The grand final is a best of three (BO3) with map advantage!

    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 CS:GO players can only use our ts.fom.lan (local) teamspeak for voice communication.
    Teams are only allowed to have 5 players + 1 coach in their teamspeak channel whilst in a competition match.

    Back to top

    4.1.7 Usage of pause

    Pauses may be taken for any reason.

    Teams are permitted 3 pauses per side in each match.
    Each pause having a maximum duration of 5 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.

    Type the following commands in console, to activate and deactivate the pause event.
    Pause = rcon mp_pause_match
    Unpause = rcon mp_unpause_match

    Illegal usage:
    DON’T USE = sv_pause
    If a team does use sv_pause, they have to surrender 1 round. (by all team members typing “kill” in console)

    Back to top

    4.1.8 Demo files

    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.

    Back to top

    4.2 Match procedure

    4.2.1 Map list

    Only the following maps are allowed to be played on during the competition:

    • de_ancient
    • de_anubis
    • de_inferno
    • de_mirage
    • de_nuke
    • de_overpass
    • de_vertigo

    Back to top

    4.2.2 Match rules

    • Diffusing through walls, crates or any other object is not allowed. The bomb must always be fully visible when defusing.
    • Throwing grenades/flash bangs/smokes across walls in maps is allowed.
    • Boosting is not considered a bug.
    • Buying and using multiple grenades is allowed but with a max of 2 flash bangs.
    • Multiple grenades are allowed but max 2 flash bangs
    • Bugs on the map must be checked before the match begins. Any protest after the match about map bugs will be ignored.
    • If a player loses connection before the first kill, the match can be restarted. If this happens after the first kill, the server can be paused and have the disconnected player reconnect. Matches won’t be restarted due to disconnections.
    • If you want a player change (sub) during the match, inform the opponent and the compo admins before the match begins!
    • To boost through walls, ceilings or the ground, sky walking, map swimming, floating and sharking are all forbidden.
    • Climbing with help of teammates is allowed in general.
    • Throwing grenades inside walls is not allowed.
    • Self-kills are strictly forbidden, unless an admin forces you to do this as a sanction for disobeying any rules.
    • Bomb planting in a way it can’t be reached is forbidden.

    Back to top

    4.2.3 Client rules

    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.

    For NVIDIA graphics card users: The use of Ambient Occlusion is strictly forbidden. If you are caught using this setting, this will result in a direct loss of the match. Getting caught for a 2nd time will result in removal from the tournament. This setting can be found in your NVIDIA Control Panel > 3D Settings > Manage 3D settings.

    The following commands are forbidden:

    • mat_hdr_enabled

    The following startparameters are forbidden:

    • +mat_hdr_enabled 0/1
    • +mat_hdr_leven 0/1/2

    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.

    Boosting through walls/ceilings/ground, sky walking, map swimming, floating and sharking are all forbidden.

    To throw grenades inside walls is not allowed. Above walls and roofs is allowed.

    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.

    Back to top

    4.2.4 Illegal scripts

    In general, all scripts are illegal except for buy, toggle & demo scripts. Some examples of illegal scripts:

    • Stop Shoot scripts [Use or Awp scripts]
    • Center view scripts
    • Turn scripts [180° or similar]
    • No Recoil scripts
    • Burst fire scripts
    • Rate changers (Lag scripts)
    • FPS scripts
    • Anti flash scripts or binding (snd_* bindings)
    • Bunnyhop scripts
    • Stop sound scripts
    • Following Commands/CVars are forbidden
    • +weapon_recoil_model 0 (Startparameter)

    The following CVAR values must be used:

    • cl_bobcycle 0.98 (First Time->Warning)

    If there are more than one player who used a wrong client setting, the match will be deleted. Exception: cl_bobcycle

    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.

    Back to top

    4.2.5 Custom files

    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.

    4.2.6 Color depth and external programs

    The usage of a color depth of 16bit is not allowed.
    The usage of external programs (ex. SweetFX, A3D,...) are not allowed to enhance vision.

    Back to top

    4.2.7 Illegal programs

    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 (e.g. NVidia SLI Display, Riva tuner Overlays) 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.

    If you play with ambient occlusion, it will be punished as cheating!!

    Punishment will be given regardless of whether the script/binding is executed via external hardware or software.

    Also binding any snd_ command is forbidden.

    Back to top

    4.2.8 In-game overlays

    All In-Game overlays – provided by the game itself – except the following are forbidden:

    • net_graph 0
    • net_graph 1
    • cl_showpos 1
    • cl_showfps 1
    • cl_showdemooverlay 1 / -1

    Back to top

    4.2.9 Technical problems and disconnects

    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:

    • In the case where Frag-o-Matic is responsible for the disconnect, the round needs to be restored to the start of the round where the disconnection happened. I.e. follow the steps as described under “4.3.2 Server crash”.
    • When a player is responsible for his own disconnect, the team with 4 players can decide to continue to play 4v5 or use a pause as described in “4.1.6 Usage of pause”.
    • The disconnected player can then reconnect to the match. If that player fails to reconnect, then the match will continue 4v5.
    • If another Frag-o-Matic participant is responsible for causing a problem, then the match needs to be paused and a tournament admin needs to be notified to make a call on what to do.

    Back to top

    4.3 CS:GO server

    4.3.1 Server settings

    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 CS:GO and the official Frag-o-Matic CS:GO server config. All matches have to be played on an official Frag-o-Matic CS:GO tournament server and on the provided server number (as listed on our fom.be website, in the csgo compo section).

    We’ll use a standard (ESL) 5v5 pro league tournament config on a 128 tickrate server:

    • Startmoney: $800
    • Maxrounds:​ 30
    • Roundtime: 1​m 55s (1.92)
    • Freezetime:​ 12 seconds
    • C4timer: ​40 seconds
    • Pause:​ 1x 5minutes per half each map.
    • Overtime:​ MR3 - $10.000 startmoney
    • Time during half time:​ 13 seconds

    Back to top

    4.3.2 Server crash

    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 use the following command:

    • rcon mp_backup_restore_list_files

    This will show you the backup files before the server crashed.
    1 team captain then executes the correct file by using the following command:

    • rcon mp_backup_restore_load_file

    Example: rcon mp_backup_restore_load_file backup_round12.txt

    All previous settings (score, money, armor, weapons,...) are then reset to the round before the server crashed and the match is set to paused.

    To continue the match, use the unpause command:

    • rcon mp_unpause_match

    Back to top

    4.3.3 Server (var) lag

    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.

    4.3.4 Server plugins

    No extra plugins will be installed on our CS:GO servers.

    4.3.5 RCON usage

    RCON is only allowed as described in “4.1.2 Game setup”.
    Usage of RCON outside the game setup is penalised by receiving an instant forfeit for the team using any other RCON commands.
    We monitor all servers and RCON logs and will use this as evidence to hand out a match forfeit to the team using RCON outside of the game setup rules.

    4.3.6 Warmup servers

    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 csgo 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.

    5. Copyright Notice

    Copyright © 2005-2022 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 csgo@fom.be

CS GO Main Compo - Scheduling

Games will be scheduled to be played between 23:00 on Friday and 18:00 on Sunday.
Be ready on the given server before the scheduled start time with all 5 players!


Poule BO1 round 1 22.00-23.00
Poule BO1 round 2 23.00-00.00
Opening show 00.30-01.00
Poule BO1 round 3 01.00-02.00


Upperbracket BO3 round 1 10.00-13.00
Upperbracket BO3 round 2 13.00-16.00
Upperbracket BO3 round 3 16.00-19.00
Upperbracket BO3 round 4 19.00-22.00
Upperbracket BO3 round 5 22.00-01.00
Lowerbracket BO1 round 2 13.00-14.00
Lowerbracket BO1 round 3a 17.00-18.00
Lowerbracket BO1 round 3b 19.00-20.00
Lowerbracket BO1 round 4a 20.00-21.00
Lowerbracket BO1 round 4b 22.00-23.00
Lowerbracket BO1 round 5a 23.00-00.00
Lowerbracket BO1 round 5b 00.00-01.00


Semi-final (BO3) 10.00-13.00
Grand final (BO3) 13.00-16.00

Due to lack of time, we have a tight schedule.
Make sure to sign up your team for the CS:GO compo before the deadline.
Once the poules are over, there will be 2 brackets on www.fom.be (pro and semi-pro).
The semi-pro will continue in a new compo.
You will need to re-subscribe when asked.

After finishing the game, fill in your score IMMEDIATELY! The brackets will be automatically updated by the admins.