9. Insurgency rules
9.1. General match rules
9.1.1. Gametype
The gametype is double elimination. Both maps are preset and chosen from the map pool. In every match, each team plays the USMC and the Insurgent side once on both maps.
9.1.2. Gameserver
If both teams have a war server, then one map is played on the server of team A and the other one on the server of team B. Except one team doesn’t have a server or both teams agree to play only on one server.
9.1.3. Score calculation
Each round the winning team is getting one scorepoint. If the roundtime exceeded without a winning team, nobody gets a scorepoint.
9.1.3.1. SteamIDs of the players
Every player has to add his STEAMID in his gameaccount.
9.1.4. Match procedure
9.1.4.1. Roundstart, server.cfg & teamswap
The serveradmin has to register with rcon on the server 'rcon_password XXXXXX'. He then has to execute the warsettings that can be downloaded here. Upload either the server file to the server into the insurgency cfg folder or copy the client file into your insurgency cfg folder on your harddisk. In case of using the server file, use this command to execute it: 'rcon exec esl5on5openingcup.cfg'. If you decide to use the client file, the executing command is: 'exec 5on5openingcup.cfg'
When both teams are ready the match will be started by the serveradmin with the roundstart.cfg by the following command: 'exec roundstart.cfg'. After the round is played, he switches both teams by using the teamswap.cfg. The command is: 'exec teamswap.cfg'. Both files can be downloaded here and have to be placed in the insurgency cfg folder on your harddisk.
9.1.4.2. Pause
The game may be paused by each team once per round for max. 60 seconds by pressing the pause button on the keyboard.
9.1.4.3. Upload
The following files have to be uploaded as soon as possible after the match. At least 24 hours after the match is over:
- rcon status screenshot [from the server admin]
- AEQUITAS log file (matchID.ZIP) [by each player]
9.1.5. Fade to black
It is possible, if both teams agree on it, to disable the fade to black mode. Therefore a sreenshot or match comment is needed to prove that both parties agree on it. The server admin has to type in console (after he has connected with rcon): rcon mp_fadetoblack 0
9.1.6. Playercounts
3on3 match: 3on3 and 4on4 are allowed
5on5 match: 5on5 and 6on6 are allowed
If a team has not enough players, their opponent can play with one player less. The necessary minimum playercount must be obeyed by both teams. The minimum playercount of for each Insurgency match is three.
9.2. Tournament rules
9.2.2. Draw
A draw results in a final round on a map from the specific map pool that wasn’t played yet. The team that signed up first to the tournament has the privilege to choose the map and the side they want to play on. The deciding map after a draw should not be a battle typed map.
9.3. League rules
9.3.1. Map pool
In an Insurgency ladder match each team can choose one map from the following pool:
ins_abdallah
ins_almaden
ins_baghdad
ins_buhriz
ins_haditha
ins_haditha_night
ins_hillah
ins_karkar
ins_samawah
ins_samawa h_night
ins_sinjar
ins_ramadi
9.4. Spawncamping
A behaviour is to be considered spawncamping when a player attacks an enemy player without leaving him the possibility to move. To move means in this case: The spawning player must have at least 3 seconds to load his weapon and start moving before he gets attacked. These 3 seconds are void and to be ignored if the spawning player either:
a) has already moved out of the certain area which he had spawned in, or
b) has already attacked his enemy
Spawncamping is a violation of the match rules and has to be clarified by an admin by the review of demo files and screenshots of the involved and/or accused individuals. It will be punished with penalty points.
9.5. Data and records
9.5.1. Demos and replays
Each player must record a demo. HLTV demos are not valid.
The demos are to be kept for at least 14 days and must be presented to the admin at request. If it should come to a protest, the demos must be kept until 14 days after conclusion of the protest.
If a player or team suspects that another player or team is violating a regulation during a game, the demo can be demanded of the opposing team straight away. The admins are only to be called in, when suspicions continue to exist even after the demos have been viewed. In this case, the clan or player may proceed and send the admin the game demos. The admin will then take the appropriate action.
It is recommended to voluntarily make all demos available to the public in order to keep the ladders transparent and interesting. For specific rules, please read the respective game rules.
9.5.1.1. Recording demo
EVERY SINGLE PLAYER is obliged to record a demo of the match. A demo is recorded at the beginning on each map via the console command ´record [demoname]´ and is completed at the end of each map via the command ´stop´.
9.5.1.2. Demanding demos
Demos can only be demanded up to a maximum of 30 minutes after a match via the 'Request match media (demos/replays)' function on the match details page. A separate demo per map has to be recorded.
Each team is obligated to check the match comments within 30 minutes after the match and if necessary load up the demanded demos within 24 hours.
9.5.1.3. Uploading Demos
Demos have to be packed into .zip archive. While being uploaded the server will check whether the file is corrupted or not. If you use WinRar to zip your files make sure that you choose "Compression method - normal", if you don't you will get an error message like "file corrupted" and the upload will be aborted.
9.5.1.4. Editing Demos
It is strictly forbidden to edit demos.
9.5.2. Aequitas Files
Each player has to use the latest Aequitas version during the entire match ( latest Aequitas version). Uploading the Aequitas files to the ESL FTP within 24 hours after the match is mandatory. You do not have to demand them via the 'Request match media (demos/replays)' function on the match details page!
Should this be not done or if the file has been manipulated, the match can be deleted and penalized by filing a protest.
The players and teams will get 3 penalty points per missing or incomplete Aequitas file. The files are to be kept for at least 14 days. If a player intentionally manipulate his Aequitas file, he and his team will get 6 penalty points. Players who repeatedly manipulate their Aequitas files will be barred from all ladders. The usage of third-party programs to bypass Aequitas will be punished with 12 penalty points (Cheating).
9.5.3. Rcon status screenshot
When all players of both teams have connected to the match server the server admin has to make a rcon status screenshot before the match is 'live'. It can be taken via the console command ´rcon status´ (after he has typed in his rcon password) and then pressing the ´screenshot´ hotkey. If someone has left the game accidentally because of a crash and then connected again, another rcon status screenshot has to be taken.
НА РУССКОМ ПРАВИЛА ПОКА ЕЩё НЕ НАШЁЛ.