General Rules
1.1 ETF2L Timezone = CET/CEST
1.2 Scheduled matches have to be entered on the League Calendar
1.3 Separate schedule & match deadline for every match – Default Date for unscheduled matches
1.4 Use the match comments to record agreements on ringers, servers and other cases
2.1 All players are welcome
2.2 Only correctly entered players are allowed to play
2.3 One team change per competition allowed
2.4 Every player has to record Demos
2.5 Every player has to play with the nickname of the league site
2.6 Abusive chat, nicknames and avatars are not welcome
3.1 League Configs must be used for all matches
3.2 Status & Scoreboard screenshots required
3.3 Scheduled Matches can only be postponed by using a Wildcard or by contacting an admin (if both teams agree)
3.4 A delay of 15 minutes is allowed
3.5 Switching line-ups or hijacking teams is not allowed
3.6 Player changes during a match
3.7 Only authorized spectators allowed
3.8 Teams may request a pause if problems occur
3.9 Warnings may lead to point deduction or removal from a competition
4.1 Timelimit for 5cp maps: 30 minutes
4.2 Winlimit for 5cp maps: Point difference of 5
4.3 On 5cp maps: Decider round in case of a draw
4.4 KOTH maps are played with Winlimit 3 (BO5)
4.5 Attack/Defence maps and payload maps are played with stopwatch mode
4.6 Gravelpit and Gorge = 2-3 Rounds using ABBA style
4.7 Deciding sides; Melee fight if teams don’t agree
4.8 cp_gravelpit: Red players may not build a teleport in their spawn area
4.9 cp_gravelpit: Players may not place sticky traps on the underside of capture point A
5.1 Be reasonable regarding servers
5.2 European server recommended
5.3 Servers need to be password proteced
5.4 Unusual server settings may classed as cheating
6.1 Bug-Using is not allowed
6.2 Cheats are not allowed
6.3 Normal Crouch Jump bind allowed
6.4 Taunt slide bug is forbidden
6.5 VAC Bans
7.1 Requesting admin help
7.2 Admins on the staff page
7.3 Admin discretion
Explanation: “Map-Pick Elimination System”
1. General Points
1.1 ETF2L Time zone = CET/CEST
ETF2L announces all times in either Central Europe Time (CET) or Central European Summer Time (CEST). All matches have to be entered in CET/CEST. A clock displaying the current time can be found on the homepage. [Link]
1.2 Scheduled matches have to be entered on the League Calendar
All scheduled matches are supposed to be entered on the ETF2L Calendar. Teams may only claim a Default Win if the match has been entered on the calendar.
1.3 Separate schedule & match deadline for every match – Default Date for unscheduled matches
Every match has its own schedule and match deadline. All deadlines can be found on our [Calendar] or at the [Events] subpage.
If a match is not arranged by the schedule deadline, admins will decide a Default Date for that match. After that, the date can only be changed if both teams agree on another date or if one team takes a wildcard.
Please note that using a wildcard in the last play week of a competition is not allowed. If your opponent uses a wildcard during the last play week please contact an admin to reinstate the old schedule.
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 an opponent. Any agreement between two teams regarding the use of mercs or servers must be recorded on the relevant match page. If anything requires verification it MUST be documented either by a screenshot of the original conversation or by leaders from both teams providing confirmation in the match comments.
If your opponent allows a merc, you are expected to extend the same courtesy to them.
2. Players
2.1 All players are welcome
Any player of any country is welcome to play in the ETF2L.
2.2 Only correctly entered players are allowed to play
Players are eligible only when they have correctly entered their Steam ID and are verified on their team’s roster.
2.3 One 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 once during a competition. A player changing from a dead team does not count as real change.
2.4 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 14 days after the match was played. 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 2 players for each map.
A player whose demos have been requested has 72 hours to upload the demo, starting from the time the request was made.
Failure to supply a requested demo will be punished.
2.5 Every player has to play with the nickname of the league site
Every player should play with the nickname they have chosen on ETF2L league site.
2.6 Abusive chat, nicknames and avatars are not welcome
Try not to use the chat function during a match to comment on anything unless it’s in a positive manner. Chat abuse or racist names/avatars will not be tolerated.
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. When submitting the result, a team leader has to upload all relevant screenshots.
If one or more score screenshots are still missing after one week, and the result has not been verified by the teams, both teams will receive a minor warning.
Missing status screenshots will be awarded with a minor warning no matter if the result has been verified by the teams. The second violation of this rule will be punished with a major warning and one point deduction.
3.3 Scheduled Matches can only be postponed by using a Wildcard or by contacting an admin (if both teams agree)
Once a game is scheduled and entered in our Calendar, it can only be postponed beyond the match deadline if both teams agree or if one team uses a Wildcard. If both teams agree to the reschedule (for example because there is a LAN) and want to postpone the match please contact an admin an explain the case. Both teams will receive a warning for any match unplayed after its match deadline.
3.4 A delay of 15 minutes is allowed
A delay of 15 minutes for showing up for a match is allowed. If a team fails to have a complete team ready on the server 15 minutes after the match was supposed to start, the other team may claim a Default Win.
After a map change, both teams have 10 minutes to organize, starting when the first player joins the server. If a team fails to have a complete team ready on the server after that, the other team can claim a Default Win, however only for the map concerned, not for the entire match.
For claiming a Default Win, please make a status screenshot of your team 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.5 Switching line-ups or hijacking teams is not allowed
A team may not be replaced in a competition by a new team or lineup without admin permission. Teams can be qualified as ‘new’ if none or very few of the lineup at the start of the season or cup are still active and participating. We will look at teams breaking this rule and holds the right to remove them from the league. Any decisions made will be at the full discretion of the admin team and all circumstances will be taken into account. If your team is facing extreme lineup changes please contact an admin.
3.6 Player changes during a match
Teams are allowed to switch players after a map change (as long as they are entered correctly on the team roster). Player changes during a map is only permitted if a player is having technical problems.
3.7 Only authorized spectators allowed
Only spectators authorized by the league, or for the use of Source TV, are allowed.
3.8 Teams may request a pause if problems occur
Teams may request a pause at any time during a match. Reasons for pausing can include:
- Player drop
- Server problems
- The match is unplayable due to network issues
If you need to pause, you must clearly request a pause and give a reason for it (for example: “Pause please, player drop”). 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 accompanied with the forfeit of the round in question, 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 not last longer than 5 minutes.
If your opponent allows a pause longer than 5 minutes or more than one pause you are expected to extend the same courtesy to them.
3.9 Warnings may lead to point deduction or removal from a competition
If a team receives enough warnings, points will be deducted from that team for the running season. Points will be deducted, and warnings applied as follows:
General System
- 3 Minor Warnings = 1 Major Warning
- 1 Major Warning = deduction of 1 point / 10 points deduction on the ladder
- 3 Major Warnings = expulsion from the league
Minor Warnings
- Incorrect/missing screenshot (can be reverted if screenshots uploaded afterwards)
- Using an unregistered player
- Using a merc without permission
- Violating the Pause Rule (1st time)
- Unplayed match after match deadline
- 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)
- Flaming (1st time)
- Not showing up for a match (and a Default Loss for this match)
- Any other rule break (1st time)
Major Warnings
- Any attempts of fraud
- Not being able to provide a requested Demo (after 1st time)
- 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, dependant on the situation)
- Any other rule break (after 1st time)
4. Maps
4.1 Timelimit for 5cp maps: 30 minutes
Timelimit 30 has to be used for all maps not played with Stopwatch mode.
4.2 Winlimit for 5cp maps: Point difference of 5
If a team reaches a 5 point lead on a CP map, that team wins the map.
This rule has no effect on Stopwatch Maps and CTF maps.
4.3 On 5cp maps: Decider round in case of a draw
If the score is tied after the timelimit has been reached, a decider round (golden cap) will have to be played. If no team has won the round after 10 minutes have passed, the win will be awarded to the team controlling the middle capture point.
4.4 KOTH maps are played with Winlimit 3 (BO5)
King of the Hill maps will have to be played until one team reaches 3 round victories and wins. Timelimit is off for KOTH maps. Please make sure mp_timelimit is set 0 on the server, and use mp_winlimit 3 to make the win trigger automatically.
4.5 Attack/Defence maps and payload maps are played with stopwatch mode
Attack/Defence and payload maps like Gravelpit, Gorge, Steel, Badwater and Upward are played with stopwatch mode. This means the first team attacking will set a time and amount of captures, which the second team will then have to beat. Please use the correct config so the time will be tracked automatically. Maps should be played one full round with each team attacking once each map awarding 1 point.
4.6 Gravelpit and payload maps: 2-3 Rounds using ABBA format
cp_gravelpit and payload maps have to be played with 2-3 rounds. In the first 2 rounds the ABBA format will be used.
In the case of both teams taking one round (1:1) there will be a decider round. In the first 2 rounds the teams should note the final cap time of the first team attacking. The team that has the best cap time (or more caps in the case a team did not cap all points) can choose if they want to attack or defend first in the 3rd round. Remember to reload the config between rounds, so teams can be switched.
Example: Team A attacks and sets a time of 4:56. Team B then attacks and caps the last point faster then Team A did, setting the score 1:0. Next team B attacks first and sets a time of 5:28, team A then attacks and caps faster. The score is then 1:1 and a decider round will need to be played. Since Team A’s attack time of 4:56 was faster then team B’s 5:28 they can choose who attacks first.
4.6.1 Golden Cap rules do NOT apply to cp_gravelpit. Whichever team wins the map will receive 3 points in League standings
Do not tick the golden cap box if your match ended 2-1 or 1-2. Full three points will be awarded to the winning team. Possible overall results are: 2:0, 0:2, 1:2, 2:1
4.6.2 Payload maps are played as best of 3
Payload maps are played as best of 3. In case of a 2-0 win, the winner gets 6 points and the loser gets 0 which equals 3 points per map played. In case of a 2-1 win the winner gets 4 points and the loser gets 2 which equals 2 points per map played. Please submit the results as follows:
- If you played two maps and the match was won 2-0, add ’2-0′ as result for both maps
- If you played three maps and the match was won 2-1, add ‘2-1′ for both maps and tick the golden cap box for both maps
4.7 Deciding sides; Melee fight if teams don’t agree
If teams can not agree which team plays red and which team plays blu, they must perform a Heavy Fist Fight. This means that a Heavy from each team have a melee fist fight where the winning team gets to decide which side to start on. No unlocks, weapon-switching, health regeneration, buffing, taunting, camping or fleeing allowed.
4.8 cp_gravelpit: Red players may not build a teleport in their spawn area
The Red team may not build a teleporter inside their spawn.
4.9 cp_gravelpit: Players may not place sticky traps on the underside of capture point A
Players may not put stickies under A to damage targets through the floor.
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 clan’s server. If you can’t agree to play either way then the game must be played on an ETF2L league server (please contact an admin to arrange this).
Make sure the server is adequate before you start – complaints cannot be made after the match.
5.2 European server recommended
The ETF2L is a European League, you cannot force opponents to play on non-European servers. We strongly recommend using servers located central in Europe, such as the Netherlands or Germany.
5.3 Servers need to be password proteced
All servers used for ETF2L matches must be password protected.
5.4 Unusual server settings may classed as cheating
Servers with abnormal settings may be refused for matches by the league and/or be classed as cheating.
6. Cheats & Scripts
6.1 Bug-Using is not allowed
Any kind of “Bug-Using” is not allowed. Player using bugs will be punished.
6.2 Cheats are not allowed
Any kind of cheats are not permitted. Players using cheats will be banned for 1 year.
6.3 Normal Crouch Jump bind allowed
Executing the normal “crouch jump” by a binding is allowed.
6.4 Taunt slide bug is forbidden
During a match, players may not use a combination of Taunt and Jump or taunt while falling from ledges (it affects the hitboxes).
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. Players receiving VAC bans before March 15, 2012 will not be affected.
7. Admins
7.1 Requesting admin help
To request help from an admin or to file a match complaint, please join our IRC channel #etf2l on quakenet, type !admin and wait for the next free admin to respond. Please do not add admins on Steam to ask questions or directly query them on IRC.
If you do not have an IRC client installed on your pc you may use our webchat plugin.
7.2 Admins on the staff page
All active admins are shown at the staff page. When requesting help from an admin on IRC you may specify for which competition you need an admin, e.g. !admin highlander or !admin 6v6
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.
Explanation: “Wildcard”
Every team has a specific number of Wildcards per competition, which are used if a team has to postpone a scheduled match without their opponent’s agreement. A Wildcard has to be used no less than 15 minutes before the game is supposed to start. A Wildcard can be used by selecting the Wildcard function located on the top of the match page. Please try to contact your opponent if you use your Wildcard on particularly short notice.
A Wildcarded match must be played no more then 14 days after the Wildcard was taken.
If one team has already wildcarded a match, the other team can also wildcard it if they have a wildcard available. Matches cannot be wildcarded more than once per team.
Explanation: “Map-Pick Elimination System”
This system may be used from time to time in different competitions as a method of deciding which maps to play in a match.
- 1st Team starts, eliminating first map.
- 2nd Team eliminates a second map.
- Continue the procedure until there are 3 maps remaining.
- The team whose turn it is now nominates their map, which will be played first.
- After that the other team nominates their map, which will be played second.
- The 3rd map is the decider map. If more maps are needed according to the specific competition rules, the most recently eliminated maps are played.
Example:
Please see specific competition rules for correct Map Pool.
- 1st Team: “We eliminate dustbowl!” – remaining maps: well, granary, gravelpit, 2fort, turbine, badlands
- 2nd Team: “Oh no, but ok, we eliminate 2fort!!” – remaining maps: well, granary, gravelpit, turbine, badlands
- 1st Team: “Yes ok, bye bye badlands!” – remaining maps: well, granary, gravelpit, turbine
- 2nd Team: “It’s ok we remove turbine” – remaining maps: well, granary, gravelpit
- 1st Team: “Hum, our map will be granary then…” – remaining maps: well, gravelpit
- 2nd Team: “Okok, ours is gravelpit.” – remaining maps: well (-> decider map if each team wins one map)
Map order for this example: granary, gravelpit, well (if needed: turbine, badlands, 2fort, dustbowl).
content rss