General Rules

1. 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, Platform Directors, Game Directors, and Head Admins for each ladder by clicking the Staff/Admins link under "Staff" 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	Teams or players are NEVER to badger Refs or Admins about a decision unless they are making an official penalty challenge or complaint. In this case only the site support ticket system should be used. Disregard for this rule can and will result in a site wide suspension.. This includes badgering an Admin through their personal instant Messaging accounts or the site personal message system.
1.6	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 support 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. Support tickets are found under "My Account">>>"Account Home".

2. Reporting a Match

2.1	To report a match, simply choose the Challenge Management icon from your user management bar in the top right portion of your screen: - User Management Bar: - Challenge Management Button: Once you are in the "Challenge Management" area, simply choose the match you wish to report and report the match.
2.2	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.
2.3	EITHER team may report the match at any time after the specified date and time.
2.4	Continued failure to report matches on time could warrant dismissal from the current ladder at the discretion of the Head Admin.
2.5	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.

3. Player GUIDs

3.1

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.

3.2

Entering your GUID on FraggedNation follow these instructions:

- Select "My Account Home" icon

(No Image = My Account Home)

- Select "Competition" tab

- Select "Manage GUIDs" icon

- Enter the last 8 characters of your GUID, select game from dropdown, and then select ( ) Add New.

- Repeat all the steps above 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, etc. To add GUIDs for these games, simply add another entry for the parent game.

4. ELO Point System

4.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 10 or more ladder games
K=20 for players who have played 20 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.

5. Private Ladders

5.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.

6. Support Tickets

6.1	Submission of Support Ticket If a team has an issue with their ladder match that they would like an admin to address they can submit a support ticket. Teams 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.
6.2	Ladders Matches Issues Only team captains can submit a support ticket for an admin to review a ladder match. In the case of 1v1 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.
6.3	Provide 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) - What was the exact error message or what is the name of the server you need addressed. 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.

7. ELO Penalty Points System

7.1

The following is the ELO Penalty point system to be used on FraggedNation, dealing with ladders, tournaments, and general FN issues. Evidence will be present before any of the following infractions are given:

General Issues (Ladders, Tournaments, Rules)
1st occurrence: Team/Player Warning
2nd occurrence: 5pt Team/Player Penalty
3rd occurrence: 10pt Team/Player Penalty (plus the original 5pt = 15pt total)
4th occurrence: Instant Team/Player Suspension (3 day)
5th occurrence: Instant Team/Player Suspension (Season)
6th occurrence: Instant Team/Player Banning (from Site)

-------------------------------

The only exception to the above system would be issues of Match Admin Abuse, the following would be the penalty system for this kind of action:

1st occurrence: Team Warning
2nd occurrence: Instant Team Forfeit (Match Ends Then)
3rd occurrence: Instant Team Suspension or banning

These penalties are match wide, not map specific.

8. User Accounts

8.1

Account Images

FraggedNation is a community oriented site that caters to a very diverse population in age, race and culture. Images containing full nudity, vulgar language, offensive symbols or signs, sexually explicit material, racist propaganda,or anything otherwise deemed offensive by members or staff will not be tolerated.

Any violation of these rules will result in the offending image being removed, and repeat offenders will be banned from the site without warning.

8.2

User Names

User names registered at FraggedNation may not be obscene or vulgar. User names containing obscenities, vulgar language, or anything otherwise deemed offensive by other members or staff will not be tolerated. Any violation of these rules will result in a warning to change your name and if not done promptly the offending account will be removed, and repeat offenders will be banned from the site without warning. If you are not certain your choice of name is appropriate please PM an admin to ask for approval.

9. Forum Conduct

