General Rules

1. Basics

1.1. All players are welcome

1.1.1. Only registered players are eligible

1.2. ETF2L Timezone = CET/CEST

1.3. Official matches have to be entered on ETF2L

1.3.1. Separate schedule & match deadline for every match – Default Date for all matches

1.3.1.1. Only submitted playdays are used to generate the Default Date

1.3.1.2. Matches can only be rescheduled by mutual agreement 

1.3.1.3. Late matches are not allowed

1.4. Use the match comments to record agreements on mercs, servers and other cases

1.5. Roster locks

1.6. Warnings may lead to point deduction and/or removal from a competition

1.7. Committing or supporting fraud is strictly forbidden

1.8. Disruption of ETF2L and its services is strictly forbidden

1.9. Players may not bet on their own matches on third party betting & gambling services

 

 

2. Players

2.1. Every player has to record Demos

2.1.1. Penalties for not providing requested demos

2.2. Nickname rules 

2.2.1. Nickname changes allowed in total

2.2.2. Players playing in matches casted by an org must use their real nicknames

2.2.3. Abusive messages, nicknames and avatars are not welcome

2.2.4. Different nicknames during official

2.3. Two team change per competition allowed

2.4. No account sharing and multi accounts

2.5. No wiping of a player’s ETF2L history

 

3. Match Rules

3.1. League Configs must be used for all matches

3.2. Status & Scoreboard screenshots required

3.3. A delay of 15 minutes is allowed

3.4. Maps need to be played in the set order

3.5. Deciding sides

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

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

3.7.1. All previous experience will be taken into account in the Open/Fresh Meat tier

3.8. Player changes during a match

3.9. Only authorized spectators allowed

3.10. Teams may request a pause if problems occur

3.11. Playoff matches must have maps chosen before matches are about to be played

3.12. Weapons and Hats rules

3.12.1. Weapons reskins allowed

3.12.2. Taunts

 

4. Premiership Only Rules

4.1. Premiership players must always use their ETF2L nicknames during officials

4.2. Premiership teams have a limited amount of team name changes

4.3. SourceTV demos for premiership matches are mandatory

4.4. Penalties during Premiership Playoffs and Tiebreakers

 

5. Servers

5.1. Be reasonable regarding servers

5.1.1. European server recommended

5.2. Servers need to be password protected

5.3. Unusual server settings may be considered cheating

5.4. Servers must be started with “-sv_pure”

 

6. Cheats & Scripts

6.1. Bug-Using is not allowed

6.2. Cheats are not allowed

6.3. Scripts

6.4. Game Modifications

6.5. VAC Bans

6.6. Exploiting the retry command is not allowed

6.7. Masking ping is not allowed

 

7. Admins

7.1. Requesting admin help

7.2. Admins are listed on the staff page

7.3. Admin discretion

 

8. Explanations

8.1. Default dates

8.2. Heavy Fist Fight

8.3. Picks/Bans System

8.4. Loser’s Pick System

1. Basics

1.1. All players are welcome

Any player of any country is welcome to play in ETF2L. However, ETF2L reserves the right to exclude certain players from its competitions.

1.1.1. Only registered players are eligible

All players participating in matches must be registered on ETF2L. Using a player not registered on ETF2L will result in the match being defaulted in the opponent’s favour.

A player that is not verified on a team’s roster before the official match start time as listed on the match page (listed as unverified on the roster, or not on the roster at all) counts as merc. Players are verified after being rostered for 24 hours. Competition specific rules apply.

1.2. ETF2L Timezone = CET/CEST

ETF2L announces all times in either Central European Time (CET) or Central European Summer Time (CEST). A clock displaying the current time can be found on the homepage. All times shown on the website are within this timezone.

1.3. Official matches have to be entered on ETF2L

All official matches are to be scheduled on ETF2L. Teams may only claim a Default Win if the match has been scheduled.

1.3.1. Separate schedule & match deadline for every match – Default Date for all matches

