 |
 |
|
| Conditions for CSS 2v2 Open Ladder #6 |
Ladder Type
If this is a restricted ladder then registration closes as soon as the competition opens. Otherwise registration can take place at any time. |
open |
Competition Opens
The date the competition opens |
11-01-2010 12:01 |
Competition Closes
The date the competition closes |
08-02-2010 11:59 |
| Total Prize Pool |
$0 |
Rounds per match
The number of rounds that must be played per match |
2 |
Report Timeout
The number of hours before matches are automatically confirmed |
24 |
Max Number of Teams
The maximum number of teams allowed on this ladder |
999 |
Min Number of Teams
The minimum number of teams that must be registered before competition opens |
10 |
Max Team Size
The maximum number of players allowed in the team |
4 |
Min Team Size
The minimum number of players allowed in the team before matches can be played |
2 |
Challenges Open
The time each day that challenges can start |
16:00 |
Challenges Close
The time each day that challenges close |
8:00 |
Score Method
The method used to calculate the team ratings |
Elo ( explanation ) |
Matches Per Week
The number of matches a team can play per week |
6 |
Allow Clan Challenges
Whether teams from the same clan can challenge each other |
1 |
Max Clan Teams
The number of teams from the same clan allowed |
6 |
|
|
1. Team Numbers
Teams consist of up to 4 players, 2 of which are allowed to participate in a match.
2. Substitute Players
You may make substitutions during a match, but only during the half-time team swap. In the case of a disconnection or dropout during live play, a substitute may join immediately. At no time during live play can a team exceed 2 players.
3. Minimum Players to start
A period of 10 minutes is allowed after the scheduled start time of the match for players to connect. Provided that each team has at least 1 player, the match must commence at this time. If a team does not have at least 1 players at the end of the 10 minute waiting period, that team forfeits the match. The 2nd player may join the server at any time.
At the half-time team swap, teams are allocated a maximum of 5 minutes for teams to switch sides and organise themselves before the 2nd half is to commence. Teams must have 1 or more players after the 5 minute period for the second half to commence, if a team has less than 1 player, that team is deemed to have forfeit the match. The 2nd player may join the server at any time.
If at any time during live play a team drops below 1 player that team is deemed to have forfeit the match.
4. Server Crash/Close
If a match is unable to be completed (first to 16) due to the server booking running out then the match is to be disputed and a ref will issue a void for the match.
If a server crashes, a league referee must be informed immediately using the Gamespace
Chatbox. If either a referee cannot be contacted or the server issue cannot
be resolved, both teams must dispute the match. This will enable the referees
to void your match.
5. Player Registration (Team)
All team members participating in matches have to be registered on the team page for a given clan before the match commences. Using last minute substitutes (slutting) that are not registered with the team can warrant a forfeit if disputed by the opposing side before the results are finalised.
6. Player Registration (SteamID)
All players listed on the team page must have their SteamID registered in their Gamespace forums account. Any disputes arising where a SteamID can not be verified will be awarded to the disputing team. (Regardless of if they played or not).
7. Terms and Conditions
All players are required to adhere to the existing Gamespace Terms and Conditions in addition to the rules outlined here. Teams found to be in breach of any of these policies may be removed from the league at the Gamespace Staff and Senior League referee's discretion.
8. Challenges
The challenging team must provide the defender with 3 time/date options for the proposed match together with 3 map options. Teams must not purposefully offer match times where no server is available. Teams found trying to manipulate challenges may receive a penalty in the form of an ELO point deduction.
Teams are encouraged to focus the majority of challenges against teams surrounding their position on the league.
Teams are not to deliberately avoid matches from other teams close to their rank in the league in order to accept matches from teams much lower than themselves.
All times are AEST (GMT+10:00 Australian Eastern Standard Time). Except when AEDT (GMT+11:00 Australian Eastern Daylight Time) is in effect.
9. Accepting a challenge
The team that accepts the challenge will choose the map and the date/time for the match.
Teams must not refuse to accept challenges from similarly ranked teams in order to protect their ranking. This practise is often called "challenge dodging" and is considered challenge manipulation. Teams that believe that they are being dodged are to follow the below process:
1 - Create a thread in Leagues & Competitions asking the team involved for prefered dates and times to schedule a match
2 - PM the captains of the team involved with the link to the thread
3 - If a match cannot be organised within a week, league refeere's are to be notified
Teams found trying to manipulate challenges may receive a penalty in the form of an ELO point deduction.
Teams must, within reason, respond to every challenge. If a team is unable to accept a challenge, they should respond with a polite rejection message detailing why they were unable to accept the challenge.
10. Matches
Teams are committed to attending their organised matches. If a team cannot make one of their matches, they must attempt to inform their opponent.
There are to be no more than 2 teams participating in each match, with 2 players representing each team. Rounds will be 1 minute 45 seconds long, with up-to 2 halves of 15 rounds per side.
The first 15 rounds are played and then the teams swap sides and up-to 15 more rounds can be played. The team that reaches 16 or more rounds won is declared the winner. If however both teams score 15 rounds each then the result should be entered as 15-15. A draw is a valid result, no overtime rules are to be played.
11. Choosing Sides
At the start of each match the team that issued the challenge receives first pick at which side they wish to commence. Alternatively, and only if both teams agree, this decision can be made through a process of knives only round, with the team that wins getting the first pick. If a team runs away to avoid being killed before the time runs out the chasing team wins the knife round.
12. Results
Responsibility of entering correct results belongs to both teams. Each team gets one chance to enter or contest (dispute) a result after the match. Once the score has been entered by the winning team, the opposition has 24 hours to either accept or dispute. Once 24 hours are up (from the point of the scores being entered) and the score is neither contested nor accepted by the other side the results will be automatically confirmed by the league system. Furthermore, the moment match scores have been confirmed the scores cannot be altered under any circumstances. The onus to ensure correct results are ALWAYS and ONLY rests with the teams participating. Registering a dispute after a confirmation will be ignored.
See results and dispute guides here.
13. Cheating & Exploits
Cheating is when any team is given an unfair advantage over another team in the league; teams found to be cheating in-game will be punished including possible disqualification from the league. Individuals caught cheating may also be subject to standard Gamespace incident reporting procedures, which may result in network-wide bans.
Cheating can be in the form of incorrectly reporting results, using any bugs that may exist in the league software or using in-game tricks which change the way the game is supposed to be played.
'Hacking' is also a form of cheating, however Gamespace applies a Zero-Tolerance policy towards hacking in all forms. Any players caught hacking will be permanently banned across all Gamespace servers; teams who knowingly allow a fellow team-member to hack may also be removed from the league; Clan Leaders/Co-Leaders and Team Captains/Co-Leaders who are caught hacking will draw a more servere punishment in the form of Clan or Team disbandment.
Map exploits are not to be used under any condition. This means walking on secret ledges, skywalking, using unfair vantage points (looking through/over walls, etc), killing hostages as Terrorists, etc. This also includes so called "easter eggs" that change the server settings or provide advantages that would normally be an exploit. The secret room on de_cpl_mill is an example of this. Players are however allowed to perform boosts.
Bunny Hopping is not permitted as it is considered a game exploit and is a form of gaining an unfair speed advantage. If you continuously jump on flat ground without stopping, resulting in a speed advantage, then you will be punished for gaining an illegal form of speed advantage. Note that doing a long jump or a sideways jump in and out of cover, for example, is acceptable and legitimate, as long as you don't jump continuously, resulting in a speed advantage. The only exception to this rule would be if you jump down a slope (such as the middle ramp near CT spawn in de_cbble or in the underpass in de_dust) and then stop jumping once you get to flat ground. In this case, you are considered to be momentum jumping, not bunny hopping, therefore are not breaking this rule. However, if you continue to jump once you get to flat ground and gain a speed advantage, then you will be seen as bunny hopping and therefore will be punished for breaking this rule.
Silent bomb plants are illegal. The bomb must be planted in a accessible location, using exploits to plant will result in a forfeit.
When defusing the bomb, players must be able to see the bomb to defuse it, defusing through an immovable object is illegal. Defusing on the ramp on de_dust2, for example, is an illegal defuse.
Registering a fake SteamID (eg: STEAM_0:0:123456) in a players Gamespace forums account will be deemed to be a player deliberately trying to circumvent the anti-cheat provisions of these rules.
14. General Behaviour
To ensure good sportsmanship, we require the following rules of conduct to be adhered during all matches or when setting up challenges. Teams breaking these rules will be issued a warning. Teams issued with multiple warnings will result in the team being removed from the league. The following are the rules which must be obeyed at all times:
1 - All disputes and disagreements need to be aired before a match goes live or after the game using the correct process.
2 - During a match players will not engage in disputes and will refrain from using global say once the game has gone live.
3 - Players must refrain from displays of contempt or discrimination during challenges or matches.
4 - Any interruptions mid game (map change etc) using rcon by either side, unless consented by the other team will warrant a forfeit (loss) to the team responsible.
If it is a team captain or co-leader that breaches these rules it may result in the team being removed from the league at the league Referee's discretion.
15. Rates, Scripts and other settings
Altering of rates and other settings is allowed. However altering these to cause the player to gain an unfair advantage such as ghosting or warping, will risk forfeiting the match. Ping masking will be treated as an automatic forfeit. Scripts will also be allowed. However using these to perform a task you would be unable to do without them is not allowed. eg. Anti-recoil scripts. All rate changes and breaches will be at the discretion of League Referees.
Zblock plugin is running on Gamespace League servers to aid in restricting settings.
Warmod plugin is running on Gamespace League servers.
16. Disputes
Any problems or disagreements will be automatically taken up with a league referee, when the "dispute match" option is selected on the reporting tool.
Lodging a dispute without supply the required evidence will be deemed frivolous. The dispute will be closed immediately and the offending team will be issued a warning. Teams issued with multiple warnings will result in the team being removed from the league.
Examples of frivolous dispute: LeetDude disputes his match
against AverageJoe. AverageJoe said “Good luck! :-)” after the
Live-on-3, and LeetDude keenly points out that this is a clear breach
of the rules. Whilst the action by AverageJoe was a breach of the
rules, the dispute by LeetDude is an obvious attempt to gain victory
through a technicality. This goes against the fair play approach of the
Gamespace League. OverworkedOp, when reviewing the dispute, is very
unhappy with LeetDude
Examples of frivolous dispute:UberNoob disputes his match
against ProGamer. UberNoob claims that ProGamer was hacking through
their match and that he should have the win. Hacking is a clear breach
of the rules. However UberNoob has not provided any specific detail to
support the claim that ProGamer was cheating. UberNoob has failed to
provide a copy of the autoref demo and failed to specific the tick
counts in the demo highlighting examples of what ProGamer was doing.
OverworkedOp, when reviewing the dispute, can see no evidence to
support the claims by UberNoob and is very unhappy.
Examples of frivolous dispute:IceTeam disputes his match against
HurriWang. IceTeam claims that HurriWang was using an unregistered
player and as a result the match should be awarded to IceTeam. IceTeam
provides a screenshot of the SteamIDs from the match. IceTeam however
has failed to check the SteamIDs against the Team List for HurriWang
and also fails to identify which player it was that was allegedly
playing unregistered. OverworkedOp, when reviewing the dispute, finds
that IceTeam did not investigate their claim themselves and as such is
very unhappy with IceTeam.
When a dispute has been raised, teams must converse in a constructive
and non-confrontational manner. This means that you do not under any
circumstances call people names or attempt too attach negative stigmas
to people’s actions.
Teams must respond promptly (within 24 hours) to any request from a
Gamespace Op. Players must not comment or involve themselves in a
dispute in which they did not participate.
17. Dispute evidence
Both teams are required to take screen shots of SteamIDs and both teams are responsible for verifying the SteamIDs in-game against the list on the specific team page in league before any dispute is made. Screenshots of the SteamIDs must be provided with every dispute, without failure, by the team who is disputing the match.
If the dispute is in relation to a non-registered player (slut) participating in the match, the team must specify the alias of the non-registered player. This evidence must be posted within 24 hours of registering the dispute.
If the dispute is in relation to hacking/cheating, the disputing team is required to review the demo and PM a league ref the ticks and the alias of the suspect player(s). In the event the auto-ref demo does not appear then the match results will stand. This evidence must be posted within 48 hours of registering the dispute.
18. Warning System
There will be a warning system in place. Teams will accumulate warnings for breaches of the Gamespace Terms and Conditions,
these rules and/or making frivolous disputes. Warnings will be issued
via PM to the captains of the team. A team receiving 3 warnings will be
removed from the league, however serious breaches may result in a team
being removed immediately.
19. League Length & Team Activity
Teams must, on average, play the equivalent of one match per fortnight to remain ranked on the ladder. The ranked status on the ladder will be increased by 2 matches for each calendar month on the ladder.
Example:
Ladder Opens - 1 match to be ranked
End month 1 - 3 matches to be ranked
End month 2 - 6 matches to be ranked
End month 3 - 9 matches to be ranked
20. Spectators
By playing in this league you agree to have your match spectated and recorded by SourceTV, which will be available for public download. Spectators other than those via SourceTV, Gamespace Refs and Gamespace approved commentators are not allowed during matches. If an additional team member/spectator joins the match mid-game they must be asked by their team captain to leave the server. If the person spectating does not comply within one minute of the request, the opposing side (if they wish) can have match awarded to them using the dispute system.
21. Approved Commentators
Gamespace permits shoutcasting of any league match without prior consultation with teams prior to the match. All shoutcasters shall enter the server and be identified with the prefix 'CASTER' or with a prefix applicable to their organisation name. All teams participating in the league accept their matches may be shoutcast.
Approved shoutcast organisations:
Gamestah.com
22. Referees
Any teams can request to have a referee present during a match. Gamespace referees can join as spectators either at the start or mid-game onto any server during a match providing they are clearly identified. Gamespace identifiable by [GS] tags and their forum username. In order for other side to question the validity of a referee they must submit a screenshot and the steam id of the referee/admin in question. If the identity of the referee is found to be false, this can result in the forfeit of the side to be found benefiting and will result in that player being banned from Gamespace Network. In addition, all matches need to have a Gamespace Auto Referee present. The aim of this is to have a complete recording from each player perspective in case a dispute of the game is called. Removing the Gamespace Auto Referee from the server automatically voids the match.
23. League maps
de_dust2
de_inferno
de_nuke
de_aztec
de_cbble
cs_office
aim_akm4ruins2
awp_india_v2
blood_assault
24. Server Settings
Official Gamespace League CS:Source War Config (war.cfg) is to be used during all official Gamespace League matches. The GS War Config is loaded on by default on all bookable GS servers.
sv_lan 0
sv_unlag 1
sv_maxunlag .5
sv_minrate 15000
sv_maxrate 30000
sv_mincmdrate 66
sv_maxcmdrate 66
sv_minupdaterate 30
sv_maxupdaterate 100
sv_client_interpolate 1
sv_client_max_interp_ratio 1
sv_client_min_interp_ratio 1
sv_voiceenable 1
sv_gravity 800
mp_autokick 0
mp_spawnprotectiontime 0
mp_autocrosshair 0
mp_autoteambalance 0
mp_buytime .25
mp_c4timer 35
mp_fadetoblack 0
mp_flashlight 1
mp_forcecamera 1
mp_footsteps 1
mp_freezetime 15
mp_friendlyfire 1
mp_hostagepenalty 0
mp_limitteams 5
mp_maxrounds 0
mp_winlimit 0
mp_playerid 0
mp_roundtime 1.75
mp_timelimit 999
mp_tkpunish 0
mp_startmoney 800
sv_airaccelerate 10
sv_allowdownload 1
sv_allowupload 0
sv_alltalk 0
tv_enable 1
tv_delay 90
tv_autorecord 1
sv_cheats 0
sv_friction 4
sv_gravity 800
sv_maxspeed 320
sv_stepsize 18
sv_stopspeed 75
sv_timeout 65
sv_voicecodec vaudio_miles
mp_allowspectators 1
decalfrequency 60
host_framerate 0
setpause 0
mp_logdetail 3
log on
wm_active "1"
wm_max_rounds "15"
wm_max_players "10"
wm_play_out "0"
wm_auto_ready "1"
wm_half_auto_ready "1"
wm_auto_knife "0"
wm_round_money "1"
wm_min_ready "2"
wm_overtime "0"
wm_overtime_max_rounds "0"
wm_overtime_start_money "10000"
wm_match_config "mr15.cfg"
wm_live_config "lo3.cfg"
wm_knife_config "ko3.cfg"
wm_block_nightvision "1"
wm_bomb_frags "0"
wm_defuse_frags "0"
wm_ingame_scores "1"
wm_block_warm_up_grenades "0"
wm_rcon_only "0"
wm_global_chat "1"
wm_lock_teams "1"
wm_auto_swap "1"
wm_auto_swap_delay "3"
wm_auto_record "1"
wm_auto_kick_team "0"
wm_auto_kick_delay "10"
wm_damage "1"
wm_remove_deathcam "1"
wm_remove_deathcam_delay "1"
wm_remove_help_hints "1"
wm_remove_grenade_sound "0"
wm_remove_kit_bug "1"
wm_remove_kit_distance "100"
wm_remove_ragdoll "1"
wm_remove_ragdoll_delay "2"
wm_require_names "0"
wm_modifiers "1"
wm_stats_enabled "1"
wm_stats_method "2"
wm_save_dir "warmod"
wm_prefix_logs "0"
wm_upload_results "0"
wm_table_name "wm_results"
wm_t "Terrorists"
wm_ct "Counter-Terrorists"
zb_active "1"
zb_matchconfig "mr15.cfg"
zb_readyup_max "10"
zb_startmoney "800"
zb_autoupdate "1"
zb_doorfix "1"
zb_allowcashcalling "0"
mp_allowspectators 1
decalfrequency 60
host_framerate 0
setpause 0
mp_logdetail 3
24. Server Admin commands
Login to Admin
rcon_password "passwordhere"
Selecting Map
rcon changelevel "map_name"
OR
rcon changelevel "alais"
Alias's
d2
dust2
nuke
train
ferno
inferno
ferno
india
cbble
ruins2
akruins
blood
Server Announcement
rcon say "This is a test"
26. Participating in Gamespace Leagues
All Gamespace leagues are governed by the Gamespace Terms and Conditions,and the rules defined here; by participating in this league you are agreeing to all of these documents. Teams found to be in breach of any of these policies may be removed from the league at the Gamespace Staff and Senior League referee's discretion.
The Gamespace Staff and the League team reserve the right amend or modify these rules at any time throughout the duration of the league. |
|
|
|
