Map veto:
- Map veto is done on the website. (Currently maps are automatically picked)

Side on map:
- Done on website

- Teams have a maximum of 5 minutes to be ready on the server. If they take longer, players who are not present will be banned and the match will be cancelled.
- Players must ensure that all players participating in the match, including players on their own team and the opposing team, as well as any killspectators, are using the anti-cheat. Teams cannot claim forfeits for failure to use the anti-cheat after the match, as it is the responsibility of the team to check beforehand.
- If a player leaves a game and there has been 5 or less rounds played. The player who left will be banned and the match will be cancelled. If you have played more than 5 rounds, then you must either finish the game with 4 players or forfeit the game. To forfeit the game, all 4 players must be in agreement and one player cant just leave and give forfeit. If that player does leave, they will also be banned for leaving.

- Also, remember that players cannot leave a game unless it is finished, and players cannot enter results if the game is not completely finished as well.

- All players must be able to communicate in simple English, call out enemies, and know basic game mechanics such as smoke usage.

- Players must have all necessary files ready before joining a SoloQ game, such as the proper COD4X patch and files for backlot_fix and also have FPS AC installed and functioning.

- Players must check their internet connection, microphone settings, etc. before joining a SoloQ game. Repeatedly joining with a bad connection may result in a ban.

- All players must record a demo of the match.

- Players are expected to play to win and to not engage in any behavior that disrupts the gameplay experience for other players. Trolling, griefing, and intentionally sabotaging your team's efforts are strictly prohibited. Any player found to be in violation of these rules will be banned.

- Matches are played on EU FPS Challenge servers.
- Every match is played on FPSPromod 263 (fps_promod_263 or newer.
- Promod_Mode knockout_mr12 is to be used.

- FPS AC is mandatory for all matches and you should also use the proper match ID.
- If the anti-cheat crashes or does not work as intended, teams must immediately contact an admin for further instructions.
- Players must ensure that all players participating in the match, including players on their own team and the opposing team, as well as any killspectators, are using the anti-cheat. Teams cannot claim forfeits for failure to use the anti-cheat after the match, as it is the responsibility of the team to check beforehand.
- 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 be ready on server, if its more than 5 minutes, players that are not present on the server are banned and match is cancelled.
- Teams have a maximum of 2 minutes to ready up during half-time (switching sides). 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.

When a player leaves or times out during a solo queue game, it is necessary to initiate a three-minute timeout. During this time, the team that lost a player is permitted to search for a substitute. Upon the arrival of a substitute player, it is mandatory that the substitute completes the game with the team.
- If a player from the original team rejoins within the three-minute timeout period and the team has not yet secured a substitute, the player is authorised to resume play.
- If a player from the original team rejoins the game after the three-minute timeout period and a substitute player has already been found, the substitute player must continue to play for the duration of the game.

- mp_backlot_fix
- mp_citystreets
- mp_crash
- mp_crossfire
- 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 - for example Crash wooden stairs - gap in wood.
- 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.
- 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 map will be forfeited.
- 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.

List of allowed spots that violates last rule:

Crash:
Bounce on the edge of the balcony - 0:12

Strike:
Bounce on the roof above A site and side balconies - 0:34
Bounce on the entrance B wall - 0:43

https://streamable.com/adlla1

- Macros are not allowed.
- 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 and you also must use proper match id.
- 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 / running macro application 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.

To clarify, having scripts and 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 24 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.

- 1st offence - 1 day ban
- 2nd offence - 3 day ban
- 3rd offence - 1 week ban
- any other offence - 2x the length of previous ban length

Repeatedly breaking the rules will result in a permanent ban.

Submitting wrong score:
- 1 hour BAN – 1st time
- 12 hour BAN – 2nd time
- 1 day BAN Every six months, the Third Time Offenses counter is reset.

14. Reporting players
- To report a player for not communicating in a solo queue game, a 5-minute clip of in-game footage needs to be provided as proof. We suggest using the Nvidia Shadowplay feature.
- In order to report a player for intentional team killing or griefing in a solo queue game, a proper clip of in-game footage must be provided as proof (a demo recording cannot be used). The team comms need to be contained inside a video. We suggest using the Nvidia Shadowplay feature.
- Players who fail to join AC can be reported, but the opposing team cannot claim a dispute win as a result of this.
- Submitting false reports or reports in the wrong format can result in penalties, such as a ban from submitting tickets and/or solo queue play. Only reports that are true and contain relevant information to the incident being reported should be submitted by players, making fake reports or multiple reports without evidence will result in a ban for the reporter.