Last Updated: 4:00 PM 27/03/07

Contents:

• Game Objective
  
• Team Size
  
• Team Names
  
• Starting Time
  
• Format
  
• Results
  
• Challenging
  
• Challenge Height
  
• Maps
  
• Team Ownership
  
• Team Members/Mercenaries
  
• Player Substitutions
  
• Server Malfunctions
  
• In Game Chat
  
• Third Party Voice Clients
  
• Source TV
  
• In-Game Exploits
  
• Cheats
  
• Referees & RCON
  
• Client Setup and CVAR's
  
  • Client Rates
    
  • Server Setup
  
  
• Ladder Timeline
  
• Spectators
  
• Finals
  
• Dispute Handling
  
• T&C / CoC / General Rules
  
• Rights Reserved

Game Objective

Win by scoring more total round wins than your opponent after playing the selected map as both Terrorist and Counter-Terrorist.

Team Size

Gameplay is 5v5.


Teams with less than four players in the applicable GameCreate server within FIVE (5) minutes of the GameCreate server coming up, are deemed to have automatically forfeited the match. This rule does not apply if both teams' captains wish to wait for the fourth to join, in which you will need to refer to the starting time rule.


Should any team drop below four players at any point during a match, that team is deemed to have forfeited the match if the exact same player(s) do not return within FIVE (5) minutes of them dropping from the server.

• "Drop Below" means the player(s) were no longer physically in the server. (IE: The status list)
  
• Players are not to type retry at any point after the initial commencement of the match (IE: Live on three), doing so will result in a forfeit.
  
• A 5th player may join at any time after the initial commencement of the match. When a teams 5th player joins, the rules will apply as if the team had started with these 5 players.
  
• Once a 5th player joins, that is it. This player cannot be substituted until half time or not at all in the second half.
  
• The 5th player may also join if the team started with only 4 players and a player drops, thus falling foul of the 4 player minimum rule. In which case the 5th player becomes the new 4th player and the missing 4th player is then allowed to rejoin at any time for the first half or replaced entirely at half time, or rejoin for the remainder of the 2nd half.
  
• Both captains are required to take rcon status screenshots under the following conditions to be able to provide evidence in the event of a dispute:
  
  • Whenever a player enters or leaves the server.
    
  • At the beginning of first and second halves.
    
  • When the server is performing poorly, along with rcon stats & ga_rates in the same screenshot. (IE: Below 35 IN on net_graph 3)

Team Names

Team Names are to comply with the GameArena Terms & Conditions and Code of Conduct.

Teams must NOT use inappropriate names, web links or name tag stealing. This includes (But is not limited to) using:

• Offensive;
  
• Abusive;
  
• Racist;
  
• Known cheating clan tags;
  
• Discriminatory;
  
• Otherwise inappropriate language or web links in a player's online nickname or clan tag.

Team Names and Tags that breach this rule will cause the entire team to be deleted from the GameArena Counter-Strike Source Ladder without hesitation.

The Ladder Administrators will have the final decision on what constitutes an Inappropriate Clan Name or Tag.

Starting Time

The match is to commence no later than FIVE (5) minutes AFTER the GameCreate server has come online, not from the time the server was scheduled to start.

Should your team (Of at least four players) be in the server and the opposing team does not arrive (Of at least four players) within FIVE (5) minutes of the server starting time, the opposing team forfeits.

The only exception is unless both captains agree to wait for either/both teams have at least four players, in which disputes based upon the starting time rule will not be accepted.

• If you intend on forfeiting the other team, DO NOT PLAY THE LADDER MATCH!
  
• Teams that decide to wait for the fourth applicable player for either side should do so no longer than FIFTEEN (15) minutes as the server is only up for ONE (1) hour.
  
  • If one team has their five players in the server, the other side only has four players and the server uptime hits the 5 minute mark, then the team with five players has the right to "Live" the match.
  
  
