Rules for the CoD2 [RS.com] DM


Failed to get game GUID id.

Custom rules


Anti-Cheat: Disabled

Custom:
rocket software is proudly present cod2 cups. we will introduce 3 cups with prizes for winners. visit our website to learn more about us. probably you are well know with sd, dm and hq series in cod2. lets play together!
sincerely yours, rs.com squad..


Standard Call of Duty 2 Search and Destroy Quick Cup rules

1. Introduction

  1. Please take the time to read through our global rules before you start playing in this ladder. These rules not only apply to CoD2 S&D but all ladders within ClanBase. Knowing the global ladder rules will avoid conflicts and will increase your chances of winning conflicts.

    Pay particular attention to our rules on freelancing, linking your accounts and the 24-hour rule, reporting a no-show and the match conflict rules.

    The General rules section covers the default punishment for breaking the rules, our right to broadcast matches, the complaints system and what counts as official match rules. The rating system is explained in detail, and provides information about the number one spot.
  2. A list of defined ladder terms can be found .


2. Match rules

  1. A match is played over two maps, one picked by each clan in the challenge form. Each clan will play one time as axis and one time as allies on both maps. The clan with the lower ranking on the ladder can choose which map is played first. Each clan may choose which side they start on their opponents map.
  2. Each map has a roundlimit of 20. Both clans play 10 rounds as axis and 10 rounds as allies. Total rounds in a match is 2x20 = 40. Rounds will be set at 2 minutes long. The score is determined by adding all rounds won from each clan over the whole match.
  3. There is a limit of one shotgun per team, as set by PAM. Using more than one shotgun in a team may result in a forfeit loss.
  4. There is a limit of one sniper per team, as set by PAM. Using more than one sniper in a team may result in a forfeit loss.
  5. The default team size for clan matches is 5on5, but you can specify a different team size in the challenge page. The minimum team size is 4on4, max team size 10on10. Matches played with other team sizes will be cancelled.
  6. This rule applies to this game's ladders which have had more than 500 activity for 30 days or more: Clans in the top 10 must play at least 5 legitimate matches within 30 days, which is not a no-show. Clans in the top 10 who haven't played 5 matches in 30 days willl be forced into hibernation without warning.


3. Optional rules

  1. TZAC: You can choose if TZAC anti-cheat should be Mandatory or Disabled.
    • Mandatory (default option)
    • Disabled


4. Maplist

  1. The maplist for CoD2 S&D is:
    • mp_dawnville
    • mp_toujane
    • mp_carentan
    • mp_burgundy
    • mp_matmata
    • mp_moscow
  2. Download maps: , ,


5. Client settings

  1. In all ClanBase CoD2 ladder matches TZAC may be used depending on the challenge. If it was made mandatory in the challenge, all players must have the latest version of TZAC turned ON during the whole match. Each player is responsible for making sure they are running it during the match and have to make sure they input the correct before starting any match. Incase someone filled in a wrong war ID, they must upload the correct war ID on war comment within 48 hours after the match was played. If they fail doing that, they will loose by forfeit.

    - If a player logged out from TZAC during the match, that clan will receive a forfeit loss.
    - If a player crashes during the match he must rejoin TZAC immediately upon rejoining the server.
    - Screenshots must be uploaded after each match ( even if they are black), screenshots not uploaded 48 hours after match will result in forfeit loss.
    - When/if a player(s) has black screenshots, player(s)/clan(s) will not be punished while they are logged in with the correct anti-cheat during the entire match.

    note: Before starting the match make sure you entered your TZAC guid to your clanbase profile and that you filled in the correct warid / server ip to avoid problems after the match.
  2. Every player must have their TZAC ID registered on their GUID page before the match's starting time, if it was chosen as mandatory in the match challange.


