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
BF3 PS3 Hardcore Ladder
This ladder is for the best of the best in Hardcore mode for BF3 PS3. These teams will battle for being the best hardcore platoon in various game modes. A minimum of 8 players are required to be on roster in order to be eligible to compete but most matches should be 12. There are no soft core matches so only those that prefer to play HC mode only.
Season Dates: 03-19-2013 - 07-20-2013
This ladder is Point based
Welcome to the Hardcore Conquest Ladder
Posted by ComeGetSome25
on Sat, Apr 06 at 04:54pm
WELCOME TO THE BATTLEFIELD HARDCORE LADDER!
**Please refer to the rules section for scoring and ladder rules
First Map - Player picked team hosts **EU/US
Second Map - Player picked team hosts **US/EU
Third Map - Higher ranked team hosts **
*Unless agreed to be played all maps on same server. This rule is geared more towards EU vs US matches.
EAST US server location is mandatory for the third map of every challenge. Unless both teams agree to play the third map on a different server.
**NOTE: When challenging US vs EU be aware of time difference. Usually a good time is between 11am-5pm EST for both sides. Also, try to contact a captain to arrange the details and the best date/time before sending a challenge
CONGRATULATIONS TO:
kRs King Rogue Squadron Season 1 regular season winners and Season 1 playoff Champs!!!
CONGRATULATIONS to GSP Genetically Superior Players in being Season 1 Playoff Runner-ups!!
WELCOME TO SEASON 2!!! There are some new additions and changes to the ladder! ANY Suggestions or changes you guys would like to see made.. please post in the forums!
NOTE: Any communication regarding matches and roster must be made and agreed on in pre-match comms. Please Utilize this feature because if there are any problems in any match that is what the admins look to for proof as it is the official comms for FN regarding matches. So if comms not in there then agreements etc.. are not valid.
ALSO, If you have any suspicions about other clans game play. Please refrain from using vulgar and offensive language towards them in any way. Instead start gathering evidence by recording video and taking photographs. Keep respect at all times. If you have any issues please create a support ticket and provide whatever proof you gathered. Without proof then no action can or will be taken.. remember your trying to prove your case to a third party so EVIDENCE IS ESSENTIAL. So, do not leave the ladder because you think a team is not playing fair..it's not that hard to collect evidence to support your reasoning
We will be starting a BF4 Ladder as soon as it's out. Or just change this one.
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: | 03-19-2013 - 07-20-2013 |
| Cash Payout? | No |
| Time Zone: | EST |
| 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 | 4 |
| 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 | Yes / No Select |
| 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. | 22 |
| 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. | 11 |
| Same Opponent Grace Period: The number of hours that must pass after reporting a match before the same opponent may be challenged again. | 16 |
| 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 8v8 Team Ladder |
| Requires GUID? Whether or not this game require a unique ID registered in your profile to play. | No |
| 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: |
| HARDCORE MODE | HARDCORE MODE ONLY |
| 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: (*) |
| Team Size | * 12v12 10v10 11v11 8v8 9v9 |
| Minimap | * OFF ON |
| Server Type | * Ranked Unranked |
| Game Mode | * Conquest/Conquest Assault CTF Rush |
| Match Set Up | * Use Fraggednation ladder setup with burn round Use Battlelog to set up match |
| 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. Admin Assignment | |
| 2.1 | Admin Assignment An admin will only be assigned to a match if they are requested by a Player/Team Captain or another Admin. Requests must be made by submitting a support ticket at least 24 hours prior to the scheduled match time. The admin request must include the following in the support ticket: Ladder name Match ID Date Teams playing If an admin is assigned they must be invited by the match host before match start time, and they will remain in the room to spectate the entire match. Admins may be requested for voice chat meetings with both teams as well. Same process applies as outlined above. |
| 3. Code of Conduct | |
| 3.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. |
| 4. Match Issues | |
| 4.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. |
| 4.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. |
| 4.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. |
| 5. Playing Matches | |
| 5.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. |
| 5.2 | Crown Holder |
| 5.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. 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 in the community and available to more community events. Unaccepted challenges with at least 3 attempted change requests will not increment the 7 day free decline counter. |
| 5.4 | Player Disconnects 1v1: If either player is disconnected before the first kill is made, the round 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. Team Based: If any player is disconnected before the first kill is made, the round must be restarted. 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 if a player disconnects. If a player cannot rejoin the game after 2 mins a sub may be used. Teams are allowed a maximum of 2 subs per map. |
| 5.5 | Lag Test A
lag test must conducted for at least 60 seconds prior to any match
being played, and any time the host is changed. Failure to conduct a lag
test will cause any support tickets
turned in to be closed. During the lag test, teams must pick the best
player (from the hosting team) to host the match. If issues occur with
players being dropped after the test has been conducted, teams should
follow the drop player rules of the ladder. All lag test must have either camera recording on an image available to show proof it was done. Teams can choose not to conduct the lag test, however, both teams must comment on the match comments saying that lag test is not needed. |
| 5.6 | Teams/ Rosters Any team on a Team-Based ladder can have as many people on the roster as they would like - however only the specified amount can play during the match. You may NOT switch a team member DURING a round of play, unless a specific Ladder's own rules permit, pursuant to appropriate circumstances. You may rotate any eligible member of your roster for play at the beginning of any round. It is the responsibility of both teams to verify eligibility of all players in the match prior to starting a new round. Playing with an ineligible player will cause your team to forfeit that round of play, unless both teams agree to allow the player to play as described in general rule 21.5. If you identify the other team has an ineligible player on their team, simply ask them to replace the player with one that is eligible. Reference general rule 15.5 for more information on allotted time to get eligible player. If they can not replace the player, the round will be a forfeit for their team unless both teams agree to allow the ineligible player to play. This agreement must be done in the match comments section. There is no exceptions to this agreement or admins will not honor the agreement when making a decision on support tickets. If both teams did not agree (in match comments) and team(s) still played with the ineligible player, submit a support ticket immediately upon the completion of the match. Ensure you have all the proof needed in the ticket prior to submitting it for admin intervention. *Only ONE ineligible player is allowed to be used during a game if both teams agree using the guidance listed above. You can check eligibility of who can play on your team by visiting the match details inside of your challenge management console. If the player is not listed, he/she was not on the team at the time of the challenge and the player is ineligible. It is recommended you get your team filled prior to challenging. All team members must have an PSN account associated with their FN account. Failure to do so may also cause a player to be ineligible. Failure to obey these rules will result in disqualification from current match, as well as a penalty designated by the Head Admin. A 2nd offense will result in removal from ladder competition. Players may only compete on ONE Team per Team Ladder, and ONE 'rung' per 1v1 Ladder. Players wishing to play on another team on the same ladder as a team they have already joined may be issued a Roster Exception. This roster exception is generated automatically when a conflicting team joins the ladder, and essentially deactivates conflicting team members from the opposing team's roster. To have a roster exception removed, a team member must leave the team, or the team must leave the ladder, and the opposing team may then remove the Roster Exception. |
| 5.7 | No Shows, Ineligible Players, and Match Overlap In the event a team does not show at the selected time and server or have they an ineligible player as described in 21.4 teams must give the other team 10 minutes past the match time. If they still don't show or can't find an eligible player then the opposing team may request a forfeit. Should the opposing team choose to wait longer, they may. In the event waiting for another player causes an overlap to another match, both teams or challenging team will receive a forfeit. Ensure there are no other matches scheduled during the time frame it would take to complete the first match. |
| 6. Definitions | |
| 6.1 | Be sure to understand the difference between each of the following key terms: Map: In each match there are 3 maps. The term 'map' refers to 1 of the 3 maps. Match: A match is the entire game to be played against another team. It includes the 3 maps and all of the rounds. Round: When playing on a map, a round is when a team is playing as either the Attackers or Defenders, or Americans or Russians. Since teams play as both sides on each map there are two rounds per map. |
| 7. General Ladder Rules | |
| 7.1 | Cheating and other Misconduct Refer to section 14 of the general rules. Using a mouse and keyboard is not allowed. |
| 7.2 | Use of banned/disabled weapons/gadgets/settings will result in automatic forfeit of the map. So if a teams agree on no mortars and it is also disabled on match settings and accepted by the other team. A team who uses that banned weapon for that specific match will forfeit the map. Glitching/cheating will be an automatic forfeit of the map. |
| 7.3 | Glitching/Cheating Certain rules such as Glitching/Cheating will cause a team to forfeit the game. If you are caught glitching/cheating (glitching/modded controller) If you are caught once you will forfeit the match If you are caught twice you will forfeit the match and receive a final warning from admin If you are caught a third time you will be suspended from match play for 1 week and the players involved will be removed from team If you are caught a fourth time you will be removed from the ladder. |
| 7.4 | Hosting: First Map - player picked team hosts Second Map - player picked team hosts Third Map - higher ranked team hosts EAST US server location is mandatory for the third map of every challenge. Unless both teams agree to play the third map on a different server. Teams can agree to do all maps on one server. In the event teams are both unranked then the Challenged team will host the third map The third map must always remain random. We want it to be challenging for both teams and get teams out of their comfort zone and be able to overcome and be victorious. If you would like to change the third map agree to it on the pre-match comms and create a support ticket requesting a change and an admin will randomly pick one for the map change. The admins have the right to deny such requests. |
| 7.5 | Requesting an Admin The "Request Admin" option should only be used to have an admin present at the start of a match to make sure both teams show up. If an admin is requested for a match they will join one of the teams participating at the start of the match to ensure both teams show up. Once they have made sure both teams are present they will leave and allow the team they were on to invite their other member. |
| 7.6 | Forfeit Procedure When reporting a forfeit also make sure you submit a support ticket for that specific ladder. In this support ticket include the match ID, date, teams playing, details of what occurred, and any proof you have. This makes the admin's job much easier to determine who receives the win by giving us a better understanding of what occurred. |
| 7.7 | Failure To Show, Late Policy, & Server Setup: If a team fails to provide a viable server within 15 minutes of the scheduled match time the first map will be forfeited. If the teams fails to provide a server within 15 minutes of the first violation they will forfeit the second map and lose the match 2-0m. If this does happen most likely the teams will be combined and teams mixed because of the failure to have the required 24 players. BOTH TEAMS SHOULD KNOW THIS BEFORE THE ROUND STARTS AFTER THE BURN ROUND. SO BOTH TEAMS SHOULD STAY AT THE DEPLOYMENT UNTIL THE TEAMS ARE FIXED BY YOUR TEAMS ADMINS: |
| 8. Rush/Conquest/CTF Scoring Rules | |
| 8.1 | Hardore Conquest & Conquest Assault Scoring: A match consist of 3 maps. One map consists of each team playing 1 round as the Americans and 1 round as the Russians. First team to win two maps wins the match. A point is received when a team wins as either the Americans or Russians. At the end of a map scores will be compared and the team which won by more points, wins that map. Points from each map do not carry over to next maps. Each map starts out 0-0. Example: Team A wins all 4 rounds (2 maps) as the Americans and Russians and Team B does not win at all, Team A wins that map 2-0. If there is a tie in wins on a map then the winner will be determined by the ticket count. Example: Team A wins the first round on American side with ticket lead of 150. Then in the second round of the same map, Team B wins on American side with ticket lead of 200. Because Team B has managed to win by higher score count they will be considered the winner of that specific map. |
| 8.2 | Hardcore Rush Scoring A match consist of 3 maps. One map consists of each team playing 1 round as the Attackers and 1 round as the Defenders. First team to win two maps wins the match. A point is received when a team successfully destroys a M-Com site. At the end of a map, points are added up and the team with more points wins that map. Points from each map do not carry over to next maps. Each map starts out 0-0. Example: Team 1 blows 1 M-Com and Team 2 blows 0 M-Coms, Team 1 wins that map 1-0. If there is a tie in M-Com's destroyed on a map then you must go by ticket count. EX: This is a example where the match has just started and it is the first map Round 1: Team A blows up 4 M-Coms with 50 tickets left Round 2: Team B also blows up 4 M-Coms but has 55 tickets left Team B wins the map and is up 1-0M because they had 5 more tickets than Team A |
| 8.3 | Hardcore Capture The Flag Rules |
| 9. Specific Ladder Rules | |
| 9.1 | Ladder Specific and Selectable Settings: Specific: GAME TYPE: HARDCORE Selectable: Game Mode: CQ/CQA, Rush Server Type: Unranked or Ranked* Minimap: On* or Off Team Size: 12v12* 11v11, 10v10, 9v9, and 8v8 Explosives (C4, Claymore, and AT Mine): Disabled or Enabled* Mortars: Disabled or Enabled* ROVs (EOD Bot and MAV): Disabled or Enabled* * - default setting when creating a challenge |
| 9.2 | BASE RAPING / VEHICLE STEALING: Base raping is allowed. Since it may be decided by ticket count if a Map becomes tied you want to be have the better ticket count in the end. Therefore you must be able to overcome adversity and work together to achieve victory by creating a strategy on the spot and adapt and achieve victory in those situations. Vehicle stealing is allowed as of right now. This game is based on warfare. Which means you must utilize the resources at your disposal. Failure to do so will ultimately make you lose the war. So if your team leaders do not communicate a vehicle is up and are not aware of base defense then you deserve to have your vehicle stolen. You must have a high awareness level on the battlefield to protect what is yours. If your vehicle gets stolen you must quickly work together, communicate and take down that vehicle asap. Perform a SITREP (situation report) and change up the strategy quickly to stop that from happening again.BASE RAPING / VEHICLE STEALING |
| 9.3 | Fraggnation setup VS Battlelog Setup: There are two ways that teams may request the setup of the battles: 1. Fraggednation: The FN way to setup the server is to have a burn round before the actual round of match play. This allows all 24 players to be in game, warm up and ready for the match to begin. So when the real round starts all 24 players should be in game and ready to play. The Burn round does not count in match play. Just to get your team and squads organized for the map. The server owned MUST make the other teams captain an admin to be in control of his side of the team. So he will be responsible to boot unwanted players of his own team. 2. Battlelog: Teams may request setup through battlelog. Using the BL roster must coincide with your FN roster or you will be in violation. Only FN roster members may participate in match play. You are not required to make any captain an admin as it will only allow invited members to participate in the match. It also already has a 15 min warmup grace period in which everyone has to click ready for the match to start. |
| 9.4 | Initial Round Start & Missing Players: If after being notified about player missing, before any kills has been made and the team hosting the map refuses to reset the server they will forfeit that map. Additionally, it is your responsibly to notify the other team about your team missing a player. Failure to do that before any kills has been made will result in this rule not being enforced To eliminate this problem, when playing on a ranked server a TDM burn round should be played as a warmup and to also ensure all players are in game and ready fot match play to begin. Remember the TDM does not count it is just a burn round to get everyone in game and ready so when the next map starts and match begins there is no need to wait to start as everyone should be ready to go. |
| 9.5 | Substitutions and Ineligibility: When creating a challenge your roster will be locked as soon as you send the challenge. Meaning anyone on your roster at the time of the challenge sent will be eligible for play. Anyone who joins your roster afterwards is not eligible. When accepting a challenge your roster will be locked as soon as you accept the challenge. Meaning anyone on your roster at the time of accepting the challenge will be eligible for play. Anyone who joins your roster afterwards is not eligible. |
Battlefield 3 Game Director(s)
BF3 PS3 Hardcore Ladder Head Admin(s)
Awarded By: ComeGetSome25
Season 1 1st Place Regular Season Winners and Season 1 Playoff Champions for the HC CQ ladder.
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.
