CalendarFAQPortalHomeRosterGalleryPretra¾nikRegistracijaCB Rules By iToxLogin
Last build: 22:26, Nov 27th -by iTox- 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 CoD4 Search & Destroy 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. 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 2x10 rounds with a fast_restart in between. Total rounds in a match is 2x20 = 40. The score is determined by adding all rounds won from each clan over the whole match.
  3. There is a limit of one sniper per team, as set by and the ModWarfare Mod. Using more than one sniper in a team may result in a forfeit loss.
  4. The default team size for the CoD4 Search & Destroy ladder is 5on5. Other team sizes are available by editing settings on the challenge form.


3. Maplist

  1. The maplist for CoD4 Search & Destroy is:
    • mp_backlot
    • mp_bloc
    • mp_bogmmap
    • mp_cargoship
    • mp_citystreets
    • mp_convoy
    • mp_countdown
    • mp_crash
    • mp_crossfire
    • mp_farm
    • mp_overgrown
    • mp_pipeline
    • mp_shipment
    • mp_showdown
    • mp_strike
    • mp_vacant


4. Server settings

  1. All CoD 4 Search & Destroy matches should be played with the following server settings:

    // Search & Destroy

    set scr_sd_defusetime 7.5
    set scr_sd_planttime 5
    set scr_sd_bombtimer 60
    set scr_sd_scorelimit 0
    set scr_sd_roundswitch 0
    set scr_sd_roundlimit 10
    set scr_sd_timelimit 2

    // Ping

    set sv_minPing "0"
    set sv_maxping "0"

    // Anti Cheat Settings

    set sv_disableClientConsole "0"
    set cl_autocmd "0"
    set sv_cheats "0"
    set sv_pure "1"
    set g_no_script_spam "1"
    set sv_punkbuster "1"

    // In-game voice communication system

    set sv_voice "0"
    set sv_voiceQuality "0"
    set voice_deadChat "0"
    set voice_global "0"
    set voice_localEcho "0"
    set winvoice_mic_mute "1"

    // Team-Balance and Voting

    set scr_teambalance "0"
    set g_allowvote "0"

    // limits the number of players that can choose each class type

    set class_assault_limit 99
    set class_specops_limit 99
    set class_heavygunner_limit 99
    set class_demolitions_limit 99
    set class_sniper_limit 1

    // enables dropping of specified weapon class

    set class_assault_allowdrop 1
    set class_specops_allowdrop 1
    set class_heavygunner_allowdrop 1
    set class_demolitions_allowdrop 1
    set class_sniper_allowdrop 0

    // assault rifles

    set weap_allow_m16 1
    set weap_allow_ak47 1
    set weap_allow_m4 1
    set weap_allow_g3 1
    set weap_allow_g36c 1
    set weap_allow_m14 1
    set weap_allow_mp44 1

    // assault attachments 1

    set attach_allow_assault_none 1
    set attach_allow_assault_gl 0
    set attach_allow_assault_reflex 1
    set attach_allow_assault_silencer 1
    set attach_allow_assault_acog 1

    // smgs

    set weap_allow_mp5 1
    set weap_allow_skorpion 1
    set weap_allow_uzi 1
    set weap_allow_ak74u 1
    set weap_allow_p90 0

    // smg attachments

    set attach_allow_smg_none 1
    set attach_allow_smg_reflex 1
    set attach_allow_smg_silencer 1
    set attach_allow_smg_acog 1

    // shotguns

    set weap_allow_m1014 1
    set weap_allow_winchester1200 1

    // shotgun attachments

    set attach_allow_shotgun_none 1
    set attach_allow_shotgun_reflex 1
    set attach_allow_shotgun_grip 1

    // light machine guns

    set weap_allow_saw 1
    set weap_allow_rpd 1
    set weap_allow_m60e4 1

    // lmg attachments

    set attach_allow_lmg_none 1
    set attach_allow_lmg_reflex 1
    set attach_allow_lmg_grip 1
    set attach_allow_lmg_acog 1

    // sniper rifles

    set weap_allow_dragunov 1
    set weap_allow_m40a3 1
    set weap_allow_barrett 1
    set weap_allow_remington700 1
    set weap_allow_m21 1

    // sniper attachments

    set attach_allow_sniper_none 1
    set attach_allow_sniper_acog 1

    // pistols

    set weap_allow_beretta 1
    set weap_allow_colt45 1
    set weap_allow_usp 1
    set weap_allow_deserteagle 1
    set weap_allow_deserteaglegold 1

    // pistol attachments

    set attach_allow_pistol_none 1
    set attach_allow_pistol_silencer 1

    // grenades

    set weap_allow_frag_grenade 1
    set weap_allow_concussion_grenade 1
    set weap_allow_flash_grenade 1
    set weap_allow_smoke_grenade 1

    // perks

    set perk_allow_specialty_parabolic 0
    set perk_allow_specialty_gpsjammer 0
    set perk_allow_specialty_holdbreath 1
    set perk_allow_specialty_quieter 0
    set perk_allow_specialty_longersprint 1
    set perk_allow_specialty_detectexplosive 1
    set perk_allow_specialty_explosivedamage 0
    set perk_allow_specialty_pistoldeath 0
    set perk_allow_specialty_grenadepulldeath 0
    set perk_allow_specialty_bulletdamage 1
    set perk_allow_specialty_bulletpenetration 1
    set perk_allow_specialty_bulletaccuracy 0
    set perk_allow_specialty_rof 0
    set perk_allow_specialty_fastreload 1
    set perk_allow_specialty_extraammo 1
    set perk_allow_specialty_armorvest 0
    set perk_allow_specialty_fraggrenade 0
    set perk_allow_specialty_specialgrenade 0
    set perk_allow_c4_mp 0
    set perk_allow_claymore_mp 0
    set perk_allow_rpg_mp 0

    // assault class default loadout

    set class_assault_primary m4
    set class_assault_primary_attachment none
    set class_assault_secondary beretta
    set class_assault_secondary_attachment none
    set class_assault_perk1 specialty_extraammo
    set class_assault_perk2 specialty_bulletdamage
    set class_assault_perk3 specialty_bulletpenetration
    set class_assault_grenade concussion_grenade
    set class_assault_camo camo_none
    set class_assault_frags 1
    set class_assault_special 1

    // specops class default loadout

    set class_specops_primary mp5
    set class_specops_primary_attachment none
    set class_specops_secondary usp
    set class_specops_secondary_attachment silencer
    set class_specops_perk1 specialty_extraammo
    set class_specops_perk2 specialty_bulletdamage
    set class_specops_perk3 specialty_bulletpenetration
    set class_specops_grenade flash_grenade
    set class_specops_camo camo_none
    set class_specops_frags 1
    set class_specops_special 1

    // heavygunner class default loadout

    set class_heavygunner_primary saw
    set class_heavygunner_primary_attachment none
    set class_heavygunner_secondary usp
    set class_heavygunner_secondary_attachment none
    set class_heavygunner_perk1 specialty_extraammo
    set class_heavygunner_perk2 specialty_bulletdamage
    set class_heavygunner_perk3 specialty_bulletpenetration
    set class_heavygunner_grenade concussion_grenade
    set class_heavygunner_camo camo_none
    set class_heavygunner_frags 1
    set class_heavygunner_special 1

    // demolitions class default loadout

    set class_demolitions_primary winchester1200
    set class_demolitions_primary_attachment none
    set class_demolitions_secondary beretta
    set class_demolitions_secondary_attachment none
    set class_demolitions_perk1 specialty_extraammo
    set class_demolitions_perk2 specialty_bulletdamage
    set class_demolitions_perk3 specialty_bulletpenetration
    set class_demolitions_grenade smoke_grenade
    set class_demolitions_camo camo_none
    set class_demolitions_frags 1
    set class_demolitions_special 1

    // sniper class default loadout

    set class_sniper_primary m40a3
    set class_sniper_primary_attachment none
    set class_sniper_secondary beretta
    set class_sniper_secondary_attachment silencer
    set class_sniper_perk1 specialty_extraammo
    set class_sniper_perk2 specialty_bulletdamage
    set class_sniper_perk3 specialty_bulletpenetration
    set class_sniper_grenade flash_grenade
    set class_sniper_camo camo_none
    set class_sniper_frags 1
    set class_sniper_special 1
    set class_assault_movespeed 0.95
    set class_specops_movespeed 1.00
    set class_heavygunner_movespeed 0.875
    set class_demolitions_movespeed 1.00
    set class_sniper_movespeed 1.00
    set scr_enable_nightvision 1
    set scr_enable_music 0
    set scr_enable_hiticon 1
    // gameplay

    set scr_game_allowkillcam 0
    set scr_game_onlyheadshots 0
    set scr_game_deathpointloss 0
    set scr_game_suicidepointloss 0
    set scr_team_teamkillpointloss 0
    set scr_game_spectatetype 1
    set scr_game_forceuav 0
    set scr_game_hardpoints 0

    // hardpoints

    set scr_hardpoint_allowartillery 0
    set scr_hardpoint_allowuav 0
    set scr_hardpoint_allowhelicopter 0

    // teams

    set scr_team_fftype 1
    set scr_team_teamkillspawndelay 0
    set scr_team_kickteamkillers 0

    // player

    set scr_player_maxhealth 100
    set scr_player_suicidespawndelay 0
    set scr_player_healthregentime 5
    set scr_player_forcerespawn 1
    set scr_player_sprinttime 4

    // UI

    set scr_hardcore 0
    set scr_oldschool_mw 0
    set ui_hud_obituaries 1
    set ui_hud_showobjicons 0

  2. You can download the official ClanBase server config .
  3. All matches must be played with ModWarfare Mod installed server as default.
  4. All servers must have ClanBase PunkBuster configs installed and stream to Game Violations.
  5. Using servers that do not authorise players original cd-keys from Activisions master server (cracked servers) is illegal and will result in a forfeit loss.