6. Server settings

  1. All matches must be played on servers that stream to the ClanBase/PBBans repository. The latest version of the script is required for all ClanBase matches. Streaming information and instructions can be found here. To check if the server you are playing on is streaming to the CB/PBBans repository, simply visit the PBBans site and check on the left hand side. The clan/player responsible for the server is also responsible for making sure it streams, their/his opponent should demand a streaming server for all matches. Matches where a streaming server cannot be organized will be cancelled. Playing continuously in non PBBans-streaming servers results in ladder suspension as defined in the punishment table..
  2. A clan cannot claim a match cancel if the server belonged to them.
  3. All CoD2 S&D matches should be played with the following server settings:
    set scr_sd_bombtimer "60"
    set scr_sd_graceperiod "3"
    set scr_sd_roundlength "2"
    set scr_sd_roundlimit "10"
    set scr_sd_scorelimit "0"
    set scr_sd_timelimit "0"
    

    Use this CB.cfg to have all official clanbase settings.
    Playing continuously without the above mention MD5 & CVAR Checks on your server results in ladder suspension as defined in the punishment table.
  4. Note: Joining uac on time (if it was choosen in the challange) and streaming the server is still mandatory. This does not mean that you can't make a conflict if you played on a modified pam.
  5. All matches must be played on zPAM 2.05 (Download zPAM v2.05) installed by clans on their server. To properly configure zPAM on servers for ClanBase matches, use the appropriate command in the console:
    • /rcon pam_mode cb (Default mode for standard gametypes)
  6. Using servers that do not authorise players original cd-keys from Activision's master server (cracked servers) is illegal. Opponents are allowed to ask for a legal server or provide their own (as long as it doesn't conflict with any other server rules). Unplayed matches will be cancelled if appropriate servers could not be found. Once a match starts, you accept the server and its settings (PunkBuster, streaming and legal servers are still always mandatory).
  7. All ClanBase ladder matches must be played using the official v1.3 patch which can be found here.


7. Demos and screenshots

  1. Demos:
    1. All players must record demos from the whole match. Demos can be requested and must be kept until the result has been accepted on ClanBase. Demos can be requested before a conflict is made (if the request is valid).
    2. In case of a conflict: both clans may request ineye demos from the other clan, but the following is required or the conflict will be discarded:
      • The clan must explain their reason(s) for their demo request.
      • The clan must immediately state the exact demos they want; players and maps.
    3. The amount of ineye demos that can be requested are: 1on1: all, 2on2: 1 per map, 3on3: 2 per map, 4on4: 3 per map, 5on5: 4 per map, 6on6: 5 per map etc. 1 demo is a 1 complete map demo of one player. A clan can only request demos once in a conflict, other requests apart from the first one will be ignored. Failure to upload requested demos or uploading demos that are broken or missing will lead into a forfeit loss.
    4. Clans who repeatedly fail to upload demos will be . Players who repeatedly fail to upload demos can be suspended from playing according to .
  2. Failure to upload requested demos or uploading demos that are broken or incomplete will lead into a forfeit loss.
  3. A demo is considered to be incomplete if it's missing 3 or more rounds. If a clan is manipulating the demo recording process (e.g. by stopping it in a live match on purpose), all the points gained in that period will be awarded to the opponent.
  4. Screenshots of the scoreboards should always be taken by each clan and kept untill 2 weeks after the matchresult has been confirmed. Only screenshots can be accepted as proof when there is a dispute about the score. Screenshots or Demos can be requested by supervisors at any time.
  5. If a clan refuses to upload their(s) demo, then you should copy the demorequest and paste it inside the conflict. Clans who force people into a pointless conflict will be punished according to The Ladder Punishment Table


