logo v21.0

Frag-o-Matic 21.0

THE SPEED EDITION

Date

01/03 - 03/03

Participants

1000/1000

CS:GO (5 vs. 5)

News

Registration opens: Wednesday 10 August 2016

Registration closes: Friday 9 September 2016 at 21:00

Tournament starts: Friday 9 September 2016 at 23:00

 

This year we have a new Anti-cheat rule!

We will go back to Rcon this edition for the rest of the edition!

Pick an empty server. Rcon = godmode

- Exec esl5on5.cfg

- mp_restartgame 1

- Rules you can find in the rulebook

- Banlist you can find here

- Timeschedule you can find here

RIV4L LAN TOUR CS:GO winners

RIV4L LAN TOUR CS:GO winners

CS:GO Gungame by Tech Data

CS:GO Gungame by Tech Data

SteelSeries returns to FoM 21.0!

SteelSeries returns to FoM 21.0!

RIV4L LAN TOUR CS:GO winners

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

CS:GO compos: Structure & changes

Starting from Frag-o-Matic 21.0, we will be organizing a different main and fun compo from the start. Participants are encouraged to participate in the appropriate compo. ...

ING Counter-Strike: Global Offensive compo

ING will be joining the Frag-o-Matic farm as our biggest partner! ING will be providing the ING Counter-strike: Global Offensive compo (Grand Compo) with € 3500 in cash ...

<< 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 8
2. AF9K 2 0 1 33 35
3. KoS 1 0 2 31 44
4. ARIUS GAM!NG 0 0 3 23 48

Poule B

Standings W D L RW RL
1. ECV.MAESTRO 3 0 0 48 8
2. Wa'yaw 2 0 1 40 16
3. EBRIOSUS 1 0 2 16 32
4. Teun 0 0 3 0 48

Poule C

Standings W D L RW RL
1. LowLandLionsCSGO 3 0 0 48 4
2. Ka-Tet 2 0 1 35 30
3. iNFUUS 1 0 2 31 32
4. Team JUPSE 0 0 3 0 48

Poule D

Standings W D L RW RL
1. Venko 3 0 0 48 8
2. ONEFIFTY 1 1 1 34 31
3. Iv. FragCats 1 1 1 36 36
4. ELIASISNENBAAS 0 0 3 5 48

Poule E

Standings W D L RW RL
1. mCon esports 3 0 0 48 6
2. DigitalFire 2 0 1 34 30
3. Stonefire.io 1 0 2 27 41
4. GKUNTA 0 0 3 16 48

Poule F

Standings W D L RW RL
1. gr1mor 3 0 0 48 4
2. #FreeZurton 2 0 1 34 17
3. Laionair-Gaming 1 0 2 17 32
4. Vae Victus 0 0 3 2 48

Poule G

Standings W D L RW RL
1. m0 3 0 0 48 21
2. KoS Female 2 0 1 35 36
3. ECV.Legacy 1 0 2 34 42
4. 2unhinged 0 0 3 30 48

Poule I

Standings W D L RW RL
1. Ghetto k1ds 2 0 0 32 4
2. SD-Gaming Academy 1 0 1 20 16
3. Belgium e-SPort Team 0 0 2 0 32

Poule J

Standings W D L RW RL
1. Sector One.GO 2 0 0 32 3
2. IceWolves.Mix 1 0 1 18 17
3. My Little Proxy 0 0 2 2 32

Poule K

Standings W D L RW RL
1. Team WinFakt! 2 0 0 32 3
2. BrainPing 1 0 1 19 17
3. chinature esportherbs 0 0 2 1 32

Poule L

Team A Team B Score Starttime
GOPA VS ECV.420 1 - 16
Qbyte. VS ECV.420 8 - 16
Qbyte. VS GOPA 16 - 1
Standings W D L RW RL
1. ECV.420 2 0 0 32 9
2. Qbyte. 1 0 1 24 17
3. GOPA 0 0 2 2 32

Poule M

Standings W D L RW RL
1. bisshbash 2 0 0 32 6
2. Team.WanTapZ 1 0 1 21 16
3. Gateway Gaming 0 0 2 1 32

Poule N

Team A Team B Score Starttime
NovaSix VS Das Daf 16 - 1
S1.stk VS Das Daf 16 - 1
S1.stk VS NovaSix 16 - 2
Standings W D L RW RL
1. S1.stk 2 0 0 32 3
2. NovaSix 1 0 1 18 17
3. Das Daf 0 0 2 2 32

