Frag-o-Matic 25.0

Contact

Before FOM : swat@fom.be

During FOM : steam account : compo_admincsgo

After FOM : swat@fom.be

Part 1 : 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 so removed.

3. Sanctions and disputes will be resolved by the main tournament admin SwAt (swat@fom.be).

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 during the tournament 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-party the team captains will sit together with the compo leader to discuss the rules to make adjustments if needed. The decisions are made by the compo leader. U can explain problems within the rules trough mail before 27th of February 2014. Mail : swat@fom.be.

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

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

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

Tournament Structure and Schedule

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

2. Games may be scheduled to be played between 23:00 (start time) Friday and 01:00 (scheduled end time of the last game) on Saturday and between 8:00 (start time) and 15:00 (scheduled end time of the last game) on Sunday. It can be that the admin decides to start earlier or end later. This year the pools will start Friday 23:00.

3. Each match will have a deadline and a suggested startime. When a team does not start at the giving starttime the other team can ask for a forfait. This forfait will only count IF the deadline is not made. The deadline is made when the scores are on the FOM website at the time that we give.

4. The schedule for the tournament may be 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 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.

7. 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, whichever is earlier.

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

9. Example :

9.1 Teams do not agree who starts in veto round.

- 2 teams join the server.

- One of the captains of the teams set the server to De_dust2!

- A knife round occurs on this map on A long (during this round guns or grenades are not allowed).

- The last team standing starts the Veto as explained under "game structure". The first map that is played is decided by the team that wins the knife round OR  , for the poules , because its the only map left.

- One of the teamcaptain changes the server to right map.

- The winning team of the last kniferound joins CT and the other teams joins T

- Another kniferound starts. The winner of this kniferound can pick sides

- After switching teamsides or not the game starts

9.2 Teams do agree on who can start the veto 

- 2 teams join the server and start the VETO for wich map(s) will be played

- The team that starts the VETO first can play their map first.

- One of the teamcaptain changes the server to right map.

- The  kniferound starts. The winner of this kniferound can pick sides.

- After switching teamsides or not the game starts

Match Rules

1. All matches in the group stage (pools) are played MR15, each team plays 15 rounds as Counter-Terrorists and 15 rounds as Terrorists on the map in the pools.  All matches in the brackets are played MR15 , until 16 wins.

2. In the group stage, matches are played Best of One on a map decided by Veto (2 or 3 bans/team) . During the play-offs, a single elimination tournament structure is used. 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 without  map advantage!

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

5. Throwing grenades/flashbangs/smokes across walls in maps is allowed (f.e. on de_dust2_se)

6. Boosting is not considered a bug.

7. Buying and using multiple grenades is allowed but with a max of 2 flashbangs (rcon ammo_grenade_limit_flashbang 2).

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

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

The map list for the tournament is:

de_dust2

de_inferno

de_nuke

de_train

de_mirage

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 and the opponent team.

10. 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 giving server number.

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

12. A team must be on the server before the startime! Otherwise the other team can ask forfait. In case that the deadline is not made the team who was to late will get forfait!

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

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

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

16. Pauses may be taken for any reason.

17. Teams are not permitted to unpause a match without consent from the other team in that match unless those 5 minutes are over.

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

19. 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. U can notice this to the admin by using the contact information on top of the page.

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

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

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

23. We will use esl config on a 128 tickrate server.

Teams and Players

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

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

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

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

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

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

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

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

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

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

1. Each pool will exist out of 6 teams who will compete against each other to make it into the brackets.
2. Each team within the pool needs to play against any other team within the pool. 
3. 16 teams will make it to the bracket system.
4. 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.
5. The map is chosen by an elimination of 2 maps by each team witch map they don’t want to play followed by each team choosing a map from the remaining maps they want to play. (VETO rules , So it is AB. ) The remaining map is the third map that needs to be played if both teams win a map. With 5 maps that can be played, 2 maps eliminated and 2 maps played the remaining map will the last map remaining.
6. For each map played in the pool the veto exists out of 2 map bans for each team. The remaining map is the map played in that poolround.Here is will be ABBA VETO

Pool system:

We are still considering wich system we will use and what the website allows us to use. This will be announced in time before the poules start.