Every official match has its own schedule and match deadline. Every schedule and match deadline can be found on the respective match page.

Default dates for every match are set at the earliest possible time after the schedule deadline is over. The date proposals and match comments from both teams are taken into account in order to ensure the best compromise in case the proposals do not match. Default dates are set automatically in the tiers using the Swiss system.

1.3.1.1. Only submitted playdays are used to generate the Default Date

Default dates in the season and playoffs are issued using only league rules, newsposts and submitted playdays from both teams. Schedule proposals, notices of availability and any other schedule-related communication exchanged between players, teams and casters, or in private conversations with admins is not valid and will be ignored when deciding default dates.

1.3.1.2. Matches can only be rescheduled by mutual agreement 

A scheduled match can only be rescheduled within the play range of the match once both teams have agreed.

1.3.1.3. Late matches are not allowed

Every match has to be played and submitted within its week’s deadline. If the results are not submitted before the result deadline shown at the top of the match page, both teams will receive no points and Minor Warnings will be applied. These warnings will not be removed, even if the match has been played. Late result submissions within a Swiss style competition are not possible.

1.4. Use the match comments to record agreements on mercs, servers and other cases

We encourage using the match comments to keep in touch with your opponents. Any agreement between two teams regarding the use of mercs or servers must be recorded on the relevant match page and cannot be retracted. Only Leaders and Deputies are given the authority to make decisions on these issues.

If your opponent allows a merc, you are expected to extend the same courtesy to them.

1.5. Roster locks

Every season will have a roster lock that gets enabled as soon as the last week of the regular season / group stage starts unless specified differently for the competition. Teams within a competition with an active roster lock are not able to add new players to their roster. The roster lock of a competition gets lifted once the wrap-up post has been published.

1.6. Warnings may lead to point deduction and/or removal from a competition

General System

  • Three Minor Warnings = One Major Warning
  • One Major Warning = Deduction of one point
  • Two Major Warnings = One Meta Warning, deduction of three points
  • Three Major Warnings = Expulsion from the current competition

Minor Warnings:

  • Incorrect/missing screenshot (Can be removed if the screenshot is provided later.)
  • Using an unregistered player
  • Using a merc without permission
  • Violating the Pause Rule (1st time)
  • Using a banned weapon
  • Use of non-English language (Note: Other languages are allowed if both teams are from the same country.)
  • Unable to provide a requested Demo (1st time) (Can be removed if the demo is provided later.)
  • Flaming (1st time)
  • Not showing up for a match (Plus a default loss for that particular match.)
  • Any other rule break (1st time)

Major Warnings:

  • Incorrect/missing screenshot (After 1st time) (Can be removed if the screenshot is provided later.)
  • Any attempts of fraud
  • Not being able to provide a requested demo (After 1st time) (Can be removed if the demo is provided later.)
  • Violating the Pause Rule (After 1st time)
  • Flaming (After 1st time)
  • Cheating (Plus a possible reduction of extra points and banning of the player involved, dependent on the situation.)
  • Any other rule break (After 1st time)

Three Minor Warnings stacking up to a Major Warning makes the Minor Warnings in question no longer removable.

In case of missing screenshots and demos you can contact the admins on Discord to get your warnings removed after submitting them on the site.

1.7. Committing or supporting fraud is strictly forbidden

Committing or supporting the act of fraud is strictly forbidden.

Different types of fraud include (but are not limited to):

  • Playing a match to a completely or partially pre-determined result.
  • Manipulating screenshots, chatlogs or match results.
  • Impersonating players, ETF2L staff or contacts of the league (with malicious intent).
  • Non-permitted acquisition of profits (e.g. selling spots on your roster, monetizing ETF2L-specific content without our permission).
  • Using alternate accounts to vote in the award polls.

Every case will be reviewed individually and penalties may vary based on the severity of each offense.

Any decisions made will be at the discretion of the admin team and all circumstances are going to be taken into account.