5. Demos and screenshots

  1. Demos:
    1. All players must record demos from the whole match. Both clans may request the demos from the other clan during a match conflict (1on1: all, 2on2: 1 per map, 3on3: 2 per map, 4on4: 3 per map, 5on5: 4 per map). If a clan hasn't uploaded its demos on the within 3 days, a matchconflict can be made to request them.
    2. Demos must be kept until the result has been accepted on ClanBase. If either clan decides to request demos in case of a conflict they must also explain their reasons for doing so.
    3. If a clan fails to provide all the requested demos, or if some of the requested demos are broken or missing 3 or more rounds, the other clan may request that the match be cancelled. Clans and players repeatedly failing to provide demos will be deleted.
    4. In case a clan wants demos from the opponent the clan should immediately state the exact demos they want (player and map). If the clan doesn't comply with this request the opponent is free to upload any demo of the match as he sees fit. A clan can only request demos once in a conflict and only during the first 3 days. Other requests will be ignored.
    5. After the requested demos are uploaded, the complaining clan has 3 days to specify specific points in the demo to check. If they fail to do so it will be assumed they have no complaints about the demos anymore.
  2. 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 can be requested by supervisors at any time.


6. Regional ladder rules

  1. The following regional ladder rules apply for all region-specific CoD4 ladders.
  2. In order to participate in a regional ladder a clan must be from that region or from a region that includes it. For example: Europe includes Germany.
  3. Any clan not from a ladder's region will be removed from that ladder.
  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 will not be punished if the match is played. When neither clan can provide a server from that region and they refuse to play, the match should be cancelled. If a clan 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 (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, if you do not have enough players in the region you will be removed from the ladder(s).
  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 killed.


7. GUID's

  1. GUID's are unique identifiers used in games to recognize players. Examples: SteamID, PB guid, CoD2 guid, UT2004 guid, ETpro guid, DWM 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. 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.
  4. 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.
  5. Players with GUID's that are listed on the Master Ban List (MBL) of the PunksBusted admin community are considered cheaters and are not allowed to play in any ladder matches.


8. Miscellaneous rules

  1. Clans are not allowed to share line-ups. Clans should not have more than 50% of their members in other clans, where they are active in the same ladders. Clans will be considered active if they are ranked in those ladders. Hibernating clans are not ranked. All violating clans will be warned by email. After this warning, the clans have five days to clear up their members list. Clans still violating the rule after this period will be deleted. This rule also applies to ‘multi-gaming’ clans.
    If the percentage of players shared is more than 50% of the total number of players in one clan, but is significantly less than 50% in another then only the first clan will be warned. For example, 51% of one clan’s roster also belongs to another clan’s, the other clan has more players so only 30% of its roster is in the first clan – the first clan will be warned, the other won’t.
  2. 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 – four or more occasions). 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 in the two matches
      - 4on4 ladder: three players are the same in the two matches
      - 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. Three or more forfeits of this type will result in the clan(s) being deleted.