• Teams can not wait for a Ladder Referee, even if the match was tagged for having one attend. Teams refusing to play because there was no Ladder Referee attending the match, will lead to their team being forfeited.
  
  • This means that if the server uptime hits the FIVE (5) minute mark, that the match will go ahead if both teams have the required amount of players and the Ladder Referee is not in the server.
  
  
• You are required to make sure you have a working version of Counter-Strike Source before the server start time. This means that:
  
  • ALL players are required to keep their Steam installations up to date.
    
  • Excuses such as "I had to wait for Steam to update" is not a valid reason.
    
  • Although there may an event of widespread Steam issues that that make it impossible for players to login/download updates/launch Counter-Strike Source within a reasonable time period, then disputes maybe lodged, however each dispute will be dealt with on a case by case basis.

In the event of a GameArena GameCreate server malfunction such as what is listed here, teams must decide whether to play on or cancel the match.

In the event of a match cancellation agreement, lodge a dispute and inform the Ladder Administrators of the issue that caused both teams to agree to the cancellation and that both teams agreed that the match should be cancelled.


Both teams will need to reply to the dispute for this to occur, along with providing screenshots as evidence.

• In most cases, the match will be cancelled by the Ladder Administrators.
  
• Make sure both teams agree IN GAME via chat, to cancel the match. Take screenshots to confirm the agreement!
  
• Teams are NOT to use servers other than the GameArena GameCreate server that has been scheduled for your match.

Format

The GameArena Counter-Strike Source Ladder uses the Max Rounds 15 format. (IE: Each half consists of 15 rounds)

There is a ONE (1) hour time limit; round time is 1.75 minutes (1 minute 45 seconds) long.


The teams must play the selected map once as Terrorist and once as Counter-Terrorist. Each "half" is played until 15 rounds have been completed (Regardless of who wins them).


The map selected to be played on cannot be changed once the applicable GameCreate server has started.


The defending team gets the choice of side for the first half. In the finals, the same rule will apply but will be based on that side's final standing's at the end of regular seasons competition.


At the end of the first half teams will be required to change to the opposite side and then after a brief warm-up (Maximum of 5 minutes) continue the game.


Teams are to not change sides until the the final "Terrorists Win" or "Counter-Terrorists Win" sound goes off.


Once a team has won 16 or more rounds, they have won the game.


A draw (15-15) IS a valid result. There is no overtime, but the defending team will be considered the winners of the match in the ladder.

Servers are set up to run for ONE (1) hour from the booking time, which is plenty of time for a war to be completed if the rules are followed. However, for reasons outside of the control of GameArena, the server may not be available at the exact starting time.

• If the server does not come up within FIFTEEN (15) minutes of the scheduled start time the war will be cancelled, regardless of whether the war is completed or not.
  
• If the server does comes up within FIFTEEN (15) minutes from the scheduled start time then the war may proceed.
  
• The onus will be on the challenging team to do whatever it takes (within the confines of the rules) to ensure that the game is completed within the remaining server time.
  
• The defending team may play (within the confines of the rules) their first half in any manner they see fit. If a game is not completed within ONE (1) hour, the current score will be taken.
  
  • EG: In the event of the server time ending, if the current score is 8-7 for the first half and 2-1 for the second half, the final score will be submitted as 10-8.
  
  
• At the end of each half, the captains are required to take a screenshot of the scoreboard.

In order to prevent matches going to an unnecessary dispute when entering “forfeit” as a result, please record the score as 0:0 in ALL instances, regardless of whether any portion of the match was played or not.

Results

At the completion of a match

• Both teams must visit the "View Challenge" page and enter (Or dispute) the match result.
  
• Results are entered independently - The defender is not required (.. and should not) wait for the challenger to enter a result.
  
• If both teams enter identical results - the match result will be accepted at 4:00AM the next day.
  
• Rankings/protected/vulnerable status will all be automatically updated if required.
  
• Both teams have up to two hours after the completion of the match to enter the result.
  
• All match results will be processed the day after the match at 4:00AM AEST, regardless of when the teams enter results.

Disputed Results

• If either team chooses to submit a dispute, the match is marked "Disputed" and regular time-outs no longer apply.
  