9.1	Advertising Advertising on FraggedNation forums without permission of any products or services - specifically any services that would be in direct competition with FraggedNation - are not allowed and will be removed without warning.
9.2	Post in the Appropriate Forum Please post in the appropriate forum so your topics can be best addressed. If you're not sure where to post your topic, post it in the General Banter forum. If your topic belongs in another forum a forum moderator will move your post to the right location.
9.3	Bypassing Language Filters FraggedNation has a list of words that are inappropriate to use on our forums. Attempting to bypass the filter by misspelling, inserting spaces or using symbols is not allowed.
9.4	Allegations of Player Cheating Cheating accusations on the forums will not be tolerated and will be removed by the forum police. If you have a concern about cheating submit a support ticket for admin review. No cheating allegations will be entertained without hard evidence.
9.5	Illegal Activities Posts that violate the law are not allowed. This includes, but is not limited to: Discussing, asking for, or providing any of the following: - Illegal copies of copyrighted software - Methods of circumventing copyright protection - Illegal copies of copyrighted media - Methods of cheating.
9.6	Prejudice Comments No member will post comments using race, religion, sexual orientation, culture, ethnicity, handicap, nationality, or gender as a means to insult and/or discriminate against other people, whether they are members of FraggedNations or not.
9.7	Repeat Threads If any post is deleted or locked, please do not start a thread identical or similar to the locked/deleted one, or make a thread asking why the previous thread was deleted/locked.
9.8	Sexually Explicit Content Sexually explicit content and sexually suggestive material is inappropriate at FraggedNation. Pornographic pictures/videos/audi or links are not allowed to be posted in the forums.
9.9	Forum Moderation FraggedNation reserves the right to remove, edit, or move any post/thread we deem necessary. This is to keep the forum moving on the right track and enjoyable for everyone. Anyone who decides to insult and/or disrespect forum moderators will be muted without warning.

10. Change Requests

10.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.
10.2	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.
10.3	Unaccepted challenges with at least 3 attempted change requests will not increment the 7 day free decline counter.

11. Ringing / Name Swapping

11.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.
11.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.
11.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.
11.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.
11.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.
11.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.

12. General Ladder Rules

12.1	FIGHTING & MISCONDUCT Will not be tolerated. Period. If there is a problem with another team or player please contact the Ladder Head 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.
12.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.
12.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. Hacking into a server owners password to gain access to their server will not be tolerated. If you have not been given the password, or permission by the owner to access the server, then it is deemed that you have done this illegally. This will result in a one game suspension for the first offense. 2nd offense will result in a team suspension for 2 weeks. 3rd offense will have the person banned from FN.
12.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.
12.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.
12.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 team in which the player at fault is on, 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.
12.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 - Forfeits handed out. - Suspension of player account and ladder or tournament membership/participation - Banishment from FraggedNation.com
12.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.
12.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.
12.10	Reporting Cheats / Hackers / Abusers It is possible to bring forward information on an alleged cheater to FraggedNations attention. Proof must be provided within 20 days from when the alleged cheat occurred. FraggedNation will not 'witch hunt' cheaters and will not act on suspicion or out of date logs etc. FraggedNation reserves judgement on all cheating matters based on all accurate information to hand. Please ensure your ladder admin is informed of any information so that FN can investigate matters further. The preferred method of raising any issue is via the support ticket system. Details of any investigation, proof & logs etc plus the outcome of any investigation will not be made public.

13. Challenging a Refs Call

13.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.
13.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 3 weeks after which time they may be discarded if an Admin does not request them.At no time will anyone other than an FN admin view the demo's recorded during any match. If you are challenging a call, you must put this through the support ticket system, and then the ref must provide the demo to the Head or Game admin for review, and you will be notified when a decision is made.
13.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 glitching call made against them. They have all 5 of their challenges available. If the Admin overturns 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.
13.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.
13.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.
13.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.

14. Times and Matches