1.8. Disruption of ETF2L and its services is strictly forbidden

Causing disruption to ETF2L (ETF2L website, ETF2L matches or any other service run by ETF2L) is strictly forbidden.

This includes, but is not limited to: 

  • Intentionally connecting to an in-game server during an ongoing match.
  • Tampering with server settings to disrupt or create an advantage for a team.
  • Attacking a server with a Denial of Service attack.
  • Connecting to a team’s voice server during an ongoing match with the intention of causing disruption. 

Every case will be reviewed individually and penalties may vary based on the severity of each offense.

Any decisions made will be at the discretion of the admin team and all circumstances are going to be taken into account.

1.9. Players may not bet on their own matches on third party betting & gambling services

ETF2L holds no responsibility for risks connected with gambling or betting on third-party services.

This includes, but is not limited to, lost bets, overturned results or other events leading to the loss of valuables and/or profit.

Players caught betting on their own matches, taking bribes or having an incentive to tamper with the genuine result of a match in any way are subject to penalties such as league bans and potential bans on the third-party service site.

Naturally the usage of alternate accounts or other people as betting proxies is also forbidden, accomplices will face a penalty as well.

 

2. Players

2.1. Every player has to record Demos

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

Admins may request demos up to the end of the competition the match was played in until the wrap-up post is published. They can request as many demos as they require.

The opposing team can request demos up to 48 hours after the match was scheduled to start. They can request demos from up to two players, who will then have to provide their demos for all played maps. Players have to record the entirety of their official matches. Missing rounds and halves can count as a missing recording and may result in a team warning and an infraction for the player.

A player whose demos have been requested has 72 hours to upload the demo, 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 hosters will be ignored.

2.1.1. Penalties for not providing requested demos

Failure to provide a requested demo will result in penalties for both the player and their team. If a team fails to supply player demos in multiple matches they will be given a more severe punishment.

Player penalties:

  • First time: No ban.
  • Second time: Player is banned for two weeks from all ETF2L competitions.
  • Third time: Player is banned for two months from all ETF2L competitions.
  • Fourth time or more: Player is banned for one year from all ETF2L competitions.

Team penalties:

  • First time: Minor Warning that can be removed if the demo is uploaded.
  • Second time or more: Major Warning that can be removed if the demo is uploaded.

Penalties are applied if a requested demo is not provided within 72 hours. If a player was in a team before being banned and is unable to rejoin due to roster-lock being active contact an admin to be re-added.

2.2. Nickname rules 

2.2.1. Nickname changes allowed in total

Name changes on ETF2L can only be done by administrators. If you want your name changed, contact an admin on Discord. You can get your name changed a total of four times. There are no exceptions.

2.2.2. Players playing in matches casted by an org must use their real nicknames

All players who play in matches casted by an org must use their ETF2L nickname. Team tags and sponsorship additions are allowed, but the nickname should be exactly the same as on ETF2L. Each incorrect nickname will warrant a separate Minor Warning; a team can receive this punishment multiple times per match.

2.2.3. Abusive messages, nicknames and avatars are not welcome

Try not to use the chat function during a match unless if it is in a positive manner. Any offensive chat as well as spamming binds may lead to a warning for your team. Chat abuse and racist or offensive names / steam avatars / … will not be tolerated and may be punished with warnings or bans.

2.2.4. Different nicknames during official

During your official matches you are forbidden from using two or more similar nicknames and from using characters that make your name invisible. Each player should have a recognizable by name.

2.3. Two team change per competition allowed

A “team change” counts as joining another team and playing a competitive match for that team. Every player is allowed to change team twice during a competition. 

Note: A player changing from a “dead team” does not count as change. A team counts as “dead” if it did not play another match in the competition.

2.4. No account sharing and multi accounts

Every player is limited to only one ETF2L account at any time. Creating multiple accounts or multiple players using one account is not allowed. Multiple players from the same household (family, close friends, roommates, …) that may be sharing the same IP address must notify admins and use seperate ETF2L and Steam accounts.

