Rules & Configs 3.0: General, 6s and Highlander Changes

Date January 20, 2020

Rules and Configs Change

After complaints made by our community and some rules being not clear, we decided to review and apply changes in the Rules. Therefore we have removed, added and rewritten some of them.

The rules and configs change will take effect immediately.

Additionally for the future and in order to keep tracks and more transparency for everyone we will implement the Latest Rules Update page with the applications dates.

WARNING: Some minor changes have not been mentioned here because the post is already long enough and those changes are situational.

Config Changes

We have decided to put on a restriction on the classes directly in the server configs.

To install ETF2L configs on your server, upload the .cfg and .txt files to your server’s orangebox/tf/cfg folder. You must execute the appropriate ETF2L config before any league match, by using the “exec [configname]” command.

General Rules Changes

Moved

  • 2.1. All players are welcome to 1.1. All players are welcome
  • 2.2. Only players with correctly entered Steam IDs are eligible to 1.1.1. Only players with correctly entered Steam IDs are eligible
  • 1.9. Roster locks to 1.5. Roster locks
  • 3.10. Warnings may lead to point deduction or removal from a competition to 1.6. Warnings may lead to point deduction or removal from a competition
  • 2.4. Every player has to record Demos and 2.4.1. Penalties for not providing requested demos to 2.1. Every player has to record Demos and 2.1.1. Penalties for not providing requested demo
  • 4.5. Maps need to be played in the set order to 3.4. Maps need to be played in the set order
  • 4.6. Deciding sides to 3.5. Deciding sides

Removed

  • 3.11. Class limits within the gamemode will also count dead players
  • 4. Maps
  • 6.4. Taunt slide bug is forbidden

Modified

  • 1.2. Scheduled matches have to be entered on the League Calendar
  • 3.6. Switching line-ups or hijacking teams is not allowed

We have added an example to be more clear:

For example in 6s if a team add 2 or less players in the roster after the provisional tiers were announced the team will receive no warning. However if a team add 3 or more players in the roster after the provisional tiers were announced and use them in one or multiple official matches the team will receive one or more warnings depending on how many matches they break the rules.

In HL if a team add 3 or less players in the roster after the provisional tiers were announced the team will receive no warning. However if a team add 4 or more players in the roster after the provisional tiers were announced and use them in one or multiple  official matches the team will receive one or more warnings depending on how many matches they break the rules.

  • 3.7. The amount of players with higher experience that can join after the Provisional Tiers are published is limited

We have worded the rules differently to avoid any misunderstanding

Each team has a 1 point limit for 6v6 and 2 point limit for Highlander. If you go over the limit you will be punished. For example in highlander if a division 1 player joins a mid team he will contribute to 2 points. No other player with higher experience than mid will therefore be authorized without breaking the rule. Please contact the admins on discord if you need your case to be reviewed. Admin discretion will be used when dealing with specific cases.

Combined 

  • 1.2. Scheduled matches have to be entered on the League Calendar
  • 1.3. Separate schedule & match deadline for every match Default Date for all matches
  • 1.5. Only submitted playdays are used to generate the Default Date
  • 3.3. Scheduled matches can only be postponed by a reschedule agreement
  • 6v6 rules 1.7. Late matches are not allowed
  • HL rules 1.8. Late matches are not allowed

To create

  • 1.3. Official matches have to be entered on ETF2L

Combined 

  • 2.5. Abusive chat, nicknames and avatars are not welcome
  • 2.8. You can have your ETF2L name changed up to 4 times
  • 2.9. Players playing in matches casted by an org must use their real nickname

To create

  • 2.2. Nicknames rules

Added 

  • 3.13. Weapons and Hats rules
  • 4. Premiership only rules
  • 6.4. Game Modifications

Modifications  that give the player a massive gameplay advantage are strictly forbidden. 

Players who are caught using banned modifications will be penalized on a case-by-case basis depending on the impact of the modification. Possible penalties may include team warnings, default losses and league bans for the offending player.

Examples of banned modifications:

  • Sniper Scope Removal
  • Shadow Boxes
  • Sound file manipulations that make gameplay situations far easier to detect (e.g. Spy decloak, Medic’s full charge sizzle, footstep sounds)
  • Removal of map props 

