Map veto:
- Map veto is done on the website.

Side on map:
- Team 1 chooses side on Team 2's map, Team 2 chooses side on Team 1's map, decider = knife for side

- Teams must have 3 players on their roster to play in the event.
- All players must have a valid SteamID64 and Discord account entered on their profile.

- Matches are played on EU FPS Challenge servers.
- If both teams agree, you may also use FSHost servers in case the FPS Challenge servers lag.
- Every match is played on FPSPromod232 (fps_promod_232).
- Servers must be running on latest CoD4x version.
- promod_mode match_mr10 is to be used on map 1 and 2.

- Teams must play using 3 players.
- A team may substitute a player in a timeout during the match as long as the player is listed on the team's roster.
- Every player must be running Steam during the match. It must also be the correct Steam account with the correct SteamID64 on your FPSChallenge profile.
- Readying up means agreeing to the players in the match. (SteamID's) - AC is ALWAYS mandatory. No matter what the teams agreed on.
- Mixers are NOT allowed. Killspecs are, but the opponent must agree, they must be on the team roster and they must use the anticheat and have a valid SteamID64 on their profile.
- Sharing your login (letting someone else play on your account) will result in a permanent ban for both players.
- It is not permitted to have more than 1 account. If you accidentally created multiple accounts (forgot password/email), contact an admin to notify them.
- Creating a new account while banned to avoid the ban will result in the ban length being doubled.

- Teams have a maximum of 5 minutes to ready up during half-time (switching sides) and 10 minutes to ready up on map change. Opponent team has to warn the team first and have their own players all in the server and readied up in order to be able to claim a forfeit win.
- If you continue to play the match, you lose the right to open a dispute.

- mp_backlot_fix
- mp_citystreets
- mp_crash
- mp_cluster
- mp_crossfire
- mp_marketcenter
- mp_strike

If a server crashes during the round, you have to replay from the beginning of that round.

- It is NOT permitted for any user to take advantage of map bugs (for example elevators, outside the boundaries of the map, under the map and so forth) or glitches during a match. This can be reviewed on a case-by-case basis by an admin.
- Glitching is defined as moving or seeing through or over a physical object and is NOT permitted.
- Selfspec is not allowed => (looking downwards next to an object, allowing you to see and not be seen (e.g.: A wooden on crash looking head down in the window allowing you to see people on the A site without them being able to see you).
- Grenade jumps and anything similar are NOT permitted.
- Players are only allowed to bounce to places which can be reached without the use of a bounce. Bouncing to roofs and balconies which are unreachable in a normal way is prohibited.
- Straightforward jumps and those that do not involve any part of the in-game character moving through a physical object are allowed.
- Boosting is only allowed to boost players to spots where a player can get to by himself.
- Standing on another player's head to peek is also allowed, the above rule also applies.
- Boosting by shooting own players is not allowed. For every round this occurs, the round will be defaulted to the opposing team. If this occurs more than 2 times during the match it will be defaulted to the opposing team.
- Players who are caught using bugs or glitches immediately forfeit the round. If this occurs on more than 2 occasions then the match will be forfeited.

- Scripts & config tweaking that affects game play including but not limited to nade scripts, wait commands, macros and so forth, including configs that change commands/rates are disallowed. These commands range from set nade binds to gain the longest throw to scripting a superior firing rate of semi-automatic weapons.
- This also includes multi-command binds such as bind KEY "toggleads; +attack" on the scroll wheel.
- Using the scrollwheel to shoot is also illegal. This includes both binding +attack to your scrollwheel as well as scrolling very fast and then holding mouse1, which can be done with certain mice. (For example to spam your deagle quickly)
- Players caught using illegal scripts and binds including nade scripts and weapon next binds will receive a forfeit loss and be banned.
- This also includes binds to turn on certain things by using a bug exploit. Depending on the bind, the player can receive a ban for bug abuse.
- Any game modification understand as changing .iwd files of game (e.g. weapon or model skins)
- Using any third party software (e.g. nVidia Control Panel or RivaTuner) to tweak graphics settings to give you an advantage -for example Ambient Occlusion- is NOT allowed and will result in a permanent ban.
- Any player caught cheating by demo or anticheat will result in a permanent ban. We have a zero tolerance policy.
- The FPS Challenge Anticheat is mandatory for all matches.
- If a player did not use the anticheat, the team gets a forfeit loss.
- If the anticheat crashed or did not work as intended, it will be reviewed on a case-by-case basis and the decision is up to the admins.
- If the anticheat catches a player using either: Macros via drivers or by config such as, but not limited to, weapnext, nadescripts, zoomscripts, fastshootscripts etc., the team receives a forfeit loss and the player will be banned as followed:
1st offence: 1 week ban
2nd offence: 1 month ban
3rd offence: 3 month ban
4th offence: 1 year ban
5th offence: permanent ban

If a player plays multiple matches but only gets caught in 1 match, only that match result will be overturned. So if a player did not trigger any violations in a match, that match will not be overturned.

To clarify, having scripts or illegal binds in your config at any time is considered illegal. Obviously, things such as scripts for moviemaking are legal. Anything related to gameplay is not, even if it hasn't been bound to a key.

- A warning or ban will be given to any player found to be abusing another team/player. Multiple warnings may result in a ban.
- Abuse against an admin in game, dispute chat, private message or anywhere else will not be tolerated and may result in an instant ban.
- Rape threats
- Death threats
- Family threats
- Illness threats
- Doxing (Seeking / releasing private information)

- Teams who wish to open a dispute for a breach of any of the above rules may do so by clicking the dispute button and entering a clear description. The case will then be handled by an admin. Do not PM an admin about this yourself.
- All matches played need to be recorded and demos should be kept until 48 hours after the match was played. Should a dispute be opened, demos should be kept until 48 hours after the dispute is solved. Failing to follow these rules will lead to a direct forfeit loss for the team.
- Teams have the right to request 5 demos from their opponents if they suspect foul play. If a demo is missing more than 3 rounds, then a default win will be awarded to the opposing team.
- Teams/players must request a demo by writing it in the MATCH CHAT - a valid reason must be supplied. Do not open a dispute unless 24 hours have passed and no demo has been uploaded.
- Teams have 24 hours to ask for demos. The other team has 24 hours to provide the requested demos. A valid reason must be supplied. An example of this is: ''we suspect player X of using a wallhack''. A demo request is not valid without a good reason.
- If a demo is not uploaded after 24 hours, you may contact an admin via Discord and explain that a demo has not been uploaded.
- A demo upload may take longer than 24 hours, this can be decided by an admin. Exceptions include things such as a player being on holiday and being unable to reach their PC within the 24 hour mark. It will be discussed with an admin and a new time limit will be set in within the player can upload their demo.
- Players have 48 hours to make timestamps which will be reviewed by the demo crew immediately.
- Timestamps must be in the following format:
Strike:
2-2 @ 1:30 - traces through the wall for 3 seconds
2-3 @ 0:43 - possible aim assist - his aim isn't on the player but still lands the kill
5-6 @ 0:22 – aims towards a player through the wall
etc.

If you want admins to check the anticheat screenshots of a match, please open a dispute and tell admins which player(s) you suspect of cheating.

RULES ARE SUBJECT TO CHANGE AT ANY TIME

- Using a VM (Virtual Machine) to play is strictly forbidden and will result in a permanent ban.
- The possession of cheats is also illegal, whether they are active COD4X 1.9 cheats or not.