Players caught creating multiple ETF2L accounts or allowing the use of their Steam account to a third party in official matches may face punishment ranging from deactivation of the account to reversal of match results and a Major Warning or a league ban. 

Evading bans via alternate accounts or unbanned players sharing their account with a banned player is strictly forbidden as well.

Each case will be reviewed individually and penalties will be assigned based on the severity of the offense and its impact on the competition.

2.5. No wiping of a player’s ETF2L history

We do not wipe a player’s ETF2L history – matches played etc. – in any way, be it by deleting an account or by allowing a player to use a new account, while blacklisting the older account. However we can switch Steam accounts linked to a player’s ETF2L account.

If you wish to change the attached Steam ID of your ETF2L account, contact admins with a reasonable motive and they will change it for you if your request seems legitimate. Admin discretion applies.

 

3. Match Rules

3.1. League Configs must be used for all matches

All ETF2L matches have to be played with up-to-date versions of our [League Configs].

3.2. Status & Scoreboard screenshots required

One member of each team has to take a status screenshot before a match is starting and after every player switch. 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 can be uploaded while submitting the result or by either team leader at a later date [LINK].

If any map screenshots are missing after the match result deadline, and the result has not been verified by the teams, both teams will receive a Minor Warning. Missing status screenshots will be punished with a Minor Warning even if the teams verify the result. The second violation of this rule will be punished with a Major Warning.

For the 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 font required will be the one that Team Fortress 2 uses by default. OSX and Linux versions have a different console font in use by default which cannot be parsed by the bot, therefore we recommend teams to have at least one player running the Windows version of Team Fortress 2 in order to take the necessary screenshots.

Warnings for missing screenshots can be removed by providing the missing screenshot and contacting an admin afterwards.

3.3. A delay of 15 minutes is allowed

A match may be delayed by no longer than 15 minutes. If a team fails to ready up with an eligible team present on the server 15 minutes after the match was supposed to start, the opposing team may claim a Default Win.

After a map change, both teams have up to 10 minutes to organise, starting when the first player joins the server. If a team fails to ready up with an eligible team present on the server after that, the opposing team can claim a Default Win, however only for the map concerned, not for the entire match.

In order to claim a Default Win, please take a status screenshot of your team being available on the server at match time, gather any evidence you think concludes the case (demos or server logs) and contact an admin about the issue as soon as possible.

3.4. Maps need to be played in the set order

Maps are required to be played in the order as they are mentioned on the match page from left to right. Teams may play already set season/cup maps in a different order if they choose to, but only if both teams agree.

3.5. Deciding sides

If teams cannot agree which team plays RED and which team plays BLU, they must perform a Heavy Fist Fight.

Note: No unlocks may be used during a Heavy Fist Fight. Only the stock fists are allowed.[Explanation]

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

Up to half of a team’s active line-up may be changed during one season. Any player that joins the roster after the provisional tiers have been published is classified as “new”. If half or more of the players you use in a match are “new”, you may receive a warning or suffer a default loss. A team can receive multiple punishments during the season if they continue to use a roster of “new” players, even if that roster remains the same.

For example:
In 6v6, if a team adds two or fewer players to the roster after the provisional tiers were announced, the team will receive no warning. However, if a team adds three or more players to the roster after the provisional tiers were announced and uses them in one or multiple official matches, the team will receive one or more warnings depending on how many matches they broke the rules.

In HL, if a team adds four or fewer players to the roster after the provisional tiers were announced the team will receive no warning. However if a team adds five or more players to the roster after the provisional tiers were announced and uses them in one or multiple official matches, the team will receive one or more warnings depending on how many matches they broke the rules.

In order to allow leniency for teams that are forced to change their line-ups, team leaders are required to contact admins on Discord 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

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. 

Each team has a one point limit for 6v6 and two point limit for Highlander. If you go over the limit you will be punished. 