Examples of allowed modifications:

  • Custom HUDs
  • Custom Hitsounds
  • Custom Viewmodels and Crosshairs
  • Removing Ambient Soundscapes
  • Flat Textures
  • No Hats

If you are unsure about the legality of a particular modification, please contact an admin to clarify the situation before using it in an official match.

  • 8. Explanations section

 

6v6 Rules

Removed

  • 1.3. Map pool
  • 1.6. Teams may not add new players from week 7 onward
  • 1.8. Premiership only rules
  • 1.9. Prizes
  • 2.2. Weapons rules

Modified

  • 1.3. No mercs allowed unless your opponent agrees

If a team wants to use a merc, they must contact the opponent before the match starts and ask if the merc is allowed to play and on which class. If the opponent agrees, make sure a log of the agreement is taken and provided in the match comments, together with links to the mercs’ ETF2L profile. 

To avoid any confusion: If a player is accepted on a specific class they must play this class and are not allowed to switch to another class unless if the opponent approved beforehand. If no restrictions are proposed the player can play any class.

Switching a merc to a different class without permission will result in a punishment.

Added 

  • 1.3.2. A team can use up to a maximum of 1 merc in Grand Final matches
  • 2.2. Maps

With a specification where KOTH Scoring has been modified to match Highlander Rules.

When the results of any KOTH map in 6v6 are 3-2 this will count as a Golden Cap win/loss. This change is an effort to divide points fairer as in the current system there is no difference from a 3-2 loss and a 3-0 loss on KOTH maps. Please remember to check the Golden Cap box if your match had a scoreline of 3-2 when submitting results.

Highlander Rules

Removed

  • 1.3. Map schedule
  • 1.4. KOTH scoring
  • 1.7. Teams are not allowed to use new players from week 5 onward
  • 1.9. Premiership only rules
  • 2.2. Weapons rules

Modified

  • 1.5. One mercenary allowed by default in mid and open only and up to 3 mercenaries if the opponent agrees

To use more than one merc, you will need specific approval from the opponent for each merc and each class.

To avoid any confusion: if a player is accepted on a specific class they must play this class and are not allowed to switch to another class unless the opponent approved beforehand. If no restrictions are proposed the player can play any class.

Switching a merc to a different class without permission will result in a punishment.

 

Added 

  • 2.2. Maps

 


ETF2L on social media:

Twitter Follow us on Twitter!
Facebook Like us on Facebook!
Steam Join our Steam Group and invite your friends!
Discord Use our Discord!

10 Comments

  1. derdan: bv16.4 - KorWIN said:

    Thank you for finally changing the rule about mercs specific classes

  2. catman: RPC - -st- said:

    still retarded, still rules are written by brain dead people

  3. ar1stotel: iTAP - She said:

    love or hate catman but he’s spittin straight facts

  4. Wynran: Snack - DK said:

    catman tell ’em

  5. AxioMr: Sborr - INTERPOL said:

    angry russia man stands up to evil capitalist system

  6. jimmij: leg said:

    removing rule 3.11 is retart:
    bruh if your med dies u could bypass the uber disad u get if someone else on your team goes med…. u could just have 2 gamers “mainclassing” medic and another class and u only ever get very small disad when ur med dies

  7. jimmij: leg said:

    nvm adding class restrictions into the config prevents this apprently

  8. HartzFartz: (ETF2L Donator) - T9! - ᴏғᴏ said:

    I don’t understand why highlander needs class limits. It’s pretty straight forward. Also it’s not our fault that these noob 6v6 players don’t know how many classes are allowed. Aoshi literally ruining etf2l. #ugcsuperiorcompetition

  9. TwiiKuu: 8D said:

    Unless the behavior has changed in recent updates, the in-game implementation of class limits is absolutely broken in edge cases, putting players in situation where they are stuck in menus unable to play, sometimes requiring coordination with other teammates who may be dead, causing literal dead locks.
    This is not an appropriate solution to such a benign problem.

  10. TwiiKuu: 8D said:

    Not only is friction introduced in a considerable amount of class switches, the in-game system still allows for class limits to be broken!
    Take the ever so common case of two (or more) dead players respawning at the same time as a class which has one available slot, they will both respawn as that class with no issue whatsoever.
    This does not even require the players to be bad actors, it can purely be a mistake in coordination.
    This is actually a non-solution.

Leave a Reply

You must be logged in to post a comment.