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: Modern Warfare 3
XBOX MW3 Singles Ladder
Singles Season 3 ladder!! Sign up now!! Be ready for the new game!! Submit your gameplay videos to the FN Youtube channel 1. Download the FraggedNation intro and add it to the beginning of your video. Your video should go after the FN Intro video. - FN Intro Video DOWNLOAD HERE ** Download the Hauppauge Version of the video, if you recorded your gameplay using a Hauppauge HD PVR. This should be added to the outro of the video, or after your video. 2. Upload your completed video to your YouTube channel, set as private, and viewable only with link then send us a link to: videos@fraggednation.com **Ensure you include any information in the email that you want us to promote for you in the video.
Season Dates: 05-17-2012 - 08-18-2012
This ladder is Point based
Season 3 Started!
Posted by Stonez
on Wed, May 09 at 07:24am
All,
There is a SteelSeries Singles tournament Bracket that are now taking signups.
The Poster for this is here
http://www.fraggednation.com/content.php?k=SteelSeries_MW3_Tournament
To join the NA ladder its here
http://www.fraggednation.com/tournament.php?tID=4656
To join the EU ladder go here
http://www.fraggednation.com/tournament.php?tID=4699
And last but not least for any questions go to the forums here
http://www.fraggednation.com/forum/topics/game-general/MW3-SteelSeries-206
Good Luck to all teams playing
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-17-2012 - 08-18-2012 |
| 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 | 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. | 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 | No, this is a 1v1 singles 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: |
| Join in progress | Not Allowed |
| Spectating | Team Only |
| Game Type | Team DeathMatch |
| Party Settings | Closed |
| Game Recording | Enabled |
| Score Limit | 5000 |
| Time Limit | 10 Minutes |
| Respawn Delay | None |
| Force Respawn | Enabled |
| Killcam | Enabled |
| KillStreaks | Disabled |
| 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: (*) |
| Game Type | * HardCore |
| 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. Admin Assignment | |
| 3.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. |
| 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 | 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:
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. |
| 4.4 | 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. 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.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. 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 | 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. |
| 5.7 | 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.8 | Hosting Challenging or Top Seeded team will have choice of host on map #2. Challenged or Bottom Seeded team will have choice of host on maps #1 and #3. This means that the CHALLENGED team is responsible for start of game invites for the opposing team to join lobby in ladders. This means that the TOP SEEDED team is responsible for start of game invites for the opposing team to join lobby in tournaments |
| 6. Class Restrictions | |
| 6.1 | Banned Weapons (Primary or Secondary) All Launchers Banned Lethal N/A Banned Perks N/A Banned Strike Packages None (Killstreaks are banned) Banned Death Streaks Revenge Final Stand Martyrdom Dead Man's Hand Banned Proficiency 2 Attachments Banned Attachments Grenade Launcher Shotgun Heartbeat Sensor |
| 7. Ladder Settings | |
| 7.1 | Maps Seatown Dome Arkaden Bootleg Carbon Lockdown Underground |
| 7.2 | All Game Modes (Options) Settings to be updated January 6, 2012 waiting on polls |
COD: Modern Warfare 3 Game Director(s)
XBOX MW3 Singles Ladder Head Admin(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!
°
°
°