For example:

In 6v6, a High/Division 2 player joining a Low team will count as two points. A player counts as “experienced” in a tier if during the last three seasons they played three 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. For example, for Season 35 experience, we will look at matches from Season 32 onwards. Playoff games will count towards the number of matches played in the respective higher tier. This means that playing a Low playoff official will count towards the total of officials played in mid. 

In HL if a Division 1 player joins a Mid team the player is accounted for with two 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. Decisions will be made at Admin discretion..

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

3.7.1. All previous experience will be taken into account in the Open/Fresh Meat tier

This rule applies to the Open/Fresh Meat tier, given that a Low tier is currently in play.

If a player has previously participated in a higher tier, all of their previous experience will be taken into account in the lowest skill tier.

3.8. Player changes during a match

Teams are allowed to switch players during the match, with or without a pause, only once per map, as long as the joining player is rostered on that team or has been approved as a merc by the opposing team. However, using this to bypass spawn times is strictly forbidden. Furthermore, a team may under no circumstances have more than six players on the server for 6v6, and no more than nine for 9v9 (Highlander). Teams are allowed to switch players after a map change (as long as they are entered correctly on the team roster or have been approved as a merc by the opposing team).

3.9. Only authorized spectators allowed

Only spectators authorized by the league, or for the use of Source TV, are allowed.

3.10. Teams may request a pause if problems occur

Teams may request a pause at any time during a match. If you need to pause, you must clearly request a pause (for example: “Pause please”). The other team is then required to pause at the first appropriate time (e.g. not in the middle of a push). Teams must pause within 15 seconds of being asked. Not responding to a pause request will lead to penalties like a Minor Warning or, in extreme cases, a Major Warning and forfeit of the map.

You may not resume the game under any circumstances without giving proper warning to the other team.

Each team has the right to one pause per map.

A pause may last no longer than five minutes.

If your opponent allows a pause longer than five minutes, or more than one pause, you are expected to extend the same courtesy to them.

3.11. Playoff matches must have maps chosen before matches are about to be played

If one of the two teams avoids or does not respond to map picks 36 hours before the match is scheduled, the opposing team will get a map picking advantage. If one of the two teams keeps being uncooperative up until four hours before the match is scheduled, the other team will get to choose all the maps for the relevant match.

If there are any issues, contact an admin on Discord as soon as possible. Use the match comments for any official agreements.

3.12. Weapons and Hats rules

Specific whitelists are used during the season for each gamemode. To see the full list of what weapons, cosmetics and taunts are allowed in official matches check this 6v6 whitelist.tf overview or this Highlander whitelist.tf overview.

Moreover hats and misc items are allowed. Unique and unusual hats are also allowed. The ETF2L 6v6/HL whitelists have to be used during official matches.

3.12.1. Weapons reskins allowed

All weapon reskins (Lugermorph, Holy Mackerel, Original, Frying Pan, Iron Curtain, Golden Wrench, Big Kill, Enthusiast’s Timepiece, “Festive” stock weapons etc.) are allowed.

3.12.2. Taunts

Only default weapon taunts and taunts with fixed durations are allowed. The ETF2L 6v6/HL whitelists have to be used during official matches.

4. Premiership Only Rules

4.1. Premiership players must always use their ETF2L nicknames during officials

All players who play a match in the Premiership division must play with their ETF2L nickname. Team tags and sponsorship additions are allowed. The nickname should be exactly the same as on ETF2L. Each incorrect nickname will warrant a separate Minor Warning; a team can receive this punishment multiple times per game.

Premiership players are not allowed to change their ETF2L nickname while the relevant season is underway.

4.2. Premiership teams have a limited amount of team name changes

All Premiership teams are allowed to change their team name to a maximum amount of 3 times per season. This applies from the day the main season starts until the team does not have any upcoming matches to play in the season. If a team has already reached the maximum amount of team name changes in a season and wants to change their team name again, they must contact an admin before doing so, otherwise the team will get a separate Minor Warning for each additional change; a team can receive this punishment multiple times per season.

