| Staff |
|---|
| 1.1 | Ladder Committee:
This Committee is made up of all the Game Admins and Head Admins for each game type. You can see the Global, Game, and Head Admins for each ladder by clicking the Staff/Admins link under "Contact" in the main menu.
All rules, mutators, mods, settings and maps will be decided upon as a group by the committee for each ladder, as well as community feedback from the forums. Once changes are opened for discussion the topic will be posted on a forum and discussed with the input of anyone in the community that wishes to voice their opinions. Poll rules are as stated in the poll itself, and/or pre-described by the Admin via email announcement.
| | 1.2 | Chain of Command:
Please do your best to filter all questions or problems through your Head Admin before contacting a Game or Global Admin. Head Admins are in place to handle situations specific to each ladder and often will have more insight into a proper course of action. If the Head Admin is unable to help then you may escalate to the Game Admin. Remember to specify which ladder you are referring to when you are asking questions or making suggestions.
| | 1.3 | Competitors' problems with a Staff member:
Game & Head Admins assign Staff at their discretion. Should you disagree with a Staff member being part of a ladder please contest to the Head Admin.
| | 1.4 | Staff contact info
You can view all Staff from the Staff/Admins contacts link in the main menu. Here ALL CONTACT information for your Admins can be found, as well as Community Staffers who are not specifically associated with ladders (Web deveolpment, Public Relations, etc...)
| | 1.5 | Trouble Tickets:
Game/Head/Global Admins very graciously list their IM accounts in their profiles. However it is unacceptable & inefficient to bombard these people with questions when they get online. The trouble ticket system is in place to help assign problems to the proper Admin so that they can handle the situation at their convenience. Please use this system so that we may track the progress of problems, and ensure our Admins are doing their jobs.
Trouble tickets are found under "My Account">>>"Account Home".
|
|
| |
| General Ladder Rules |
|---|
| 2.1 | FIGHTING & MISCONDUCT:
Will not be tolerated. Period.
If there is a problem with another team please contact the Ladder Admin or Game Admin to have it resolved. Any bad mouthing or trash talk can result in that person and/or their team being banned from the Ladder.
| | 2.2 | CHEATING:
Will not be tolerated. Any team caught cheating will be banned from FraggedNation immediately. Period.
FraggedNation enforces Zero Tolerance with regard to past known cheaters. If there is evidence presented, or the community is threatened by the presense of a cheater, they will be banned - no exceptions. We strive to make FraggedNation a level grounded place for everyone to play, and the comfort of the participants is our primary concern.
Should you find yourself banned from FraggedNation competition, we always encourage you to attempt to get community support to return to the fray. If there is enough support to bring a player back, we will consider it - however we will not extend our services or use our staff to propagate such a return as we feel this is not in the best interest of FraggedNation nor a proper use of resources.
| | 2.3 | HACKS:
FraggedNation enforces ZERO TOLERANCE on hacks. Any hack found in use will result in the player and/or team being banned from competition.
| | 2.4 | MAP FLAWS:
ANY exploitation of a map flaw without reporting it to an Admin is grounds for disqualification and removal from ladder & tournament competition. | | 2.5 | REPEAT OFFENDERS:
Who have been punished, but not banned, will be removed from ladder & tournaments, and subsequently banned from FraggedNation.
Failure to follow these simple rules will result in disqualification of players & teams from competition. | | 2.6 | Ladder Ref Abuse:
Under NO circumstances should the Ref EVER be abused for making a call. If a Ref is harassed in this manner, the player at fault will be penalized HARSHLY. Repeat offenders will be removed from competition. Please see the section regarding "Challenging a Call" for more information on the proper way to handle these situations.
| | 2.7 | Spectators:
The ONLY people allowed on a server during any ladder or tournament matches are those competing in said match, and appropriate Refs or Admins needed for play.
Players and specs not adhering to this rule will be penalized with, but not limited to:
Replaying of maps that specs were watching, regardless of outcome.
Disqualification of match, and forfeits handed out.
Suspension of player account and ladder or tournament membership/participation.
Banishment from FraggedNation.com
| | 2.8 | Ladder Membership / Account Activity:
Your ladder membership will be automatically disabled if you do not participate in at least one (1) match PER MONTH. Furthermore your account will be automatically disabled if you have received 3 consecutive forfeits against you.
This is done each night at midnight. If your account is disabled, you may re-enable at any time, however it will continue to be disabled each night until you have played a match. | | 2.9 | Ladder / Tournament / Game Specific Rules:
If a rule is not posted in the General Rules section (what you are reading right now), or not in the specific rules for the game / ladder / tournament, then the rule can not, and will not, be enforced.
Only rules that are clearly defined in the rules sections for that particular game / ladder / tournament will ever be considered rules that must be adhered to.
Conversations in the forums or other such medium shall never, under any circumstances, consitute a rule. |
|
| |
| Times and Matches |
|---|
| 3.1 | The challenging team selects 3 Date/Time combinations when making the challenge. The Challenged team must accept one of these times, or forfeit the match.
No one wants forfeits (wins or loses), so use the Change Request system. It is to your advantage.
Change Requests are described in Section 13.
| | 3.2 | All matches will be played on FraggedNation sanctioned servers which have been defined by the Head Admin for each ladder.
If you would like your server, or your teams server to be listed, please contact them.
The exception to this rule is ladders that have been setup to allow 3rd party servers as selection. You will know if the ladder is eligible for this when you attempt to challenge. | | 3.3 | Once a challenge has been made and accepted, all players involved will receive an email with the randomly generated maps, or the team/player's map selections, and any Admins assigned to the match (team ladders requiring Ref only).
| | 3.4 | In the event a team does not show at the selected time and server within 10 minutes, 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 on the same server, both teams will receive forfeit.
Please ensure there are no other matches scheduled on that server before waiting additional time. | | 3.5 | All ladder matches are played in a "Best Of" format. Most ladders are set to 3 rounds which is best of 3. The winner is the team who takes the match in "Best Of 3 - Win 2 maps".
Tournaments may vary. Head Admins will prescribe match & tournament format prior to launching.
| | 3.6 | Random map generation vs Player/Team selectable:
Random: All maps are generated at the time of challenge using a random selection algorithm.
Selectable: Players/Teams on "selectable maps" ladders are as follows:
Challenging team chooses map #1.
Challenged team chooses map #2
Map #3 is randomly selected (using the random algorithm described above).
| | 3.7 | Either winner or loser of a match may report once the match is completed.
Both players/teams, apon either reporting the match, are then programatically restricted from re-challenging any other player/team for a period of ~1 hour.
|
|
| |
| Challenging and Accepting |
|---|
| 4.1 | Any team may challenge another team if:
- The team being challenged is within the challenge point restriction threshold for point based ladders, or within the rung restriction and ranked higher in the standings for rung-based. You may not challenge DOWN in rung based ladders
- You do not have a pending challenge
- The player/team you are challenging does not have a pending challenge
- The player/team you are challenging is NOT the same account that you played in the most prior match unless the ladder is rung based
- You have rejoined the ladder from inactivty and waited 24 hours (applies only if you have deactivated, then re-activated yourself)
- Your most recent match has been reported no less than an hour prior
Note that near the end of a season you might find yourself locked out from being able to challenge because there are too few days left in the season to select 3 different date/time combinations. | | 4.2 | To Challenge another team:
- Click the 'Challenge' icon next to the team in the Ladder Standings OR view the team profile by clicking the team and locating the challenge button
- Select a Server
- Select 3 Date/Times
- Choose Map #1 (if ladder is set to player-selected maps)
- Submit the challenge
The system will enforce the earliest possible challenge time by disallowing the selection of date/times that are earlier than allowed. For most ladders this is 72 hours out from current time unless otherwise specified.
| | 4.3 | To Accept a Challenge:
In your Account Menu click the ladder with a corresponding Pending Challenge.
- Click 'Respond' to the challenge.
- Accept Challenge on one of the 3 Date/Times listed.
You MUST RESPOND TO A CHALLENGE WITHIN 48 HOURS OR RECEIVE FORFEIT!
If none of the times are good for you/your team, accept the challenge and immediately use the Change Request system to work with your opposition. IM/PM/email/Change Request the opposition, and include your Head Admin.
Get those matches played!
| | 4.4 | Declining a Challenge:
In the event your team wishes to decline a challenge, you may do so by clicking 'Decline' from the respond menu. You/your team will receive a forfeit loss upon declining.
| | 4.5 | Ladder Challenge Point Restriction:
Each ladder has a pre-defined value for the amount of points that equates to the difference in points between yourself and the opponent you wish to challenge. You will be unable to challenge someone if the distance between point values is greater than the value specified for the ladder. You may view the current point restriction for your ladder by looking in the ladder details on the right side of the screen, next to the ladder standings.
In the instance of Rung-Based ladders, the point restriction is replaced with a rung restriction whereby you may only challenge up X rungs, and never challenge DOWN.
|
|
| |
| Offset Point Scoring (Deprecated; For reference only!) |
|---|
| 5.1 | NOTE: AS OF 10/31/05 ALL NEW LADDERS AND RESTARTING LADDERS WILL MIGRATE TO ELO POINT SYSTEM.
The point system outlined below is for REFERENCE ONLY on ladders that have yet to convert
------------------------
All ladders will be scored using the same algorithm to derive points for each match played. Furthermore, each ladder has with it a few associated static point values. These values vary for each ladder:
A)Points for Win
B)Points for Forfeit
C)Points for 2 Round Win bonus
Lets assume the following example for ladder ABC:
*** NOTE: THESE VALUES ARE EXAMPLES AND VARY FROM LADDER TO LADDER ***
Points for Win: 100
Points for winning in 2 rounds: 50
A match is played between teams A and B. This is the outcome:
Offset Scoring Mechanism:
While points are calculated using the above formula, the overal position on the ladder is calculated using an offset formula so as not to award the most active players, but rather the most consistent. The formula is as follows:
OffsetPoints = (YourPoints * (100 + (100-((YourMatches/MostMatchesPlayed)*100))))/100
Round 1:
Team A: 5
Team B: 2
Round 2:
Team A: 3
Team B: 1
Team A would get 100 points for the win, and then a bonus of 50 points for winning in 2 rounds.
Team B would receive points following this schedule:
(Combined Loser Points / Combined Winner Points) * Ladder Win Points
So Team B would get the following:
( 3 / 8 ) * 100 = 38 points (rounded up)
Final Scores:
Team A: 150 pts
Team B: 38 pts
This method allows the loser to walk away with what they have earned over the course of the match.
In the rare instance that the loser actually out-scores the winner in total points, they will retain the calculated value unless the ladder is specifically set to cap the losers points. This is different for each ladder and can be seen from the Ladder Information page in the navigation to your left. If the ladder is set to cap the score of the loser, they will receive the ladder win point value minus 1. So in the example shown above the loser would get 99 points if they out-scored the winner, and the winner would get 100 points.
Offset Scoring Mechanism:
While points are calculated using the above formula, the overal position on the ladder is calculated using an offset formula so as not to award the most active players, but rather the most consistent. The formula is as follows:
OffsetPoints = (YourPoints * (100 + (100-((YourMatches/MostMatchesPlayed)*100))))/100
| | 5.2 | Ladder Penalties:
Certain ladders have pre-defined values for penalties that have been decided on by the Head Admins. Be sure to check the ladder specific rules for the ladder you are participating on to get familiar with the penalties you will need to watch out for, and the amount of points each offense will cost you.
| | 5.3 | Warnings & Penalties
When Refs need to assign Warnings &/or Penalties, the Ref will 'Spam' the chatbox with the warning as many times as are needed to produce a "Recognition" reply from the Warned/Penalized team.
ie;
"Team A Flag camping" or "Player A Flag Camping" "First Warning"
"Team A Spawn Killing First Penalty", "Team B Foulmouth Taunting Penalty"
The Warned/Penalized team then has to respond to the Warning/Peanlty with their "Recognition";
"OK, Ref", or "Received Ref" until the Ref responds back "OK" so that all parties involved understand a Warning/Penalty has been assigned. This should happen as quickly as possible, to limit match disruption.
The Ref must be Warning/Penalty specific in their spam.
If the Warned/Penalized team does NOT respond wihtin 20 spams or 10 seconds, the first Warning/Penalty will be assigned, and a second Warning/Penalty will be spammed, pending 2nd offense/awaiting 2nd Recognition. Escalating to maximum Penalties allowed.
Preferably the Warned/Penalized player or team Captain should respond to the Ref, but any player on the Warned/Penalized team can reply with their "Recognition".
|
|
| |
| Ladder Seasons |
|---|
| 6.1 | FraggedNation ladders will run for periods pre-determined by Game & Head Admins. Each ladder has a start and end date that is visible in the ladder or tournament's details. These dates are listed to the right of a ladder's standings.
At the end of the season, the team with the highest point rating, or in the #1 rung will be declared the winner of that season.
All ladder data will be reset at the end of the season except for teams and members. All win/loss record, etc. will start fresh.
If there are any prizes to be awarded you will be notified should you be the winner at the end of a season.
| | 6.2 | Private ladders run without seasons (indefinitely) but may be reset by the ladder owner at any time, at their discretion. |
|
| |
| Ladder Maps |
|---|
| 7.1 | Maps are selected one of two ways at FraggedNation and depends on the setup of the ladder.
1. Maps are auto-generated by the system. All maps (depending on number of rounds) are automatically selected and assigned to the challenge with no user input.
2. Maps are picked by a combination of the system, the challenger, and the challenged. When making the challenge, the challenger will pick the first map. The challenged will pick the second map when accepting the challenge. The system will auto-generate a tie-breaker third map.
Please contact your Head Admin if you have questions about map selection.
| | 7.2 | All matches must be played on the maps that were generated. In the event players/teams are caught in a match be playing on a map that was NOT specified in the challenge, both players/teams will be disqualified and possibly removed from ladder competition. | | 7.3 | Should a map NOT be available on a server at match time, players/teams may agree on a different map to play in the current list of maps for that ladder that are available on that server. UNDER NO CIRCUMSTANCES should this occur if the map specified in the challenge details is available for selection. See ladder specific rules regarding penalty points.
| | 7.4 | Map lists will not be changed mid season. Once a map has been selected for the ladder, it cannot be removed. Likewise, additional maps will not be considered until the season has ended. Some ladders may have additional rules for maps which also need to be followed. |
|
| |
| Ladder Servers |
|---|
| 8.1 | For 1v1 matches:
Any and all servers listed as a selection for the 1v1 ladders will have at least 1 accompanying Admin on the Ref roster. It is your responsibility as both the challenger and challengee to ensure that an Admin is present should the need arise. Admins on 1v1 ladders are not assigned to matches and therefore have no way of knowing they are needed unless contacted specifically.
| | 8.2 | For Team Matches:
Your Head Admins will do the best they can to ensure the Admin/Ref assigned to your match has Admin priveleges or is at least in contact with an admin for the server selected. If you feel that the Admin assigned to your match does not have the ability to administer the server selected, please contact the Head Admin and voice your concerns.
| | 8.3 | Matches that Require a Ref:
You are not permitted to play and report that match unless the Ref is present for all maps played. If any team plays a match without a Ref this match is null and void. In the event the match starts without a Ref do not play the match until one is present. In the event a Ref should disconnect and not return right away, both teams should stop playing and contact an Admin right away.
| | 8.4 | Server Settings:
It is important as both the challenger and challengee to ensure that the server is running the proper configuration before starting the match, and certainly before reporting the match.
In the event you notice a server needs modification, it is your responsibility to notify an Admin to correct the situation BEFORE MATCH TIME. All servers are run by different admins, so there is a possibility there may need to be a change.
|
|
| |
| Forfeits |
|---|
| 9.1 | All forfeits require Admin approval. Once submitted, your Head Admin will receive an email notifying them that there is a forfeit request to process. Please be patient with your Head Admins on weekends, when they may not be checking their emails.
Please note that for forfeit requests on matches for failure to respond, while the forfeit is pending approval, the challenged team may still accept the challenge. Should the team accept the challenge before the Head Admin approves the forfeit, the challenge is considered to be final. This helps us ensure that there is no wasted time, and that more matches are able to be played than forfeits awarded.
| | 9.2 | Should you receive a forfeit that you feel was not justified, please contact your Head Admin as soon as possible with all email and/or chatlog correspondance with your opponent. Without proof, your Head Admin will be left with no choice but to let the forfeit stand. | | 9.3 | All forfeit wins are 1/2 normal ladder win value. Exception to this is explained below in the Change Request Incentive program. | | 9.4 | Change Request Incentive:
In the event a forfeit is necessary, a 50% point incentive will be added to the win automatically if a Change Request has been submitted and accepted by either team. This ensures that at least one attempt has been made to get the match played before resorting to a forfeit.
In the event the challenge is DECLINED (not accepted) the team challenging will always receive 100% win value.
| | 9.5 | Holiday Forfeit Procedure:
In observance of holidays, we will not be processing forfeit requests that are put in for matches scheduled to be played on the date of any recognized US, Canadian, or European holiday. This includes but may not be limited to.
US Holidays:
Thanksgiving day
Memorial Day
Independance Day
Labor Day
Canadian Holidays:
Victoria Day
Canada Day
Labor Day
Thanksgiving Day
Boxing Day
Euro Holidays:
Three Holy Kings Day
Ascension Day
General Holidays:
Christmas Eve/Day
Christmas Day
New Years Eve/Day
New Years Day
Good Friday
Easter Sunday
Easter Monday
In the event that a match has been scheduled to be played on a holiday, we encourage both teams to use the change request option to reschedule the match. If a new date is not able to be worked out, then the challenge will be deleted without penalties to either team.
|
|
| |
| Teams and Rosters |
|---|
| 10.1 | 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. | | 10.2 | You may rotate any eligible member of your roster for play at the beginning of any round. | | 10.3 | You may NOT switch a team member DURING a round of play, unless a specific Ladder's own rules permit, persuant to appropriate circumstances. | | 10.4 | You may substitute 1 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 2 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.
| | 10.5 | You may NOT under ANY CIRCUMSTANCES substitute a non-roster player for play in a ladder match. Should your team not have enough people showing at the match, you will be forced to take a forfeit loss. | | 10.6 | 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.
| | 10.7 | Teams may have no more than 4 captains - this is enforced programatically. | | 10.8 | Players may only compete on ONE Team per Team Ladder, and ONE 'rung' per 1v1 Ladder. |
|
| |
| Challenging a Refs Call |
|---|
| 11.1 | If you wish to have a match reviewed or a specific call reviewed you must submit a request via the Trouble Ticket system to a Head Admin or Game Admin. You must submit the following information when putting in an official trouble ticket challenging a refs call:
1: Match date, time, and ladder.
2: The name of the Ref who was assigned to the match in question.
3: What exactly you wish to have reviewed.
Be patient and wait for the ADMIN to contact you with the results of the review. Once this process is finsihed do not contest
the ADMINS decision. Doing so will result in misconduct penalty.
If you do not follow the procedure listed above you risk losing a challenge for that season. | | 11.2 | Refs are required to keep a demo from each match they Ref if there is the possibility of a call-turnover. These Demos must be saved for 1 week after which time they may be discarded if an Admin doesnt request them. | | 11.3 | 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.
(Example) Team A challenges a flag camping call made against them. They have all 5 of their challenges available. If the Admin oveturns the Ref's call after reviewing the match, then that team keeps all 5 of their challenges.
If the Admin does not overturn the call, the challenging team loses the decision. Team A will lose 1 challenge and will have 4 challenges remaining for the season.
Admins will be noting in the team notes sections when a challenge has been used.
| | 11.4 | Teams or players are NEVER to bother Refs or Admins about a Ref's decision unless they are making an official penalty challenge. Disregard for this rule will result in a penalty, assigned by the appropriate Game Admin.
| | 11.5 | Once your team runs out of challenges you will not receive any more until the ladder resets for the next season. If you use your challenges wisely, you should not run out.
| | 11.6 | 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 persuant to the specific ladder's penalty point guidelines.
|
|
| |
| Ringing / Name Swapping |
|---|
| 12.1 | Players shall have only one account under the player's name used in the community most frequently. This will be enforced programatically by IP. Any duplicate entries will be reported to the head admins at 12:01 on the day of account creation via scheduled task. Players will only compete under the one account, and under the one name. Changing names for any reason, or playing under any other name could result in permanent banishment from ladder competition pending the situation. | | 12.2 | Under NO circumstances will one player play AS another player for a scheduled official ladder match. In the event someone is found to be doing this (hereby referred to as ringing) they will be banned immediately from 1v1 play until the following season, and penalized 3 team matches on EACH ladder they are a participant of. | | 12.3 | If you feel you have competed against someone ringing for an official ladder match, please inform an Admin so they can do a check of the server logs for IP addresses, and subsequent investigation. This needs to be done ASAP, to have the best & most current info available.
| | 12.4 | If a player is banned for misconduct for any reason and attempts to rejoin the ladders for competition until said ban is finished, it will result in a permanent IP level ban. | | 12.5 | If a banned player is a team captain, they will be forced to add another captain to the roster and have themselves removed. Failure to do this could result in the team being removed from play until the situation is resolved. | | 12.6 | In the event the same household / IP has 2 players (such as siblings or spouces) please notify a Head Admin of the situation to ensure the account does not get deleted.
|
|
| |
| CHANGE REQUESTS |
|---|
| 13.1 | 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.
Please be sure to review the Change Request Incentive program outlined in the section of these rules entitiled Forfeits |
|
| |
| Reporting a Match |
|---|
| 14.1 | If you have won or lost a match, you have 4 hours from match end to report the loss. Failure to do so could result in a forfeit or penalties assessed by the Head Admin at their discretion.
| | 14.2 | EITHER team may report the match at any time after the specified date and time. | | 14.3 | Continued failure to report matches on time could warrant dismissal from the current ladder at the discretion of the Head Admin. | | 14.4 | Even if the match is potentially subject to review and / or challenge, the match MUST BE REPORTED. In the event something needs to be reversed, it will be done by the Admins at the time of such decision. Not reporting a match because of the possibility of an Admin decision is expressly forbidden, and could leave you/your team subject to penalties specific to each ladder.
|
|
| |
| Player GUIDs |
|---|
| 15.1 | Entering your GUID on FraggedNation:
[*] Move mouse pointer over My FraggedNation
[*] Click on My Account
[*] Click on Manage GUIDs
[*] Enter the last 8 characters of your GUID
[*] Select game in the dropdown list
[*] Click + Add New
[*] Repeat the above 3 steps to add your GUID to more than one game.
Note:
There is no seperate area to enter your GUID for add-on games such as PoE for Vietnam or United Offensive for Call of Duty. To add GUIDs for these games, simply add another entry for the parent game. | | 15.2 | Player GUIDs are required on a per-game basis. If you do not have a GUID entered for a particular game, you will be notified when attempting to join a ladder. GUIDs can be quickly and easily added to your account. |
|
| |
| ELO Point System |
|---|
| 16.1 | OVERVIEW
Players gain
rating points for each win, and lose rating points for each loss. Because ratings take into account not only the
number of wins and losses but also the skill of each opponent, they are a useful measure of the true skill level
of a player.
The rating system used is the same Elo rating system that is used in competitive chess, golf, and
tennis. The Elo rating is a scientific model which provides a meaningful way to compare the skill level of different
players, based on the assumption that skill levels follow a normal bell curve.
This web page provides an overview of how the rating system works, and how
FraggedNation.com maintains its ladders.
PROBABILITY OF WINNING
The probability of each player winning a ladder game is computed based on that
player's rating and the ratings of each of the player or team he is playing
against. This probability is used to determine how many rating points the player
wins or loses for winning or losing the game. A player who wins against a much
higher rated player will gain many points for the victory, while a player who
wins against a much lower rated player will gain very few points.
The following formula is used to compute the
probability of winning:
Probability = 1 / (1 + 10^(-difference_in_ratings / 400))
You can use the following charts to quickly estimate your probability of winning against another opponent:
When playing a HIGHER rated player:
|
When playing a LOWER rated player:
|
Rating Difference
|
Probability of Winning
|
Rating Difference
|
Probability of Winning
|
400
|
9.1%
|
0
|
50%
|
350
|
11.8%
|
50
|
57.1%
|
300
|
15.1%
|
100
|
64%
|
250
|
19.2%
|
150
|
70.3%
|
200
|
24%
|
200
|
76%
|
150
|
29.7%
|
250
|
80.8%
|
100
|
36%
|
300
|
84.9%
|
50
|
42%
|
350
|
88.2%
|
0
|
50%
|
400
|
90.9% |
Each player is assigned a development coefficient (K), which determines the maximum
number of rating points that can be won or lost in any one game. The development coefficient
starts at 50 and then drops lower as the player becomes more experienced. This enables new
players to move quickly towards a rating that reflects their true ability level, while adding
a level of stability to the ratings of more experienced players.
The development coefficient is calculated according to the following rules:
- K=50 for new players
- K=30 for players who have played 15 or more ladder games
- K=20 for players who have played 30 or more
ladder games
Each player who completes a ladder game wins or loses points according to the following formulas:
- Winner's rating increases by K * (100% - probability_of_winning)
- Loser's rating decreases by K * probability_of_winning
All players start out each season with a rating of 1000
Forfeits are assessed as a loss and points are awarded as if the match had been played and lost to both winner and loser.
|
|
| |
| Private Ladders |
|---|
| 17.1 | Private ladders are "owned" by an individual and will require a password to join. To obtain this password you will need to get in contact with the owner. You may bypass this join password if an invitation to the ladder has been extended to you by the owner through the invitation process. |
|
| |
Online Chat 
= Donating Member, 
= Clan Owners, 
= Clan Members
, [DBU]Wrath