14.1	A Challenge can be made directly to a participant on the ladder standings page, or posted as an "Open Challenge" in the Match Finder; where available. Some ladders have been configured by the Owners/Admins to disable the Match finder and the ability to have more than 1 challenge open at a time.
14.2	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 (PC Only) - In the event waiting for another player causes an overlap to another match on the same server, both teams or challenging team will receive forfeit. Ensure there are no other matches scheduled on that server before waiting additional time. (Console Only) - 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.
14.3	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.
14.4	Random map generation vs Player/Team selectable Random: All maps are generated at the time of challenge using a random selection algorithm. (System Generated) Selectable (3 Maps): Players/Teams on "selectable map" 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). Selectable (1 Map): - On this system, the map is auto generated using the random algorithm. (System Generated)
14.5	Either winner or loser of a match may report once the match is completed, and this must be done within 4 hours of match start.

15. Challenging, Accepting and Declining

15.1	A participant my post a challenge if: 1. 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. NOTE: You may not challenge DOWN in rung based ladders 2. They have entered a GUID for the specific game, where applicable. NOTE: Not all games require GUID entry. Please see specific ladder details for this information. 3. If posting a challenge to a particular participant, they have not played this same account inside a 6 hour time period. NOTE: Some ladders may have this time adjusted so see ladder details. 4. They have recently joined a ladder, or rejoined the ladder from inactivity and waited 6 hours. NOTE: Participants will appear as ineligible until this time period has lapsed.
15.2	Challenging Go to the console type, game name, and then ladder standings page. Select the "Challenge" icon beside the members name you wish to challenge: On the next screen, select a Date/Time/Server (where applicable) and a Round 1 map (where applicable) and click 'Post Challenge'. An email will be dispatched to you, and your opponent as confirmation of the challenge.
15.3	Accepting, Declining, Changing Matches Click on the Challenge Management icon in the upper right hand portion of the screen: - User Management Bar - Challenge Management Button Locate the challenge you want to accept under "Pending Acceptance" and click the Edit icon to the far right. From there, choose Accept, Decline, or Change request.
15.4	Declining a Challenge: Challenges can be declined without penalty, but only under certain circumstances. Condition 1: Each ladder has a configurable option for"Declines/Ignores Per week" allowance. This is defaulted to 3, but may be different for each ladder. The amount of remaining declines for the week can be seen when viewing a pending challenge. Participants may decline that many challenges per week without penalty. Each decline will increase this counter for the seven day period, unless otherwise specified in the other conditions (see below). Condition 2: The challenge was posted with less than 48 hours notice from the time of challenge to the requested date/time of play. Declining this challenge does not increase the Declines per Week counter. Condition 3: The person being challenged has submitted at least 3 change requests to get the match date changed to an acceptable time. Declining a challenge with 3 or more change requests does not increment the weekly decline count. Change requests may be made by the challenger, or the challengee, however only one change request may be active at a time. Declining or Accepting a change request will provide the opportunity to submit a new request. Note: Declining or Ignoring a challenge with an accepted change request will never be a "free" decline and will go against the weekly decline count, and/or an immediate forfeit win for the opponent.
15.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. Participants you are unable to challenge will display a 'Cannot Challenge' in place of a 'Challenge' button. 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.

16. Ladder Seasons

16.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 in the Ladder Header at the top of the screen when viewing the 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, and matches archived. If there are any prizes to be awarded you will be notified should you be the winner at the end of a season.

17. Ladder Maps

17.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 on a particular ladder.
17.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.
17.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.
17.4	Maps can be added/removed during a season by popular vote only, and said vote must be initiated and mitigated by the Head Admin running the ladder.
17.5	If you are unhappy with a particular map on a ladder, be sure to go and rate the map via the Ladder Standings page. Click the "Detail" tab and then "Maps" tab: The option to rate a map or leave a comment is displayed along with the current ratings or comments left by other members

18. Ladder Servers