9. Cheating and abuse

  1. The applies to all ClanBase ladders. Any cheating or abusive behaviour during a match will result in a forfeit loss.
  2. 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.
  3. 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.
  4. 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. 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.
  5. 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.
  6. Clans abusing the ladder system in any way in order to gain an advantage or just to be a nuisance will be deleted. Further punishment may include deletion of the accounts of the person responsible for the abuse, in extreme circumstances. For example, someone who has made fake accounts for fake wars may lose all of his/her accounts.


Global rules

10. General

  1. If the ladder rules for a specific ladder conflict with these global ladder rules, then the specific rules have precedence.
  2. The proper functioning of the ladder system depends on the sportsmanship of the participating clans. We expect everybody to play by the rules, but also to be flexible when circumstances require it and to be reasonable when an opponent has problems beyond their control.
  3. Not knowing the ladder rules is never a valid excuse for not following them.
  4. Any rule violation will result in a forfeit loss unless stated otherwise in the ladder rules. A forfeit loss means: the clan getting punished will lose 120 points and the opposing clan will gain 10 points.
  5. ClanBase reserves the right to broadcast every match. This can be done with online game broadcast tools for spectating purposes. The recording of such broadcasts can't be refused by the clans. In many cases ClanBase will allow or ask third parties to broadcast the matches. Spectators may never be charged.
  6. For any questions or comments concerning the ladder or the outcome of conflicts, contact the ladder supervisor by e-mail. For any questions or comments concerning the ladder or the outcome of conflicts that the supervisor can't resolve, or for complaints about the supervisor, read .

    Mail not written in English will not be understood and will not be read. Mail containing abusive language will be ignored. Mailed complaints will be ignored by the ladder managers where they involve, (a) where a controversial issue has not been discussed with the ladder supervisor first, or (b) a decision made by the ladder supervisor who has correctly applied the rules.
  7. Agreements and arrangements made in the challenge notes field, on the server or elsewhere are not binding. Only the official ladder rules and settings (maps, optional rules) decided on the challenge form should be followed and be considered as the correct rules. Agreements that contradict the ladder rules will be overruled in conflicts.

    For example: In conflicts, we will ignore clans who claim that the opponent agreed that they could use a freelancer on IRC or that the clan had put ‘24-hour rule doesn’t apply’ on the challenge notes and the opponent accepted. Proposed servers are never binding and are ‘suggested’ play locations only.
  8. Disclaimer: references to any gender in any ladder rulebooks within this website do not imply these ladder rules are gender-specific.


