| STA CSX Rules |
I. Introduction
II. Terminology
III. Scheduling & Match Results
IV. Server Settings
V. Match Play
VI. Playoffs
VII. SourceTV
VIII. Mercy
IX. Member Rules & Substitutions
X. Conduct
XI. Ping Imbalance
XII. Disputes
XIII. Suspensions & Ejections
XIV. Cheating
XV. Entrance & Retention
XVI. Clans With Multiple Teams
XVII. AntiCheating Software
XVIII. Screenshot Rule
XIX. Division Format
XX. Caveat
XXI. Rules Amendments
XXII. STA-CSX Map Rotation
XXIII. Edit History
I. Introduction
Welcome to STA-CS:S, Stronger Than All's Counter Strike: Source league.
STA-CS:S was previously titled STA-CSX. The name was changed to reflect the league's transition to Counter Strike: Source match play. In order to appreciate the spirit of this arena, an understanding of its predecessor is in order. STA-CSX was born from the ashes of STA-CS, which was destroyed by cheaters and clans that couldn't act like professionals. With that in mind, the rules for STA-CSX were designed to ensure that everyone has fun and that matches are as fair as possible. They are very detailed and objective and will hopefully cover all contingencies. STA-CS:S continues the tradition established by STA-CSX.
STA-CS:S currently uses only defusal maps for match play. Maps are nominated for a vote by consensus of the administrators; in particular, certain maps are EXCLUDED (also by consensus) due to poor design. Once a map is nominated by the admins, clans will decide via a vote if the map will be included in the rotation. E-mail the appropriate admins with any questions, comments, and/or future map requests.
II. Terminology
Battle: Any of the 'individual periods' during game play. A battle is worth one point for either team.
Round:A round is a fixed number of battles (currently 15) played on one server.
Match: Two rounds, or more if overtime rounds are necessary.
Offensive Team: Team that plays offense for map in question. For defusal maps, terrorists are the offensive team.
Defensive Team: The team that's not the offensive team (counter terrorists for de_ maps).
Home Clan: Any clan listed first for their match on the schedule. (i.e., if match says ABC vs. DEF, ABC is home clan)
Away Clan: The clan listed last for their match on the schedule page.
Serving Clan: The clan who is in control of the server that is currently being used.
Nonserving Clan: The clan playing opposite the serving clan.
Forfeit: A match result recorded as a loss, often due to a failed dispute, poor sportsmanship, or lack of attendance. May result in suspension or ejection.
Technical Forfeit: Both clans receive a loss for the match in question.
Nulled Match: Neither clan is awarded a decision for the match. It's as if the match never happened.
Bye Week: A week during which a clan is not scheduled to play a match. These occur either because there is an odd number of clans in a division or because of extenuating circumstances (in case a clan requests it).
Messagemode 1: Public talk on a server, i.e. that which is heard by both your team and the other team. Associated with the 'say' command.
Messagemode 2: Private talk on a server, i.e. that which is ONLY heard by those on your team. Associated with the 'say_team' command.
Standard Scoring: 2 rounds of fifteen 2.5 minute battles. Scoring is wins/losses.
III. Scheduling & Match Results
Only the winning clan will be REQUIRED to post their scores. However, if the losing clan intends to dispute the match, or wants to submit scores they can. Results MUST be posted by 11:59 est on friday.
Clans play at the time designated by the schedule page.
The default times are:
Alpha Division: 9:30pm EST on Thursdays.
All results for matches should be submitted immediately after match completion. Admins have the option of disregarding any match results not received by 11:59pm EST FRIDAY, unless the match in question was rescheduled for Saturday or later. Only the winning clan will be REQUIRED to post their scores. However, if the losing clans intends to dispute the match, or wants to submit scores they can. If the winning clan does not report the scores and the losing clan does the scores posted by the losing clan will be considered valid! If neither clan reports the match by 11:59 est on friday the match will be a technical forfeit and the winning clan could face possible disciplinary action.
Clans are scheduled based on some of the following factors:
* current rank (win/loss record)
* previous opponents
* win/loss streak
* number of matches played
* recent margins of victory
STA-CS:S will endeavor to schedule opponents that clans have not played in the previous two weeks (and further back if at all possible).
Reschedules
Clans may reschedule a match any time prior to the default Thursday time without the permission of an admin. In the event of a reschedule later than the default time, an admin must give permission for the reschedule. We highly discourage reschedules later than Friday, so think ahead if you can't make the default Thursday time.
IV. Server Settings
Each clan will have a choice of their own server for a round. The home team will choose which server is for the 1st round (see Home Team Advantage below for details).
Servers must be in the United States or Canada unless both clans agree to a foreign server. Clans must have servers located in the Eastern or Central Time Zones.
All servers must have the correct map version for the map assigned. Use of the STA-CS:S configuration file is mandatory. In addition, servers must have the latest publicly released version of Counter Strike: Source, unless a specific exception is made.
All servers must be dedicated CS Source servers. Listen servers and standard DSL or cable modem servers are not acceptable under any circumstances. Uncapped cable modems or SDSL servers may be approved for match play after inspection by an STA-CS:S admin. Players' rates should not be higher than 25000. Server variable sv_maxrate should set at a value between 20000 and 25000.
If any of these settings are not correct, the opposing clan may refuse to play the round on that server. Failure to correct the problem(s) within 15 minutes of the start of the round will result in a forfeit for the transgressing clan.
The following settings may be changed if both clans agree to the changes. If no agreement is made, default settings will be used:
Default:
* 5 on 5 match (minimum number of players per team: 4)
* assigned map
* mp_roundtime 2.5
* sv_maxrate 25000
* mp_maxrounds 15 (can be set to zero or greater than 15 to avoid map cycling between rounds if both teams have agreed to play their entire match on one server)
Challenging Server Settings
Server settings may only be challenged during prematch (i.e. NOT after the match, once the match is played, there are NO DISPUTES over server settings). It is the responsibility of the serving clan to maintain the integrity of the server settings during the match. If the serving clan (taken to mean the clan that is in control of the current server) is not using default or agreed-to settings during prematch, they have 15 minutes from the match's start time to correct their problems or forfeit the match.
If, during the match, the server settings change, then the nonserving clan MAY challenge the server settings. In this case, the following actions will be taken:
If the serving clan provides proof that both clans agreed to the new settings, then the nonserving clan forfeits the match. However, if the serving clan cannot provide proof of an agreement to change settings to the disputed settings, then the serving clan forfeits.
Personal Demos are REQUIRED for all match participants unless it is agreed upon by both clans not to record. If the clans agree to not record they, however, cannot dispute the fact that the other team does not record demos.
V. Match Play
** The Home Team Advantage
Home clan will choose which clan's server to play on first. If there is only one server available among the two clans involved, then each clan will play one offensive round and one defensive round on the server. If 2 servers are available the home clan will play offense on the home server and the away clan will play offense on the away server (offense is Terrorist on defusal maps). Note: teams may always agree before starting their match to play all rounds on a single server, but, this must be established prior to starting the match.
Pre Match
Clans must have all match information - server locations, times, order of server, passwords - exchanged at least ninety minutes before the scheduled match time. This way, if one clan decides to no-show, the other clan can still attempt to salvage their evening.
Clans have 15 minutes after the default time, or the mutually agreed to time (see rescheduling above), to join the server. Failure to comply will cost the offending clan a forfeit. Under extraordinary circumstances, such as connection problems for a majority of members, STA-CS:S may allow an exception. If there is an error caused by the in-game server browser, clans are required to attempt to connect to the server in question via a different method, e.g. GameSpy, HLSW, Xfire or the /connect console command.
All clans are expected to be ready to play at the default time. Clans should send a representative to the #sta-css IRC channel on gamesurge to avoid disagreements and potential problems. If a clan cannot be contacted as of scheduled match time, then that clan will forfeit.
During prematch, when the initial joining begins, NO shooting or hostage touching is permitted. Players that have joined the wrong team must switch.
If anyone is killed during prematch then the map is to be restarted using the mp_restartgame command. This cycle will be repeated as needed. If a player repeatedly kills others during the prematch, he may be kicked from the server. If players from a team persist in killing during prematch, then that team will forfeit the match and the clan may be suspended or removed from STA-CS:S.
The first battle will go until both teams acknowledge that they are ready to begin match play (clan leaders can do this via mm1), after which the server operator must announce "Next restart is live!" and issue the mp_restartgame 10 command. This way, neither team begins with any score or money advantage. Live game play begins after the mp_restartgame command takes effect. Note: Clans may opt to instead use a "Live on 3" configuration file to automate the beginning of matchplay rather than executing commands manually.
Finally, during prematch, both the serving and nonserving clans should check server settings to verify that they are correct. Failure of the serving clan to correct settings problems will result in a forfeit for the serving clan. See the Challenging Server Settings area above for more information.
Match
Either participating clan may refuse to start the match until no later than 15 minutes after game time, but only if the refusing clan was present at scheduled match time (i.e., they may not show up late). At this time the match starts, or the refusing clan forfeits.
Only leaders are allowed to use messagemode1 (public talk) during a match. This includes mm1 while in ghost mode. Excessive mm1 spamming may be grounds for forfeit loss. However, clans will not be penalized if they are on friendly terms and choose to chat during the match. Understand that if your team opts to talk during the match and the opposing team is NOT on good terms (or on talking terms) with you, then you could be penalized.
If the server crashes during play, all battle wins up to the point of the crash will be counted. The serving clan then has 5 minutes to revive their server. If the server cannot be revived in time, play will move to the opposing clan's server. There, the remaining battles will be played; this includes the remaining battles from the interrupted round plus any battles from rounds yet to be played. Make sure that clans join the right sides of the map. For example, if clan A is T and B is CT on A's server, and A's server crashes with 6 battles played, then the remaining 9 battles for that round will be played clan A on the T side, regardless of what server the round is completed on.
Good rule of thumb:
Each clan must play 15 rounds as terrorists and 15 rounds as counter-terrorists (not counting overtime)
In the event of a server crash, clans are encouraged to find a mutually acceptable solution, in accordance with the rules above. If none can be reached, an STA-CS:S admin will issue a ruling.
Once a match has begun, there is no challenging of server settings. If setting change DURING a match, the visiting clan will earn a forfeit win.
If you are a victim of a problem with ping that violates the ping rule, you should follow the procedure laid out below in Ping Imbalance.
Ties:
There can be no ties in STA-CS:S matches. If a match is tied after two rounds of 15 battles , then pairs of rounds will be played until the tie is broken. Each of these overtime rounds will have 5 battles; i.e. mp_maxrounds should be set to 5 for OT rounds. Additionally, the starting money value should be increased to 10000, i.e. mp_startmoney = 10000. Otherwise, these overtime rounds will be played just as the initial rounds are. CT/T status and server choices alternate. For example, if clan A started as Ts on clan B's server, then the first round of any OT round pair will have clan A playing as Ts on clan B's server once again (and clan B will hence play as CTs on clan A's server). For the overtime rounds, a prematch is not necessary; however, if a prematch is not played, no disputes with regard to match timing will be considered. Clans may use this non-prematch privilege at their discretion, for OT rounds only.
Also, All clans should have the STA overtime config (sta_ot.cfg) available on their server in case
overtime is needed. The 2 Changes in this config are mp_maxrounds 5 and sv_startmoney 10000. Changing the listed cvars manually would also be allowed after running the standard STA-CS:S config (stamatch.cfg) and then changing mp_maxrounds 5(can be greater) and sv_startmoney 10000 before going live.
If a pair of overtime rounds is scheduled too late, a clan may ask an STA-CS:S admin to get both clans to reschedule the overtimes for another day. Should this issue be brought up, an STA-CS:S admin will judge the degree of lateness and make a decision accordingly. In the event of a reschedule, overtime rounds will be played as indicated above, with respect to where the clans left off.
One note: If your match is entering a third overtime period, then you may reschedule the remaining rounds; if the opposing clan has trouble rescheduling, an STA-CS:S admin will make a ruling.
Forfeits:
If a clan shows up with 3 or fewer members in a standard match and fails to reach the required 4, they have until 15 minutes after the agreed start time to do so before they forfeit the match. If only one clan is present at an agreed-upon match time or on the default night at match time, it will be considered a forfeit for the clan that is absent. See more about forfeit conditions below.
Post Round/Post Match
After the first round is completed, clans are allowed to take a 10-minute break and head back to IRC. Clan leaders should meet, in #sta-css if necessary, to exchange info regarding the second round (server, etc.). After the match is complete, THE WINNING CLAN is to go to the scores submission page to fill out the match form. This form should be filled and submitted immediately following the match. The Losing clan can submit scores and MUST do so if they intend to dispute the outcome.
Match Scoring
The numbers of battles won by each team over the course of the first two rounds and all required overtime rounds are compared. The team with the most battle wins is awarded the win for the match, assuming no disputes or other circumstances arise.
VI. Playoffs
Playoffs will be played with the top teams, top teams are decided by the rank on the website. For the final match an STA admin must spectate the match. Also match will be played on a netural server pick by and an STA admin. After Final match it will be a must to submit all demos for review.
STA Keeps registration open during the season so teams that have need added after week three will not participate in playoffs. Also After week 6 the rosters will be locked.
VII. SourceTV
SourceTV
SourceTV is allowed for use in STA matches. The team providing the server must use the offical STA SourceTV Config.(STA_csstv.cfg) Source TV must also at all times be set at its maximum delay. SourceTV is still under development so the non-serving team may request SourceTV to be disabled or turned off. The Serving or hosting team must accept the request and disable SourceTV. (tv_stop)
VIII. Mercy
When a clan has passed the point of being able to win, they may request "Mercy" from the opponent and end the match. All remaining rounds are credited to the victor. Please note, this is entirely at the discretion of the winning clan and they do not need to grant mercy. If a losing clan drops from the server without agreement, they will earn a forfeit loss by dispute (see disputes) and may face disciplinary action.
Conditions
Once a clan has lost 16 battles, they may request mercy.
IX. Member Rules & Substitutions
STA-CSX will not tolerate ringers or multi-clanners. A ringer is any person playing for a CSX clan they are not currently a member or recruit of. A multi-clanner is any player currently in a CSX clan participating in the STA who belongs to another CS clan, whether or not that CS clan is currently participating in STA.
In order to be as effective as possible in stopping the above mentioned problems, STA controls clan rosters which include player name and STEAM ID. Only players listed on our roster are eligible to play in matches. Rosters may be edited on Sundays only.
Additionally, if a CS "club" exhibits organizational structure like a clan, i.e. has leaders, schedulers, match records, and the like, then for the purposes of our rules, it will be considered a clan, and players may be punished accordingly. So-called "clubs" - with members from several clans - are not eligible for entrance into STA.
Punishment for the first offense will be forfeiture of the match in which the ringer/multi-clanner played. Further offenses will result in ejection from STA-CSX.
Addendum for disputes regarding roster violations:
Roster disputes will be handled much like server setting disputes. They must be handled during prematch. All player names and STEAM ID's are to be checked during prematch for all starting players. Both teams must agree on rosters before the match is begun. In the event of a substitution, the subs name and STEAM ID should be checked immediately after the half is over. If it does not match, STA officials should be contacted and the match will be ruled a forfeit against the offending clan.
If a substitute is not listed on our roster and is playing in an STA competition with your team, you are in violation. PERIOD. "I forgot to add him" is not a valid defense. You are a professional, update your roster.
Substitutions
In game substitutions are allowed, providing the following conditions are met:
- You cannot willfully substitute out players that disqualified another server due to ping.
- No more than 6 players from your clan can be connected to the server at once. If the player that is to be substituted for is timing out, that player must disconnect/drop before the new player comes in. Rule of thumb: sub out before you sub in.
X. Conduct
Clans are expected to conduct themselves professionally at all times, both in game and out.
Nuking, channel takeovers, spamming, crashing a match server, or any other form of denial of service will not be tolerated. If it is proven that any clan has engaged in the above activity, that clan will be REMOVED from STA-CSX immediately. There is ZERO tolerance for this type of behavior. Adequate proof in the form of screen shots, demos, and server logs must be provided to STA-CSX before a ruling is made.
STA-CSX Admins will have final say on punishment.
Cheating of any form is prohibited in STA-CSX. (see Cheating section)
If it is found that cheating occurs, notify an STA official and proper punishment will be decided on. Make sure to have proof. Proof may include demos and console logs. If your clan claims that another clan has cheated and cannot supply enough evidence to substantiate the claim, then the claim will be discarded. Spurious accusations of cheating will be considered a violation of proper conduct and action will be taken against the accusing clan.
Precautions that can be taken by an STA-CSX Coordinator if individuals in a clan have been suspected of cheating are:
1. An STA-CSX Coordinator must be given rcon to check IP addresses during a match if it is deemed necessary by the Coord.
2. Both sides may be asked to submit in-game screen shots during the match or at any time the STA Coordinator feels suitable. Although there is no screen shot rule, it is in your best interests to do so.
Sportsmanship
Clans that have sportsmanship or conduct issues will be treated harshly. Poor sportsmanship will typically result immediate ejection from STA CSX. Activities that would warrant this consideration include excessive mm1 spamming (in-game), and public defilement of other clans. Keep in mind that sportsmanship covers issues not specifically addressed here and admins will use their best judgement on these issues.
External Communication Programs
Use of external communication programs such as Ventrilo and Team Speak
Admins
Members of clans in STA-CSX will treat STA-CSX staff with respect at all times. Admins will treat members of clans with respect as well.
Staff volunteer their time and effort for this league; if you fail to respect them, you will no longer play for STA-CSX. Without clans, there is no league, and administrators will treat clans with respect, even when disputes arise.
XI. Ping Imbalance
There is currently one regulation with regard to ping imbalance. The matter has been considered in detail; any concrete, detailed rule that regulated ping balance would yield more problems than it solved.
Each clan is entitled to their choice of server provided that no more than two of the visiting clan's players have a ping of over 250 ms. This rule will be applied on a case-by-case basis at the discretion of the appropriate coordinator or administrator.
Additionally, note that if a server is disqualified under this rule, those players that pinged over 250ms should play on whatever server is used as an alternate for the disqualified server. If a clan brings in lagging players for the purpose of disqualifying a server, they will be punished for poor sportsmanship.
Ping Problems During Match
If your clan has a ping problem during match, you should contact an admin ASAP (IRC is the only definite real-time way you can do this). This should only happen if the ping rule is violated for a considerable length of time, i.e. more than one battle.
XII. Disputes
In the event of a dispute, both clans involved must submit claim packages to their division coordinators for review. A claim package is a precise representation of a clan's claim that the opposing clan's actions warrant a forfeit loss for that clan. Claim packages must include:
* rule violated by opposing clan, as quoted from this document
* how the rule was violated by the opposing clan
* proof that the rule was violated as described - proof may be in the form of server logs, e-mails, ICQ logs, IRC logs, (in-game) screen shots, or in-game demos
For any one dispute, each clan involved may submit no more than four claim packages. Division coordinators will evaluate the submitted material and the result will be one of the following:
* technical forfeit - both clans earn a loss
* forfeit by dispute - one of the two clans involved will earn a win by forfeit; the other will earn a corresponding loss
* nulled match - neither clan earns a win or loss
The transgressing clan (only in forfeit by dispute case) may be suspended or ejected if its division coordinators deem it appropriate due to the situation at hand.
Note: YOU must take the initiative and submit evidence to us. Do NOT ask us to e-mail you for evidence.
Real-Time Dispute Handling
If a dispute must be handled immediately, the disputing clans should send ONE representative to IRC channel #sta-cs on irc.gamesnet.net. There they may contact their division coordinator or disputes handler, as listed on the STA-CSX contacts pages. If there is no STA official able to handle the dispute at the time, clans must follow the outline given above.
Rules & Rulings
During match night, any STA-CSX coordinator may handle your dispute, providing that coordinator is not in your clan and does not have a clan in your division. Once a dispute is settled, you may not appeal the decision with another admin. If you believe you were penalized due to an unfair ruling, contact the STA-CSX League Administrator, but be prepared to justify your case. Clans will be punished for poor sportsmanship if they abuse this privilege, e.g. in hopes of a ruling reversal when the ruling was valid. If a dispute is not covered by the rules, a committee of admins will issue a ruling that upholds fairness and the spirit of the rules.
Important: If there is a dispute during a match, STA must be notified BEFORE the match is over. Once a match is played, both clans have signified that they agreed to the server and server settings. Hence, the match result will stand unless it is discovered that there were extenuating circumstances of some kind.
Note that for all disputes, clans are encouraged to find mutually acceptable solutions without the aid of an STA-CSX official.
Addendum:
Any clan entering a dispute without proof will be subject to disciplinary action under the sportmanship clause.
XIII. Suspensions & Ejections
A clan is marked as suspended if any of the following conditions occur:
* clan is going inactive and has requested the suspension
* clan forfeited most recent match
* clan has violated rules (severe manner but not enough to warrant ejection - e.g. first offense) and its division coordinators have agreed to suspension.
Suspended clans are not scheduled for play. Division coordinators may deny a clan's request for suspension. Any clan that is inactive for one month will be removed from STA. They may later request reinstatement; such requests will be handled on a case-by-case basis.
A clan is ejected from the STA-CSX league if any of the following conditions occur:
* clan has not contacted their division coordinator after having been suspended for at least one week due to forfeit rule (see above)
* clan has violated rules (severe infraction) and its division coordinators have agreed to ejection
Charlie clans may be dropped at any time for any reason. As a member of a Charlie Division, you are a probational member of STA-CSX.
Coordinators may agree on suspending or ejecting a clan for reasons not outlined in this document.
XIV. Cheating
Cheating of any type is not permitted in STA-CSX. Cheats include, but are not limited
to:
* gl_alphamin exploit
* "silent run" scripts
*speed exploit
* fullbright command
* pitch adjustment scripts (defunct as of CS beta 6)
* transparent texture override
* models that extend beyond reasonable bounds (a.k.a. hacked models)
* any mechanism by which information that is not normally available to the player is obtained
(e.g. aim proxy, RW eavesdropping, observing LANed players)
NOTE - this includes ghost recon. STA-CSX defines ghost recon as floating
("ghosting") in the map while dead and broadcasting enemies' positions to living teammates via external communication programs. This action is prohibited in STA-CSX. To assist in the enforcement of this rule, the sta server config enables "forced chase cam 1" mode. Additionally, STA-CSX does not permit the use of custom models. These include, but are not necessarily limited to, player models, weapon models, and hostage models. The only exceptions to this rule are that players may replace the v_*.mdl files with their own; these are the models for the weapons as you view them while holding them.Keep in mind that there might be cheats NOT explicitly mentioned here. Clans are required to use proper judgment in deciding what exploits and/or bugs are considered cheats. Feel free to ask an STA-CSX administrator if you are in doubt. Clans may be punished for cheats not mentioned here. If it is somehow determined that a clan is cheating in league play, that clan will be removed from the league immediately and permanently.
Map Exploits
Players may not move hostages to any place where a lone CT is unable to access the hostage*. Players may not use "hostage jumping" as a means to get to otherwise inaccessible sections of the map being played. Players may not "swim" (enter sky brushes) on any map. There may be other exploits not covered here; while they may not fall under the category of cheating, they may be considered violations of proper sportsmanship. Disputes will be handled accordingly. (Again, use proper judgment.)
Examples of Exploits
Defusing the bomb from under the train(de_train) while the bomb as been planted on top of the train car is illegal.
It is not legal to intentionally cover a planted bomb with objects so as to make the bomb undefusable.
* Despite the hostage rule, on de_* maps players MAY boost each other and plant the bomb where it cannot be reached by a lone CT.
Grenade Tosses
Grenades may not be tossed over any wall that is supposed to be the top of the map. As always, if you have a question regarding a wall in a map please contact and admin. This rules has changed since 1.6. An example is in 1.6 flashing over the walls in b on dust2 was illegal because the nades were going through what was designed to be the ceiling. On source this is now legal because by design the same wall has no intended ceiling. This rule will effect maps as they are released for source.
XV. Entrance & Retention
The Entrance Process
This is detailed in the information section of the site.
Requirements
The following are requirements for clans that wish to join STA-CSX. Any clan that applies for entrance must meet these requirements, or entrance will be denied without notice.
The clan must be in good standing in the CS community. No cheaters or unsportsmanlike clan will be invited to STA CSX.
The clan must supply:
* game server IP address
* clan web site
* clan name
* clan tag
* contact information: The member of the clan in charge of coordinating matches and representing the clan (not necessarily the leader) must supply nickname and at least 2 of the following 3: e-mail address, ICQ UIN, clan IRC channel & server.
Clan web sites must have a posted roster. Additionally, the clan must have at least 6 members on their posted roster. If possible, the clan should also supply a second contact, and IPs/ports for any CS servers they have access to. All contacts supplied must be able to effectively coordinate matches and communicate with STA-CSX in the event of a dispute or other event warranting communication with the league. Additionally, all inter-clan communications (e.g. rescheduling requests) are to be done between the contacts listed on the STA-CSX site, unless a division coordinator or administrator grants a specific exception.
Any clan that enters must operate or have administrator access to a CounterStrike server that meets our requirements, and must note this on their entrance application. Clans that demonstrate that they do not understand (or did not read) these rules will be denied entrance.
Retention
A clan must meet the above requirements in order to remain in the STA-CSX league. If a clan is suspended and does not contact the league within one week of the suspension, then they will be removed.
Additionally, any clan in CSX that demonstrates that they are not aware of the rules or standards by which we operate may be ejected without notice. We wish to keep this league as enjoyable and as efficient as possible, and we will exercise this ejection rule aggressively if we must.
Forfeit Rule
If a clan fails to get in contact with an opposing clan in time, or fails to show for a match on time with a sufficient number of players (as outlined above) then it will be ejected from STA-CSX without notice. The ejected clan may appeal STA's decision, but will have to wait a minimum of three match weeks to return. When this time is up, the clan will be evaluated for 'fitness' and a decision will be made about whether or not it is ready to reenter STA-CSX. Additionally, a ruling as to whether the clan's record will be reset or not, and what division the clan will go into will be issued.
XVI. Clans With Multiple Teams
The question of multiple teams under one clan has arisen on several occasions. A clan may submit more than one team for entrance into STA-CSX provided they meet the following requirements.
1. They operate as separate clans, with separate leadership and rosters.
2. They have separate web pages which clearly list which members are on each team. (although they may exist under the same domain name or server.)
3. They wear separate tags that clearly identify which members belong to which team.
4. They do not 'trade players' back and forth on a regular basis. Behavior such as this would violate the ringer rule and would meet with harsh consequences.
5. They each have their own CS server.
STA-CSX will continue this policy as long as we do not have problems with multiple teams.
XVII. AntiCheating Software
Current Requirements:
With the lack of Anti-Cheat support from valve at the time of these rules being written (2-7-05) clans are STRONGLY encouraged to record demos. If you agree to not record demos you cannot dispute for cheating unless absolute proof can be found in another way. However, if a clan is suspected of cheating they can be required by the admins to record even if the clan they are playing doesnt require it.
Once valve determines where their anticheat is headed and it is released it WILL be required for match play in STA-CSX.
*****Update: Valve's Anti-Cheat (VAC) is Required for all matches
XVIII. Screenshot Rule
It is encouraged that your members take screen shots, and it is in your best interests to have them do so. Screen shots are no longer required in STA-CSX. However, this rule may change if problems arise.
XIX. Division Format
All divisions are ranked. The Alpha Division is the main competitive area of this league. It is, for now, the only division in which titles are awarded and contested. The Charlie Division is the way new teams get into CSX. A clan has four match weeks in Charlie to prove themselves. At the end of those four weeks, they are either moved to Alpha or are removed.
Alpha divisions have title holders. Each week, there will be a title match and a title shot match. The titleholder and winner of the previous week's title shot match will match for the title. Title shot participants are selected from the remaining clans, usually those that have the longest winning streaks against the higher ranked clans in the division.
All STA-CSX matches are Friendly Fire ON.
XX. Caveat
We reserve the authority to rule according to our interpretation of the rules, should it be necessary. If a situation that needs a ruling is not covered by the rules, in whole or in part, then we will appeal to common sense and fairness, as well as precedence, in making a ruling.
XXI. Rules Amendments
Should a rules amendment be deemed necessary by any STA-CSX coordinator or administrator, it will be added and will be noted in the edit history section at the bottom of this document. Any member of a clan in STA-CSX may suggest a rules amendment on the STA-CSX public forum. Such an amendment must survive review by other clans and by the STA-CSX Council before it will be implemented here.
XXII. STA-CSX Map Rotation
DE Maps:
de_aztec
de_cbble
de_dust
de_vegas
de_prodigy
de_inferno
de_train
de_dust2
de_nuke
de_torn
de_storm
de_chateau
de_piranesi
de_rotterdam (custom)
de_celtic (custom)
de_legato (custom)
de_fang (custom)
CS Maps:
cs_assault
cs_office
cs_italy
cs_backalley
cs_assault2k
XXIII. Edit History
This section contains the history of rules modifications made after the rules were finalized on Thursday, June 28, 2001.
Friday, June 29th 2001:
1. Updated members section with clarification on roster disputes.
2. Minor wording changes to introduction.
3. Added definitions for Standard and CO scoring.
4. Added paragraph "Recruiting New Clans" to Entrance & Retention section.
5. Added new section "Mercy".
Wednesday, July 4th 2001:
1. Added section "Clans With Multiple Teams."
Monday, July 9th 2001:
1. Updated PunkBuster section to include the required Cvar.cfg
2. Changed rules to reflect that match results must be submitted within 24 hours.
Wednesday, July 18, 2001:
1. Changed "Home Team Advantage" to the old style where Home Team plays offense 1st round on the home server.
Saturday, Aug 11, 2001:
1. Added Charlie divisions.
2. Removed references to CO scoring.
3. Updated server settings section.
Friday, Aug 17, 2001:
1. Removed DE_THUNDER and DE_VERTIGO
2. Added DE_CELTIC
Tuesday, Aug 28, 2001:
1. Added DE_NUKE
2. Added CS_ASSAULT2K
Monday, Oct 1, 2001:
1. Entrance process outlined in more detail in Entrance & Retention section.
2. Division format area clarification: Charlie clans have 4 match weeks to prove themselves, not 30 days as noted before.
Monday, Oct 8, 2001:
1. Entrance process moved to information section of site. Requirements for entrance and retention remain in the rules.
Sunday, Oct 21, 2001:
1. Ping imbalance updated to 250ms rule; 'lagger stipulation' added.
2. Match play section updated: not being able to connect to a server via in-game server browser is invalid excuse for being unable to join game server.
Tuesday, Oct 23, 2001:
1. Server settings section clarified, added to (Gamevoice).
2. Substitution rule added to Member Rules area.
3. Ping imbalance rule updated.
Saturday, Nov 17th 2001:
1. Added clarification to the Diputes section involving frivolous disputes.
2. Added examples to cheating section.
Saturday, Feb 2nd 2002:
1. Added "24 hour rule" to roster section.
Thursday, Feb 20th 2002:
1. Added the map de_legato to the STA-CSX map ro, 2001:
1. Added DE_NUKE
2. Added CS_ASSAULT2K
Monday, Oct 1, 2001:
1. Entrance process outlined in more detail in Entrance & Retention section.
2. Division format area clarification: Charlie clans have 4 match weeks to prove themselves, not 30 days as noted before.
Monday, Oct 8, 2001:
1. Entrance process moved to information section of site. Requirements for entrance and retention remain in the rules.
Sunday, Oct 21, 2001:
1. Ping imbalance updated to 250ms rule; 'lagger stipulation' added.
2. Match play section updated: not being able to connect to a server via in-game server browser is invalid excuse for being unable to join game server.
Tuesday, Oct 23, 2001:
1. Server settings section clarified, added to (Gamevoice).
2. Substitution rule added to Member Rules area.
3. Ping imbalance rule updated.
Saturday, Nov 17th 2001:
1. Added clarification to the Diputes section involving frivolous disputes.
2. Added examples to cheating section.
Saturday, Feb 2nd 2002:
1. Added "24 hour rule" to roster section.
Thursday, Feb 20th 2002:
1. Added the map de_legato to the STA-CSX map ro, 2001:
1. Added DE_NUKE
2. Added CS_ASSAULT2K
Monday, Oct 1, 2001:
1. Entrance process outlined in more detail in Entrance & Retention section.
2. Division format area clarification: Charlie clans have 4 match weeks to prove themselves, not 30 days as noted before.
Monday, Oct 8, 2001:
1. Entrance process moved to information section of site. Requirements for entrance and retention remain in the rules.
Sunday, Oct 21, 2001:
1. Ping imbalance updated to 250ms rule; 'lagger stipulation' added.
2. Match play section updated: not being able to connect to a server via in-game server browser is invalid excuse for being unable to join game server.
Tuesday, Oct 23, 2001:
1. Server settings section clarified, added to (Gamevoice).
2. Substitution rule added to Member Rules area.
3. Ping imbalance rule updated.
Saturday, Nov 17th 2001:
1. Added clarification to the Diputes section involving frivolous disputes.
2. Added examples to cheating section.
Saturday, Feb 2nd 2002:
1. Added "24 hour rule" to roster section.
Thursday, Feb 20th 2002:
1. Added the map de_legato to the STA-CSX map ro, 2001:
1. Added DE_NUKE
2. Added CS_ASSAULT2K
Monday, Oct 1, 2001:
1. Entrance process outlined in more detail in Entrance & Retention section.
2. Division format area clarification: Charlie clans have 4 match weeks to prove themselves, not 30 days as noted before.
Monday, Oct 8, 2001:
1. Entrance process moved to information section of site. Requirements for entrance and retention remain in the rules.
Sunday, Oct 21, 2001:
1. Ping imbalance updated to 250ms rule; 'lagger stipulation' added.
2. Match play section updated: not being able to connect to a server via in-game server browser is invalid excuse for being unable to join game server.
Tuesday, Oct 23, 2001:
1. Server settings section clarified, added to (Gamevoice).
2. Substitution rule added to Member Rules area.
3. Ping imbalance rule updated.
Saturday, Nov 17th 2001:
1. Added clarification to the Diputes section involving frivolous disputes.
2. Added examples to cheating section.
Saturday, Feb 2nd 2002:
1. Added "24 hour rule" to roster section.
Thursday, Feb 20th 2002:
1. Added the map de_legato to the STA-CSX map rotation.
Saturday, Mar 30, 2002:
1. Updated "Member Rules and Substitutions" to reflect the new Roster System.
Sunday, Nov 30, 2003:
1. Added rule banning use of riot shield!
Tuesday, June 29, 2004:
1. Added rule that was posted in news on Sep 29, 8:42 AM EST but did not get put in the rules.
Thursday, March 11, 2005:
Changed over rules for Counter-Strike Source.
Sunday, May 29, 2005:
1. STA Overtime config added (sta_ot.cfg)
2. Changed the overtime Rules (maxrounds and startmoney)
SourceTV rules added
1. New section for SourceTV has been added.
2.SourceTV Config has beed add. (STA_csstv.cfg)
Playoffs & Map expoilts
1. Added Playoffs Section
2. Added Map exploit examples
| Last Updated on November 6, 2006 |
|
|
|