18.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 the 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.
18.2	Team Matches Your Head Admins will do the best they can to ensure the Admin/Ref assigned to your match has Admin privileges 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 or host the server selected, please contact the Head Admin and voice your concerns.
18.3	Matches that Require a Ref You are not permitted to play and report these type matches 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, simply halt the game, and 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.
18.4	Server Settings It is important as both the challenger and challengee to ensure that the server is running the proper configuration or settings before starting the match, and certainly before reporting the match. In the event you notice settings or server configuration needs modification, it is your responsibility to notify an Admin to correct the situation BEFORE MATCH TIME or BEFORE THE MATCH BEGINS. All servers are run by different admins, so there is a possibility there may need to be a change.
18.5	Should you specify a custom server when challenging, it is your SOLE responsibility for the readiness of said server. Failure to provide a viable server at the specified time and address will result in full forfeiture of match.

19. Forfeits

19.1	All forfeits that are not automatically processed by the system will 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, otherwise Head Admins have a 24 hour period to process forfeits.
19.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.
19.3	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(4th Thursday in November) Memorial Day(Last Monday in May) Independance Day(July 4th) Labor Day(First Monday in September) Canadian Holidays: Victoria Day Canada Day(July 1st) Labor Day(First Monday in September) Thanksgiving Day Boxing Day(December 26th) 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. The no forfeits rule for Holidays in a country in which you do not live, will not apply. Example, if your team is from Europe, Canadian and US holidays will not apply for your team and matches will still required to be played. In order for the match to be considered for a forfeit because of a holiday, your team must be from or have a majority of people from the country in which the holiday is a factor.

20. Teams and Rosters

20.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.
20.2	You may NOT switch a team member DURING a round of play, *unless* a specific Ladder's own rules permit, persuant to appropriate circumstances.
20.3	You may rotate any eligible member of your roster for play at the beginning of any round.
20.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.
20.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.
20.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.
20.7	Teams may have no more than 4 captains - this is enforced programatically.
20.8	Players may only compete on ONE Team per Team Ladder, and ONE 'rung' per 1v1 Ladder.
20.9	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.

21. Rung Based Ladders

21.1	Rung based ladders, though much more rare than ELO Point Based Ladders, are not based on wins but rather on placement due to wins and losses. The entire concept is designed to let the winner of a match either A) retain their position B) lose their position to their opponent When losing position, the losing team is bumped down ONE rung, and the winning team is awarded their position in the standings.
21.2	When a team is awarded the position of another team due to a win, it's important to note that ALL standings are affected. When the losing team is bumped down one rung, so is EVERY OTHER participant on the ladder to make room for them in their new spot.
21.3	Consider Rung Based ladders much like "King of the Hill" - doesn't matter how many times you've fallen off, you're still the king if you knock the person on top down.
21.4	Rung Based standings are in NO WAY affected by participant ratings, OR Win/Loss percentage. It's strictly a "Who got themselves on top" situation.
21.5	It's entirely possible that a team with a perfect record be ranked very low in the standings if they are not playing matches and reaffirming their position in the standings. Teams ranked lower can challenge up higher and get placed above them, and it's possible that someone with a perfect record could even be in last place if they're not paying attention! It's all about getting on top, and staying there!
21.6	If a team defends their position in the standings successfully, no changes are made to the standings. There are no penalties for losing a challenge where a team is attempting to take over another teams position - it's up to the team defending their position to do so in order to not be bumped down a rung.
21.7	All rung based ladders are single-challenge ladders, which means that any member may only have 1 pending challenge at a time, unlike ELO ladders where (unless disabled by the admin) many matches can be scheduled for play on the same ladder simultaneously.

1.	Staff
2.	Reporting a Match
3.	Player GUIDs
4.	ELO Point System
5.	Private Ladders
6.	Support Tickets
7.	ELO Penalty Points System
8.	User Accounts
9.	Forum Conduct
10.	Change Requests
11.	Ringing / Name Swapping
12.	General Ladder Rules
13.	Challenging a Refs Call
14.	Times and Matches
15.	Challenging, Accepting and Declining
16.	Ladder Seasons
17.	Ladder Maps
18.	Ladder Servers
19.	Forfeits
20.	Teams and Rosters
21.	Rung Based Ladders