May 25, 2019
Season 33: Premiership Qualifiers
EDIT: As CHILLWAGON has folded before playing in the lower seed match, Turbo Teammates will be playing in their place against goonsquad. The winner of this match as well will receive a spot in Premiership tier with the losing team getting placed in Division 1. The victory from Generation karnax will remain and they secure their spot for Premiership.
We’ve received a total of 10 applications for Premiership this season with 6 of them receiving a direct placement in Premiership, for both retaining their spot from Season 32 and getting directly invited. This will result in 4 teams playing through the Qualifiers in a single-elimination stage, with 2 teams playing from a higher seed and 2 teams playing from a lower seed. Winners of these matches will receive a spot in Premiership for Season 33.
The following 6 teams will automatically get a spot into Premiership.
- Faint Gaming
- War & Sons – Promoted from Season 32 Division 1
- Ora Elektro – Invited
- top5rocket – Invited
While these 4 will be battling it out for the remaining 2 spots.
- CHILLWAGON – Higher Seed
- Generation karnax – Higher Seed
- goonsquad – Lower Seed
- Turbo Teammates – Lower Seed
CHILLWAGON will be playing against Generation karnax first in a BO3 match, the winner will receive a spot in Premiership while the losing team will be playing a BO3 match afterwards against goonsquad for the remaining Premiership spot. The losing team of this match will be playing in Division 1. All teams have until 2nd of June to make sure both matches have been played.
We will also be releasing a couple of fixes to some already existing rules, a thank you from us to whoever pointed these things out!
First off, we’re fixing a small issue with the newly modified Golden Cap rule, where if neither team has the middle point in control due to any possible round resets they must start a second Golden Cap with the first team to capture the middle point winning it.
4.1.3 Golden Cap: Decider round in case of a draw
If the score is tied after the timelimit has been reached, a decider round (golden cap) will have to be played. The golden cap will be played with winlimit 1 and timelimit 15, if neither of the teams manage to get a round in this time then the team to hold middle point will win the golden cap. The winner of a map that ended with a golden cap round gets 2 points, the loser gets 1 point. If the map timer runs out during the golden cap when neither team is controlling the middle point, teams must play a second golden cap round. Whoever captures the middle point first is then declared the winner.
Secondly we want to clarify what exactly counts to us as a valid status screenshot, due to the SteamID Parser bot on the site having been in effect since early 2009, before the OSX and Linux versions of the game were out and due to how it’s fixed to support only a specific font, Lucida Console, which is present by default in the Windows version of Team Fortress 2. This rule change will not change the way how SteamID/Status screenshots are taken and read, but more so make it specific on what is required to be done for the screenshots to be read by the bot.
3.2 Status & Scoreboard screenshots required
One member of each team has to take a status screenshot before a match is starting and after every player switch. A screenshot of the final score has to be taken at the end of every map/round. Please note that a scoreboard screenshot is not sufficient for all attack/defense maps as it does not show the winner – the screenshot explicitly declaring one team to be the winner is required instead. Screenshots can be uploaded while submitting the result or by either team leader at a later date.
If any map screenshots are missing after the match’s result deadline, and the result has not been verified by the teams, both teams will receive a minor warning. Missing status screenshots will be punished with a minor warning even if the teams verify the result. The second violation of this rule will be punished with a major warning.
For the screenshots to be readable by the SteamID parser bot, the screenshots are required to be taken on the Windows version of Team Fortress 2 with the default console font, Lucida Console, in use. Custom HUDs can potentially have different console fonts that cannot be read even when used on Windows OS, we recommend teams and players to ensure that the font required will be the same as Team Fortress 2 has by default. OSX and Linux versions have a different console font in use by default which cannot be parsed by the bot, therefore we recommend teams to have at least a single player running the Windows version of Team Fortress 2 to take the screenshots.
Warnings for missing screenshots can be removed by providing the missing screenshot and contacting an admin afterwards.