Poule O

Standings W D L RW RL
1. Leonid Gaming 2 0 0 32 0
2. Qbyte.Eagle 1 0 1 16 16
3. Frag Squad 0 0 2 0 32

Poule P

Team A Team B Score Starttime
Amazotics VS Iv Axis 16 - 12
KroepKoek VS Iv Axis 16 - 8
KroepKoek VS Amazotics 16 - 1
Standings W D L RW RL
1. KroepKoek 2 0 0 32 9
2. Amazotics 1 0 1 17 28
3. Iv Axis 0 0 2 20 32

Bracket overview

Team A Team B Score Server Starttime
m0 VS gr1mor 0 - 1 -
Venko VS I LOVE NANA 2 - 1 -
gr1mor VS I LOVE NANA 3 - 16 -
m0 VS gr1mor 8 - 16 -
gr1mor VS mCon esports 16 - 12 -
m0 VS ECV.MAESTRO 16 - 12 -
Team WinFakt! VS gr1mor 14 - 16 -
m0 VS LowLandLionsCSGO 16 - 14 -
Ghetto k1ds VS gr1mor 0 - 1 -
Team WinFakt! VS SD-Gaming Academy 16 - 5 -
Sector One.GO VS LowLandLionsCSGO 4 - 16 -
ECV.420 VS m0 14 - 16 -
Ghetto k1ds VS Leonid Gaming 16 - 5 -
Team WinFakt! VS bisshbash 16 - 6 -
Sector One.GO VS Qbyte. 1 - 0 -
ECV.420 VS Leonid Gaming Academy 16 - 13 -
DigitalFire VS Leonid Gaming 8 - 16 -
Team.WanTapZ VS Ghetto k1ds 0 - 16 -
Antwerp Addicts Green VS bisshbash 3 - 16 -
Qbyte.Eagle VS Team WinFakt! 1 - 16 -
Qbyte. VS KroepKoek 16 - 13 -
ONEFIFTY VS Sector One.GO 5 - 16 -
Leonid Gaming Academy VS S1.stk 16 - 9 -
Wa'yaw VS ECV.420 0 - 1 -
BrainPing VS DigitalFire 7 - 16 -
Team.WanTapZ VS Ka-Tet 19 - 17 -
Antwerp Addicts Green VS KoS Female 16 - 5 -
Qbyte.Eagle VS AF9K 2 - 0 -
Qbyte. VS #FreeZurton 16 - 5 -
NovaSix VS ONEFIFTY 5 - 16 -
IceWolves.Mix VS Leonid Gaming Academy 4 - 16 -
Amazotics VS Wa'yaw 8 - 16 -
I LOVE NANA VS Venko 0 - 2 -
ECV.MAESTRO VS Venko 0 - 2 -
I LOVE NANA VS mCon esports 2 - 1 -
Venko VS gr1mor 2 - 1 -
ECV.MAESTRO VS SD-Gaming Academy 2 - 1 -
LowLandLionsCSGO VS mCon esports 1 - 2 -
I LOVE NANA VS m0 2 - 1 -
gr1mor VS ECV.420 2 - 1 -
Venko VS S1.stk 2 - 0 -
SD-Gaming Academy VS Sector One.GO 2 - 0 -
ECV.MAESTRO VS KroepKoek 2 - 1 -
mCon esports VS Team WinFakt! 2 - 0 -
LowLandLionsCSGO VS bisshbash 2 - 0 -
m0 VS Ghetto k1ds 2 - 1 -
I LOVE NANA VS Leonid Gaming 2 - 0 -
ECV.420 VS DigitalFire 2 - 0 -
gr1mor VS BrainPing 2 - 0 -
S1.stk VS Ka-Tet 2 - 0 -
Venko VS Team.WanTapZ 2 - 0 -
Sector One.GO VS KoS Female 2 - 0 -
Antwerp Addicts Green VS SD-Gaming Academy 0 - 2 -
KroepKoek VS AF9K 2 - 0 -
ECV.MAESTRO VS Qbyte.Eagle 2 - 0 -
Team WinFakt! VS #FreeZurton 2 - 0 -
mCon esports VS Qbyte. 2 - 1 -
bisshbash VS ONEFIFTY 2 - 0 -
LowLandLionsCSGO VS NovaSix 2 - 0 -
Ghetto k1ds VS Leonid Gaming Academy 2 - 0 -
m0 VS IceWolves.Mix 2 - 0 -
Leonid Gaming VS Wa'yaw 2 - 0 -
I LOVE NANA VS Amazotics 2 - 0 -