Other

1. Frag-O-Matic reserves the right to change these rules at any time.

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

3. Frag-O-Matic reserves the right to broadcast any match. Teams may not refuse such broadcasts.

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

5. For NVIDIA graphicard users :

The use of Ambient Occulsion is strictly forbidden. Caught using this setting will result in a direct lose 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.

Part 2 : Rules

 

1. Match Media

All match media (screenshots, demos, etc) must be kept until the end of the event. Faking or manipulating match media is of course 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 it can be punished for.

1.1. Screenshots 

The admin can ask for screenshots of every game on any moment during the event. When he does this the teamleader has 15 minutes time to deliver the screenshot to the admin.

 

1.1.1. Score screenshot

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.

 

1.1.2. Rcon Status screenshot

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

 

1.2. 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 the admin decided, if it also will be treated as missing demo. 

If a protested is opened for a match, all matchmedia need to be kept for at least until the end of the event.

 

1.2.1. Requesting Demos

Demos can only be demanded 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.

 

1.2.3. Editing Demos

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

 

2. Settings

2.1. Player settings

2.1.1. 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 clientsetting, the match will be deleted. Exception: cl_bobcycle

 

2.1.2. GameAccount 

It's mandatory that everyone have their SteamID for CS:GO (SteamID CS:GO) entered in their profile. If a player haven't one or a wrong one in their profile the player/team will be punished. It's not enough, if a SteamID of another Steamgame ist allready entered but the one for CS:GO, even not, when the are exactly the same one. If there are transposed digits in the Gameaccount, the Admin Team will decide from case to case if there is a need for a punishment.

 

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

 

2.1.4. Color depth

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

 

2.1.5. Cheating 

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

 

2.1.6. Illegal programmes

2.1.6.1. Config changes - Videocard drivers or similar tools

Changing the game graphics or textures with the help of videocard drivers or similar tools is illegal. Furthermore any kind of overlay that displays the system performance while playing (e.g. Nvidia SLI Display, Rivatuner Overlays) is illegal. Failure to comply with this rule will result in 6 penalty points 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.

 

2.1.7. Content of the Configfolder 

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

 

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

 

3. Match rules

3.1. Before the match

3.1.1. Server choice 

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

 

3.1.2. Nickname and clan tag

Each player has to use a nickname that is at similar to the nickname he/she entered on the FOM 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.

 

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

 

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

 

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

 

3.1.5.1. SourceTV delay 

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

 

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

 

 

3.2.1 Number of players 

Following terms of minimum number of players are:

4on4, 4on5 and 5on5 is allowed. If one player in a team is missing the team can nevertheless play the match. The opposing team can decide freely whether they want to play with all players or with one player less as well.

 

3.2.2. Server crash

When the server crashes all rounds without a screenshot will be played again. For example when a team takes a screenshot after the 15^th round and the 18 round the server crashes then the rule applies that the second half must be played again from the start.

Only the screenshots during the half and on the end counts.

 

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

 

3.2.5. Change of players 

Players can be changed at any time but the opposing team and the admin has to be informed in advance. If necassary the game can be paused (see rule Usage of Pause function). 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 SteamID CS:GO and it's recommended to do a status screenshot when a new player arrives on the server.

 

3.2.6. Usage of Pause function 

If you have a problem that prevents you from playing on, you are allowed to use the pause function. The pause function has to be used at the beginning of the next round (freezetime). You have to announce the reason before or immediatly after you used it. If no reason is given, you may unpause the game and continue playing. Unpausing or pausing the game without any reason will be punished.

 

3.2.7. Abortion of a map after 16 victorious rounds 

If a team achieves 16 won rounds at a map, the teams can abort this map. All missing rounds of this map will then be added to the team that stayed on the server.

 

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

 

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

3.3.1. Bomb

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

 

4.1. Illegal graphic settings

Changing graphic settings to irregular values can be punished.

 

4.2. 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/scipts in any and all forms will be punished with 6 Penalty Points after the first violation without active usage and 12 Penalty Points after repeated violation or after active use of them.

 

Regardless of active use, if these Scripts are found in parts or in full in your configfile, this will be penalized.