4.3. SourceTV demos for premiership matches are mandatory

For every match in the premiership division it is mandatory to upload SourceTV demos for all maps played. The responsibility to upload the demos is on the team that owns the server or, if the server is owned by neither team, on the team that arranged the server.

In case of a technical failure of the server, the demo does not have to be uploaded, if it can be proven.

Failure to upload the demo within 72 hours is punished with a Minor Warning for the responsible team. The warning can be removed if the demo is provided before the end of the regular season (before the release of the playoff fixtures). Repeated offenses will be punished with a Minor Warning each.

4.4. Penalties during Premiership Playoffs and Tiebreakers

Specific Minor and Major Warnings now result in a cut of any prize money in that specific competition. A Minor Warning results in 10% of any cash prize won being docked. A Major Warning results in 30% being docked. Please note that admin discretion is applied to every single case related to penalties in the Premiership Playoffs. Only specific Minor and Major Warnings are applied to this rule, they include but are not limited to:

  • Flaming (Minor and Major)
  • Using an unapproved merc
  • Using an unlisted player
  • Nickname rule violation
  • Fraud Attempt
  • Using a banned player
  • Cheating
  • Missing, wrong, or incomplete status screenshot
  • As a special rule, forfeiting or not showing up to a match in the Premiership Playoffs is punishable by 50% of any cash prize being docked.

5. Servers

5.1. Be reasonable regarding servers

Both teams can agree on the server which both maps are played on, or agree to play one map on each team’s server. If a third map is needed to be played or if both teams failed to reach a compromise an admin will provide the teams a server to play on.

Make sure the server is adequate before you start – complaints cannot be made after the match.

5.1.1. European server recommended

ETF2L is a European League, you cannot force opponents to play on non-European servers. We strongly recommend using servers located in central Europe, such as the Netherlands or Germany.

5.2. Servers need to be password protected

All servers used for ETF2L matches must be password protected.

5.3. Unusual server settings may be considered cheating

Servers with abnormal settings may be refused for matches by the league and/or be classed as cheating.

5.4. Servers must be started with “-sv_pure”

Match servers must have the parameter “-sv_pure” or “-sv_pure 2” in the launch options to support the sv_pure setting. sv_pure must be set to 2 in all ETF2L competitions.

 

6. Cheats & Scripts

6.1. Bug-Using is not allowed

Any kind of “Bug-Using” is not allowed. Players abusing exploits and map bugs will be penalized on a case-by-case basis depending on the intent and impact on the matches. Possible penalties may include warnings, default losses for one or more match rounds and league bans.

Examples of banned exploits:

  • Quantum Crouch/Schrodinger’s Crouch
  • Jetpack Exploit
  • Demoman explosive crouch jump bug against sentry fire
  • Bugging player model animations
  • Damaging/Killing players during setup time

Most commonly seen banned map spots include:

Upward: Teleporter in dropdown spot on 3rd point, resupply cabinet through the wall at RED forward spawn

Gullywash: Last point shutter shoot through

Gullywash: Taunting through the ceiling of elbow

Product: Skybox bugged spot

Steel: Using flamethrower through steel sliding doors on A

If you are unsure about the legality of any sneaky spot on a map, please contact an admin on Discord to clarify the situation and prevent complaints from your opponent.

6.2. Cheats are not allowed

Any kind of cheats are not permitted. Players who are found guilty of using cheats will be banned for 1 year from any ETF2L competitions. There is no appeal process for bans.

6.3. Scripts

Scripts that allow a player to perform an action in-game that they would not be able to execute without the script, or scripts that purposefully disrupt the player hitbox are banned. Scripts that freeze or glitch the player model (e.g. in mid-air to be less predictable) to make it harder to hit are also banned.