Pro: min. total of €4000 cash

 

1st Place:

2nd Place:

3rd Place:

 

Semi Pro:

 

1st Place:

2nd Place:

3rd Place

 

Roccat Suora Keyboard

 

Roccat Kova

 

 

Roccat Taito

 

Rulebook CS GO 18.1

Contact

  • Before the LAN:

  • During the LAN :

    • The communication during the LAN will be trough steam or at the compo desk.

    • Steam account : http://steamcommunity.com/profiles/76561198249019782/

  • After the LAN :

    • See ‘Before the LAN’

Quick notes

  • This rulebook is copyrighted.

  • When you subscribe to this compo you agree with the agreements on the next page : http://www.fom.be/contents/view/prizemoney-policy

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

  • 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 decision. When a team refuses, we will remove them from the competition to make room for other teams.

General

  • 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. Such removal may also void any potential winnings for teams so removed.

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

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

  • 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 through sending an email to csgo@fom.be before September 5th 2016.

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

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

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

 

Tournament Structure and Schedule

  • The exact tournament structure will be announced once the number of teams competing is known.

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

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

  • The schedule for the tournament may be subject to change at any time.

  • Games 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 has 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 (1) hour before either the new or the old starting time, whatever is first.

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

  • Veto rules for the tournament:

    • 2 teams join the server.

    • The default map will be set to de_dust2 by the server.

    • A knife round occurs on this map. No lane obligated. You have 5 minutes to knife the other team. At the end, one team must be killed. The team that is responsible for not having a clear end-result, will forfeit the match. IT IS NOT ALLOWED TO PLANT THE BOMB (this will result in a lose. Go to the admin to proceed)

    • The last team standing can choose who starts the VETO (Veto is explained under “game structures”). The map of team A will be played first.

    • The server will automatically change to the right map.

    • Join the side where your teamname is mentioned.

    • Another knife round starts. The winner of this knife round can pick sides

    • After switching team sides or not the game starts.

Match Rules

  • The map list for the tournament is

  • All matches in the group stage are played MR15, . All matches in the brackets are played MR15, until 16 wins.

  • In the group stage, matches are played Best of One on a map decided by Veto (2 or 3 bans/team). All games are Best of One/three (Bo1/Bo3) in the bracket, decided by the VETO rules. The grand final is a best of 3 with map advantage!

  • Defusing 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 (f.e. on de_dust2)

  • Boosting is not considered a bug.

  • Buying and using multiple grenades is allowed but with a max of 2 flash bangs (rcon ammo_grenade_limit_flashbang 2).

  • GoTV demos must be recorded for each match. It is the responsibility of both team captains to ensure that GOTV is recording. If this is not the case then the admins will decide when a dispute occurs.

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

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

  • Maplist :

    • de_dust2

    • de_nuke

    • de_train

    • de_cache

    • de_mirage

    • de_overpass

    • de_cbblestone

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

  • 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 given server number.

  • A team must be on the server before the start time! Otherwise the other team can ask forfeit.

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

  • Spectators are not allowed on the match server. Only tournament admins may be in spectator mode during a match.

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

  • Pauses may be taken for any reason.

  • Teams can not unpause without the consent of the other team (forced by server).

  • Pauses will only be activated at the start of the next round. So make sure you ask for a pause the round before.

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

  • If a match is unexpectedly interrupted (for example, by a server crash, power failure or other technical fault), and cannot be continued, We will attempt to load the old round. When this is not possible the admin will decide if the match needs to be replayed, a half needs to be replayed or a winner is declared.

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

  • We will use ESL config on a 128 tick rate server.

  • 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 its necesarry (also cooperation). 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.

Teams and Players

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

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

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

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

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

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

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

