Latest Rules & Configs Updates


General Rules Change


  • 2.6. Flag/Nationality change
  • 2.6.1. Flag change allowed in total

Flag change on ETF2L can only be done by League Admins. If you want your Flag changed, contact them on [ETF2L’s Discord server]. You can get your Flag changed a total of two times. This includes European and United Kingdom Flag. There are no exceptions.

  • 2.6.2. Nations Cup

Joining a National Team (and not necessarily playing) whether it’s 6v6 or Highlander will be considered their finale choice of Nation. The player will have to play for this Nation and no other.

  • 2.6.3. Punishment

A player caught trying to get a false Flag/Nationality change won’t be able to change it ever again, will receive 1 month league ban and a permanent ban from Nations Cups.


  • 3.6. Switching line-ups or hijacking teams is not allowed

Any player that joins a team’s roster after the competition’s Provisional Tiers have been published is classified as “new”. Teams may only play official matches with a number of “new” players less than half of the lineup respective to the competition. For 6v6 and Highlander respectively, the limits are of 2 players and 4 players.

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

A player counts as “experienced” in a tier if during their last three 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).

Please contact League Admin Staff on Discord if you need your case to be reviewed. The lengths of inactivity will be taken into consideration when making decisions.



  • 6.2. Cheats are not allowed
    Any kind of cheats are not permitted. Players who are found guilty of using cheats will be banned from all ETF2L competitions according to the following:

    • First Time: 2 Years
    • Second Time: Permanent Ban

There is no appeal process for cheating bans. ETF2L league bans for Team Fortress 2 VACs count as a cheating ban.


  • 6.5. VAC Bans
    As of March 15, 2012, any player with a VAC ban on the Source engine will be banned for 2 years. Players with VAC bans that do not apply to Team Fortress 2 will not be affected.


  • 6.5.1. Multiple Team Fortress 2 VAC Bans
    Any player that has received a Team Fortress 2 VAC ban while already having been ETF2L league banned for a VAC before will receive a permanent ban.
  • 6.2.1. Permanent Cheating Ban Appeals
    Players who have been permanently banned from ETF2L for cheating may appeal their ban if certain conditions are met:

    • Their permanent ban was applied at least 2 years ago.
    • There have been no attempts to evade their ban. This for example includes creating alternate accounts on ETF2L or sharing accounts with other players.
    • They have not cheated again or received a TF2 VAC during their ban time.
    • There have not been any substantial behaviour reports made against the player after their ban.
    • The ban did not happen after a previous appeal was already successful.

In order to file an appeal, please contact our admin staff on Discord. Decisions will be made at admin discretion.


  • 6.5.1. Multiple Team Fortress 2 VAC Bans
    Any player that has received a Team Fortress 2 VAC ban while already having been ETF2L league banned for a VAC before will receive a permanent ban.


  • 2.1.2. Lower demo infraction limit for players with an appealed permanent cheating ban
    Players who have received a permanent cheating ban that was lifted by a successful appeal have a lower demo infraction limit. As long as they have no prior demo infractions on their record the following applies:Player penalties:

    • 1st time – no penalty
    • 2nd time and onwards – player is banned for one year from all ETF2L competitions



  • 1.3. Mercenary (“merc”) clause: up to three mercs allowed if the opponent agrees, one allowed by default in Division 3, Division 4, Division 5 and Division 6



Server Configs Changes

  • Changed sm_remove_medic_attach_speed to 0 in Highlander and 6v6 config.



  • 1.1.2. Any Form of Harassment/Racism/Toxicity/Etc is Punishable:

ETF2L does not support any form of harassment of its players. People harassing others based on ethnicity, culture, religion or similar will get punished for their actions. We understand that things can get heated within a competitive game and will handle cases with this in mind. We do ask people to keep it civil.



  • 2.1. Every player has to record demos

Demo files can be requested by an admin or any player of the opposing team.

Admins may request demo files at any time until the end of the competition an official match was played in; a competition is considered ongoing until its wrap-up post is published. Admins may request as many files as they require.

The opposing team can request demo files at any time until 48 hours have passed after an official match was scheduled to start. They can request demos from up to two opposing players, who will then have to provide their demos for all played maps. A team is only allowed to make four demo requests in a single competition.

Players have to record the entirety of their official matches. Missing segments of any kind (e.g. rounds, halves) can count as a missing recording and may result in a team Warning and an infraction for the player. As a rule of thumb, we advise you to check whether you have a demo file recording whenever you join a server, especially after a connection loss or a map switch. A player whose demo files have been requested has 72 hours to upload them, starting from the time the request was made. All requested demos up to 100 MB have to be uploaded to ETF2L; links to third party hosts will be ignored.



  • 2.2.3. Offensive messages, nicknames and avatars are not welcome:

We do not tolerate offensive team names/nicknames, avatars and messages regardless of where they are posted – this includes (but is not limited to) the forum, match comments, and in-game during official matches. Any form of offensive behavior, including offensive bind spamming in the in-game chat, is not allowed. Admins reserve the right to contact the players involved to have their name changed and will change offensive names on their own if the players are uncooperative. All cases are reviewed individually. Penalties may vary based on the severity of each offense, with any decisions being made at the discretion of the admin team. All circumstances will be taken into account.


Server Configs Changes

  • Removal of the class limitation in the Highlander config.
  • Addition of France TwiiKuu ‘s plugin to the config.
    • sm_deterministic_fall_damage 1
    • sm_fix_ghost_crossbow_bolts 1
    • sm_fix_slope_bug 1
    • sm_fix_sticky_delay 1
    • sm_remove_halloween_souls 1



Server Configs 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


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


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


  • 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 clearer.

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

We have worded the rule differently to avoid any misunderstanding.


These are centain rules that have been removed or partially reworked in order to make the rules clearer.

Origin Rules New Rules
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
1.3. Official matches have to be entered on ETF2L
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
2.2. Nicknames rules


  • 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


  • 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


  • 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.


  • 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


  • 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


  • 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.


  • 2.2. Maps


Server Configs Changes

  • Added tf_dropped_weapon_lifetime 0
  • Added tf_preround_push_from_damage_enable 1
  • Added tf_spawn_glows_duration 0


Server Configs Changes

  • Set mp_bonusroundtime to 10 (was 0)


Server Configs Changes

  • Added mp_highlander 0 to etf2l.cfg


Server Configs Changes

  • Added mp_enableroundwaittime 1


Server Configs Changes

  • Added tv_relayvoice 0
  • Added host_framerate 0
  • Added mp_friendlyfire 0
  • Added sv_allowupload 0
  • Changed sv_mincmdrate to 66
  • Changed sv_minrate to 20000
  • Changed sv_minupdaterate to 66
  • Added etf2l_custom.cfg
  • Renamed config packs


Server Configs Changes

  • Removed class limits from 6v6 config


Server Configs Changes

  • Updated 6v6 class limits


Server Configs Changes

  • Updated config packs


Server Configs Changes

  • Added 6v6 KOTH config


Server Configs Changes

  • Added mp_maxrounds 2 to Stopwatch configs


Server Configs Changes

  • Added tf_avoidteammates_pushaway 0


Server Configs Changes

  • Added tf_birthday_ball_chance 0


Server Configs Changes

  • Added sv_restrict_aspect_ratio_fov 0; added comments throughout the config file.


Server Configs Changes

  • Disallowed using TF2’s server voting system
  • Allowed a broader range of interpolation ratios (from 0 to 5)
  • Allowed a broader range of rate values (from 30000 to 100000)
  • Shortened player timeouts to avoid issues where players can’t rejoin
  • Smaller cap on future ticks a player is allowed to send prematurely


Server Configs Changes

  • Fixed bug with mp_maxrounds not being reset after entering payload.


Server Configs Changes

  • Removed trailing tabs and spaces; Shortened and clarified printed text; Changed version date to DDMMYY.
    Removed some tv_* settings that are more appropriate for the server owner to decide; Removed host_framerate so it’s up to the server owner to set; Changed sv_client_max_interp_ratio to 3 so players are free to use broader client-side settings; changed sv_allow_color_correction so users are free to use client-side colour correction. Changed sv_client_cmdrate_difference to comply with actually attainable values
    Removed mp_teamplay, mp_autocrosshair, mp_falldamage, mp_time_between_capscoring, mp_weaponstay, mp_enableroundwaittime due to having little to no effect on competitive tf2; Removed mp_idlemaxtime, mp_chattime, mp_autoteambalance, mp_stalemate_timelimit and decalfrequency due to redundancy with other commands.


Server Configs Changes

  • Added tf_flag_caps_per_round 5; Added whitelists


Server Configs Changes

  • Added stopwatch config, mp_highlander set to 0
  • Added tf_teamtalk 1, tf_use_fixed_weaponspreads 1


Server Configs Changes

  • Added note about mp_windifference 0 on CTF maps


Server Configs Changes

  • Added: mp_windifference 5

Other changes are archived.