Ultiduo Cup #7 Playoffs

Round of 16

Round commencing: 10 Jun 2023, 19:30 - 10 Jun 2023, 20:45

Schedule deadline: 8 Jun 2023, 00:00 | Result deadline: 10 Jun 2023, 20:45

Scheduled: 10 Jun 2023, 19:30
Results submitted: 10 Jun 2023, 20:15
by piggles (HULKAMANIA)

ultiduo_baloo_v2

2 - 0

[Screenshots: A ]

ultiduo_lookout_b1

2 - 0

[Screenshots: A ]

HULKAMANIA vs Eepily fan club
6 - 0

Warnings

• HULKAMANIA [Minor] Missing, wrong or incomplete status screenshot
• Eepily fan club [Minor] Missing, wrong or incomplete status screenshot

3 Comments

1. Default Date said:
   

   Sat 10 Jun 2023, 21:22

   A default date has been set for this match by ETF2L.
   The default date is: Saturday, 10 June 2023, 19:30
   Please play this match on the appointed time and submit the results.
   If the default date does not suit you, please contact your opponent and ask them to reschedule.

2. ETF2L Staff said:
   

   Sat 10 Jun 2023, 21:23

   Welcome to the Ultiduo Cup #7 Round of 16 Playoffs!

   This match will be played as a best-of-three. For this match the pick & ban system will be as follow:

   Both teams need to agree on who eliminates first. If the two teams cannot agree, they need to perform a Heavy Fist Fight. The winner of this Heavy Fist Fight can decide which team is Team A and which is Team B.

   Map pool reminder

   – koth_ultiduo_r_b7
   – ultiduo_baloo_v2
   – ultiduo_grove_b4
   – ultiduo_gullywash_b2
   – ultiduo_furnace_b2
   – ultiduo_obsidiian_a10
   – ultiduo_lookout_b1
   – ultiduo_raksha_beta7

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

   Good luck to both team!

3. ETF2L Staff said:
   

   Tue 13 Jun 2023, 23:32

   Dear teams,

   No status screenshots and/or 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.