8. Regional ladder rules

  1. The following regional ladder rules apply for all region-specific CoD2 ladders.
  2. In order to participate in a regional ladder a clan/player must reside in that region or in a region that includes it. For example: East Europe includes Hungary.
  3. Any clan or player not from a ladder's region will be removed from that ladder. Depending on the kind of violation, the clan/player might face suspensions from a forfeit loss to a 3-month suspension from all regional ladders for that game.
  4. All matches MUST be played on servers within that region. Once a match has started then the server's settings and region is accepted, so clans/players will not be punished if the match is played. When neither clan/player can provide a server from that region and they refuse to play, the match should be cancelled. If a clan/player does have a server from that region and the opponent doesn't, the match must be played on the server from that region. In this case, the opponent may not refuse the server with the correct region and if they do, then the clan/player (with the correct server) should report the match as a no-show in the ladder channel.
  5. During matches a certain number of players must be from the ladder's region. The values are as follows:
    • In a 2v2 : both players must be from that region
    • In a 3v3 : 2 players must be from that region
    • In a 4v4 : 3 players must be from that region
    • In a 5v5 & 6v6 : 4 players must be from that region
    • In a 7v7 : 5 players must be from that region
    • In a 8v8 : 6 players must be from that region
    • In a 9v9 & 10v10 : 7 players must be from that region
    • Anything above this must have a minimum of 8 players and must be a minimum of 70% of the team

    Violating this rule will result in a forfeit loss. In addition, you will be suspended for a period of time depending on the type of violation as stated in the . If the players are faking nationalities, more harsh punishments may be used.
  6. It is a clan's responsibility to make sure its clan & player flags are correct for when clans are checked for regional status.
  7. IPs can be traced to a country by using IP trace tools such as 'Network Tools' and 'Geektools'.
  8. Any clan found guilty of abusing the regional ladder rules by faking nationality will be punished, depending on the violation, with a forfeit loss or more harsh measures. Players who continually rejoin ladders they were removed from despite warnings will have their responsible clans .