• If both teams enter results but they are different, the match result will be disputed at 4:00AM the next day. The match will be marked as disputed; team captains will receive an e-mail detailing the dispute.

Forfeits

• A game that has been accepted by a defending team must be played at the scheduled time on the agreed map.
  
• The team that fails to play at the scheduled time will be deemed to have forfeited the match.
  
• Each team requires at least four players to begin play.
  
• If the defender enters a result within 2 hours but the challenger does not, the defender will be awarded a forfeit-win the next day at 4:00AM.
  
• If the challenger enters a result within 2 hours by the defender does not, the challenger will be awarded a forfeit-win the next day at 4:00AM.
  
• If neither team enters a result, the defender will be awarded a forfeit-win at 4:00AM the next day. This mirrors the current behaviour - the challenger must enter a result to avoid a forfeit.

Please check the results before submitting them! This is the main cause of all disputes so try to be careful.
The explanation for a teams subsequent status after a result is explained in the GameArena Counter-Strike Source General Rules.

Challenging

When challenging, you must select:

• 3 different maps;
  
• 3 different challenge times that are not within the same half hour.
  
  • 18:00, 19:00 & 20:00 are valid challenging times;
    
  • 18:30, 19:00 & 20:00 will be rejected by the system and you will be required to choose different times.

Challenge Height

The challenge height is 50% of the teams current ranking, or 10 rungs - whichever is higher.

Maps

The following maps will be used in the GameArena Counter-Strike Source Ladder:

• de_aztec
  
• de_cbble
  
• de_dust2
  
• de_inferno
  
• de_nuke
  
• de_train
  
• de_losttemple_pro
  
• de_season

Team Ownership

Team Ownership cannot be transferred, except as follows:

If the team founder retires within the teams first season, the team will be deleted. Don't create teams unless you are prepared to play out the teams first season!

In subsequent seasons if a team founder retires, the team may continue so long as:

• The team founder is replaced by an active member who was active for 80% of the Teams previous regular season;
  
• The team also has one other remaining member who was also active for 80% of the teams previous season;
  
• Both these players remain active for the current regular season.

So long as the team founder is with the team and the founder remains active for the current regular season the teams line up can change in any form it so wishes.

In any other case, if the team founder resigns, the team will be deleted from the GameArena Ladder.

Intention of Team Ownership Rules:

• Stop people creating teams then resigning from the team. If they can't stick it out for a single season then they shouldn't have created the team in the first place. Don't join teams with unstable leaders!
  
• Stop people taking over a high ranked team by replacing the team with players who never were responsible for getting the team to the ranking it is at.
  
• Allow a process so teams can be taken over internally by players responsible for the teams current ranking so a team founder need not stick around for multiple seasons. We do not expect a team founder to spend the rest of their lives in a team for the team to stay alive.
  
• Ensure players who were responsible for the teams end of season rank actually be the players who play in the finals.
  
• Ensure the players in the team are actually active as this is also what occurs, the founder stays, but is inactive. The team is meant to be made up of active players not a bunch of mercenaries or team take-over and the team founder who doesn't actually take any part in the teams wars.

Teams found to either be breaking or bypassing the team ownership rule will be deleted and/or banned from GameArena at the complete discretion of the Ladder Admins.

Team Members/Mercenaries

Players

• You can only be a member of 1 team on the GameArena Counter-Strike:Source Ladder.
  
• Players may not play for any team they are not registered for, whether they are participating in the GameArena Counter-Strike:Source Ladder or not.
  
• Players may not have multiple GameArena Accounts and/or STEAM ID's or otherwise try and circumvent this rule.
  
• Players who fail to comply with these rules will have ALL their GameArena Accounts and STEAM ID's banned from ALL GameArena services.

Teams

• Only players marked on your current roster may play in the match.
  
• Using players not on your official GameArena team roster will result in your team being removed from the GameArena Counter-Strike Source Ladder.
  
  
• At a specified time before the finals start the rosters will be locked and no players will be able to be added to the teams rosters.
  
