Official Tournament Rules
Rules are subject to change.
Please ask your Coach or Program Administrators for any clarification.
Registration
Teams will register through the link distributed by Lollipop Labs. Teams are required to have a minimum of 5 players on the main roster. One substitute player may be listed. If a separate individual is listed for each role, the roles will not be interchangeable.
Teams will submit for following for the use of prizing and/or broadcast integration, including but not limited to the following:
First Name
Last Name
Grade
Email Address
Riot ID
School Affiliation
Public Valorant Tracker.gg Profile (optional)
The registration period will be limited and outlined by Lollipop Labs. Late registration will not be allowed, except at the discretion of Lollipop Labs for unique cases.
Seeding
Seeding will occur after the team registration period, based upon the highest 5 ranks included within the roster of players eligible for match play. Ranks will be pulled from Valorant Tracker.gg. Failure to provide a Tracker.gg will result in a presumed lower ranking.
Teams will be assigned a seed relative to their team’s “weight”. A team’s weight will be the sum of their rank values. Each rank’s value is as follows:
Radiant 20 Points
Immortal 3 18 Points
Immortal 2 16 Points
Immortal 1 14 Points
Ascendant 1-3 12 Points
Diamond 1-3 10 Points
Platinum 1-3 8 Points
Gold 1-3 6 Points
Silver 1-3 3 Points
Bronze 1-3 2 Points
Iron 1-3 1 Point
For example, a team of 1x Radiant, 1x Immortal 3, and 3x Diamonds would be valued at 68 points. However, if their sub was Ascendant, then their value would be 70 points, as the Ascendant rank would overwrite one of the Diamond players.
Cheating & Behavior
No cheating of any kind is allowed, including, but not limited to: aimbot, scripting, wall hacks, spinbot, etc. The discovery of any cheats whatsoever will result in the immediate disqualification of a roster, and potential suspension from future competitions.
No in-game exploits of any kind. This includes, but is not limited to, boosting teammates onto higher surfaces without utility, placing utility in “unbreakable” positions, leaving the map boundaries through glitches, accelerating movement through methods unintended by the
developers, etc. The discovery of in-game exploits will lead to a warning, then a round penalty, then a disqualification.
Unsportsmanlike behavior of any kind is not allowed. This includes typing negatively in chat, crouch spamming, or spraying bodies. Melee eliminations are allowed. Vulgar behavior of any kind is not allowed. This includes, but is not limited to, crouching while facing other
players/death models, spam swapping abilities while tapping backwards movement, or interacting with in-game sprays.
Smurfing is not allowed. If a player is discovered to be using an account that is lower than their main rank, they will be disqualified.
Tardiness & Forfeits
Teams have 15 minutes after the end of the previous match to set up for their match. If a team exceeds 15 minutes, they will lose a round for every 2 minutes they’re late. At 26 minutes (13-0), the team forfeits the map. If the series is Best of 3, and the team is late, an additional 13 minutes, they will forfeit the series.
A team may not intentionally forfeit or “sandbag” a game. This will result in potential disqualification/exclusion from future events. If a team is down a player, and has no readily available sub, they will be made to forfeit. A sub may be recruited at the discretion of Lollipop Labs, for special cases.
Equipment
Players are allowed to use their own peripherals, mousepad, headset, etc. Players will be held responsible for any technical issues caused by their own equipment.
Players must use their set-up period to check their equipment and flag any issues to the referee to avoid being penalized during the match. Players are allowed to choose between using in-game chat or Discord. In the case of Discord, the referees and the team’s adult supervisor must
both be present in the server or call.
Lobby Setup
Lobby codes should be used to invite all parties, including production. The higher seed will select Team A or Team B in the map pick/ban process.
The format is as follows for a BO1 Pick Ban Process:
Team A bans 1 map
Team B bans 1 map
Team A bans 1 map
Team B bans 1 map
Team A bans 1 map
Team B picks map 1
Team A picks side for map 1
The format is as follows for a BO3 Pick Ban Process:
Team A bans 1 map
Team B bans 1 map
Team A picks map 1
Team B picks side for map 1
Team B picks map 2
Team A picks side for map 2
Team A bans 1 map
Team B bans 1 map
Map 3 is only Map remaining
Team A picks side for map 3
The map pool will be the current Competitive map pool. Custom Lobby settings will be as
follows:
Allow Cheats: OFF
Tournament Mode: ON
Overtime: Win By Two: ON
Play Out All Rounds: OFF
Hide Match History: OFF
Server: N. California
Match Play
Every participant must have the Blood feature turned off. To do this, go to Settings in the game and scroll down to the Other section. Look for “Show Blood” and select “Off”.
The Final Four/Championship matches will be played in-person. All team members must be present. No virtual playing allowed.
Each team is afforded 2 tactical timeouts per map. Tactical timeouts do not rollover into overtime or other maps.
In the case of an overtime, each team is granted 1 timeout to be used during overtime, until the map ends. A team may call for a technical pause due to technical issues during a buy phase. Players may not talk about the game during technical pauses, and may not attempt to use pauses as a tactical timeout. A ruling will be given by the referee if a technical pause was valid, and if a course of action needs to be taken. A technical issue at the fault of the player will be penalized, but the pause will be allowed.
Coaches, substitutes, and external parties may not speak with players during live match play. Coaches are the only additional members able to speak during tactical timeouts. Substitutions may only be made between maps.
The game may only be paused for the following reasons:
Player drop
Player disconnect
Server crash
Technical issues