BF3 PS3 Hardcore Ladder
This ladder is for the best of the best in Hardcore mode for BF3 PS3 and soon on BF4. These teams will battle for being the best hardcore platoon in various game modes. We are bringing it old school when it comes to how to set up a challenge. Got two teams with at least 5 guys online, set up a DOM match that night and record the results afterwards! On the ladder but need help growing your team, get approval from the other team to allow players from another clan that isn't on fraggednation to play against you! Unless you think your clan isn't truly Hardcore, then I don't see a reason why you aren't on this ladder! See you on the battlefield!
Season Dates: 08-28-2013 - 09-30-2013
This ladder is Rung based
BF3 PS3 Hardcore Ladder
Posted by csjbccreager° on Sun, Dec 01 at 11:51am
THIS LADDER WILL BE CLOSED IN THE NEXT COUPLE WEEKS.
WELCOME TO THE BATTLEFIELD HARDCORE LADDER!
Season 3 has come to an end! We will not be hosting a Season 4 due to BF4 coming out. If someone is interested in hosting a Season 4 or even continuing a ladder on PS3 BF3, let the HA know via PM.
GSP Genetically Superior Players Season 3 regular season winners!!!!
CONGRATULATIONS TO: All teams that actually made an effort to battle this season!!
We will be starting a BF4 Ladder as soon as it's out and I'm hoping we'll be able to just transition this ladder at this time. HA will keep you posted!
The Match Finder is disabled for Rung-Based ladders. By it's very nature, rung-based ladders move players up by beating teams ranked higher - multiple challenges and hidden opponents is not conducive to this style of play. In order to use the Match finder, the ladder Owner/Admin will need to set the Ladder Type to ELO Point Based.
|Ladder Season:||08-28-2013 - 09-30-2013|
|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
|Ranking Type:||Rung Based|
|Challenge Map Selection:||Randomly Generated|
|Challenge Point/Rung Restriction:|
The number of Rungs, or Points, that a participant must be within to challenge another participant.
|Rounds Per Challenge:||3|
The type of data collected when reporting a Challenge
|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.
|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.
|Same Opponent Grace Period:|
The number of hours that must pass after reporting a match before the same opponent may be challenged again.
|Multiple Challenges at a Time?|
Specifies whether or not each participant may have more than 1 concurrent challenge pending at any given time.
Is this a 1v1, or a Team Ladder
|Yes, this is a 5v5 Team Ladder|
Whether or not this game require a unique ID registered in your profile to play.
|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|
|HARDCORE NO MAP||HARDCORE NO MAP 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|
|Server Type||* Ranked|
|Game Mode||* Conquest/Conquest Assault|
|Match Set Up||* Use Fraggednation ladder setup with burn round|
|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|
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:
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|
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|
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.
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.
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|
Teams must be actively challenging starting at the season's start date. Teams which are inactive over a two week time period may be set to inactive, at the Head Admin's discretion.
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.
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.
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.
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.
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.
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.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.
Certain rules such as "Glitching or Cheating" will cause a team to forfeit the game.
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 removed from the ladder.
|7.4||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 the match will be able to be played based on the reason a request for HA was made. Once they have made sure both teams content with the need for a HA, they will leave and match may begin.
When reporting a forfeit you must select the forefeit option when reporting the match. This will result in a support ticket being created. You do not report any wins/loses. It will be up to the HA assigned to the ticket to record the results after an investigation is completed. You should also comment the reason for the request in the comment area of the reporting section. This will help speed up the investigation.
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. This doesn't include the burn round. If the teams fails to provide a server within an additional 15 minutes of the first violation they will forfeit the second map and lose the match.
If the team does not gather the minimum players within the 15 minutes of the start of the match the team must either play with the players that they have or the other team can request a forfeit of the match. If the team agrees to stay, most likely the teams will be combined and teams getting mixed up at the start of the next round. Both teams must stay in the waiting pattern to allow admins to move players to the appropriate sides. You are not allowed to spawn into the game. This eliminates potential damage cause to vehicles if a player is moved that was sitting in it and eliminates the "definition" of what is consider a teams "spawning area".
Definition of less than minimum players
when the next round starts and teams are mixed up, if admins are unable to move all players do to the system indicating the sides would be unbalanced, then the match win goes to the team that had the appropriate amount to continue.
|8. Game Mode Scoring System|
Conquest and 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 win is determined when a team wins as both the Americans and Russians.
In the event both teams win a side, ticket count will be compared and the team which won by retaining more tickets, wins that map.
In the event both teams have the same number of retained tickets, the team that won the other map will get the win.
Points from each map do not carry over to next maps.
|8.2||Capture The Flag Scoring|
Working on it!
Working on it.
|9. Specific Ladder Rules|
Ladder Specific and Selectable Settings:
The goal of the following ladder rules modification we are making is to allow teams to set things up old school. If you have 5 players from your FN clan online and there is another team willing to accept your challenge, then set up a DOM match. This would go the same with as many as 12 players online and doing a CQ match. Just make sure both teams understand that a 5v5 on CQ probably isn't the right game mode.
Here is how it will work. Teams will communicate though PSN when setting up matches. Once agreed on the number of players and the game mode, you would then decide on the following options.
Agree to picking all 3 maps and starting right away
Agree to a time that will allow the match to be set up on FN
The time that you pick will have nothing to do with when you have agreed to battle. It's merely setting up the random maps that you must play. No exceptions!
Next step is to get a 3rd Party involved.
A 3rd Party is someone that both leaders have on their PSN friend list. This person must be online at the time the match is verbally agreed upon and we would prefer that they had a team on FN but we don't expect everyone to have everyone on their friend's list on PSN. At that time, both players must contact the 3rd Party and let them know all the details. Time it will be played is probably the most important and will be explained below. It is now the responsibility of that 3rd Party to reply to both leaders. In there reply, it must include all match details that were sent to them.
RECORDING SCHEDULED MATCHES THAT WERE ALREADY PLAYED AT A TIME PRIOR TO THE SET TIME ON THE FN CHALLENGE
Winning team must wait until after the time the match was officially set up on FN and would follow the rule around the timeframe to record results set up by FN.
If a team agrees to a match, gets the 3rd Party response, sets it up on FN but the other team doesn't accept the challenge most likely do to losing, then a support ticket must be created showing the 3rd Parties response to the winning player. No further correspondence is needed. HA will simply contact 3rd Party to confirm what information was provide. If 3rd Party confirms, a win will be given and the losing team will be warned. After the third warning, your team will be removed from the ladder.
RECORDING UNSCHEDULED MATCHES ON FN
Once the match is completed, the winning team has an hour after the completion of the match to send the official challenge on FN. The losing team has up to 2 hours prior to the official match set up to confirm the match. At which time, the winning team must report the win within the timeframe set forth in the FN rules.
If winning team doesn't send a challenge within the hour allotted, the losing team has an hour at that time to submit the challenge but with a win for them. Most likely this will result in a conflict. Simply submit a support ticket with proof that a 3rd Party was involved, the match had completed at such a time and that the "winning team" failed to record the match in the time allotted.
If the losing team fails to accept the challenge, a support ticket must be submitted showing proof from the 3rd Party that the match had actually be agreed upon. HA don't need any further proof than from the 3rd Party. That is why it is crucial to get them to reply with as much detail about the match as you can and more importantly why we need a 3rd Party involved.
Game Mode: CQ/CQA are priority but all other games modes will be approved as long as both teams agree. Playoffs will strictly be CQ/CQA with the possibility an additional Tourney set up with DOM to allow teams that still struggle to retain 12 players by the end of the season but are actively battling other teams under the new rules.
Server Type: Ranked
Team Size: 12v12 is preferred for CQ/CQA. Matches can be as small as 5 v 5 on DOM but this is meant to be an option for those teams that currently struggle putting together enough players for CQ/CQA.
All weapons are allowed because this is a HARDCORE ladder.
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.
This game is based on military 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 that may result in your vehicle(s) being "borrowed" by the other team.
Initial Round Start & Missing Players:
When playing on a ranked server a TDM burn round must be played as a warmup and to also ensure all players are in game and ready for the 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 will begin.
If setting up matches with less players than can be allowed into the server, both teams must have at least 1 player with admin rights. A maximum request of 2 admins may be allowed. If random players show up, it is both teams responsibility to remove that player. This is crucial because if a random achieves a total of 5 kills or deaths, that map side must be replayed or the match may not be recorded. This can be overruled if both teams agree.
Substitutions and Ineligibility:
When creating a challenge your roster will be locked as soon as you send the challenge or accept. 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 until the next match is set up.
Season 3 change
While setting up a match on PSN, as long as it is agreed upon between teams and the player added isn't on another team on FN, then they may be allowed into the match. One exception, they must have the appropriate clan tag on. There is ZERO exceptions to allow someone to play with a different tag.
The goal of this addition to the rules is to help small teams add players that may not feel they want to join a clan. This is not to allow teams to clan stack! We want teams to build so they can be prepared for BF4. If your team is caught "stacking", then you will be removed from the ladder.
Battlefield 3 Game Director(s)
BF3 PS3 Hardcore Ladder Head Admin(s)
Awarded By: csjbccreager
This award is in recognition of your teams effort to actually battle this season!
Awarded By: csjbccreager°
This award is in recognition of your teams effort to actually attempt to battle this season!
Awarded By: csjbccreager°
This award is in recognition of your teams effort to actually battle this season!
Awarded By: csjbccreager°
Congrats to Kelevra Competitive for being PS3 BF3 Hardcore Ladder Season 3 Runner-up!
Awarded By: csjbccreager°
Congrats to GSP for being PS3 BF3 Hardcore Ladder Season 3 winner!
Awarded By: csjbccreager°
Congrats to Seven for being PS3 BF3 Hardcore Ladder Season 2 playoff runner up!
Awarded By: csjbccreager°
Congrats to GSP for being BF3 PS3 Hardcore Ladder Season 2 regular season and playoff Champions!
Awarded By: ComeGetSome25
Fraggednation PS3 BF3 Season 1 Playoff Championship Runner Up
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.