11. Clans and Players

  1. Any clan registered on ClanBase can participate in any ladder. For information on how to register your clan on ClanBase, read the .
  2. It is not forbidden for a player to be a member of more than one clan if the player links their personalities by using the link on the admin page. Any player in more than one clan without will be considered to be a freelancer in all clans except the one they were registered with first.

    All except the oldest account of the player’s unlinked accounts will be deleted. Where the oldest account has been abandoned the next oldest (used) account will remain. The only exception is when the duplicate accounts are no longer active and are unused.
  3. Only players who are registered in a clan on ClanBase can play in ladder matches, and they can only play with the nick (or very similar) they're registered with in that clan. Only players that have been registered as clan member for 24 hours or more are allowed to play for their new clan. Unregistered players, registered clan members who use a different nick or members that aren't in the clan for more than 24 hours will be considered to be freelancers.
  4. The above 24-hour rule does not apply to clans that have been created less than 48 hours before the official match time. The 24-hour rule does not apply to players who were briefly removed from the clan, for instance accidentally by the clanleader. A brief period is considered no longer than 18 hours. Players who are absent for longer than this period will be considered new to the clan again and must be in the clan for a further 24 hours before they are eligible to play.
  5. Using a freelancer in a ladder match will result in a forfeit loss. Using multiple freelancers (three violations) will result in deletion of the clan. Violations are accumulated over time. Freelancers used over a year ago will not count, unless the clan has a long history of using freelancers.


