x
ETF2L is looking for new Staff to recruit! Are you interested in supporting the league? Then click here for more details on what we can offer and how to apply! 

Highlander Winter 2024: Low

Low

Week 2

Round commencing: -

Schedule deadline: | Result deadline:

Date Scheduled:
Results submitted:
by ETF2L Staff

Default Win

Argentina Los Pibes del Tanque vs Russia сука_баZука
0 - 6

SteamID Screenshots: A

Players

Los Pibes del Tanque (8) Paharito, Luc4stello, Parkrover, suchihoku, satee, Felina, Ryisuh, _hate
сука_баZука (9) manuhamu, wasd, ligtaz, karell, zlot, IVANZOLO, spice kot, yoghard, reishi
Unrostered (1) nicoapkm

Warnings


8 Comments

  1. Default Date said:

    A default date has been set for this match by ETF2L.
    The default date is: Thursday, 25 January 2024, 20:00
    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. satee: LPDT said:

    Hi can you play in weekend? Saturday or Sunday 20 cet or default day and time ?

  3. ligtaz: DIRECTOR - 1KLA$ said:

    https://etf2l.org/forum/user/136712/ def merc

  4. satee: LPDT said:

    https://steamcommunity.com/id/idkwhocaresxd/ def merc

  5. satee: LPDT said:

    https://etf2l.org/forum/user/131186/

  6. vsn said:

    ебать вы тупые обсосы

  7. ETF2L Staff said:

    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.

  8. ETF2L Staff said:

    Dear teams,

    Due to “Los Pibes del Tanque” using an unapproved merc the match will be defaulted in favour of “сука_баZука”.

    1.3. Mercenary clause:

    Definition:
    Mercenaries or “Mercs” or “ringers” are defined as players who are not part of a team’s roster. Players who are listed as “unverified” on a roster also count as mercs if they were listed as such at the time an official was set to start.

    Standard:
    A team can use up to a maximum of 3 mercs (including default merc) per map and simultaneously, even if the opponent would allow the use of more than 3 mercs.
    A team can only use 1 default merc as per rule 1.3.3 Default Mercs.
    Otherwise, no team may use a merc at any time during a match unless the player(s) is/are granted explicit written permission to play by the opposing team.
    Other leagues are included in experience. You can see how we count experience compared to other leagues in the tables in 1.3.3 Default Mercs.

    Process:
    Merc permission grants are player-based and class-based: teams are free to choose whether a player is allowed to play for their opponents as a merc and which classes they are allowed to play. All permitted classes should be explicitly stated by the team granting permission. If no specific classes are stated, a player allowed to play as a merc can play any class of their choice.

    All agreements for merc permission grants and the usage of default mercs must be logged and provided in the official match’s respective comments. Those logs must explicitly contain links to each approved merc’s ETF2L profile. Teams are advised to check if the proposed default merc is indeed eligible as per rule 1.3.3 Default Mercs.
    All mercs have to be registered on ETF2L.

    The team that requested the merc is responsible for making sure that this permission is granted. If a team wants to use any players who are not eligible to be a default merc, they must contact the opponent before the match starts.

    Breaking the rules:
    Failing to present a default merc to the opposing team will grant you a minor warning.
    A team using an unapproved merc or an unregistered player will receive a minor warning and Default Loss.

    In addition to that a minor warning has been issued to “Los Pibes del Tanque” for using an unapproved merc.

    For any questions please contact us in our discord https://discord.etf2l.org

Leave a Reply

You must be logged in to post a comment.