Game structure

  • Frag-o-matic will use a pool system and a winner-losers bracket system.

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

  • Each team within the pool needs to play against any other team within its pool.

  • 16-32 teams will make it to the winner bracket system. How many teams will make it to the loser bracket system will depend on the number of teams.

  • The bracket system will work with a winner’s bracket and a losers bracket were a BO1/Bo3 (best of one/three) will be played. When a team wins 16 rounds he will win that map.

  • The map is chosen by an elimination of 2 map (when BO3) by each team wich map they don’t want to play followed by each team choosing a map from the remaining 3 maps they want to play. (VETO rules, so it is ABBA ban and AB pick .) The remaining map is the third map that needs to be played if both teams win a map. With 7 maps that can be played, 4 maps eliminated and 2 maps played the remaining map will the last map remaining.

  • For each map played in the pool (or bracket Bo1) the veto exists out of 3 map bans for each team. The remaining map is the map played in that round. This will be ABABBA VETO

  • These Veto rules are managed by the server. If not they need to be followed by the players.

Other

  • Frag-o-matic reserves the right to change these rules at any time.

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

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

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

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

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

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.

Demos

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

  • 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 the side (CT or T) and the map, if more maps have been played.

  • 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

Settings and cheating

Anti-cheating LAW

  • During the events we will not investigate cheats external to that event. When we discover someone cheating during the LAN event, that player and his team will be banned from the compo and the player will be also banned for the next 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 startdate of the event.

  • There needs to be enough evidence that that player is cheating and the compo admins will judge if the evidence is enough or not. OR caught cheating on the next platforms :

    • Faceit

    • Esl

    • Valve (vac ban for any counterstrike 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.

  • Everyone may sent evidence to csgo@fom.be when they suspect someone of cheating.

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]

    • Jumpthrown 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

Game Account

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

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

Color depth and external programs

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

  • The usage of external programs (ex. SweetFX) are not allowed to enhance vision.

Cheating

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

  • 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 )

 

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.

Content of the Config folder

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

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

 

Match rules

Server choice

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

  • Players and teams have to agree on a server that offers both sides an equal ping. Nevertheless every player should know, that they will sometimes have to play with a bigger ping difference. In this case we have to appeal to the sportsmanship and fairness of the players and teams. The right to change server or fake lag does not exist.

Nickname and clan tag

  • Each player has to use a nickname that is at similar to the nickname he/she entered on the Frag-o-matic registry page. You are not allowed to change your nickname in-game. In team matches the players are allowed to use a clan tag, but it has to be the same for all players of this team. However you cannot file a protest or write a support ticket to complain if your opponent breaks this rule.

  • If an admin’s job is hindered because of wrong or difficult nicknames or clan tags, the team will get a warning.

Warmup

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

Map check

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

Match Broadcasting

  • All forms of game broadcasting are allowed if both sides agree. If one side wants to broadcast a match, the details of the broadcast should be discussed before the match takes place. Further details can be found in rule 1.4 Game Coverage.

GOTV delay

  • If GOTV broadcasts a game, the delay has to be 90 seconds or more.

GoTV

  • It is legal to broadcast a match via GoTV as longs as one team wants to do so and is able to provide the necessary server. Any other kind of broadcast is legal if both teams agree on it. If you want to broadcast a match please discuss it with your opponent in advance. For further information please check 1.4 Game Coverage. However you are obliged to upload an rcon status (and TV status) screen that shows the necessary delay of at least 90 seconds.

Number of players

  • Following terms of minimum number of players are: m4on4, 4on5 and 5on5 is allowed.

  • If one player in a team is missing the team can play the match nonetheless. The opposing team can decide freely whether they want to play with all players or with one player less as well.

Player drop

  • 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 (see rule Usage of Pause function).

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

Change of players

  • Players can be changed at any time (only if the previouse player is unable to play) but the opposing team and the admin has to be informed in advance. If necessary the game can be paused (see rule Usage of Pause function). This change may not take more than 10 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.

Forbidden weapons or grenades

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

Bugs and forbidden actions

  • 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, sky walking, sharking

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

Climbing

  • 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. For example the barbed wire fence in prodigy and nuke upper hall roof.

Grenades

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

Self-kills

  • Self-kills by console or by other means (e.g. Abysses) in order to receive money quickly or in order to shorten the round time is strictly forbidden.

  • Any bug-using is forbidden.

Bomb

  • To plant the bomb in a way that it cannot be reached is forbidden. Places that can reached with help of a team mate are allowed. Violating this rule will result in the deduction of 3 rounds.

Illegal graphic settings

  • Changing graphic settings to irregular values can be punished.

Illegal scripts

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