12. Ladders

  1. ClanBase only creates ladders when we believe there's a 'market' for it. When a new game or mod is released, we usually create a European ladder for it first, and country ladders later as the European ladder becomes busier.
  2. If you would like to request a new ClanBase ladder for a new game, mod or an existing game and you think there will be enough interest from other clans to make it competitive - please start a petition (or vote for an existing petition) using .
    Next, we will consider adding the ladder, based on the popularity of the game or mod and based on our relevant expertise in order to provide a great working ladder. There is no set number of votes that will ensure a ladder or game is added. The ladder/game may be rejected if it has been tried before and failed.
  3. Country/region ladders may be restricted to clans of the corresponding nationality, appearing in the Regional Ladders section of the rules. Not every ladder has these rules, but the restriction for all regional ladders is that matches for country/region ladders have to be played on servers in that country/region, unless both clans prefer not to. When clans play on a server not within the region, neither clan can later dispute the score because of it, as when a match starts – servers and settings are accepted. Disputes need to be settled before the match starts.
  4. The inactivity system will remove clans from all the ladders with more than 20 active clans, who haven't played for 8 weeks. Read for more info. The inactivity system is designed not to work on ladders with no or little activity. Dormant clans will not be forcibly removed from inactive ladders by the ladder chiefs unless they hold the number one spot. Please do not ask us to do so, alternatively challenge more active clans in the ladder.
  5. The gold, silver, and bronze ladder icons can be obtained only in large/active ladders. These icons feature next to the clan’s name.
  6. Playing several matches against the same opponent in a short period of time is considered cheating as it distorts the ranking. As a rule of thumb, never play the same opponent twice in less than one week unless you also play many other matches. In case of grave violations it will be assumed the matches are fake.
  7. Clans without the required amount of players can be removed from the ladder after 7 days.
  8. When a possible fake match is discovered, both clans involved will be deleted from ClanBase without warning. Clanleaders have 72 hours to against this decision, but they must supply proof of the match in the form of screenshots or demos. Players should appeal by mail to the supervisor that reported them; unless the supervisor’s details were not included in the clan’s deletion notes.


13. The rating system

  1. ClanBase ladders use a rating system based on the ELO system known from chess. Every clan starts with a rating of 1000 points. After each match, points are added or subtracted based on whether the outcome of the match was a win, a loss or a draw (the score has no importance).
  2. How many points you gain after a win or lose after a defeat depends on the rating difference between you and your opponent before the match. The ELO formula is very complicated, but the following easy examples will give you a good idea:
    • Beating an opponent with the exact same rating gets you 60 points.
    • The maximum amount of points you can win for a single victory is 120, but to get this many points you'll have to beat an opponent who is 700 or more points ahead of you in the ranking. You get 100 points for beating an opponent who is 200 points ahead.
    • Beating lower ranked opponents gets you less than 60 points. If they were 200 points below you you only gain 20 points, if they were 300 points below you only get 10 points, and if they were 400 points below you get a mere 5 points.
    • If a match ends in a draw you will gain points if your opponent was ranked higher, or lose points if they were ranked lower.
    • The number of points you can win and the number of points you can lose always add up to 120. So if you can only win 30 points with a victory, you can lose 90 points with a defeat.
  3. Against clans that have played less than 3 matches in a ladder, you only win or lose half the amount of points you could win or lose.
  4. The ladder leader does not have a rating, but is considered to have an infinite rating instead. Top 5 clans can take the top spot by challenging the current ladder leader and beating them in a direct confrontation. If that happens they become the new ladder leader while the old leader will return to the normal ranking with the points they had before. If the challenger loses or plays a draw, the ladder leader’s position doesn’t change.
  5. The ladder leader is not allowed to refuse playing the other top 5 clans without a valid reason (valid decline options are proposed by the system, see below). Repeatedly rescheduling to senseless dates or with non-default match rules or only playing lower ranked clans in order to be able to decline challenges will be considered abusing the ladder system and the clan will risk being removed from the first spot.
  6. Clans outside the top 5 can also challenge the ladder leader, but such challenges can be declined freely. If the ladder leader is beaten then they're switched with the second ranked clan while the challenger gains 120 points. If the ladder leader wins, nothing changes.
  7. In case the number one has been deleted for ladder, cup or C&A violations, the second clan in the ladder is set to number one.


