Winter Rule Updates & Staff Changes

Date January 7, 2023

Banner by UnitedKingdom soda

 

Staff changes

Germany Jonez has decided to leave the League Admin Staff. We wish him the best in his future endeavors. Meanwhile Poland supra will move from the League Admin Staff to the Webmaster Staff.

General rule edits

2.2.1. Nickname changes allowed
You are allowed 4 name changes in total. A single exceptional permission will be granted to revert your name to a previous version if you have not changed your name in 2 years and that you have not enacted that right before.

To change your nickname you must contact League Admins on [ETF2L’s Discord server] and not be rostered in a team actively playing an ongoing competition.

Note: Nicknames must be at least 2 characters long and some characters are not allowed.

3.6. Switching line-ups or hijacking teams is not allowed
Definition:
Players who have joined the team before the Provisional Tiers have been published are considered verified by the league. Any player joining after that is considered new and unverified by the league.

Provisonal tier publishing time will be announced ahead of time, players added anytime after this will count as a late joiner for hijacking purposes.

Standard:
In 6v6 it is allowed to play with 2 players counting as new.
In Highlander it is allowed to play with 4 players counting as new.

Breaking the rules:
If you go past these limits your team will be punished with:

– For Div5/Low and Div6/Open
1st Offense: Minor Warning
2nd Offense: Major Warning
3rd Offense: Default Loss
4th Offense: Expulsion from the competition

– For Prem, Div1-2/High and Div3-4/Mid
1st Offense: Minor Warning
2nd Offense: Default Loss
3rd Offense: Expulsion from the competition

Appeal:
In order to allow leniency for teams that are forced to change their lineups, team leaders are required to contact League Admins on [ETF2L’s Discord server] when facing extreme roster changes.

Each case will be dealt with individually and all factors will be taken into account.

3.7. The amount of players with higher experience that can join after the Provisional Tiers are published is limited
Definition:
A team’s active line-up may only consist of a limited amount of higher skilled players that joined after the Provisional Tiers were published. A point system is used to determine this restriction. A player will be given one point for each tier of experience higher than the division of the team the player joins.

A player counts as experienced in a tier if during their last 3 active seasons they played 3 or more officials in that tier. (This also includes matches in higher tiers which will stack to the closest tier below if no more than three matches have been played in a single tier. Playoff matches count towards the number of matches played in the respective higher tier, with finishing 1st or 2nd automatically counting as the higher tier regardless of the amount of playoff games played (e.g. Division 2 playoffs count as Division 1).

Highlander and 6s experince will count as equivalent between gamemodes

Standard:
In 6v6 teams have a limit of 1 point.
In Highlander teams have a limit of 2 points.

Breaking the rules:
If you go past these limits your team will be punished with:

– For Div5/Low and Div6/Open
1st Offense: Minor Warning
2nd Offense: Major Warning
3rd Offense: Default Loss
4th Offense: Expulsion from the competition

– For Prem, Div1-2/High and Div3-4/Mid
1st Offense: Minor Warning
2nd Offense: Default Loss
3rd Offense: Expulsion from the competition

Appeal:
Please contact League Admin Staff on [ETF2L’s Discord server] if you need your case to be reviewed. The lengths of inactivity will be taken into consideration when making decisions.

Note: Cups (pre-season cups, one-day cups, nations’ cup etc.) do not count towards skill contribution.

Highlander rule edits

1.3. Mercs clause
Definition:
“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.

1.3.3. Default mercs
One merc is allowed by default in all divisions:
– For Premiership, default mercs cannot be rostered in a Premiership team and/or have Premiership experience. Default mercs cannot be class-restricted. RGL Invite is considered to be equivalent to Premiership.

– 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.)

– For D5/Low and D6/Open specifically they cannot be more experienced than the tier the match is being played in (in accordance with General Rule 3.7), and they cannot be rostered in a team placed in any tier higher than that of the official match in question. Default mercs cannot be class-restricted. Experience in other leagues is also included.

If you wish to contest the default status of a merc, please contact a League Admin on ETF2L’s Discord server so they may decide whether or not the player is valid for the Default merc clause.

2.2 Maps
KOTH (King Of The Hill)
There is no time limit. A win limit of 3 rounds (mp_winlimit 3) is set. The first team to win three rounds in the map wins.

If the final score of a KOTH map has a difference of only 1 point (i.e 3-2, 2-3), it is classified as a “Golden Cap” result, with the winner being the team who won 3 rounds.

6v6 rule edits

1.3. Merc clause
Definition:
“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 2 mercs (including default merc) per map and simultaneously, even if the opponent would allow the use of more than 2 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. Classes deemed as “off-classes” (i.e. Pyro, Heavy, Engineer, Sniper and Spy) are allowed by default. 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.

1.3.3. Default mercs
One merc is allowed by default in all divisions:
– For Premiership, default mercs cannot be rostered in a Premiership team and/or have Premiership experience. Default mercs cannot be class-restricted. RGL Invite is considered to be equivalent to Premiership.

– 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.)

– For D5/Low and D6/Open specifically they cannot be more experienced than the tier the match is being played in (in accordance with General Rule 3.7), and they cannot be rostered in a team placed in any tier higher than that of the official match in question. Default mercs cannot be class-restricted. Experience in other leagues is also included.

If you wish to contest the default status of a merc, please contact a League Admin on ETF2L’s Discord server so they may decide whether or not the player is valid for the Default merc clause.

 

JOIN, FOLLOW AND SUPPORT US ON OUR MEDIAS

  

4 Comments

  1. Sabesaroo: UG - COGU said:

    why remove the ‘in accordance with rule 3.7’ bit?

  2. Uncle Sam: OTP said:

    they removed it due to the case of OTP vs. ETF2l Admins, where the (in accordance with General rule 3.7) caused confusion due to there being a specific definition of “experience” being used in rule 3.7 that is not intended to be used for the default merc clause

  3. Luigixby: CROCKET - Slava! said:

    why not unban market gardener instead?

  4. Buck824: MWA said:

    Not sure about the Prem def merc situation, guess it just turns them into regular mercs where you have to be granted permission but vast majority of def mercs are obviously going to have prem experience so that might cause some weird scenario and tension

Leave a Reply

You must be logged in to post a comment.