• Only players who have played for their teams at least once in the current regular season will be allowed to compete in the finals for their team. (See the Finals section for more info).
  
• All team members are required to submit the STEAM ID they will be using when playing on the GameArena Counter-Strike Source Ladder which can be done at this link.
  
• Players must use the STEAM ID they registered against their GameArena player name.
  
• All players must log in using the Official GameArena "The Arena" Client software with the GameArena nickname they have registered against their STEAM ID.
  
• Teams that have players who cannot manage to use names that reasonably match their registered GameArena nickname, will be forfeit in the event a dispute arises for any reason. This may result in both teams being forfeit in the event multiple breaches occur.
  
• Permissible names are listed on the View Challenge page.
  
  
• In the event of a dispute, teams that do not have 5 members in their team with STEAM_ID's set correctly, will have their team deleted from the GameArena Counter-Strike:Source Ladder.
  
• Randomly from time to time, the GameArena Counter-Strike:Source ladder teams maybe audited to check that they have the sufficient 5 members with STEAM_ID's set correctly. Teams found to not be in compliance will have their team deleted from the GameArena Counter-Strike:Source Ladder.

The use of players who are not on your roster is considered cheating, which is why the penalties are severe for both the player and team in question.

Player Substitutions

If a player drops out during a game, the game must go on and the player is to rejoin play as soon as is possible.

• If the player(s) fails to return it is at the discretion of the player's captain to continue the game or forfeit.
  
• Players may not substitute while the game is live.
  
• However, teams may switch their current line-up by bringing in new player(s) at the half-way point of the match. (IE: When competitors switch sides)

Server Malfunctions

In the event of the booking email not having details and/or booking ID:

• Contact a Ladder Administrator with the details of your match so it can be cancelled as soon as possible.

In the event of a server crash:

• If under 3 rounds have been played, the half is restarted.
  
• If 3 or more rounds have been played, the half is restarted but the score retained.
  
• A round is complete as soon as the game says "Terrorists Win" or "Counter-Terrorists Win"

If the server crash is found to be malicious, GameArena will take legal action against any and all users found to be involved.

In the event of poor server performance:

• Enable your net graph by typing net_graph 3 in console - make sure this is visible and not obstructed while the console is open.
  
