For some reasons (like coverages) it's allowed to play with mp_tournament "0". In this case it's important that both teams write "ready" into the chat and the serveradmin restarts the round with mp_restartgame "1".
9.1.2. Plugins
To prevent unwanted or unnoticed manipulations of the game, the installation of any plugins is forbidden, if they are not formally allowed in this section.
9.1.3. Choice of server
If it is not possible to agree on one server, every team has to play his own map on his own server.
It is also allowed to use a neutral server, if both teams agree.

If both teams can not agree on one server within a Weekly Match in the 6on6 Ladder, the team on the left side in the matchsheet is allowed to choose which map is to be played on which server.
9.2. Match
9.2.1. During the match
9.2.1.1. cp_gravelpit, cp_dustbowl, pl_goldrush and cp_wolf
Both maps start with a Heavy-only melee round at point A/1. The winning team decides whether to play attacker or defender first.

cp_gravelpit: Every team plays two rounds as attacker and two rounds as defender. (mp_maxrounds "4")
cp_dustbowl: Every team plays one round as attacker and one round as defender. (mp_maxrounds "2")
pl_goldrush: Every team plays one round as attacker and one round as defender. (mp_maxrounds "2")
cp_wolf: Every team plays one round as attacker and one round as defender. (mp_maxrounds "2")

The timelimit is deactivated. (mp_timelimit "0")
Both maps are played in stopwatch mode. (mp_tournament_stopwatch "1")
9.2.1.2. Other maps
Other maps are played with a timelimit of 30 minutes (mp_timelimit "30"). After that time the final score can be seen on the scoreboard. Sudden death mode has to be deactivated.
9.2.1.3. Decider
(Cup/Premiership only) If one map results in a draw a decidermap has to be played. The decider will be picked by eliminating out two of the three following maps: cp_well, cp_badlands and cp_pro_granary.

The team which stands on the left side in the matchdetails has to start eliminating.

The decider will be played as a golden cap. The first team to capture all 5 Control Points wins.

(Exception) If cp_gravelpit ends in a draw in a cup/premiership, a third round of cp_gravelpit has to be played.
9.2.1.4. Custom maps
If custom maps are played, the most current version of the map has to be used.

It's allowed to play cp_granary instead of cp_pro_granary if both teams agree.
9.2.1.5. ESL Aequitas
The usage of ESL Aequitas is mandatory. The Aequitas file of every player has to be uploaded within 24 hours after the match and has to be saved for 14 days.

If you fail to upload the files in time, your opponent is allowed to file a protest and request a deletion of the match.

The player(s) and the team will be penalized with 3 penalty points for every missing or incomplete Aequitas file. If it can be proofed, that a player has manipulated a Aequitas file intentionally, he and his team will recieve 6 penalty points. Players, who fail to upload Aequitas files multiple times, can be banned from all Team Fortress 2 leagues.
9.2.1.6. Forbidden scripts or configs
The usage of the following scripts is forbidden in ESL matches:
- Doublejump scripts
- Highjump scripts (this doesn't affect rocketjump scripts)
- Fastshoot scripts (f.e. fastshoot/-explode for pistol, rifle, stickies, ..)
- +duck spam to manipulate your hitboxes
- +duck or +attack on mousewheel
- Taunt command abuse during fights/escapes

It is not allowed to change the following cvars:
- cl_pitchspeed 225
- cl_yawspeed 210

Using illegal scripts configs will be penalized with two, four or six penalty points if the script lead to a game advantage. This depends on the script concerned and it is up to the admin responsible to decide this.

The usage of marcos or external programes (e.g. drivers) in order to bypass this rule will also be penalized if it has been proven.
9.2.1.7. Game interruption
In 1on1 and 2on2 competitions, the game has to be interrupted with the "Pause" command in case of a player drop. It is not allowed to continue the match 2on1 in 2on2 competitions. The remaining player / team has to wait for 10 minutes and has to write a protest ticket, if the dropped player / team fails to return on the server.
9.2.2. Matchbegin
As soon as both teams are ready, the match starts automatically (F4 / Tournament mode / ready).
If there are any problems with the map, it has to be reloaded and the game has to be restarted.

If you need to restart the Tournament mode, please use mp_tournament_restart.
9.2.3. Teamsize
The default teamsize is 6on6, but matches can be played 8on8 if both teams agree. In 8on8 events, the default teamsize of course is 8on8.
If one team is short of a player, the match can be played with uneven teams (6on5, 8on7), if both teams agree. This is not allowed, if a team is short of two or more players! Mercenaries (short "mercs" or "ringers") are not to be used at any time!
The match has to be postponed then (if both teams agree), or the complete team enters "didn't show up" as result.
9.2.3.1. Class restrictions
Classlimitations:
6on6: Classlimit 2, Mediclimit 1
3on3: Classlimit 1

Violating class restrictions is not allowed and will be penalized with three penalty points. The game can also be deleted if the winning team takes an advantage because of disregarding the classlimits.

Unlockable weapons:
Medic: all allowed
Pyro: all allowed
9.2.4. Bugs
Bugusing is not allowed and will be penalized with two, four or six penalty points if the bug lead to a game advantage. This depends on the bug concerned and it is up to the admin responsible to decide this.

Getting through floors and ceilings and skywalking is not allowed and also all positions, where textures disappear.
9.2.5. Nicknames
Every player has to use a nickname during matches, which has to be similar to the nickname in his ESL playersheet. Changing the nickname after the match has started is forbidden. Teams are allowed to use a clantag during teammatches. Filing a protest or support because of this rule is not allowed.
If an admin is impeded in his work because of an invalid nickname, he can penalize the team and the player.
9.2.6. Matches between subteams
Matches between subteams are allowed in the ladder, but have to be marked as such in the matchcomments.
9.2.7. Challenges within a Ladder (TF2)
Only one match is allowed between two participants within 7 days. After a team/player has been challenged, further challenges between the two teams/players are blocked for 7 days. After this, the team/player can be challenges once again.
9.3. Matchmedia
9.3.1. Screenshots
9.3.1.1. Results
A screenshot of the final scoreboard has to be taken after each round. Both teams are responsible for uploading those screenshots after the match.
9.3.1.2. Status screenshots
The command 'status' in the console shows a list of all players and their steamids. A screenshot of this list has to be taken. Both teams are responsible for uploading this screenshot after the match.
9.3.2. Demos / Replays
All players have to record demos from every single round of the match. Demos are recorded with the command 'record demoname'. The recording is stopped with 'stop'.
9.3.2.1. Requesting demos
Demos have to be requested within 30 minutes after the match. Every player is required to check the matchcomments and upload his demos if they were requested. Every team can request four demos. Non-specific demo requests are invalid.

Missing demos are penalized with 3 penalty points and the match is deleted if necessary.