Tournament Rules and Regulations

The rulebook lives on GitHub, where you can track changes and see the full update history.

Jump to section
  1. 1 Registration Regulations
  2. 2 General Attendance Rules
  3. 3 Broadcast and Media
  4. 4 Event Rules
  5. 5 Penalties
  6. 6 Tournament Administration
  7. 7 Definitions and Key Terms

1 Registration Regulations

1.1 Registration Payment/Fee

  • 1.1.1 All attendees must register through the official Frag website (https://frag.to), or through an advertised partner as listed for certain events.

  • 1.1.2 Unless advertised as an invitational event, all Frag events are open to the public with no qualification events.

  • 1.1.3 Team tickets are non-transferable and non-refundable. Purchaser of team ticket MAY NOT resell or request refund of a Frag Team Ticket.

  • 1.1.4 Upon ticket purchase completion, ownership of the ticket is assigned to the designated team captain.

  • 1.1.5 If the team you are signing up with has a VRS ranked core, you must provide the name of the core as it is on the VRS rankings. If you will be playing in the tournament under a different name, you may also provide that.

1.2 Roster Submission Guidelines

  • 1.2.1 During ticket purchase, purchasers will be prompted to designate the team captain. The team captain must be a player from the team's Frag core.

    • 1.2.1.1 Team captains have 1 week after they receive a Team Form to submit a Frag core of 3-5 players. After this 1 week period, these players are locked as the Frag core. Failure to submit a Frag core within the 1 week period will result in penalty.
    • 1.2.1.2 Designated captains can request the captain role to be transferred at any time.
    • 1.2.1.3 Teams are required to play all matches with a minimum of 3 or a majority of their submitted Frag core.

  • 1.2.2 Frag rosters will lock 17 days before the tournament. Changes to the team's submitted Frag roster cannot be made after this 17 day period.

    • 1.2.2.1 If a team cannot attend they must inform Frag using the Discord ticket system before the 17 day roster lock. If a team fails to inform Frag of their inability to attend after the 17 day roster lock, the submitted Frag roster will be seeded into the tournament and all matches will be recorded as forfeits.

  • 1.2.3 Any roster change that does not break a team’s Frag Core, can be made before the roster lock. Players added through a roster change will not count towards the Frag Core. You must play each match with your Frag Core except in the case of a provable medical emergency.

  • 1.2.4 If participation majority as stated in 1.2.1.3 is not affected, teams can submit roster additions at check in of the event. These additions will incur a fee of 1/5th of a full price team pass per player.

1.3 Roster Limitations

  • 1.3.1 There are no limitations on gender or region for rostered players. All are welcome at Frag.

1.4 Substitutions

  • 1.3.1 A team may make a substitution in-between matches for any reason, but they must maintain a majority of their Frag core except in the case of a provable medical emergency.

  • 1.3.2 A team may make a substitution during a match or in-between maps only in the case of a provable medical emergency.

    • 1.3.2.1 Emergencies will be determined at the Head Admin's discretion.

  • 1.3.3 Once a substitution has been made, the team may continue to play with the substitute player until they choose to revert to their submitted roster.

  • 1.3.4 Once a team returns to their original roster, they may not use any more substitutions except in the case of another provable medical emergency.

1.5 Check In

  • 1.4.1 Teams may be required to present payment receipt and/or verification when checking in.

  • 1.4.2 All players must carry a valid Government issued photo ID for verification purposes.

  • 1.4.2 A team's Frag core must be present for check in.

  • 1.4.3 Check in times are scheduled in a manner to ease traffic at the check-in table. Teams that arrive early will be asked to wait until their scheduled check in time.

  • 1.4.4 Teams must wait for seating assignments before setting up. When checked in, teams will be assigned seating.

2 General Attendance Rules

2.1 Participants Guideline

  • 2.1.1 The following actions may carry penalties ranging from an immediate and permanent ban from all Frag events to involvement of local authorities. These rules apply to all attendees, including (but not limited to) players, spectators, media, press, and staff.

    • 2.1.1.1 Attendees will not engage in hate speech, or verbal abuse related to sex, gender identity and expression, sexual orientation, race, ethnicity, disability, or religion.
    • 2.1.1.2 Weapons are prohibited at Frag events at the discretion of event staff.
    • 2.1.1.3 Attendees will not engage in any form of harassment or intimidation.
    • 2.1.1.4 Attendees will not engage in any type of theft or scam during the event.
    • 2.1.1.5 Attendees will not disrespect or intentionally disrupt event production during the event.
    • 2.1.1.6 Attendees will not enter restricted areas during the event.
    • 2.1.1.7 Attendees shall be responsible for all costs associated with any items damaged or destroyed by said attendee, including (but not limited to) equipment owned or rented by Frag, or any equipment owned or rented by the venue hosting the event.

  • 2.1.3 Attendees shall NOT disrupt players while games are being played, including (but not limited to) verbal and physical interruptions or tampering with players’ equipment.

  • 2.1.4 Attendees shall NOT share or relay any information about a live match to players participating in any match.

  • 2.1.5 All attendees must adhere to venue policies as well as the rules defined in this section. Venues may have penalties that differ from Frag’s enforceable at the venue staff’s discretion.

2.2 Bag Policy

  • 2.2.1 Only rostered players will be allowed to bring bags into the venue. All other attendees will not be allowed to bring bags into the venue. All bags are subject to search before entry.

2.3 Laws

  • 2.3.1 All attendees must adhere to local laws and regulations.

2.4 Confidentiality

  • 2.4.1 All communication with officials and admins, whether verbal or written, is strictly confidential and may not be shared without the written consent of Frag.

2.5 Age Restriction

  • 2.5.1 There is no age restriction for players. Players under 18 years of age may participate if accompanied by a legal guardian or with written consent from a legal guardian.

3 Broadcast and Media

3.1 Broadcast Rights

  • 3.1.1 The restream, rebroadcast, or redistribution of any part of a Frag event is strictly prohibited without the express written consent of Buck Ten LLC.

  • 3.1.2 All broadcasting rights of Frag are owned by Buck Ten LLC. This includes, but is not limited to: bots, shoutcast streams, video streams (e.g. POV-streams), CSTV, replays, demos, and TV broadcasts.

  • 3.1.3 All broadcast elements (not including the game itself or partner advertisements) are the intellectual property of Frag and the usage of said elements without the written consent of Buck Ten LLC is prohibited.

  • 3.1.4 Players shall not stream their POV without prior approval from Frag.

3.2 Media Obligations

  • 3.2.1 By registering for a Frag event, all players and coaches are required to participate in any broadcast content and media if requested by event staff. Players who decline will incur a penalty to their team’s prize money.

3.3 Media Usage and Licensing

  • 3.3.1 All media recorded within the venue of a Frag event is owned by Frag. If a license is purchase for any media, ownership of the licensed media will default to shared ownership, but full ownership can be negotiated.

  • 3.3.2 Usage for all media posted in an official event album by staff photographers is free if all requirements are met. Requirements for free usage are:

    • No altering of the media.
    • No hateful usage of the media.
    • No removal of a watermark except if being used as a profile picture on social media platforms.
    • No for-profit usage of the media. Meaning no addition of sponsor logos and branding or using the media in a way that generates ad revenue such as YouTube thumbnails.

  • 3.3.3 A license for any media available under the free usage rule can be purchased by contacting the Head of Media through the Discord ticket system. Owning a license grants the licensee the right to alter licensed media, own a copy of the licensed media without a watermark, and use the licensed media for-profit.

    • All licenses are non-refundable.
    • Any hateful usage of media will result in the loss of the license.

4 Event Rules

4.1 Roster/Player Details

  • 4.1.1 All player aliases will be used as submitted on the team form. Players will not have the ability to change their alias once the tournament has begun.

  • 4.1.2 All player Steam IDs shall be submitted in the STEAMID64 format in the roster submission form. Teams who fail to properly submit information in the team form may be subject to penalties.

  • 4.1.3 Player 1 on the team form will be designated as Team Captain and will be responsible for representing their team during all event processes.

  • 4.1.4 Team logo submissions are subject to approval. Teams who fail to submit a logo may have one chosen for them by tournament staff. If a logo is not accepted, teams will be given one chance to submit a replacement before the event.

4.2 Peripheral Requirements

  • 4.2.1 Participants are required to bring their own peripherals including mouse, keyboard, mousepad, headset, and in-ear monitors or earbuds that fit under a standard pair of over-ear headsets. In the event of a peripheral breaking, Frag is not responsible for providing a replacement.

4.3 Time-outs

  • 4.3.1 All teams are given 3 tactical time-outs for the regulation rounds of each map . All forms of communication are allowed during a tactical time-out.

    • 4.3.1.1 At the start of overtime, all existing tactical timeouts saved from regulation are removed. Each team is awarded one tactical timeout for each overtime period.

  • 4.3.2 All teams are given the ability to activate technical time-outs during any freeze-time. All forms of communication except communication with an admin are prohibited during technical time-outs, and will result in a penalty.

    • 4.3.2.1 All technical timeouts require a clearly stated reason in all chat by the team that initiates it and must be acknowledged by a match admin before being ended.

4.4 Coaching

  • 4.4.1 Depending on available hardware, coaches may or may not have access to team communications. In the event that a coach does not have access, they are not permitted to interact verbally with the team at any point during a live match.

  • 4.4.2. If a coach is provided access to team communications, they will only be allowed to speak to players during the team’s allotted tactical time-outs (3 per map). Any communication outside of tactical timeouts will result in penalties.

4.5 Event Formats and Active Maps

  • 4.5.1 The format of Frag events are subject to change (e.g. GSL, Swiss, Double Elim Bracket).

  • 4.5.2 Unless otherwise specified, all matches will be a Best of 3 maps.

  • 4.5.3 Unless otherwise specified, all map vetoes will be done in the game server using the integrated veto system.

    • 4.5.3.1 Broadcast/Stage matches will be subjected to manual vetoes completed by the admin staff on site with team captains.

  • 4.5.4 The veto format is as follows:

    • 4.5.4.1 Teams A and B are chosen by the higher seeded team.
    • 4.5.4.2 For a Best of 1:
      • Team A Bans
      • Team B Bans
      • Team A Bans
      • Team B Bans
      • Team A Bans
      • Team B Bans
      • Remaining Map, Knife For Sides
    • 4.5.4.3 For a Best of 3 series:
      • Team A Bans
      • Team B Bans
      • Team A Pick Map
      • Team B Select Side
      • Team B Pick Map
      • Team A Select Side
      • Team A Bans
      • Team B Bans
      • Remaining Map, Knife For Sides
    • 4.5.4.4 For a Best of 5 series:
      • Team A Bans
      • Team B Bans
      • Team A Pick Map
      • Team B Select Side
      • Team B Pick Map
      • Team A Select Side
      • Team A Pick Map
      • Team B Select Side
      • Team B Pick Map
      • Team A Select Side
      • Remaining Map, Knife For Sides

  • 4.5.5 Frag events will use the current active duty map pool as decided by Valve.

4.6 Third Party Programs and PC Security Protocols

  • 4.6.1 The use of any software that could be used for cheating is strictly forbidden. The Head Admin shall have sole discretion in deciding what software is allowed.

  • 4.6.2 The head admin reserves the right to use any method they deem necessary to inspect participants and their equipment, with or without prior notice. Participants are not allowed to refuse these inspections.

  • 4.6.3 Players may not use programs that will alter or change the default coding of the game.

  • 4.6.4 All players must use the computers and monitors supplied by Frag. No other computers or monitors may be used for any purpose.

4.7 Seeding Formula and Placement

  • 4.7.1 Events are seeded by the VRS World then Regional Ranking. Once all VRS ranked teams are seeded, the Head Admin evaluates the following criteria, in no particular order, to determine the most fair seeding for the remaining teams: current league status, LAN experience, league history, faceit elo.

  • 4.7.2 Frag uses a “snake” method for group stage seeding. If there are not enough teams to fill every group, some teams may be given a BYE based on seeding, with priority given to higher seeded teams.

  • 4.7.3 The Head Admin shall be responsible for notifying teams if there is a change in seeding and/or check-in time. Failure to check-in may result in removal from the event and counted as a forfeit loss.

4.8 Event Disruptions

  • 4.8.1 In the event that a player is unable to play in a round due to PC crash, game crash, or other issue beyond the player’s control, the Match Admin may use Match Medic to roll back the match to the start of the round in which the issue occurred.

    • 4.8.1.1 In the event that a player is unable to play due to a technical failure as listed in 3.5.1., their teammates may type “Not Live” or “NL” using the in-game chat. If the opposing team responds with “Not Live”or “NL”, then both teams must return to their designated spawn areas of the match and wait for the round to end, at which point they may contact a Match Admin to use the Match Medic feature. If a failure occurred before damage was done and the team calls “Not Live”, the round will be reverted back once the player is back in the server.
    • 4.8.1.2. If any player in the match has taken any amount of health damage before “Not Live” or “NL” is typed, then they must continue to play out the round.
    • 4.8.1.3. Match Admins have the final say as to whether or not Match Medic will be used.

  • 4.8.2 Match and map start times may be moved. The Admins will communicate any changes to team captains.

4.9 Match Settings

  • 4.9.1 The match settings are configured as follows:
    • Rounds: 24 (mp_maxrounds_24)
    • Round Time: 1 minute 55 seconds (mp_roundtime 1.92)
    • Start Money: $800 (mp_startmoney 800)
    • Freeze Time: 20 seconds (mp_freezetime 20)
    • Buy Time: 20 seconds (mp_buytime 20)
    • Bomb Timer: 40 seconds (mp_c4timer 40)
    • Overtime Rounds: Best of 6 (mp_overtime_maxrounds 6)
    • Overtime Start Money: $12,500 (mp_overtime_startmoney 12500)
    • Round Restart Delay: 5 seconds (mp_round_restart_delay 5)
    • Break During Half Time: 15 seconds (mp_halftime_duration 15)

5 Penalties

5.1 Player Form Submission Failure

  • 5.1.1 Teams that fail to submit their team form properly and on time may incur the following penalties: loss of bans during map vetoes and loss of picks during map vetoes.

5.2 Punctuality

  • 5.2.1 Teams that do not arrive at their scheduled check-in time will incur the following penalties:
    • 15 minutes late = Loss of map veto
    • 30 minutes late = Loss of map veto and forfeiture of map 1
    • 60 minutes late = Loss of series

5.3 Failure to Start Match On Time

  • 5.3.1 Teams that fail to have all players in the server and at their desks will have two tactical timeouts removed.

  • 5.3.2 Teams that have all players in the server and at their desks but have not marked their team as ready will have one tactical timeout removed.

  • 5.3.3 If an admin discovers that a team is abusing technical timeouts for any reason a tactical timeout will be removed in place of the technical timeout used.

  • 5.3.4 If a team abuses the ability to use technical timeouts repeatedly, they will lose all tactical timeouts for the remainder of the current stage of the tournament.

5.4 Communication Violations

  • 5.4.1 Speaking during technical time-outs will be punished as follows:

    • 5.4.1.1 Talking during technical time-outs to anyone but the admin will first result in a verbal warning. Every instance of the rule being broken after the initial verbal warning will incur the loss of one tactical timeout. If a team has used or lost all tactical time-outs, the team will only be given one warning followed by the loss of their ability to use tactical time-outs for the remainder of the event and the immediate and permanent removal of their coach from the tournament.
    • 5.4.1.2 Teams without coaches found to be speaking with each other during technical timeouts will incur the same penalties as a team with a coach would, including a final verbal warning before the loss of their ability to use tactical time-outs for the remainder of the tournament.

5.5 Repetitive Issues

  • 5.5.1 Players and/or teams who repeatedly break rules or receive penalties may face temporary or permanent bans from Frag events or be fined prize money at the discretion of the Head Admin.

5.6 Penalty Disputes

  • 5.6.1 Any player or team that wishes to dispute a penalty must do so on site with a member of the Frag Management.

6 Tournament Administration

6.1 Admin Abuse

  • 6.1.1 Teams, including support staff, found to be abusing, disrespecting, or attempting to gain advantages from tournament administrators will be penalized. Repeat offenses will result in removal from the tournament.

6.2 Admin Authority

  • 6.2.1 Tournament administrators reserve the right to make any decisions they deem necessary to ensure the smooth operation of the event and tournament schedule while upholding competitive integrity and fairness at their discretion. All administrative decisions are final and may supersede any rule stated in this rulebook.

7 Definitions and Key Terms

Attendee: Any person attending a Frag event, including (but not limited to) players, team staff, media personnel, spectators, vendors, volunteers, staff, and management.

Team Captain: Must be one of five players in the submitted Frag core. The person responsible for a team, listed as Player 1 on the submitted roster form. The person responsible for communication with admins and being present for all event processes.

Frag Core: The 3-5 players submitted 1 week after ticket purchase, one of which is the team captain.

Team Form: The form sent to Team Captains to collect their initial roster information.

Head Admin: The admin responsible for the event.

Match Admin: The admin assigned to a specific match.

Freeze-Time: The time between playable rounds.

Technical Timeout: An indefinite pause during a match used solely for the purpose of resolving a technical issue. May be initiated by players and must be explained in match chat before being ended.

All Chat: The in game text communication visible to both teams.

Match Medic: The automated process for restoring a match to a previous point.

Vetoes: The pick and ban process for determining which maps will be played in a match.

Management: BUCK TEN, LLC.