9. GUID's

  1. GUID's are unique identifiers used in games to recognise players. Examples: SteamID, PB guid, CoD2 guid, UT2004 guid, ETpro guid, DMW client nr and Xbox Live Gamertag.
  2. Every player must register his PB guid on the . Click to find out how to retrieve and register your GUID. Use the console commands '/pb_plist' or '/pb_power' to show all players' GUID's in a match.
  3. Entering a CoD2 guid to ClanBase is optional. Click to find out how to retrieve and register your GUID. Use the console command '/rcon status' to show all players' GUIDs in a match. PB guids are required and they are used on ClanBase.
  4. On a player's profile a GUID will only show the last 8 characters, the other digits/characters are hidden because of privacy reasons. The last 8 characters of a GUID do need to be 100% correct, while the "hidden" part may not affect the conflict result. Players should correct their GUID when a mistype is found within the "hidden" part. Editing your CoD2 GUID can be done via Help Desk.
  5. The last change of a GUID can not be done later than 24 hours before a match. Players who did not register the correct GUID more than 24 hours before a match will be considered freelancers.
  6. Only the last entered GUID (the one you can see on your account's page) in the changelog will be considered as valid to play with.
  7. Players with GUID's that are listed on the Master Ban List's (MBL) of Game Violations, PBBANS and Punksbusted are also considered cheaters and are not allowed to play in any ClanBase ladder matches.
    Old GUID's from GUID logs aren't valid proof of the person cheating or being banned. It must be verified that the person in question actually triggered the ban before any action will be taken.


10. Miscellaneous rules

  1. At least half the line-up used in every match (not 1on1) should be different from those used by any other clan in the same ladder. This does not apply to 2on2 ladders (unless it happens too regularly - both clans use the same line-up in 4 or more occasions) or matches older than 14 days. The following list shows what is not allowed, based on the line-up of two matches, one for each clan:
      - 3on3 ladder: two players are the same
      - 4on4 ladder: three players are the same
      - 5on5 ladder: three players are the same
      - 6on6 ladder: four players are the same
      - 7on7 ladder: four players are the same
      - And so on


    Violating clans will receive a forfeit loss for all of the matches in which they are violating the shared line-up rule. Two or more violations of this rule will also result in .
  2. Once the match starts, neither clan can complain that the other clan is using a "shared lineup". That should have been checked before the match started.

    If you find out that your opponent have a "shared lineup" before match starts, you should ask them to replace that player(s) who are violating the "shared lineup" rule. If they refuses or can't replace the player(s), you can claim a noshow win.
  3. Once a match starts on the suggested server in the challenge, a clan cannot claim 50/50 unless the server has serious ping issues or both teams agree the server is not fit to be used or the game server has major problems. Evidence must be taken of the serious disadvantage (preferably a screenshot with the full line-up with visible pings) caused by the server issues. Clans abusing the rule or failing to provide proof for their claims will lose the match by default or have their claims discarded.
  4. Before each game can start, the server admin always has to make sure that both teams are ready. If one member of a team says that his team is ready he is considered to speak for the whole team, regardless of his status in the clan. Once a game has started it may only be restarted if both clans agree. If a game was started without the agreement of one of the teams, that team can demand that the game is restarted as long as at least one of their members remain in the spawning area.
  5. Substituting a player during the match is only allowed between games (so at team side changes or at the map change), or in case of extreme connection problems during the game. If the new player has not showed up after 5 minutes the opposing team can demand that the match starts without him (also see the rule regarding kicking players).
    In 1on1 matches, if a player drops and fails to reconnect for 5 minutes, the opponent may:
    • Claim the rest of the rounds and enter the score accordingly if the match passed 1/4 of its total length (1 side of a map).
    • Enter a match cancel if the match has not passed the 1/4 of its total length.
  6. If a player drops because of a technical error, the match must be paused. You can call a time-out via Quick Chat or "\openscriptmenu call timeout". The maximum time you can pause is 5 minutes - after which the match will auto-resume -, which is enough time to reboot and reconnect. The maximum total pause time is 10 minutes per map per team (5 minutes per side and only one pause per team per side). you do not need a reason to call a time-out. At map or side change clans can take a maximum of 5 minutes for a break, the match is to resume after that time. When the 5 minutes are up spectators can be removed freely. Staying in spectator will lead to the automatic loss of the round. If a clan does not ready up in time after map change, it will lead to a forfeit loss for the violating clan. A clan must clearly state their claim of the forfeit win on the server (while recording a demo) which the opponent is forced to accept, then may leave the server as the match is concluded. But if the clans decide to continue the match (team matches only) after the allowed pause time is up, a forfeit win can't be claimed later on.
  7. If the server crashes during a match, the map will be restarted only if the crash occurred less than 1 minute after the start, or during the 1st round for round-based games. In all other cases the remaining time (rounded to the closest minute and with a minimum of 2 minutes) or rounds will be played, after which the scores will be added to determine the map win.
  8. It is not allowed to kick players from the opposing clan, failure in doing so may result in a default loss of the match. If the game is paused, and a player is stuck in time-out phase the following things can happen:
    • - A substitute arrives in his place during the pause, the line-up is complete, the player waiting to drop out can be removed freely.
    • - Pause time is over: since the player waiting to drop out can not ready up, he can be removed freely (regardless if a substitute is present or not)

    Note: it is recommended to use the pb_sv_kick command instead of the regular kick command, because the latter may put the player on a local ban list which may cause inconvenience during the rest of the match.
  9. Spectating during an official match is not allowed. If a player leaves the server for any kind of reason and joins again he needs to choose sides immediatly. When spectators that are not allowed to join the server enter the match, it should be paused and they should be made to leave before the match is continued.
  10. The bomb can be planted to any location around the bombsite as long as it stays defusable. You are also allowed to plant on top of the bomb. Of course the use of 333 fps, nade or boosting is not allowed when you plant a bomb, or anywhere else in the game.


11. Cheating and abuse

  1. The applies to all ClanBase ladders. Any cheating or excessive abusive behaviour during a match will result in a forfeit loss. Cheating and/or using suspended players in matches results also in different kind of .
  2. If both clans cheated and/or used a suspended player in the match, both clans get a forfeit loss.
  3. Ladders are moderated by four methods: join applications, score changes, suspensions and deletions:
    • Join applications are dealt with by the ladder/mod supervisors to stop fake clans, members with fake GUIDs and countries from the wrong region from entering the ladder.
    • Matches may be edited to a cancellation, no-show, forfeit loss or a win for the opponent - depending on the ladder rules and severity of the problem. A forfeit loss is the standard punishment for all violations unless the punishment is otherwise stated in the rules.
    • Suspensions are used to punish abuse of the ladder system and range from short-term to long-term/permanent suspensions, from one ladder only to all ladders. Suspensions are added by the ladder chiefs and assistants.
    • Punishments are summarised in a table, found . Clans that are suspended from a ladder may not form the same clan elsewhere to play that ladder, this includes new clans or altered existing clans. The guidelines for determining if a clan with an active suspension has rejoined with a new clan will not be given out so don't ask for them.
    • If a clan is suspended from a ladder the suspension can be viewed by using the clan's matches page. Appeals to the suspension reporter will only be acknowledged if the accusation against the clan can be proven false. Provide all necessary proof immediately on the war summary page. Members may only contact the ladder assistants/chiefs if the reporter is not mentioned.
    • Clans or accounts may be deleted without warning as described in the .
  4. It is strictly forbidden to use accounts of other users, even if the users are in your clan. Such cases will always be considered abuse and subject to temporary bans. This does not apply to players who are forced to share GUID's.
  5. It is not allowed to take advantage of or abuse bugs. Any kind of bug abuse is considered cheating and will lead to a forfeit loss, unless otherwise mentioned specifically in the game-related rules.
  6. All programs or files, either changed game files or new files, that change the game or add to its functionality, or which interact with the game in any way, are strictly forbidden unless other rules specify otherwise. Modified versions of the game's resource files are always forbidden, regardless of what they do. The use of any forbidden program or file by any clan member during a match, leads to a forfeit loss, and could lead to a removal and ban from ClanBase in major cases.
  7. Programs that do not interact with the game in any way are allowed, even if they can be used and operated simultaneously with the game. Voice communication programs are examples of such programs.
  8. Any types of scripts proven to give a real advantage or are part of not allowed binds/scripts below will not be tolerated and will result in a forfeit loss. Config settings that give a distinct advantage over the opponent may be deamed config abuse and can lead to a forfeit loss depending on severity of claim.

    Not allowed bind and scripts:
    • any 'exec' or 'vstr' bind (this does not include anything related to demos or demo players)
    • 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
    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.
  9. Players are allowed to jump to special places (including "trickjumping") which can be reached without any additional aid (example another player or explosives) as long as it doesn't violate the bug abuse rule (example exploiting 2-way mirror walls).
  10. "Clipping" will lead to round loss, if you clip multiple times you will loose by forfeit. This is how "clipping" looks like, this on the other hand is not clip.

    Jumps on mp_toujane
    Allowed/not allowed, jumps that require nades or 333fps are not allowed.
  11. Clans abusing the ladder system in any way in order to gain an advantage or just to be a nuisance will be deleted or suspended from ladder(s). Further punishment may include deletion of the accounts of the person responsible for the abuse, in extreme circumstances. Abusing any clear loopholes in the rules is forbidden, Chiefs of Ladders can punish clans/players for abuse not described in these rules.
  12. Using Game-Violations' Eye-dent tool to provide proof is allowed, but comes with restrictions. You may only post screenshots which show all the important columns (player name, player ip, guid, date and server ip). Highlighting the important parts on the picture is advised, but any other modification to the picture (for example adding text) is not allowed. If the proof is intended to show matching IPs where both Clean and Banned guids were used by the same IP, we will only accept it if the Clean/Banned guids were used on the IP is on the same day, unless you have very strong proof that the IP is static. IPs found older than a year are also unaccepted.
  13. We will only accept proof if you provide it the proper way. We wont accept anything where the provider requests any input from our side, or has any unnecessary limitations (for example rapidshare or megaupload), in other words, proof must be accessible directly. Some free image hosting sites are imageshack and photobucket. You may use other hosts, but make sure images can be viewed internationally. Also, be sure to save a copy of the image somewhere, in case the host removes it. Demos should be uploaded to the ClanBase demo FTP (see ).
    We wont accept any so-called "busted.avi" videos as proof, you must make timestamps for the original demo.
  14. When providing timestamps for demos, remember to state which player's demo and what map you are referring to. The round indication should be clear for everyone to be able to follow. If the match was interrupted by a map restart (for example because of pause) or similar and the round ordering has changed, be sure to mark those too to make everything clear. Every timestamp must be exact, saying "watch demo" or "whole round" are unacceptable and will not be taken into consideration while watching the demo. A small amount of explanation may be added to the timestamps to make situations clear, but you must make them in English (regardless if it is a regional ladder or not), because our demo crew consists of people from different countries.