logo v19.1

Frag-o-Matic

19.1

Date

08/09 - 10/09

Participants

646/1000

CS:GO (5 vs. 5)

News

Head admin: SwAt

Admins: yookes, cpf

Usefull links :

  1. Infopage CS GO
  1. Seedings+ poules

Steamaccount to add as friend: 

  1. Steampage

 

 

 

Registration opens: 5 January 2016

Registration closes: 5 February 2016 at 21:00

Tournament starts: Friday 5 February 2016 at 23:00

CS:GO Semi-final and Finals

CS:GO Semi-final and Finals

CS:GO Scores

CS:GO Scores

CS:GO Poules to brackets

CS:GO Poules to brackets

CS:GO Semi-final and Finals

Only just a couple of hours remain at Frag-o-Matic 19.0 and we’ll host our semi- and grand final for CS:GO pro and semi-pro. Make sure to watch twitch if you want to ...

CS:GO Scores

Our server assign problem has been fixed, all servers should now be allocated correctly. If not, please let us know at the compo desk. We would like to remind you that ...

CS:GO Poules to brackets

The poule matches are behind us.   The first round of the bracket phase must start at 10:00!   For the teams that didn’t make it to the pro-bracket, a semi-pro ...

CS:GO subscription and start times

The sign-up for the CS:GO competition is available until 22:00.   If your team is already signed-up, please check-in at the compo desk before 22:00 (so that we know ...

Compo prizes FOM 19.0 announced!

All prizes are available on the compo pages! Grand  Competitions: CS:GO 5v5 LoL 5v5 Hearthstone 1v1 Rocket League 3v3 Normal ...

<< previous next >>

Poules

Best 2 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

Poule A

Standings W D L RW RL
1. I LOVE NANA 3 0 0 48 15
2. sectorONE 2 0 1 40 21
3. Qbyte 1 0 2 24 35
4. ShrimpRefuge 0 0 3 7 48

Poule E

Standings W D L RW RL
1. SD-gaming 3 0 0 48 3
2. AF9K 2 0 1 34 30
3. uSelesS 1 0 2 31 32
4. VICTORY! 0 0 3 0 48

Poule H

Standings W D L RW RL
1. mCon esports 3 0 0 48 5
2. ECVG3MIX 2 0 1 33 26
3. GeNeS!s 1 0 2 22 43
4. ARIUS GAM!NG 0 0 3 19 48

Bracket overview

Team A Team B Score Server
heXagon VS norga 0 - 1 -
I LOVE NANA VS LowLandLions 1 - 0 -
LowLandLions VS norga 16 - 10 -
heXagon VS LowLandLions 10 - 16 -
mCon esports VS LowLandLions 5 - 16 -
heXagon VS Groetjes Thuis 22 - 20 -
mCon esports VS Gypsy eSports 16 - 9 -
heXagon VS SD-gaming 22 - 20 -
KLEPxKLEP VS Gypsy eSports 13 - 16 -
Neolitis Belgium VS mCon esports 9 - 16 -
TEAM XAPSO VS SD-gaming 11 - 16 -
avenue esports VS heXagon 7 - 16 -
KLEPxKLEP VS mCon Lost in Translation 16 - 12 -
inVoked eSports CSGO VS Neolitis Belgium 14 - 16 -
TEAM XAPSO VS bad Mongos 16 - 11 -
venko-gaming VS avenue esports 14 - 16 -
mCon Lost in Translation VS Invoked.GODEN 16 - 9 -
Playcasters | ModMic VS KLEPxKLEP 5 - 16 -
Neolitis Belgium VS Amicitia Fortior 16 - 8 -
Slackers VS inVoked eSports CSGO 12 - 16 -
Ceaseless Six G2A VS bad Mongos 10 - 16 -
iV Ad Victoriam VS TEAM XAPSO 2 - 16 -
IV. Team Omnicron VS avenue esports 8 - 16 -
rodcad-gaming VS venko-gaming 6 - 16 -
mCon Lost in Translation VS AF9K 16 - 3 -
Playcasters | ModMic VS EYEBALLERS 19 - 16 -
mCon Female VS Neolitis Belgium 7 - 16 -
Slackers VS sectorONE 16 - 7 -
ECV.GASEROP VS Ceaseless Six G2A 11 - 16 -
iV Ad Victoriam VS GladiatorGaming 16 - 13 -
IV. Team Omnicron VS ECVG3MIX 16 - 10 -
MASSIVELIONS VS rodcad-gaming 0 - 1 -
I LOVE NANA VS norga 2 - 0 -
norga VS Groetjes Thuis 2 - 1 -
I LOVE NANA VS LowLandLions 2 - 1 -
Gypsy eSports VS Groetjes Thuis 0 - 2 -
norga VS mCon esports 2 - 0 -
LowLandLions VS SD-gaming 2 - 0 -
I LOVE NANA VS heXagon 2 - 1 -
Groetjes Thuis VS venko-gaming 2 - 0 -
avenue esports VS Gypsy eSports 1 - 2 -
mCon esports VS TEAM XAPSO 2 - 0 -
norga VS bad Mongos 2 - 0 -
SD-gaming VS inVoked eSports CSGO 2 - 0 -
LowLandLions VS Amicitia Fortior 2 - 0 -
heXagon VS KLEPxKLEP 2 - 1 -
I LOVE NANA VS Invoked.GODEN 2 - 0 -
venko-gaming VS AF9K 2 - 0 -
Groetjes Thuis VS mCon Lost in Translation 2 - 0 -
Gypsy eSports VS EYEBALLERS 2 - 0 -
avenue esports VS Playcasters | ModMic 2 - 0 -
TEAM XAPSO VS Neolitis Belgium 2 - 0 -
mCon esports VS mCon Female 2 - 0 -
bad Mongos VS sectorONE 2 - 0 -
norga VS Slackers 16 - 6 -
inVoked eSports CSGO VS Ceaseless Six G2A 2 - 0 -
SD-gaming VS ECV.GASEROP 16 - 3 -
GladiatorGaming VS Amicitia Fortior 0 - 2 -
LowLandLions VS iV Ad Victoriam 16 - 6 -
KLEPxKLEP VS ECVG3MIX 2 - 1 -
IV. Team Omnicron VS heXagon 0 - 2 -
Invoked.GODEN VS rodcad-gaming 2 - 0 -
I LOVE NANA VS MASSIVELIONS 2 - 0 -

TOTAL COMPO VALUES

Cash € 2200,00
Products € 3380,00

  • 5x SteelSeries QcK Black
  • 5x SteelSeries Rival 100 White
  • 5x SteelSeries Siberia 200 White
  • 5x ASRock Z97X Killer
  • Cash € 1200,00

 

  • 5x SteelSeries QcK Black
  • 5x SteelSeries Rival 100 White
  • 5x SteelSeries Siberia 200 White
  • 5x SteelSeries Apex Raw US
  • Cash € 600,00

‚Äč

 
  • 5x SteelSeries QcK Black
  • 5x SteelSeries Rival 100 White
  • 5x SteelSeries Siberia 200 White
  • Cash € 400,00

Rules

This rulebook is copyrighted.

Compo admins

  • Yookes

  • SwAt

  • CPF 

Contact

We will provide an information page for CS GO! Follow this page for updates!

We consider the one who registered the team into the compo on the Frag-o-matic website as captain!

The compo admins reserves the right to change these rules at any time.

General rules

General

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

  2. Teams which violate these rules will be sanctioned, and may be removed from the tournament without compensation. Such removal may also void any potential winnings for teams.

  3. Sanctions and disputes will be resolved by the main tournament admin . The admin’s decision on any sanction or dispute is final.

  4. Abusive behavior towards the Frag-o-matic staff, tournament admins or opponents at any time  is unacceptable and will be punished.

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

  6. In the beginning of the LAN (before the tournament starts) 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 through sending an email to compos@fom.be until 5 days before the event.

  7. The team captain must have read and understood the rules.

  8. The team captain is responsible for ensuring his team and players obey to the rules. Ignorance of the rules is not an excuse for rule violations.

  9. The team captain may choose at any time to nominate another player 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.

  10. All official communication between a competing team and the tournament admins must be conducted by the team captain.

  11. Clarification of any point in the rules is available from the tournament admins at any time during the tournament.

  12. Teams may be required to play any match on the stage. If so, teams will be notified at least twenty (20) minutes prior to the start time of that match.

  13. Frag-o-matic reserves the right to broadcast any match. Teams may not refuse such broadcasts

  14. In any situation not covered by these rules, the compo admins will make a decision. The compo admins’ decision is final.

  15. Excessive use (“spam”) of global written chat (say commands) in game is not allowed.

Players and Teams

  1. Teams are permitted to substitute players during pauses and between rounds. 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 on top of the page.

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

  3. Spectators are not allowed on the match server. Only tournament admins, shout casters and Source TV servers may be in spectator mode during a match.

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

  5. All players must play at their designated seats for all tournament games unless otherwise instructed by the tournament admins

  6. Only players registered for a team in the tournament may play for that team.

  7. Players registered for a team in the tournament may not play for any other team in the same tournament.

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

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

  10. Teams are permitted to change their tags between matches, but are not allowed to change their tags during a match.

  11. Duplicating (exactly or approximately) the tags used by another team in the tournament is not permitted.

  12. Team tags and player nicknames may not be offensive. Tournament admins reserve the right to reject any tag or nickname they deem inappropriate.

  13. As teams may be required to compete on the stage, it is required that all teams remove any offensive material from their desktops.

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

Game structure

General

  1. Frag-o-matic will use a poules system and a winner-losers bracket system.

  2. Map list:

    1. de_dust2

    2. de_inferno

    3. de_train

    4. de_cache

    5. de_mirage

    6. de_overpass

    7. de_cbblestone

  3. All matches are played MR15 and all overtimes are played MR3 with $10,000.

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

  5. Teams will continue to play overtimes until a winner has been found.

  6. If there is insufficient time to complete a match, the tournament admins may at any time declare one team 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 as an emergency measure.

  7. For the brackets a customized seeding system will be used to enhance fairness. More information can be acquired at the compo desk.

  8. Teams are permitted two (2) pauses per map in each match, each pause having a maximum duration of five (5) minutes.

  9. Pauses must occur before the start of a round (during buy-time). Any pauses after that are considered illegitimate and must be unpaused immediately until the round is finished.

  10. If a match is unexpectedly interrupted (for example, by a server crash, power failure or other technical fault), and cannot be continued, the round in progress will be replayed.

 

Poules

  1. Each poule will exist out of 4-6 teams who will compete against each other to make it into the brackets.

  2. All teams can earn points by winning or drawing a match.

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

    1. The match between the 2 teams

    2. The won rounds total

    3. The lost rounds total

    4. Seeding
      We can also look at other criteria if we feel that it’s necessary (this includes cooperation with the tournament admins). The admin is allowed to overrule these criteria. If there is not enough data to validate a criteria the admin can decide to ignore that criteria.

  4. You will need to follow the VETO rules as described in the section “Match progression”.

  5. You can find the structure of the poules on the FOM website.

  6. The poules will be BO1 through the whole poulefase.

 

Brackets

  1. Depending on the number of teams participating there will be a pro and semi-pro bracket.

  2. 16-32 teams will make it to each bracket. How many teams will make it to the semi-pro bracket will depend on the number of teams.

  3. Each bracket (pro or semi-pro) will consist of a double-elimination: Winners and losers brackets.

  4. The winners bracket will consist of all BO3 matches, with overtime. Unless there is a lack of time in which the admin will decide which matches will be BO1.

  5. The losers bracket will consist of all BO1 matches, with overtime.

  6. You will need to follow the VETO rules as described in the section “Match progression”

  7. You can find the structure of the brackets on the FOM website.

  8. Matches are played until the first team reaches 16 rounds won.

  9. The grand final is a BO3 with map advantage.

 

Match progression

  1. All vetoes need to be discussed over the all-chat in the server assigned for that match.

  2. This is how u start a match:

    1. When BO1:

      1. Each team can eliminate 3 maps (so 1 remains which will be played)

      2. Veto rules are ABBAAB (Team A bans, Team B bans, Team B bans, …)

      3. Team A is the team which is on the CT side of the ebot match (random).

      4. When there is no ebot a knife round (de_dust2) will decide who team A is.

      5. After the Veto is completed the servers needs to be set to the right map (the one that is left over)

      6. On that map a knife round occurs to decide the start side (CT or T) to start the match.

    2. When BO3:

      1. Each team can eliminate 2 maps (so 3 maps remain which will be played)

      2. Veto rules are ABBA (Team A bans, Team B bans, Team B bans, Team A bans). After team A picks his map of choice, following by Team B’s map of choice. The third map is the remaining map.

      3. Team A is the team which is on the CT side of the ebot match (random).

      4. When there is no ebot a knife round (de_dust2) will decide who team A is.

      5. After the Veto is completed the servers needs to be set to the right map (Starting with the map of choice of team A, following by the map of choice of team B and if a draw occurs the remaining map will be played)

      6. On that map a knife round occurs to decide the start side (CT or T) to start the match.

Time schedule

  1. The exact tournament timings will be announced once the number of competing teams is known.

  2. Games may be scheduled to be played between 23:00 on Friday and 18:00 on Sunday. It can be that the admin decides to start earlier or end later, but this will be communicated to all team captains.

  3. Each match will have a deadline and a suggested start time. When a team does not start at the given start time, the other team can ask for a forfeit. This forfait will only count if the deadline is not made. The deadline is made when the scores are filled in at the Frag-o-matic website at the time that was set by the admins.

  4. The schedule for the tournament is subject to change at any time.

  5. Games may be rescheduled to a later time, delayed, postponed or cancelled at any time by the tournament admins without prior notice.

  6. Games will not be rescheduled to an earlier time on the same day without the consent of both team captains.

  7. Where possible the tournament admins will notify any teams involved in a rescheduled game of the new game start time at least one (1) hour before either the new or the old starting time, whichever is first.

  8. In the event a game is cancelled, the tournament admins will notify the teams involved as quickly as reasonably possible.

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

 

Game rules

Match rules

  1. Defusing through walls, crates or any other object is not allowed. The bomb must always be fully visible when defusing.

  2. Throwing grenades/flash bangs/smokes across walls in maps is allowed (f.e. on de_dust2)

  3. Boosting is not considered a bug.

  4. SourceTV demos must be recorded for each match. It is the responsibility of both team captains to ensure that GOTV is recording.

  5. If any player alt-tabs out of the game and gets advantage in the game because of the flashbug, that player has to use the console command “retry” immediately after noticing this. Failure to do so will be considered as bug abuse and results in a forfeit loss.

  6. Frag-o-matic will supply servers for matches. All games related to the tournament will be played on these servers.

  7. Before a match starts, both teams must state that they are ready to start the match. Should a player or a team have temporary problems, the opponent must be informed and the start must be repeated.

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

  9. Server crash

    1. If Ebot : The match will be restored just after the latest round completed.

    2. If Warmod : If the server crashes before three rounds have been completed (in a half), the server must be restarted and the half’s score will be reset to 0-0.

    3. If the server crashes after the third round has been completed, the half must be restarted with start money set to 2000 and the score will be counted from the last completed round. The start money is set to 2000 and the team that lost the last round kills itself using “kill” in the console. This round does not count. The half continues with the following round. The start money has to be set to 800 again.

  10. 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 will be paused at the end of the current round.

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

  12. If the player, or a substitute player does not connect within that time then the match is continued 4on5, or 4on4 if the opposing team agrees.

  13. Players can be changed at any time but the opposing team and the admin has to be informed in advance. If necessary the game can be paused. This change may not take more than 5 minutes. After the waiting time the game can be also continued without the full team and the player can join in the running game. Changed players must be registered in the team with their Steam ID CS:GO and it’s recommended to do a status screenshot when a new player arrives on the server.

  14. There are no forbidden weapons or grenades. Feel free to use all new weapons and grenades implemented in CS:GO even the Molotov grenade and the revolver.

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

  16. To boost through walls, ceilings or the ground, sky walking, map swimming, floating and sharking are all forbidden.

  17. Climbing with help of the team mates is allowed in general. Not allowed are positions where textures disappear in walls or grounds if a special movement (e.g. a jump) is required.

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

  19. To plant the bomb in a way that it cannot be reached is forbidden. Violating this rule will result in the loss of that match.


 

Settings

 

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

    1. Stop Shoot scripts [Use or Awp scripts]

    2. Center view scripts

    3. Turn scripts [180° or similar]

    4. No Recoil scripts

    5. Burst fire scripts

    6. Rate changers (Lag scripts)

    7. FPS scripts

    8. Anti flash scripts or binding (snd_* bindings)

    9. Bunnyhop scripts

    10. Stop sound scripts

    11. Following Commands/CVars are forbidden

    12. +weapon_recoil_model 0 (Startparameter)

  1. The following CVAR values must be used:

    1. cl_bobcycle 0.98 (First Time->Warning)

  2. 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 can be found in your NVIDIA Control Panel > 3D Settings > Manage 3D settings.

  3. We prefer that everyone has their Steam ID for CS:GO (Steam ID CS:GO) entered in their profile. It’s not enough if a Steam ID of another Steam game is already entered but the one for CS:GO is not, even when they are exactly the same one.

  4. 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 advert 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.

  5. The usage of a color depth of 16bit is not allowed.

  6. All forms of cheating in matches are forbidden, and will result in an overall lose on the tournament. Possibilities for cheating in Counter-Strike: global offensive are for example all kinds of multihacks, wallhack, aimbot, colored models, No-Recoil, No Smoke, No Flash and sound changes.

  7. 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. It will be recognized as cheating. An example of this: Hardware from the brand Bloody (these are mice that come with software that reduces recoil on weapons )

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

  9. If you play with ambient occlusion, it will be punished as Cheating!!

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

  11. binding any snd_ command is forbidden.

  12. In the config folder you are only allowed to have config files. Pictures, Demos, Screenshots and zipped Files are forbidden.

  13. All In-Game overlays except the following are forbidden:

    1. net_graph 0

    2. net_graph 1

    3. cl_showpos 1

    4. cl_showfps 1

    5. cl_showdemooverlay 1 / -1

 

Media

  1. 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 severe penalties. 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 an admin is hindered in their work because of bad match media names then there can be consequences.

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

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

  4. An Rcon status screenshot must be taken:

    1. at the beginning of the match

    2. in case of a server/player change

    3. if a player reconnects

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

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

  7. It is recommended for all players to record point of view (POV) demos for the full duration of all matches without exception. A possible knife round is part of the first halve and should be recorded. As long as one of the players/teams is able to upload the knife round on admin request there will be no consequences for a missing knife round. Protests regarding missing knife rounds are not valid.

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

  9. If a protest is opened for a match, all match media need to be kept until the end of the event.

  10. Demos can only be requested up to a maximum of 30 minutes after a match via the admin.

  11. A demo request must state the side (CT or T) and the map, if more maps have been played.

  12. If a player or a team illegally aborts the match, they lose their right to demand demos.

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

  14. It is strictly forbidden to edit demos. If a demo is manipulated, it will be treated as missing demo.