Assassin Creed Revelations
Assassin's Creed: Brotherhood
Battlefield 3
COD: Black Ops
COD: Modern Warfare 3
Dirt 3
FIFA 12
Forza Motorsport 4
Gears of War 3
Ghost Recon Future Soldier
Halo Reach
Madden NFL 12
Marvel vs Capcom 3
MLB 2K11
Mortal Kombat
NHL 12
Street Fighter x Tekken
Super Street Fighter 4
Tekken 6
Starhawk
Uncharted 3
BF: Bad Company 2
Counter-Strike: Global Offensive
Halo Combat Evolved
League of Legends
Minecraft
Nexuiz
Quake III
Quake Live
StarCraft II
Team Fortress 2
Tribes Ascend
Unreal Tournament 99
FEAR 3
Homefront
Mario Kart
COD: Black Ops
PS3 COD Black Ops Team Ladder
Summer Season 2010
Season Dates: 05-10-2011 - 08-19-2011
This ladder is Point based
Input Needed
Posted by Quanicuffs
on Sun, Apr 10 at 10:37am
Please Tell Use About Your Experience and Share any Input You May Have
http://www.fraggednation.com/forum.php?action=showPosts&topicID=17174&startPos=0
Invite someone to Join this Ladder
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: | 05-10-2011 - 08-19-2011 |
| 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 | 3 |
| Ranking Type: | Point 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. | 0 |
| Rounds Per Challenge: | 3 |
| Reporting Type: The type of data collected when reporting a Challenge | Score Entry |
| Matches Require a Referee? | Yes |
| Challenge Out Hours: The minimum numbers of hours from the current time to which a challenge date may be specified. | 3 |
| 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. | 3 |
| 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. | 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: |
| Specific Game Type Settings Depend on Selection of Game Modes | Must be set up accordding to rules |
| Hardcore Mode | Depends Team Decision in Challenge Menu |
| Allow Killcam | Enabled |
| Headshots Only | Disabled |
| Allow Sprint | Enable |
| Force Respawn | Enable |
| Wave Spawn Delay | None |
| Max Health | None |
| Health Regeneration | Normal |
| Spectating | Team Only |
| Friendly Fire | Enable |
| Class Editor | Allow Player Classes |
| Perk Editor | Allow Perks |
| Game Recording | Enable |
| 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: (*) |
| Allow Kill Streaks | * Yes No |
| Team Size | * 3v3 4v4 5v5 6v6 7v7 8v8 |
| Game mode for map 1 | * Teamdeath Match CTF Domination Search and Destroy |
| Game mode for map 2 | * Teamdeath Match CTF Dominition Search and Destroy |
| Game mode for map 3 | * Teamdeath Match CTF Domination Search and Destroy |
| Hard Core Mode | * Core Hardcore |
| Equipment | * Yes No |
| 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. Referee Assignment | |
| 3.1 | Referee Assignment A Referee will
only be assigned to a match if they are requested by a Team Captain or
FN Admin. Requests must be made by submitting a support ticket at least
24 hours prior to the scheduled match time. The referee request must
include the ladder, match ID, date, and teams playing. If a ref 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. |
| 4. Match Issues | |
| 4.1 | Referee Calls If a player disagrees
with a Referee's call, they must submit a support ticket. Challenging a
call made by the Ref should NEVER be done DURING the match. Should any
player attempt to argue with the Ref mid-match, they will be subject to
penalties at the Ref's & Head Admin's discretion. Each
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 Included in the support ticket must be UNEDITED video as proof. If a team member or host dashboards on a map or there is no video for us to review, the match may be awarded to the other team. |
| 5. Playing Matches | |
| 5.1 | Challenges Teams/Players
may only issue ten challenges per one week period, starting at the
season's start date. Teams/Players exceeding ten challenges will have
the extra challenges removed, and will be subject to penalties. |
| 5.2 | 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. |
| 5.3 | 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. |
| 5.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. |
| 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. Lag tests must be conducted on a map not scheduled
for play in that match. |
| 5.6 | 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. |
| 6. Agreements | |
| 6.1 | By signing up to this ladder you agree to all Rules attached to this ladder and failure to comply would be subject to disciplinary action. Also you agree we have the right to contact you by email. |
| 7. Match Settings | |
| 7.1 |  Team Death Match has all regular settings Except time limit is unlimited.Capture the Flag
· Domination
· Search and Destroy
|
| 7.2 | The game modes are agreed upon by both teams in the challenge management area. |
| 7.3 | If any of the above settings are incorrect, the hosting player
forfeits that map. The hosting player is responsible to ensure all
setting are correct prior to beginning any map. If the settings are
incorrect, the map needs to end and the next map needs to be played. The
player that was not hosting is responsible for obtaining valid proof to
show that the hosting player did not have the settings correct. A
ticket with valid proof must be submitted immediately after the match
has been completed. |
| 8. Ladder Maps | |
| 8.1 | All matches must be played on the maps generated. No agreement between teams can be made to change maps because they don't like the maps generated. Any teams found making such deals will be subject to disiplinary action |
| 8.2 | If you feel strongly that a map does not have a feesable space in the ladder please raise your concerns in the designated thread set up by the Head Admin |
| 8.3 | If you are unhappy with a particular map on a ladder, be sure to go and rate the map via the Standings page. Click the Detail tab, then the Maps tab to see a list of maps. The option to rate a map or leave a comment is displayed in the list. |
| 9. Support Ticket | |
| 9.1 | In the event of any of the rules outlined in sections 1-6 are broken a support ticket must be submitted. All
issues are solved via the Ticket System and staff have been instructed
not to discuss personal issues or situations outside the ticket system.
Under no circumstances must you ask a member of staff for information
regarding a matter. Please monitor your ticket and you will receive your
reply there |
| 9.2 | Support Tickets must only be used for: - Match Issues - Site Issues - Member Or Team Issues - Ladder Questions Any other issues you may contact the Staff via PM Or FraggedNation Chat. Any member found abusing the Ticket System will be subject to Disciplinary action |
| 9.3 | Support Tickets are handled by our Staff so please use user friendly language and provide solid evidence if necessary. Remember it is a support ticket give us all the information not half the story. We can only help what we see. |
| 9.4 | Providing Details When a team/player
submits a support ticket it needs to be for a specific issue and
detailed so the admins can effectively address your problem.Only
specific problems are addressed in a support ticket. If you fill out a
support ticket that is vague on details, the admin will respond back to
you asking for clarification and further details such as: Which player broke the rule. What map was the issue in. About how far into the map was the rule broken (it is preferred if you can give the exact time on the timer). A screenshot or unedited video recording of the incident. If
you submit a support ticket over a call a ref made please provide which
call, which player, what map and when in the map. A support ticket will
not open a whole match up for review, only for the specific issue the
team is asking to be addressed. |
| 9.5 | Submitting Support Tickets Only team
captains can submit a support ticket for an admin to review a ladder
match. In the case of 1 vs 1 ladders all players have the option of
submitting a support ticket. Please do not contact a staff member
directly regarding your support ticket. We assure you it will be
answered in a timely manner. If a match is disputed, and no proof is provided by either team, the match may be deleted. Please include the match ID when submitting a support ticket. |
| 9.6 | Proof It is highly suggested that at least
one member per team provides evidence in the form of a Video or
Screenshot so if any situations occur regarding results you will have
solid evidence to back you up. It is suggested a
screenshot is taken after the results of every round although the most
advisable method is to record every round. Please attach any links to such proof on your support ticket and not via PM. |
| 9.7 | All Tickets are handled to the best of our ability. If you feel the outcome of the Ticket was incorrect please re-submit your Ticket although please note If you consistently flame admins with the same ticket over and over again until you get your result you will be expelled from the ladder. |
| 9.8 | Admins and Staff are neutral towards all Tickets submitted We act on a professional basis and therefore all friendship and emotions are left behind when we decide to work here. Please do not insult an Admin's decision just because it didn't go your way. Also our Admins accept no type of bribe |
| 10. Forfeits | |
| 10.1 | This ladder allows you to select the team size for your match. |
| 10.2 | If a team does not have the required amount of players the team that does have the required amount of players may submit a forfeit request. |
COD: Black Ops Game Director(s)
PS3 COD Black Ops Team Ladder Head Admin(s)
PS3 COD Black Ops Team Ladder Ladder Referee's
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.
Ladder Membership Status
ShoutBox!