14. Arranging matches

  1. The deadline for reacting to a challenge is 7 days after the challenge or 7 days before the war, whichever is later. If by the deadline the opponent still hasn't reacted to the challenge, they get a penalty of 5 points. If the ladder leader ignores such a challenge, they will lose their position to the second clan. You can set an earlier deadline for accepting the challenge, but then there is no penalty if the opponent doesn't react in time.
  2. You can only refuse a challenge from another clan in the following cases:
    • Reschedule: You want to reschedule the match to another date. This date has to be within 14 days of the original challenge.
    • Unequal match: There is a gap of 10 ranking positions and 100 points between you and your opponent, or you have more than 1100 points and it's your opponent's first match.
    • Busy in this ladder: you already have 2 or more matches in this ladder in the next 30 days.
    • Custom maps: the opponent selected custom maps.
    • Declinable matchrule: the opponent selected a declinable match rule in the challenge form.
    • Hibernate: you want to set your clan as inactive in this ladder. You lose 32 points but after that you can decline all challenges. All your scheduled matches are cancelled when you go into hibernation. Hibernation ends automatically when you play an official match for this ladder again.
    These options are only available for the ladder leader:
    • Unequal match: The challenging clan is not ranked in the top 5 of the ladder.
    • Resign: Using this option will make the ladder leader lose it's position in the ladder to the second ranked clan.
    If you don't want to play the match for some other reason, you'll have to contact the other clan (e-mail, IRC, ICQ) and persuade them to cancel their challenge.
  3. A scheduled match can be cancelled until 12 hours before the starting time on the . The side that wishes to cancel the match will either have to request a reschedule or go into hibernation.
  4. When both clans agree not to play a match it can be cancelled for any reason after its scheduled starting time. Just choose the 'Match was cancelled' option on the result form.
  5. If a match is played without being arranged on ClanBase first, then both sides are depending on each other's sportsmanship to accept the result afterwards. We will not force match results when there was no accepted challenge for that match.


15. Before the match

  1. To find your opponent before a match, you should look on their clan channel on IRC or contact them directly through ICQ, MSN, e-mail or any other means if you don't use IRC.
  2. If you can't find each other this way, go to the ladder's IRC channel (linked in the Ladder Info box on the ladder page) and put your clan tag before your nickname.
  3. If you still haven't managed to get in touch with your opponent 10 minutes after the scheduled starting time of the war, you can fill in a no-show. You have to state on the ladder's IRC channel that the opponent did not show. This will be considered proof of your presence and your opponent’s absence. One way to report a no-show in the channel is as follows: ‘filling in a no-show for ‘my-clan’ vs. ‘other-clan’, warid=[]’. To contest this, the other clan must also log a no-show.
  4. If you're more than 10 minutes late, you have to accept a no-show if your opponent insists. If you feel there's a good reason the result shouldn't be a no-show, you'll have to convince your opponent of that.
  5. If one clan is short of players or refuses to start the match with the rules agreed upon in the challenge form, the other clan can demand a no-show to be filled in. Remember that challenge notes, the proposed server and agreements made elsewhere are not considered to be binding rules.


16. During the match

  1. Once a match has started, its result counts, unless both sides agree it shouldn't. Ping, lag issues or incorrect server settings are no excuse for leaving; you should have checked the server before you started playing.
  2. If one clan walks away from the match, the score at the time when their last player quit can be considered to be the result of the match by the clan that stayed. If this score doesn't reflect the probable final outcome of the match, ClanBase can change it to the advantage of the clan that stayed.


17. After the match

  1. Either clan can enter the result of a match, unless the other has already done so. A match result can be:
    • The real score of the match.
    • A no-show if the opponent didn't show up.
    • The result reflects the punishment specified in the rules which the opponent violated.
    • A forfeit if the opponent violated rules with no punishment specified.
  2. In case of a no-show it's strictly forbidden to fill in any score (even 1-0), even when both clans agree. Instead you must check the no-show box on the result form, which will result in a fixed penalty of 10 points for the clan not showing up. No-show matches where a score has been entered may be cancelled or changed to a no-show without warning.
  3. Once one clan has entered a result, five things can happen:
    • The score is edited by the clan that entered it.
    • The score is accepted by the other clan, and ladder ratings are adjusted accordingly.
    • The other clan refuses to accept the score, and enters another result.
    • The other clan refuses to accept the score, making it a match conflict (see below).
    • Both clans do nothing for 4 days, after which the score is accepted automatically.


