Free cookie consent management tool by TermsFeed
December Donation Goal (€150.00 of €200.00)

Call of Duty 2

AMERICA 5vs5 SD SoloQueue

Our advice to you is to read the rules before playing!
If game doesn't allow in-game voice chat then it is required to join TeamSpeak3 IP: ts.cod2servers.pro

1 . SoloQ explained

Ruleset for soloQ 5v5SD:
- Veto until one map remains
- Autopick sides from site

Ruleset for soloQ 1v1 DM:
- Veto until one map remains
- Duration of the match = 15 minutes
- Without Scope and Shootgun

Maplist:
Toujane / Burgundy / Dawnville / Carentan / Matmata / Vallente_Fix/ Breakout_TLS/ Chelm_fix / Crossroads

- All matches must be played on the FPS Challenge server and all players must join Offical FPS Challenge teamspeak. If all players agree to join other thats fine but if they don't all agree, they must join the fps one.
Rcon from the server will be visible only to captains.

- If one of the players in the PUG did not come on server. The match needs to be disputed. Be specific in your dispute reason.

Quick how to:
- You join "soloQ" and get put into waiting line
- When there are enough players in line, you will be asked to ready up (Players have 60 sec to ready up)
- When all people accept, teams will be created based on ELO
- You join server and play.
- You cant join new queue if you have one or more matches/games on status Ongoing

Normal ladder rules apply for all SoloQ matches, players aren't auto banned for not joining server after ready up but we expect players to play when they ready up.

Things that will be punished:
1. Not joining server and be ready (pressed f) in 5 minutes after the server has been created
2. Not joining teamspeak/discord
3. Leaving early
4. Trolling or disruptive gameplay
5. Server settings abuse
6. Not adding a score after the match
7. Submitting wrong score
8. Not using your FPS-nickname, From now on it is mandatory to play with your FPS nicknames in SoloQueue.

Offical FPS Challenge teamspeak
ip: 193.87.79.232:27010
pw: fpschallengecod2

- If you have any questions feel free to contact CoD2 admin on Discord.

2 . Server settings

All standard FPSChallenge ladder matches must be played using the official v1.3 patch.
Minimal version 3.00 of zPAM in competative mode has to be used.
PAM mode
• In CoD2 S&D 2v2 Ladder, pam_mode cg_2v2
• In CoD2 S&D 3v3 Ladder, pam_mode cg_mr12
• In CoD2 S&D 5v5 Ladder, pam_mode cg_mr12
Punkbuster need to be OFF
Antilag need to be OFF

FPSChallenge doesn't support illegal game executable files (cracked), but teams may agree to play on them with ready-up.
Teams are allowed to provide their own server, as long as it doesn't conflict with any other server rules.
Proposed servers are never binding and are 'suggested' play locations only.
Once a match starts on the suggested server, another team cannot claim 50/50 unless the server has serious ping issues or both teams agree that server does not fit to be used or a game server has major problems.
Evidence must be taken of the serious disadvantage (preferably a screenshot with the full line-up and visible pings) caused by the server issues.
Teams abusing the rule or failing to provide evidences for their claims will lose a match by forfeit or have their claims discarded.
Unplayed matches will be cancelled if appropriate servers could not be found.
If all players ready-up, they indicate that they accept the following server settings:
• Ping
• Server config
• PunkBuster and streaming status
• PAM mode
• MD5 & CVAR checks

3 . FPSChallenge Anti-Cheat (FPSAC)

In all FPSChallenge CoD2 EU Ladder matches FPSAC must be used.
Each player is responsible for making sure they are running it during a match and have to make sure they enter the correct match ID before starting any match.
In case someone filled in a wrong match ID, they must write the correct match ID in Public/Private discussion within 48 hours after a match was played.
If they fail to do so, they will lose by forfeit.

4 . Demo

All matches must be recorded (/record) and demos should be kept until 48 hours after the date listed in the match details.
If a dispute gets open, demos should be kept 48 hours after a dispute is solved.
Failing to follow these rules will lead to a direct forfeit loss for a team. Player in question will be punished according to Match Ban Policy.

- Note, DM mode does not have automatic record. Don't forget to turn on the record.

In order to officially request a demo you must make a valid demo request :
Players/teams must request a demo by posting a FPSChallenge account of the required player(s) in the match discussion, not in-game.
If a player has a different nickname in-game, you may request a player to use their FPSChallenge nickname.
If you want to request a demo in a dispute, make sure you make a valid demo request in the dispute discussion.
Only first demo request is valid, all other ones will be ignored.

A valid demorequest looks like this: (playerlink + maps)
https://fpschallenge.eu/user/head - Toujane & Burgundy

You can request limited amount of demos:
• 2v2: 2 both demo
• 3v3: 2 both demo
• 4v4: 3 both demo
• 5v5: 4 both demo, etc.

Players have 48 hours to upload the requested demos from the request date
Failure to upload requested demos or uploading demos that are broken or missing will lead into a forfeit loss.
If a demo is missing 3 or more rounds then a forfeit win will be awarded to the opposing team.
Also, if a player is manipulating a demo recording process (e.g. by stopping it in a live match on purpose), all points gained in that period will be awarded to an opponent.
Once the match is completed any remaining demorequests become invalid.

5 . Cheating + bugabuse + verbal abuse

The installation of any public or private cheat is strictly forbidden and will lead to a Match Ban.
Any form of cheating will be punished, that includes modified PAM / modified files / custom .DLL / etc

It is strictly forbidden to promote any type of cheats.
Such cases will always be considered abuse and rigorous measures will be taken against these players.

Players who are found playing knowingly with cheaters or RWBs in one match will be banned.

Abuse is reviewed case by case.

Smoke bugging is not allowed and will be punished with a forfeit loss.
Any types of scripts (that includes macros) proven to give a real advantage or are part of not allowed binds/scripts below will not be tolerated and will be punished with ban.

Not allowed bind and scripts:
• any "exec" or "vstr" bind (unless they are demorelated)
• any script including "lookdown"
• any bind including "rate" cannot have a value outside 25000
• any bind including "com_maxfps" cannot have a value below 40 or above 250
• any bind including "attack" cannot be combined with any other command
• any bind including "frag" cannot be combined with other commands/binds[/indent]All binds/scripts that are not covered by above not allowed scripts/binds will be reviewed on a case-by-case basic to see if they do give an advantage.

"Clipping" and fast reloading will lead to round loss, if player does it in three or more rounds, forfeit win will be awarded to an opponent. Silent climbing on ladders is allowed, but silent dropping from roof is not, and will lead to the round loss. Smoke bugging is not allowed and will be punished with a forfeit loss. Players are allowed to jump to special places (including "trickjumping") which can be reached without any additional aid (example another player or explosives) or 333 FPS, as long as it doesn't violate the bug abuse rule (example exploiting 2-way mirror walls).

Players that have been banned by FPSChallenge are not allowed to participate in any of the FPSChallenge matches.

Any form of cheating that isn't mentioned in the rules will be handled case by case.