• Log into RCON (If you haven't already) and type rcon status, rcon stats & ga_rates.
  
• Type jpeg in console to take a screenshot of the console print out and of net graph.
  
• Take a screenshot of the scoreboard to be used alongside the screenshot of the console print out.

In the event of the server not showing up within FIFTEEN (15) minutes:

• Lodge a support job to the GameArena Staff, using the drop down box to select "GameCreate", quote the details that was included in your challenge booking email (Details about the war, including the booking ID, time & server IP:Port and name the server was booked under) and state what happened so the matter can be investigated and rectified.
  
• Lodge a dispute, making sure to and state that the server did not show up and that you've logged a job about it.
  
• In all other cases where the server shows up albeit late, the game will continue as it normally would if it had started up correctly at the booking time.
  
  • When the server is late, anything based off the starting time will be based off the time the server went online and NOT the server booking time.
    
  • If the server does not go online within the fifteen minutes, please do NOT contact a Ladder Admin or any other GameOp, as there is nothing they can do other than redirect you to the Contact Support feature.

Captains will need to then agree that the server is unplayable and if so, take the screenshot of the agreement if applicable and dispute the match using the ladder dispute system, which is found here.

In Game Chat

All Players are allowed to use Global Chat BEFORE the war starts and after the war has completed or result achieved.

No Global Chat (MM1/Message mode 1) will take place between either team while the match is live, nor during half time except under the following circumstance:

• The player wanting to talk is the teams captain and is tagged up with something similar or matching [C].

The teams captain should be nominated when your team enters the server and should not change, unless the nominated captain drops from the server. (IE: Not in the status list)

Team members are only allowed to use Team Say Chat (MM2/Message mode 2) and voice communication during the war.

We advise that players who are not captains unbind their Global Chat keys so no accidents occur, this can be done by typing "unbind y" in console and can be rebound by typing "bind y say".

The Ladder Administrators will have the final decision on what constitutes a breach of the In Game Chat rule and what penalty may apply.

Third Party Voice Clients

Third Party Voice Clients are an acceptable method of voice communication in the GameArena Counter-Strike Source Ladder.

GameArena makes no guarantee that GameArena provided voice chat services will be available for use when a team has a war.

In the event that voice chat services as provided by GameArena or any other party is unavailable, matches will be played as scheduled.

Source TV

By entering the GameArena Counter-Strike Source Ladder, you agree to have your game available for spectators via Source TV. If you do NOT agree with this term you must not enter the GameArena Counter-Strike Source Ladder.

We do not guarantee Source TV support for any match.

In-Game Exploits

The following section should clarify what is and what is not allowed to occur within gameplay, even if the exploit is unknown at the time:

• "Boosting" (Jumping on the head of a team mate to reach a higher point) is allowed, so long as the players remain within the correct map boundaries.
  
  • EG: Boosting to ledges on Dust2 & Aztec is allowed.
  
  
• Players are to use VALVe's default GCF models, material and texture files for everything!
  
• Map specific exploits (EG: Sky walking, Flashbang Bugs) are not permitted.
  
• Gameplay specific exploits (EG: Deliberate weapon muting, silent bomb planting, grenade boosting, planting the bomb in places that can not be reached for defuse, or may cut out mid way (not including places reached by standard boosting) are not permitted.
  
• Grenades may be thrown over the tops of walls and buildings.
  
  • EG: Dust2, Inferno and Cbble.
  
  
• Strafe Jumping to reach places not normally accessible to a single player is allowed.
  
  • EG: Certain crates on Cbble.
  
  
• Strafe Jumping (Bunny Hopping) for the purposes of moving around the map quicker is not allowed.
  
  • However, momentum jumping down slopes is allowed.

Any team found utilising such exploits deliberately will be removed from GameArena Counter-Strike Source Ladder and the player(s) involved may be banned permanently from GameArena.

Ladder Administrators will have the final decision on what constitutes an In-Game Exploit.

Cheats

GameArena Terms & Conditions
GameArena Code of Conduct

No Cheats of any kind are to be used in the GameArena Counter-Strike Source Ladder in any way, shape, manner or form.

It is the captains' and the Teams players responsibility to ensure that their team complies with this rule.

• Should one of a teams players be caught cheating on a GameArena server, the whole team will be banned from competing in the Counter-Strike Source Ladder for the remainder of the season.
  
• The cheating player(s) in question will be PERMANENTLY BANNED from all GameArena public and competition servers, in accordance with the GameArena Terms & Conditions.
  
• A team that elects to report player(s) from within their own team for using cheats, will not have the complete team banned from the GameArena Counter-Strike Source Ladder.
  
• Only the player(s) proven by evidence to have cheated (At any point upon GameArena servers) will be permanently banned.
  
• Any team member is free to submit an incident report at any time if they have specific concerns about a player within their team or any other team, so long as they provide sufficient evidence that there was a breach of the GameArena Terms & Conditions.

In the event of a team self reporting a team member, the team may be subjected (But is not limited) to:

• Having their team rank demoted.
  
• Having their team removed from the GameArena Counter-Strike Source Ladder.

This is subject to the Ladder Administrators decision on how much of an advantage the team has received by having the cheating player(s) in their team.

Cheat Definition
Cheating includes, but is not limited to:

• Map hacking; (EG: Wall hacks, etc)
  
• Auto aim or auto recoil;
  
• Grenade spam;
  
• Cvar exploits;
  
• Anything that attempts to bypass any client side settings put in place by GameArena;
  
• Wireframe drivers;
  
• Launching denial of service attacks or packet flooding an opponent;
  
• Models that extend beyond reasonable bounds;
  
• Speed hacks;
  
• Or any other gameplay altering cheats.

Cheating is a very contentious issue within Counter-Strike. We have a zero tolerance policy with regard to any cheating. Any exploitation of either the Source engine or the modification of normal play is not acceptable in this ladder.

Referees & RCON

Whilst we encourage teams to play their games by themselves at any point during a challenge, or on the expectation of a challenge by the defending team, you may request a GameArena Ladder Referee to be present (but not participate) during your game.

You must abide by ALL the referee's instructions at all times during the game.

The referee's purpose of being present in the match is to do the following:

• To sit in spectator for the entire game and not join either of the two competing teams;
  
• Record the match into two separate "demo" files, one for each half;
  
• To take screenshots of rcon status, rcon stats & ga_rates;
  
• To also take screenshots of the scoreboard at the end of each half;
  
• To administrate the server via RCON;
  
• To advise what teams will need to do with ladder related issues;
  
• To report back to the Ladder Administrators about required aspects of the match and server after the match has ended;
  
• To submit any cheater they may have spotted with the footage that they've recorded.

Teams found doing any of the following things: (But is not limited to)

• Kicking the Ladder Referee from the server;
  
• Abusing the Ladder Referee (Or their position) in any way;
  
• Ignoring the Ladder Referee's requests;
  
• Waiting for a Ladder Referee past the FIVE (5) minute uptime mark;
  
• Changing any server side variable via RCON;
  
• Using rcon say for anything deemed inappropriate or unnecessary;
  
• Being disruptive in any way;

.. will lead to the team(s) being punished according to the Ladder Administrators discretion.

Due to demand, GameArena cannot guarantee a Ladder Referee for all matches.


It is your responsibility to nominate one player as an administrator for the match, providing a referee does not show.

This administrator can be from either team, but must be already playing in the match (That is, no extra player is allowed in the server).

This administrator must be able to use RCON proficiently, as well as knowledge in the MR15 Match format, rules of this ladder and must also be well aware of the GameArena T&C and CoC.

Acceptable RCON commands that the administrator can use are the following:

• rcon_password, so they can log into RCON and use commands;
  
• rcon say, so they can speak to both teams when necessary;
  
• rcon status, to get a list of all the currently connected players Steam ID's & IP's to the server;
  
• rcon stats, to show server performance details;
  
• rcon exec war, to use the Official Ladder Configuration (This gets applied automatically when the server starts up);
  
• rcon exec lo3, to use the Official Ladder Live on Three Configuration so the half can be started;
  
• rcon quit, only for when the server comes up as "VAC insecure" after typing in status.

Any user found changing any other variables will have their team punished, according to the Ladder Administrators discretion.

Client Setup and CVAR's

Players are encouraged to use the games default settings, adjusted to suit their internet connection.

GameArena will force all settings deemed as a prerequisite to playing in the Counter-Strike Source Ladder.

Client Rates

These are the only client rate settings allowed on the GameArena Counter-Strike Source Ladder

• rate 30000; cl_cmdrate 67; cl_updaterate 67
  
• rate 20000; cl_cmdrate 55; cl_updaterate 55
  
• rate 15000; cl_cmdrate 45; cl_updaterate 45
  
• rate 7500; cl_cmdrate 35; cl_updaterate 35

Please see the GameArena Rate Setup thread here for information on how to setup your client rate settings.

Rates must be checked by both teams BEFORE the war starts. i.e. Before the 1st half Live on 3.

All client rate issues must be worked out BEFORE the war starts.

If players cannot set their rates using one of the four rate settings listed above within 10 minutes of the server coming up, do not play the war, and submit a dispute with appropriate ga_rates & rcon status screenshot evidence.

If you allow a team to use illegal/disruptive rates, disputes based on the client rate rule will not be accepted.

Any team with players found to be changing their rates without explicit (screenshotted) consent from the opposition team after the beginning of the war, will be forfeited.

Please screenshot the ga_rates console output at the start of the 1st & 2nd halves during the live on 3 script, and at anytime you realise or suspect a change has been made to the opposition players client rates. If you do not have this evidence, then you cannot dispute based on the client rate rule.

You can also assist ladder admins by issuing the rcon ga_rates command in console when you take a ga_rates screenshot. Please note that this is not a replacement for screenshots.

No Screenshots = No Evidence = No Dispute.

Server Setup

mp_allowspectators 1
mp_autokick 0
mp_autoteambalance 0
mp_buytime 0.25
mp_c4timer 35
mp_chattime 15
mp_defaultteam 0
mp_fadetoblack 0
mp_falldamage 0
mp_flashlight 1
mp_footsteps 1
mp_forcecamera 1
mp_forcerespawn 1
mp_fraglimit 0
mp_freezetime 5
mp_friendlyfire 1
mp_limitteams 0
mp_logdetail 3
mp_maxrounds 0
mp_playerid 1
mp_roundtime 1.75
mp_spawnprotectiontime 0
mp_startmoney 800
mp_teamlist 0
mp_teamoverride 1
mp_teamplay 0
mp_timelimit 0
mp_tkpunish 0
mp_weaponstay 1
mp_winlimit 0

sv_accelerate 5
sv_airaccelerate 10
sv_allowdownload 0
sv_allowupload 0
sv_alltalk 0
sv_cheats 0
sv_footsteps 1
sv_friction 4
sv_gravity 800
sv_rcon_log 1
sv_lan 0
sv_maxspeed 320
sv_maxunlag 1.0
sv_maxrate 30000
sv_minrate 7500
sv_maxupdaterate 67
sv_minupdaterate 0
sv_maxcmdrate 67
sv_mincmdrate 25
sv_client_cmdrate_difference 10
sv_min_cl_interp_ratio 1
sv_max_cl_interp_ratio 2
log 1

Ladder Timeline

The GameArena Counter-Strike Source Ladder season will run for as long as needed, at which point will be declared closed when needed.

The top SIXTEEN (16) teams in the ladder will then go on to the finals.

If a new version of Counter-Strike Source is released during play, GameArena may at its option cancel all current challenges; at which point new challenges will not be permitted for a period of one week.

Spectators

With the exception of the Ladder Referees, spectators are not allowed within the actual server. They must spectate the game via Source TV (If it exists).

Players are not to join the spectator team at any time during the actual war for any reason.
Players are not to join the other team until the last round for the half has been completed.

Once a match starts, no one will be allowed to pause a game or otherwise disrupt the technicalities of the game. (IE: Warping, leaving the server, pausing, etc)

Disruptions of this nature will result in a forfeit.

Finals

Finals are organised by the Ladder Administrators.

• The finals will consist of the top 16 remaining teams, playing each other in a double elimination format.
  
• Once the winner is decided, they will be declared Season Champion.
  
• In all subsequent ladders, the Season Champions will be recognised in their information pages.
  
• After a short break the ladder will commence for another season.

Eligibility To Play
To be eligible to play in the finals, players on a teams roster must have participated in at least 1 fully completed, regular season war for that team.

Wars where the other team doesn't show up, or a result recorded where all the necessary rounds were not played to ensure an outcome, are not considered to be complete.

This rule is in place to ensure your team is made of players who were actually responsible for getting the team into the finals.

Dispute Handling

Both challengers and defenders have the privilege to dispute the result of the match. A dispute should be lodged in any of the below cases:

• Scores were recorded incorrectly
  
• Evidence that the opposition team broke one or more of the ladder rules

All teams are required to review the Source TV demos and log files (If applicable) before filing a dispute in an effort to reduce workload on Ladder Administrators and the number frivolous disputes.

• Players can use the demoui command to review Source TV and player made demos.

If you dispute your ladder match, you must provide a summary of the ladder rule infringement, along with evidence and/or links to evidence that demonstrate the ladder rule infringement, within 24 hours of the end of the match that. Failure to do so will cause your team to be forfeit and demoted to the bottom of the ladder.

The following required screenshots & information must be provided in your dispute within 24 hours of the completion of the match:

• End of 1st & 2nd half screenshots (mandatory)
  
• rcon status screenshots (mandatory)
  
• ga_rates screenshots (mandatory for client rate disputes)
  
• any other screenshot evidence (mandatory)
  
• The final score (mandatory)

Ladder Adminstrators will not request this information from teams, and failure to provide all of the above required screenshots & information in your dispute within 24 hours of the end of the match, will result in the dispute being dismissed out of hand and your team forfeited and demoted to the bottom of the ladder.
Teams may use the GameArena Incident Report System to upload evidence. Be sure to quote the Incident Report number in the dispute, otherwise the same punishment will apply to your team, as if you presented no evidence at all. Teams may use multiple incident reports if the evidence is larger than the 8MB Incident Report maximum.

If the opposition team does not wish to contest the allegations, then a short response advising that the allegations are not disputed should be made within 24 hours of the completion of the match. Failure to reply within 24 hours will cause an instant forfeit and demotion to the bottom of the ladder.

If the opposition team does wish to contest the allegations, they must provide their required screenshots & information, along with their version of events, and any other counter-claims within 24 hours of the dispute being lodged. You may also use the incident report system in the same manner as described above.

There should be no further correspondence from either team UNLESS in response to a specific request for further information or clarification by the Ladder Administrator.

Teams that fail to comply with these guidelines and go on to use the dispute system to argue with each other, will be deemed to be conducting a frivolous dispute and will be forfeit & demoted to the bottom of the ladder.

In the course of a dispute, teams that lead the GameArena Counter-Strike:Source Ladder Administrator to believe that they have not bothered to read the GameArena Counter-Strike:Source Ladder rules at all, will be DELETED from the GameArena Counter-Strike:Source Ladder.

Please Note: If your team lodges a dispute, be absolutely sure that your team is in 100% compliance with the GameArena Counter-Strike:Source Ladder rules, as the chances are likely that you may find your own team forfeited, and/or demoted, and/or deleted and/or players banned.

No Screenshots = No Evidence = No Dispute.

T&C / CoC / General Rules

By playing in the GameArena Counter-Strike Source Ladder, you agree to be bound and comply with the GameArena Terms & Conditions, Code of Conduct and the Counter-Strike Source Ladder General Rules.

Rights Reserved

Ladder Suspension
GameArena reserves the right to:

• Suspend the GameArena Counter-Strike Source Ladder at any time, as and when the Ladder Administrators consider circumstances which warrant it.

Playable Maps

GameArena reserves the right to:

• Remove a map from the Ladder, if it deems that map is not suitable for competitive play.
  
• Add other maps as they are officially released by Valve.
  
• Add new maps released during a current season as they become available (New maps will have a 2-4 week delay to learn the map(s) before being added to the selection for Ladder games)

Team Ownership
GameArena reserves the right to:

• Have the final decision on what constitutes a Team Ownership rule breach.

Client CVAR's
GameArena reserves the right to:

• Employ any 3rd party software it sees fit to enforce any CVAR that is deemed necessary.

Cheat Detection

GameArena reserves the right to:

• Introduce any anti-cheat system required to stop cheats at any stage of the ladder, including the Finals.
  
  Examples of these may include combinations of: (But not limited to)
  
  • VAC;
    
  • HLGuard;
    
  • Cheating Death;
    
  • Screenshot applications;
    
  • AMX;
    
  • Player submitted demos.

Rules
GameArena reserves the right to:

• Modify the rules as needed at any time it sees fit to do so.
  
• This includes changes due to software updates or releases, Ladder Administrator decisions and all other changes deemed necessary to the ladder.
  
• Teams should check the rules on a regular basis and prior to every match to ensure they are in complete compliance.
  
• Teams must understand that the rules listed are guidelines that GameArena will use to try and ensure fair and competitive play and are subject to interpretation by the Ladder Administrators based on the spirit of the rule and game.
  
• Where no specific penalty is stated, teams that break the letter or spirit of the rules may have their members banned temporarily or permanently from GameArena and its services, and/or the team forfeited, demoted or deleted and/or all members banned from playing the remainder of the season.
  
• Ladder Administrators have final discretion on whether a rule has been broken and what penalty, if any shall apply.