18. Match conflicts

  1. The match conflict system functions as a court room with ClanBase admins acting as judges. A match conflict can be made when the result entered by one clan is not accepted by the other. Due to the extra workload conflicts cause, the rules below are to be strictly followed.
  2. The system will not allow the creation of match conflicts during the first 24 hours after the match time, so try to solve the conflict with your opponent by IRC/ICQ/e-mail or in the match report first. Not making an effort before starting the official match conflict, will result in an automatic loss of the conflict.
  3. If you can't resolve the conflict with your opponent then try entering the appropriate match result first. Only after the opponent changes the result, you should initiate a conflict. Entering false match results will result in an automatic loss of the conflict.
  4. In the conflict both sides must explain the problem in a short but clear and complete way. Only relevant and proven facts may be mentioned. Links to proof must be included right away. If proof is requested from the other clan, it must exactly be stated what, from who and for what reasons. Failure to make a proper match conflict will lead to an automatic loss of the conflict.
  5. Clans are allowed to write conflicts and comments in the language of a regional ladder if the ladder supervisor is from that same region. But a translation in English must always be provided as well. If in the event the conflict is looked at by another supervisor, everything not mentioned in English will be ignored.
  6. Examples of valid proof are demos, in-game screenshots and server logs that were obtained from a neutral party. Private logs from IRC, ICQ, etc or server logs provided by either clan will not be considered to be evidence because they can be easily falsified. If a demo is used as proof of cheating or other malicious actions, you must immediately specify the exact moment(s) (down to the exact minute and second) where the cheating occurred or the conflict will be lost automatically. Supervisors will not look at entire demos.
  7. If the ladder rules allow a clan to request something from the other clan (demos, screenshots,...) and the conflict is made because the opponent failed to provide requested items, they have 3 days to the items on to the ClanBase ftp using the . The other clan can also make such request but only during the first 3 days of the conflict. Upload requests can only be made once by both sides. When a requested upload is complete, the other clan has 3 days to provide all info as how the requested and uploaded items would make proof for their claims.
  8. Both sides must state the match result they claim. In case of a score, links to screenshots must be posted immediately. Making ungrounded claims will result in an automatic loss of the conflict.
  9. Any form of abuse, starting off-topic discussions, making unproven accusations, needless repeating already mentioned facts or any other comments not relevant to solving the case will all result in an automatic loss of the conflict.
  10. It is strictly forbidden to contact any admin in private to defend your case. You may only ask the admin processing your conflict in private, after one calendar month how long a result on your conflict will take. Anything you have to say must be said openly. Trying to influence an admin in private will lead to an automatic loss of the conflict.
  11. An automatic loss of the conflict means the claim of the opponent will be granted. If the opponent didn't make a claim, the result will be a no-show loss.
  12. If both clans violated the ladder rules, the match will be cancelled. Such closure of the conflict does not mean proven individual cheating will go unhandled, such cases can be reported to the ladder supervisor by mail in order to punish the player(s).
  13. If a clan does not comment within 3 days since the last reply, it will be considered they have nothing more to add.
  14. The admin will only look at the comments on the conflict page when judging a case. Comments or links to proof on match reports or anywhere else will not be taken into consideration.
  15. Match conflicts will be judged by the ladder rules at the time of the match and by the match rules agreed upon in the challenge form.
  16. Match conflicts are never urgent and the admin will typically let a week go by before looking at a case to give both sides the chance to explain their case. Wait patiently until a decision is made. Only when a conflict is older than one month, you can mail the game supervisor.
  17. Clans who repeatedly make conflicts, that have no foundation in the rules or that are clearly made for the sole purpose of complicating the match process, will be deleted. Clans who repeatedly violate the ladder rules and force other clans into making conflicts will also be deleted. Three conflicts that have been made without foundation or are pointlessly forced (within the last year) will be considered sufficient to delete the responsible clan.