We are happy to announce that we got a new feature for sending results - you can do that by sending a logs.tf log! We have updated our site backend and resolved a vulnerability reported to us, thanks to Anton Maryasin!
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 Season 34 (Summer 2025)

Mid

Week 3

Round commencing: -

Schedule deadline: | Result deadline:

Date Scheduled:
Results submitted:
by ETF2L Staff

Default Win

European Xenon vs Greece BLEU
0 - 6

SteamID Screenshots: A

Warnings

  • Xenon [Minor] Using an unapproved merc

2 Comments

  1. Default Date said:

    A default date has been set for this match by ETF2L.
    The default date is: Friday, 29 August 2025, 21: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. ETF2L Staff said:

    Dear teams,

    it has come to our attention that team “Xenon” used the player Acoul as a default merc in this game. Unverified players cannot default merc for their own team. Furthermore, due to their prior league experience they would not be eligible to default merc in Mid either. Due to “Xenon” using an unapproved merc the match will be defaulted in favour of “BLEU”.

    1.3.3. Default mercenary

    One merc is allowed by default in all divisions:

    For D1/High, D2/High, D3/Mid and D4/Mid default mercs cannot be rostered in a team and/or have experience in the tier that the match is being played in, or any other tier above that. Default mercs cannot be class-restricted. Experience in other leagues is also included. (e.g. A high team will only be able to present a default merc from mid.)

    1.3. Mercenary clause:

    Definition:
    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.

    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 “Xenon” for using an unapproved merc.

    For any questions please contact League Admin Staff on our Discord: https://discord.etf2l.org

Leave a Reply

You must be logged in to post a comment.