Battlefield 3
Call of Duty: Black Ops 2
COD: Modern Warfare 3
Crysis 3
Far Cry 3
FIFA 13
Gears of War: Judgment
Halo 4
Halo Reach
Medal of Honor: Warfighter
Dust 514
Ghost Recon Future Soldier
God of War Ascension
NFL Madden 13
Playstation All-Stars Battle Royale
Starhawk
Uncharted 2
Uncharted 3
Ghost Recon Online
Halo Combat Evolved
League of Legends
Minecraft
Quake III
Renaissance Heroes
StarCraft II
Tower Wars
Tribes Ascend
Unreal Tournament 99
World of Tanks
Assassin Creed Revelations
FEAR 3
Homefront
Mario Kart
Battlefield 3
Close Quarters CQ Domination 4on4 Europe
This is a ladder for Close Quarters Conquest Domination. Its a default 4on4 ladder, but matches can be "3on3 or 5on5" if both clans agree. See rules for more info. This is a EU ladder, so all teams must give priority to EUR timezone. The ladder time is CET Have fun!
Season Dates: Indefinite
This ladder is Point based
Close Quarters Ladder TeamSize Review
Posted by eL-X-
on Sat, Apr 27 at 02:11pm
Most Common "Not Followed Rules"
I've created this topic here which lists the most common mistakes that can lead to a forfeit loss.
Please read it and also be aware of the Ladder rules.
New Rule
Choosing sides!
Team choose sides on their choosen Map
Team A choose side on Map A (map choosen by Team A)
Team B choose side on Map B (map choosen by Team B)
If war is tied and its necessary to go to 3rd map, the team with less amount of tickets from the 2 previous maps will choose side.
Before you join!
Please dont join the ladder if you dont have enought members to make a team. After you join please check if you have the correct GUIDs recorded or else you will not be able to play. You want to join the ladder to play, right? 
Fell free to contact the Head Admin under the Staff Tab if you have any doubts!
All teamleaders can apply to FN CQ Domination Platoon Wars here: http://battlelog.battlefield.com/bf3/platoon/2832655241506082074/
Use the search tool below to find a match date/time combination that you are able to play. Please note
that once a match has been accepted, you and/or your team will be subject to forfeiture of match and points if the match is not played out
according to ladder rules and settings.
** Please Note: You WILL NOT SEE
your own challenges when searching the Match Finder, only those posted by other participants will be displayed to help keep search results meaningful.
| Ladder Season: | Indefinite |
| Cash Payout? | No |
| Time Zone: | GMT+2 |
| Challenging Disabled? | No |
| Signups Closed? | No |
| Allowed Declines Per Week: The number of challenges a participant may decline/ignore in a 7 day period without being penalized. Please see the general rules for specifics on Challenge Declines | 3 |
| Ranking Type: | Point Based |
| Challenge Map Selection: | Participant Selected |
| Challenge Point/Rung Restriction: The number of Rungs, or Points, that a participant must be within to challenge another participant. | 0 |
| Rounds Per Challenge: | 3 |
| Reporting Type: The type of data collected when reporting a Challenge | Score Entry |
| Matches Require a Referee? | No |
| Challenge Out Hours: The minimum numbers of hours from the current time to which a challenge date may be specified. | 0 |
| Accept Timeframe Hours: The number of hours allowed to accept a challenge - failure to respond inside this timeframe will result in the system processing it as an 'Ignore'. Please see the general rules for more detail on this. | 0 |
| Same Opponent Grace Period: The number of hours that must pass after reporting a match before the same opponent may be challenged again. | 12 |
| Multiple Challenges at a Time? Specifies whether or not each participant may have more than 1 concurrent challenge pending at any given time. | Yes |
| Team Ladder? Is this a 1v1, or a Team Ladder | Yes, this is a 4v4 Team Ladder |
| Requires GUID? Whether or not this game require a unique ID registered in your profile to play. | Yes |
| Static Match Settings: | |
|---|---|
| The settings below are REQUIRED settings for every match played on this ladder. All matches must adhere to these settings or risk disqualification. These settings CANNOT be modified for a specific match without the express permission of a Head Admin or Game Director. To have your opinion heard on these settings, please visit the forums; forum links are available to the right of the standings just above the ShoutBox. | |
| Setting Name: | Setting Value: |
| tickrate: | 150 |
| friendly fire: | ON |
| Selectable Match Settings: | |
|---|---|
| The settings below are selectable on a per-match basis. You will have the opportunity to select these options during the challenge process. The default option is denoted with a * next to it. | |
| Setting Name: | Options: (*) |
| 1. General Rules | |
|---|---|
| 1.1 | General Rules The full general rules can be found here. The
following rules are provided for easy reference only, and are not a
complete list. It is the responsibility of all members of a team to
understand and abide by the complete list of general rules. |
| 2. Code of Conduct | |
| 2.1 | Code of Conduct In order to
create a friendly and comfortable environment for all participants, the
following Code of Conduct will be strictly enforced: Members
will treat each other with respect at all times. No member will use
comments about nationality, age, gender, race, religious belief, or
sexual orientation to insult others. Members will exhibit good sportsmanship at all times. There will be no taunting, harassing, or unsportsmanlike conduct. Profanity
and language of an offensive nature will not be tolerated, whether on
forums or any type of voice or text communications. There will be no
discussion of nudity, sexual content, use of illegal substances, or any
other adult content, whether by images, text or voice communications. Members
will not attempt to manipulate the game or ladder system in an attempt
to give any player or team an unearned advantage. This includes
intentionally killing one's teammates or oneself. Penalties for violating the Code of Conduct include, but are not limited to:
For more information on how penalties are assessed, please see the General Rules. |
| 3. Match Issues | |
| 3.1 | Admin Calls If a team/player disagrees with an Admin's call, they must submit a support ticket. Challenging a call made by the admin should NEVER be done DURING
the match. Should any player attempt to argue with the admin mid-match,
they will be subject to penalties at the admin's and/or Head Admin's
discretion. Each player/team will have 5
challenges to use per season. If your team wins the challenge, your 5
challenges remain. If the decision is not overturned by an Admin, then
your team will lose 1 challenge. |
| 3.2 | Reporting Match Issues If a player/team has an issue with their ladder match that they would like an admin to address they can submit a support ticket. Teams/players have 5 days from the reporting of their match to submit a support ticket for admin review. If a support ticket is submitted after 5 days from the reporting of the match the support ticket will not be reviewed. Included in the support ticket must be UNEDITED video as proof or images. Failure to provide proof may cause the ticket to be closed. |
| 3.3 | Reporting a Tie In the event of a tie
during a match, a player/team will move onto the next map in the round.
If at the end of playing all the maps someone has not won best
2-out-of-3, then play the first map tied again. |
| 4. Playing Matches | |
| 4.1 | Challenges If your team is set as inactive, simply submit a support ticket when you are ready to have your team reactivated for play on the ladder. |
| 4.2 | Crown Holder |
| 4.3 | Change Requests Anytime a
match is rescheduled, a change request must be submitted and accepted at
least 4 hours prior to the originally scheduled date and time. If
a change request is not submitted in the allotted time and a team or
person fails to show up on time then a forfeit may be requested or the
match may be deleted at the discretion of the team that is present and
on time. Accepting a Change request will add
reputation points to your account, as will submitting a change request
that gets accepted. This is to encourage matches to be played by
rewarding them with community reputation points that make a member more
credible within the community. |
| 4.4 | Player Disconnects If any player is disconnected before the first kill is made, the match must be restarted. If
a player is disconnected during a 1 vs 1 game after the first kill then
that member will forfeit that game, regardless of score at time of
disconnection. If while playing a team match and the host disconnects prior to the first kill the map will be restarted with a new host. In the event that the host disconnects after the first kill the hosts team will forfeit that map. For Team
Based matches the match shall continue, and the dropped player may
rejoin as soon as they can. No substitutions may be made during a map. |
| 4.5 | Glitch/Floating Spots For
these ladders, a 'glitch' spot is defined as any area where a player is
inside a wall or other object, or standing where at least one foot is
not on solid ground. Individual 'glitch' spots are subject to review by a
ladder's Head Admin. |
| 4.6 | Teams/ Rosters You may rotate any eligible member of your roster for play at the beginning of any round. You
may substitute one ineligible player for play during the match. An
ineligible player is someone who was NOT on your roster at the time of
challenge, but as of the date of the match has been on the roster for at
least 36 hours. Any team may substitute an
ineligible player who was not on their roster at the time of the
challenge, but has signed on AT LEAST TWO HOURS PRIOR to the time and
date of the match.This is contingent on agreement from the opposing
team. No exceptions will be made for players NOT on the roster 2 hours prior to the match. Substituting more than 1 ineligible player in accordance to the rules above is strictly prohibited unless otherwise specified in the ladder specific rules regardless of any team agreements. Both teams will be penalized. |
| 5. Settings | |
| 5.1 | 1) Weapons / Attachments - shotguns - m320 - m26 (only smoke allowed) - rockets (engineer) - Crossbow Attachments Not allowed: - c4 - m18 claymore - t.ugs / mav drone (on recon) - spawn beacon - laser light - tactical light All other weapons and attachments are allowed. If a player uses a forbidden weapon / perk his team will loose the round where infraction occured You should take a screenshot with a proof of it (it can be a screenshot of players weapons/perks - death screen - , a screenshot of player using weapon/perk or a video) 2) Server Settings: vars.ranked "0" punkBuster.activate 1 vars.allUnlocksUnlocked 1 vars.friendlyFire true vars.teamKillCountForKick 0 vars.teamKillValueForKick 41 vars.teamKillValueIncrease 1 vars.teamKillValueDecreasePerSecond 5 vars.autoBalance false vars.killCam false vars.miniMap true vars.3dSpotting true vars.miniMapSpotting true vars.3pCam true vars.vehicleSpawnAllowed false vars.vehicleSpawnDelay 100 vars.bulletDamage 100 vars.nameTag true vars.regenerateHealth true vars.roundRestartPlayerCount 1 vars.roundStartPlayerCount 2 vars.onlySquadLeaderSpawn false vars.soldierHealth 100 vars.hud true vars.crossHair true vars.playerManDownTime 100 vars.playerRespawnTime 100 vars.unlockMode all |
| 6. Server Responsability | |
| 6.1 | Players and teams must provide their own Servers and come to anagreement with their opponent as to which to use. As this is a EURladder, the match must be played in a EUR server. The only exception isif both teams are from outside EUR. The team who makes the challenge is responsable to make sure there is a server to play. If not, contact the other team before making the challenge. If there is no server at the match time, and both teams cant provide a server, the team who made the challenge will loose by forfeit. In case both teams have server it must be used the one that offers better overall condition to all players (latency, etc) If both teams agree the match can be reschedule to a later date, however the challenged team is not forced to accept this. |
| 7. Team Size | |
| 7.1 | This is a 4on4 ladder, so the standard match will be in this team size, however if both teams agree, the match can be played in a 3on3 or 5on5 limit teamsize. If there isn't agreement, then the match must be played 4on4 |
| 7.2 | If there is a player with problems connecting, or dropped before match start, his team has 15 min to fix it or to get a substitute. After that period if the problem isn't solved they can choose to play with one less player (3x4) or forfeit the match. |
| 8. Matches | |
| 8.1 | Matches are played in 3 maps (check maplist for more information). 1 round of 150 tickets each map. Be aware that Operation 925 is 100 ticket default, so you must manually set it to 150 tickets. Final Score will be: 3 - 0 2 - 1 1 - 2 or 0 - 3 Challenger picks 1st map, Challenged picks 2nd and system generates 3rd. You must take screenshot of final score and then submit it when you are making the match report |
| 8.2 | Choosing sides! Team choose sides on their choosen Map Team A choose side on Map A (map choosen by Team A) Team B choose side on Map B (map choosen by Team B) If war is tied and its necessary to go to 3rd map, the team with less amount of tickets from the 2 previous maps will choose side. |
| 9. Penalties | |
| 9.1 | Failing to follow the above rules may lead to match cancelled, round lost or match forfeit loss. |
This ladder is not configured for any prize payouts. Please click this link to search the list of ladders that have been configured for prize payouts.
Not Joined
ShoutBox!
Ladder Servers
- Arranged by teams 2
123.123.123.123:12346
- Arranged by teams 3
123.123.123.123:12347
- Built-In Multiplayer
123.123.123.123:12345
°
°
°