6v6 Season 41 Top Tiers Powered by Copenhagen Games

Division 1

Quarter Finals

Round commencing: 13 Mar 2022, 00:00 - 20 Mar 2022, 00:00

Schedule deadline: 16 Mar 2022, 00:00 | Result deadline: 20 Mar 2022, 00:00

Scheduled: 16 Mar 2022, 21:15
Results submitted: 18 Mar 2022, 02:12
by Doughy (trust the process)

trust the process vs Duplo
6 - 0

SteamID Screenshots: A

Players

trust the process	(6) Jordy, silves, hemp, Spirit, Doughy, Derpy Hooves
Duplo	(6) _gar, phille ツ, ombra, balder, satan, alba

4 Comments

1. ETF2L Staff said:
   

   Sun 13 Mar 2022, 17:51

   Welcome to the Season 41 Powered by Copenhagen Games: Division 1 Quarter Finals!

   This match will be played as a best-of-three.

   Maps will be decided using the following Map Elimination System:

   As the higher seed Eilert’s Angels can decide if they want to begin the pick/ban as “Team A” or if Team trust the process have to.

   Team A bans a map
   Team B bans a map
   Team B picks a map
   Team A picks a map
   Team B bans a map
   Team A bans a map
   The remaining map is the decider

   Good luck for both teams!

2. _gar: duplo said:
   

   Mon 14 Mar 2022, 20:49

   B please

   [7:42 PM]
   Doughy:
   Aite, we ban process

   [7:43 PM]
   calle:
   ban sunshine
   pick metal

   [7:44 PM]
   Doughy:
   pick product

   [7:46 PM]
   calle:
   ban gully

   [7:48 PM]
   Doughy:
   ban gran, snake decider

3. Doughy: SKΣDDA - BRIT said:
   

   Mon 14 Mar 2022, 20:50

   [18:37]
   Doughy:
   gimme 8 more mins
   do you want team A or B? you decide

   [18:42]
   calle:
   B please

   [18:42]
   Doughy:
   Aite, we ban process

   [18:43]
   calle:
   ban sunshine
   pick metal

   [18:44]
   Doughy:
   pick product

   [18:46]
   calle:
   ban gully

   [18:48]
   Doughy:
   ban gran, snake decider

4. ETF2L Staff said:
   

   Thu 24 Mar 2022, 13:06

   Dear teams,

   No scoreboard screenshots have been submitted for this match. Please upload the required screenshots for this match. You can do so here:
   https://etf2l.org/wp/wp-admin/index.php?page=add_screen

   3.2. Status & Scoreboard screenshots required:

   One member of each team has to take a console status screenshot before a match starts, and after every player switch made by a team during an official. 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 should be uploaded while submitting the result, but can also be [uploaded] by either team leader at a later date.

   If any map screenshots are missing after the match result deadline and its result has not yet been verified by the teams, both will receive a Minor Warning. Missing console status screenshots will be punished with a Minor Warning even if the teams verify the result. Repeated violations of this rule during a competition, regardless of the type of missing screenshot, will be punished with Major Warnings.

   For the status 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 console font in use by their Team Fortress 2 clients is the default; additionally, we recommend teams to have at least one player running the Windows version of Team Fortress 2 in order to take the necessary screenshots, as OSX and Linux game clients have a different console font in use by default which cannot be parsed by the bot.

   Warnings for missing screenshots can be removed by providing the missing screenshot and contacting an admin afterwards.

   Therefore a minor warning has been issued to both teams. Once you have uploaded the screenshots contact an admin in our discord https://discord.etf2l.org to get the warning removed.

Leave a Reply

You must be logged in to post a comment.