TeamTeam HardcoreTeam (EU)Team Hardcore (EU)DoublesDoubles (EU)SinglesSingles (EU)

TEAM LADDER

Season: Fall 2010

Total Teams: 367

Currently viewing season:

GENERAL

General · Rosters · Challenges · No-Shows · Reporting · Tickets · Cheating · Referees · Proof · Settings · Matches

Rules are subject to change at any time, so please check them often.
It is the responsibility of all users of this ladder to know and understand the rules.
By sending or accepting a challenge, including on the Match Finder, you acknowledge that you have read, understand and agree to abide by the posted rules.
ConsoleBattles is intended to provide fair and competitive matches. Cheating, intentional disputes and abusive behaviour are prohibited. Valid proof is required for accusations.
Only team management may request team-name changes. Team names, messages, logos and links are subject to community rules.
Teams must contain the minimum number of eligible players to remain active.
Users are responsible for their own accounts, invitations, gamertags and account security.

Both teams are responsible for verifying player eligibility before or during a match. A team using an ineligible player may forfeit.
If an ineligible player is present, the opponent should be asked to replace that player within the applicable grace period. Problems must be raised promptly and supported by valid proof.
Users may be listed on only one team on each ladder at a time and may use only one gamertag per ladder.
Gamertags must be valid, legitimately owned and accurately entered. Eligible players display a green eligibility indicator.

Accepted matches may be cancelled through support when both teams agree or when the request meets the cancellation window.
A team cannot repeatedly play the same opponent within the restricted challenge period.

A team has 15 minutes to appear with the required number of eligible players and be ready to start. Failure to do so may result in a forfeit.
No-show claims should be reported promptly through the match and support systems.

Both teams are responsible for reporting a match after completion. Conflicting reports create a dispute and both teams may submit valid proof.
Teams with multiple unresolved disputed matches may be restricted from accepting additional matches until disputes are resolved.
If one team reports and the other does not, the reported result may be processed automatically. Matches unreported by both teams may be removed.
Teams must report the actual result first, then use the dispute/support process for rule violations. Intentionally false disputes can result in penalties.

Support tickets must include all applicable details. Match-related tickets should include the match reference and relevant evidence.
Proof should clearly show the full in-game scoreboard, scores and gamertags. Video or image evidence must be readable and directly related to the claim.
Private conversations, messages or unsupported allegations are not by themselves valid proof.

Default settings are followed unless a challenge option explicitly changes them. Verbal or off-site agreements are not supported.
Matches must be played in their entirety unless both teams agree to postpone or cancel through the supported process.
Randomized maps and challenge-selected options must be followed. Hosting alternates according to ladder rules and challenge details.
Teams should complete a lag test before the match and resolve hosting problems before competitive play starts.
If a player disconnects, the match continues according to the game-mode rules and eligible substitutes may be used where allowed.
If a map is tied, it is replayed with the same sides and settings.