Usage of banned scripts will be penalized on a case-by-case basis, depending on the intent of the script and the impact on the match. Possible penalties may include warnings, default losses for one or more match rounds and league bans.

Examples of banned scripts:

  • Chargeturn script (this includes the use of other peripherals to achieve sharper turn angles)
  • Panic Script
  • Freeze glitching via spamming hud_reloadscheme

Examples of allowed scripts:

  • Duck jump script
  • Null-cancelling movement script 
  • Rocket/Detonator jump script
  • Mask uber script
  • Team say scripts

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

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 [e.g. via surfaceproperties])
  • Removal of map props 

Examples of allowed modifications:

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

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

6.5. VAC Bans

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

6.6. Exploiting the retry command is not allowed

Reconnecting to the server to reset your respawn time and gain an unfair advantage is considered exploiting, and may be punished with a default loss for the map and a Minor Warning for the offending team.

6.7. Masking ping is not allowed

It is prohibited to alter or mask your in-game ping in official matches. Players found manipulating their ping may be punished by a Minor Warning.

Private messages and friend requests on Steam etc. do not have to be acknowledged by our admin staff.

7. Admins

7.1. Requesting admin help

To request help from an admin or to file a match complaint, please create an admin request in our Discord. To do so, follow the instructions in the “#admin_requests” channel.

7.2. Admins are listed on the staff page

All active admins are shown on the staff page.

7.3. Admin discretion

The ETF2L rules are enforced at the discretion of the admin team. Any complaints will be judged on a case-by-case basis and different punishments may be handed out in each case.

 

8. Explanations

8.1. Default dates

ETF2L sets a default date for all matches based on the submitted available playing days for both teams. Teams can still play on a different date if both teams agree, but not after the deadline for the match.

Note: Teams do NOT have to reschedule matches which have been given a default date.

8.2. Heavy Fist Fight

A Heavy Fist Fight can be used to settle arguments over map pick advantages or choice of team colour. Please only use a Heavy Fist Fight to settle an argument when it is explicitly stated in the rules of the competition or advised by an admin.

One Heavy from each team participates in a melee fist fight. The winning team gets to decide which side to start on or who gets the map pick advantage in a situation where both teams are equally seeded. No unlocks, weapon-switching, buffs or healing of any kind, taunting, camping or fleeing is allowed. Multiple Heavies from each team are allowed as well if both teams agree.

8.3. Picks/Bans System

This system is used to decide maps for playoff and tiebreaker matches when specified by the competition.

Case 1: For any matches where both teams are equally seeded (e.g. tiebreaker matches, cups), the following system has to be used.

Both teams need to agree on who eliminates first. If the two teams cannot agree, they need to perform a Heavy Fist Fight [Explanation]. The winner of this Heavy Fist Fight can decide which team is Team A and which is Team B.

  • Team A eliminates a map
  • Team B eliminates a map
  • Team B picks a map
  • Team A picks a map
  • Team A bans a map
  • Team B bans a map
  • The remaining map is the decider map

Case 2: For any matches where both teams are unequally seeded (e.g. playoffs), the following system has to be used.

The higher seeded team can decide if they want to start or if the other team should.

  • Team A eliminates a map
  • Team B eliminates a map
  • Team B picks a map
  • Team A picks a map
  • The higher seeded team chooses the decider map from the remaining three maps

For both cases a map pool consisting of seven maps is assumed. If less maps are available, instructions on how to proceed will be given on the match page.

8.4. Loser’s Pick System

This system is used to decide maps for playoff and tiebreaker matches when specified by the competition.

  • High seed picks the first map
  • Loser of the first map picks the second map
  • Loser of the second map picks the tiebreaker map (if necessary)

For any matches where both teams are equally seeded (e.g. tie-breaker matches, cups), the following system has to be used:

  • Both teams need to agree on the first map. If the two teams can not agree, they need to perform a Heavy Fist Fight [Explanation].
  • Loser of the first map picks the second map
  • Loser of the second map picks the third map (if necessary)