Open & Intermediate:
Once a team schedule has been released, it is up to the team captain or scheduler to submit vetoes for that specific match.
Please note: If teams are requesting to reschedule or confirm a new date via the match page (IE: rescheduling due to a LAN event, holiday, etc) the system will still draw the map 48 hours before the official scheduled time on the match page regardless of any agreement in the comments.
Important: Please do not leave it to the last minute to veto, claiming a technical issue occurred because your team will not have another chance to veto
Vetoes must be submitted over 48 hours before the match is scheduled to start to lock in successfully.
Below you can find two simple scenarios of the process and the interface users will see:
Example Map Pool:
de_dust2, de_inferno, de_train, de_nuke, de_cache, de_mirage, de_overpass.
Scenario 1
Team A: bans de_inferno, de_mirage, de_dust2
Team B: bans de_overpass, de_nuke, de_cache
One map left: de_train
Scenario 2
Team A: bans de_inferno, de_cache, de_dust2
Team B: bans de_overpass, de_nuke, de_dust2
Two maps left: de_mirage & de_train
Therefore, there is a 50% chance the system picks mirage and a 50% chance the system picks train.
There is no downside to securing your vetoes earlier as only your team can see the maps. Your opponents, the general public and even our own league staff cannot see what you have selected. Teams must submit their vetoes before the deadline otherwise they will be treated as not having vetoed any maps. Admins cannot reset or remove any already vetoed maps so it is the responsibility of your team leader and scheduler to make sure this has been done and is correct.
The veto system will draw the map two days before the scheduled time occurs. If the match is brought forward and less than 48 hours remain then the system will instantly apply the vetoes and draw the map.
Any vetoes submitted after the 48 hours will not be accepted or secured and the predetermined maps will stand.
Main & Advanced:
The divisions of Main and Advanced will now have in-server vetoes take place instead of the default match page format. If you are disputing the server then please complete the veto on the original server before swapping to a new server.
The Veto Format follows the ESL’s veto format from the EPT rulebook:
The higher seeded team will be decided by a coin flip, for regular season matches, and they decide whether they will be Team A or Team B. Team A starts the process and the order of the ban/pick is as follows:
- Team A removes one map.
- Team B removes two maps.
- Team A removes two maps.
- Team B removes one map.
- The remaining map will be played.
The starting sides on the map are determined by a knife round.
Each team will have a 150-second veto timer. The timer for your team will begin counting down when the server is waiting on a veto command from your team, and the time of day has passed the match’s scheduled time. Teams may freely veto before the timer starts to complete the veto process quicker.
For example, if the match is scheduled to 20:00 UTC, then your team’s counter will only count down if the time is 20:00:00 UTC or later. Typically, servers are assigned 15 minutes before the match's scheduled time, and forfeits become available 15 minutes after the match's scheduled time.
Once a team’s own timer hits zero, they will no longer be able to veto manually, and all future vetoes will become automated and randomized on a 10-second timer
-
- Examples
- If Team A spends 100 seconds on their first “.ban” command, they will have 50 seconds for all subsequent vetoes. Your timer does not replenish between votes.
- If Team A spends 100 seconds on their first “.ban” command, Team B will still have 150 seconds to veto their picks, the timers of the two teams are separate.
- Examples
- Server Warnings
- The veto format will be printed in chat before any vetoes have been made
- “Veto Format: a:first,a:ban,b:ban,b:ban,a:ban,a:ban,b:ban”
- “Veto Format: a:first,a:ban,b:ban,b:ban,a:ban,a:ban,b:ban”
- The server will give teams a 30-second warning to the veto timer’s activating.
- “150 second veto timers will be enabled in under 30 seconds. Please prepare to make your vetoes”
- “150 second veto timers will be enabled in under 30 seconds. Please prepare to make your vetoes”
- The server will notify each team when veto timers have been enabled.
- “Veto timers have been enabled, you now each have 150 seconds to complete your vetoes”
- “Veto timers have been enabled, you now each have 150 seconds to complete your vetoes”
- The server will prompt every 15 seconds which team’s turn it is in the veto, how much time they have left to veto, and which veto command they must use.
- “Team A/B has (seconds) remaining to complete their vetoes. Once (seconds) have passed, their remaining picks/bans will be automated”
- The veto format will be printed in chat before any vetoes have been made
Full Veto Example
Server: 150 second veto timers will be enabled in under 30 seconds. Please prepare to make your vetoes
Server: Team X decides who goes first with: .first us/them
Server: Veto format: A: Ban, B: Ban, B: Ban, A: Ban, A: Ban, B: Ban
Server: Veto timers have been enabled, you now each have 150 seconds to complete your vetoes
Server: Team X has 150 seconds remaining to complete their vetoes. Once 150 seconds have passed, their remaining picks/bans will be automated
Server: Team X decides who goes first with: .first us/them
Server: Veto format: A: Ban, B: Ban, B: Ban, A: Ban, A: Ban, B: Ban
Mythik: .first us
Server: Team X, BAN the next map with .ban
Server: Remaining maps: de_inferno / de_vertigo / de_overpass / de_mirage / de_nuke / de_ancient / de_dust2
Server: Team X has 135 seconds remaining to complete their vetoes. Once 135 seconds have passed their remaining picks/bans will be automated
Mythik: .ban de_inferno
Server: Team X has banned de_inferno.
Server: Team Y, BAN the next map with .ban
Server: Remaining maps: de_vertigo / de_overpass / de_mirage / de_nuke / de_ancient / de_dust2
Server: Team Y has 150 seconds remaining to complete their vetoes. Once 150 seconds have passed their remaining picks/bans will be automated
…
…
…
Server: Team Y has 15 seconds remaining to complete their vetoes. Once 15 seconds have passed their remaining picks/bans will be automated
Server: Team Y has run out time for their veto. Their remaining picks will be automated.
Server *** Team Y Automated Veto ***
Server: Team Y has banned de_mirage.
Server: Team X, BAN the next map with .ban
Server: Remaining maps: de_vertigo / de_overpass / de_nuke / de_ancient / de_dust2
Server: Team X has 133 seconds remaining to complete their vetoes. Once 133 seconds have passed their remaining picks/bans will be automated
…
…