| STA HL2DM Rules |
I. Introduction
II. Fundamental Rights
III. Player Exceptions
IV. Eligibility Requirements
V. Rosters
VI. Sportmanship
VII. Ringers
VIII. Cheating
IX. Dispute Handling
X. Season Format & Seedings
XI. Team -vs- Team Pairing
XII. Match Times and Rescheduling
XIII. Game Recordings
XIV. Match Basics
XV. Detailed Pre-Match
XVI. Detailed Match
XVII. Detailed Post-Match
XVIII. Miscellaneous
XIX. Team Inactivity
I. Introduction
STA-HL2DM 2vs2 was created for clans to compete for fun and glory in the game of *Half-Life 2 TDM*. Please keep in mind that STA administrators sacrifice large amounts of their free time to maintain this league. They do so with zero monetary compensation, and completely for your own enjoyment. This is the framework for all rulings made in the league. The rules are also written under the assumption that they will be used in good faith by all parties involved, which sometimes is not the case. To this end, even if the rules for your particular league do not state it, administrators always have the final say on whether or not to apply a particular rule, or how it should be applied. They also may make rulings contrary to the written rules if the ruling serves the purpose of fairness and maintains the integrity of the league. This is not to say that administrators will go around randomly ruling on things depending on their mood for the day - admin abuse is taken seriously by senior administration and we never tolerate it. This does, however, give the admins some leverage so that their hands are not tied by a rule that did not take a certain circumstance into account when written.
II. Fundamental Rights
All STA leagues operate under the same basic tenets of order, logic, equality and fairness. Clans and their members are reserved the following rights:
1. Active league administrators who respect proper chain-of-command.
___For clan leaders:___
League administrators are required to make themselves accessible to clan leaders in a timely fashion so as to address all concerns, disputes, and queries seriously.
___For clan members:___
If any member of a clan within STA-HL2DM requires contact regarding personal issues, they may approach an administrator directly. However all other operations, including official clan business, should be channeled appropriately through the team's listed contact. Administrators reserve the right to deny communication with clan members if its capacity is related to official clan operations.
2. Clans will not be penalized on unsubstantiated grounds.
To protect players from unsubstantiated accusations of misconduct, STA administrators will discard claims and accusations lacking in sufficient evidence.
3. Clans and their members have the right to a fair and just decision.
Under any circumstances that require a ruling by an STA-HL2DM official, clans and their members have the right to a fair and just decision. At a minimum, clans are entitled to rulings whereby the active administrator is not directly affiliated (e.g. clanmate) with any gamers held subject under his or her decision.
III. Player Exceptions
League members have certain responsibilities that must be fulfilled for the STA league to remain functional. Those responsibilities include:
1. It is expected that all clan members are fully familiar with the rules. Much as in real life, ignorance is not an excuse.
2. Clan leaders must be easily accessible. Email must be working and checked regularly. Contact must also be possible through IRC.
3. Clan members are expected to keep current with all changes posted on the website. This includes but may not be limited to: schedule updates, rule changes, and the latest news. The STA website is to be checked right before a night's match is scheduled to start.
4. All clan members are held responsible for the actions of their clanmates. The poor decisions of one member may in some circumstances place the entire team at risk, and so members are encouraged to educate their teammates on proper conduct and official STA rules.
5. Clans and their members are required to respect the rulings of an STA administrator. Attempts to denigrate an administrator may result in a suspension of your clan. All rulings are final.
6. You cannot lie to an admin. Intentionally misrepresenting your situation may be construed as a flagrant disregard for the rules and action will be taken in kind. All rule violators are normally given a chance to fess up. If hard proof of a violation is at hand and the culprit lies to the administrator to try and escape the situation, harsher penalties will be given.
IV. Eligibility Requirements
In order for a clan to participate in the STA-HL2DM league, the clan must supply:
- Clan name
- Clan tag
- Up to date Roster with SteamID's
- IRC channel
- Clan Coordinator e-mail address
These requirements are non-negotiable. If your application contains inaccurate information or is missing key details, it will be rejected.
For clans that have multiple teams please mark the team name/tag when registering to join. i.e we dont have 3 clans on the rankings all with the exact same tag/name
V. Rosters
All teams are required to maintain an updated listing of their roster during the season. This information must be located in the clan's profile page found on our website, and on this page all players’ SteamIDs must also be listed. The rules below for player eligibility for rosters are also applied to SteamIDs. Even if a player has been on the roster long enough, if that player’s SteamID has not been submitted before the day of the match, that player will be ineligible to play in that match.
Players must play using the names displayed on their team’s roster. If the offending team has a player that doesn’t use the correct alias and refuses to change said alias at the request of the opposing clan’s leader, then the match will result in a forfeit for the team with the offending player. If, however, the match commences with the offending player using an incorrect alias, the option for dispute on those grounds will be null.
VI. Sportmanship
Persons who do not display proper sportsmanship towards others will be considered for expulsion. Activities that warrant such consideration include excessive defilement of other clans or incredibly virulent behavior in general in STA mediums or relating to the STA league.
Enforcement of this rule may apply to any communication medium involving members of STA-HL2DM. Please remember that an entire clan can be held responsible for the actions of a single member, and so teammates should take all necessary action to keep each other in-line with expectations.
___In-game Chat (mm1):___
In-game chat (mm1) is allowed for all players as long as both teams show sportsmanship and agree to use mm1. If a captain of a team should at any time (before or during a map) decide to ask for "mm2 only", that request shall be immediately granted by both teams. When this request is made, mm1 will only be allowed for team captains (as shown on the STA rosters) while the map is under way. mm1 will still be permitted to be used by all players before the map, during warmups, during timeouts, and after the map has ended. Minor infractions of the mm1 rule will not neccessarily constitute a forfeit, but if the administrators see it as being excessive in quantity or content, and see it happening week after week, a team may be penalized. All communication is to be conducted in a sportsman like manner and showing obvious self constraint.
Note Bene: STA-HL2DM is not in the business of censorship. The above rules are, except in the most extreme circumstances, restricted purely to official league business. This encompasses pre-match, match, immediate post-match communication, the STA forums, and other official STA channels of communication. Most other activities will fall outside the jurisdiction of STA-HL2DM except in those cases which administrators warrant as being a flagrant derision of its members.
VII. Ringers
The league does not tolerate ringers/smurfers. A ringer is loosely classified as any person playing on a team for whom they are not eligible to compete with. The most common violation of this rule takes place when a gamer competes for a team whereby they are not listed on that team's official roster or a player is playing under a name on that team’s roster but not with a SteamID that is on that team’s roster.
If a team plays with a player not on their roster, regardless if both teams agree that said player can play, the offending team will face punishment.
Rosters are not automatically accepted by both teams when the match starts, like server settings are. This can be disputed after the match.
Persons found to be violating this rule may face severe punishment for themselves and their clan(s), regardless of who was aware of what circumstances and when. Thus, STA-HL2DM firmly recommends that clan leaders investigate all incoming members with intense scrutiny. Due to the fact that all offenses are different, the punishment for using a ringer will be different for each scenario. Common punishments involve the banning of the ringer and the team captain, a forfeit loss for the team, and a team suspension.
VIII. Cheating
Internet gaming is plagued by a population of irresponsible individuals who do not see the harm in introducing cheats, hacks, and spam into the community. It is expected that no clan in STA-HL2DM cheat. Violations include, but are not limited to:
1. Texture/Model/Map/Physics hacks.
2. Any type of unauthorized pak or file editing
4. Any mechanism by which information that is not normally available to the player is obtained. (e.g. Source:TV eavesdropping)
5. Nuking, channel takeovers, spamming, crashing a match server, or any other methods of Denial of Service.
6. Any type of driver hacks (e.g. See through walls, ATi Smartshader effects, nVidia NULL functions) that causes the game to render improperly.
7. Any type of program (such as 3DAnalyze) running that causes the game to render improperly.
8. Any type of unauthorized utilization of in-game bugs.
a.) cl_cmdrate > 30 is not permitted in STA league play. The sta server config has setup for logging of this information as to coincide with the update that Valve released.
b.) Mining Objects - It has been determined that hiding SLAM's inside of objects to prevent the laser from being seen is an exploit. This tactic is illegal and will result in a forfeit loss for exploiting this tactic.
9. Automated HUD item timing scripts, programs and proxies.
10. Any type of lag hacks including running P2P programs to artificially lag.
11. Exploit scripts* (ie: shooting, jumping, or centerview scripts that give a player an advantage).
12. Touch screen monitors or any other touch screen viewing devices.
The STA-HL2DM league will only deal with violations that take place within the exact context of those events which fall under our jurisdiction. However, if a player is found out to commit these violations outside of league play and enough evidence is submitted so that the administrators can rule that that particular person was the one to make the offense without any reasonable doubt (demos, screenshots, witnesses, logs, SteamIDs, IP addresses), then that person may be banned from league play for that particular season and the match will result in a forfeit for the offender's team. Any offense made outside of the league after the roster deadlines (if two divisions have different cut off dates, then this rule goes by the earlier date), or before a season starts, will warrant a ban for the rest of the current season and playoffs and the next season.
If a player is caught cheating in an official match for another Half-Life 2 TDM league or ladder, then that player will be permanently banned from the STA Half-Life 2 league. This is not dependent on the administrators of the other leagues, and their ruling makes no difference in STA's ruling. The STA administrators must be able to make the decision themselves regarding whether or not the player was cheating, just as they would while deciding whether someone was cheating in an STA match.
If an active player is caught cheating in STA, another league, or on a public server, then demos may be reviewed from past STA matches to determine if that player was cheating in them. The team captains from those past matches must file a dispute to the administrators and provide all the neccessary information required in a standard dispute. If sufficient information is found, then the disputing team will receive a forfeit win for that past match while the offending team will receive a forfeit loss. Regular season match outcomes can not be changed once the first week of the playoffs's matches have been played. If this happens during the playoffs and forfeits are awarded for past playoff matches, then the matches affected by the outcomes of that match may be replayed. If a match is not affected or the same match-ups occur after the directly affected matches are replayed, then those identical matchups will not be replayed.
If something in your system setup generates false-positives with respect to screenshots or file scanning, contact an administration well before you play a match so the situation can be documented ahead of time.
If you suspect another clan of cheating or someone on your own clan of cheating, immediately contact an administrator for assistance in resolving the conflict.
STA will require all servers to be using VAC2.
IX. Dispute Handling
First and foremost, clans are encouraged to find mutually acceptable solutions without assistance from STA-HL2DM officials. If this proves impossible, then the next step is to file a dispute.
All disputes must be filed no later than 6 hours from the beginning of the match in question. If more time is needed to gather demos and other evidence, than an extension of these 6 hours may be approved by the administrators during these first 6 hours. If no approval is given in this time, then assume the standard 6 hours. Do not submit your team scores if you intend to dispute, as a submission of scores is an acknowledgement that you accept the circumstances of the given match and its outcome.
Ideally, disputes can be resolved in real-time with the help of an onsite admin. Any team that needs to locate STA-HL2DM personnel should log on to our #sta-hl2dm IRC channel, on "Gamesurge" network.
In the event of a dispute, a clan must submit a subpoena for review to the league. This subpoena acts as a precise representation of one clan's claim against the actions of their opponent. The contents of this dispute must be extremely detailed to even be considered for review. In particular cases where cheating may be involved, administrators will require timestamps for exact instances in which a transgression may have taken place. There are no exceptions to this standard and the league will not indulge half-measures in this regard. A clan has only two options; either file a comprehensive dispute, or don't.
:: The subpoena must include ::
1. Rule violated by opposing clan, as quoted from this document.
2. An exact description of how and when the rule was violated.
3. Extremely specific proof of the transgression in the form of: Server logs, chat logs, e-mails, demos, screenshots, or condumps.
Note: Disputes such as “They cheated” with no other information will not be taken seriously. The subpoena rules above must be followed specifically otherwise the dispute will be thrown out. If a team is found to be taking advantage of the dispute process by filing many unwarranted disputes, action may be taken against said team.
:: Disputes may end in one of the following manners ::
1. Discard; no action taken.
2. Replay; match must be restarted.
3. Positive; team who filed receives 3 points, other team 1 point.
4. Negative; claim reviewed but no action taken.
5. Forfeit; egregiously bad behavior from one or both parties prompts that the team(s) are/is awarded a forfeit, 0 points awarded.
It should be noted that in extreme circumstances, a dispute might end in the additional suspension of any guilty clan(s).
X. Season Format & Seedings
STA-HL2DM 2 vs 2 operates on a seasonal format. Scheduling for the regular season adheres to our specially created system, outlined in *Section XII.
___Seasonal Layout:___
- 8 weeks of regular season
- 2 weeks of playoffs
- Championship match
___Seeding Criteria:___
- Total Points
- Head-to-Head victories. (2-way ties only)
- Highest Round Differential
- Head-to-Head victories. (2-way ties after the first 3 criteria only)
- Most amount of cumulative "maps won".
- Head-to-Head victories. (2-way ties after the first 5 criteria only)
If teams are still tied after these 5 criteria, the playoffs will be delayed a week and these two teams will face off at the date and time that the playoffs were supposed to begin on a map that will be determined by the administrators.
*Please note that the rankings page incorrectly accounts for Head-to-Head and the amount of cumulative “maps won”, and that Head-to-Head only plays a role when comparing 2-way ties.
___Playoff Seedings:___
The top 8 seeds after week 8 will move on to the playoffs. The playoffs use a standard bracket system.
First round: 1v8, 2v7, 3v6, 4v5.
Second round: Winner of 1v8 vs. winner of 4v5. Winner of 2v7 vs. winner of 3v6.
Final round: The remaining two teams play each other for the championship.
The team with the higher seed at the start of the playoffs will become the home team for each match in the playoffs. For example, if seed 8 beats seed 1, seed 8 would still be the away team when they play either seed 4 or seed 5 in the second round.
Note: We encourage the two losing teams from the round before the championship round to play each other for 3rd place whenever it is convenient for the two teams. This is not required, but it is seen as a positive thing for these two teams to do so.
XI. Team -vs- Team Pairing
Stronger Than All has employed a semi-swiss method for league scheduling. This specially designed system allows for artificial tiers with lots of exciting matches, while still keeping the league inherently porous.
___How It Works___
Win = 3 points.
Loss = 1 point.
Forfeit = 0 points.
Bye = 3 points.
1. Teams play each other only once, except perhaps seeds 1-8 after week 7
2. Teams of varying points are placed into groups.
3. Teams receive a separate seeding for that particular group.
4. If the total amount of teams is odd, the lowest seed in the lowest group automatically receives a bye, under the assumption that the team hasn't already received a forfeit win or a bye.
5. Starting in the highest group, the top seed plays against the lowest seed in that group, which they have not already played against once before. The higher seed becomes the home team.
6. Once all possible match-ups have been made within a group, any team(s) still remaining automatically become the highest seed(s) in the next lowest point group.
7. Any team that registers for the league after the season has began is not eligible to receive a bye.
8. In week 8, Seeds #1-8 form their own grouping, and are paired regardless of potential repeat matches. The rest of the division follows the normal swiss rules.
9. As opposed to previous seasons, seeds 1-4 will not be locked after week 7 and the scheduling will continue as normal for these seeds.
___Byes and Forfeits___
If a team receives a forfeit win, that team gets the 3 points for the win. In that week, the winning differential for all matches (that were not byes or forfeits) should be averaged together. The team that received a forfeit win should receive said differential. The team that receives a forfeit loss not only doesn’t get a point, but they get the negative differential of the week's winning differential average added to their total diffe ential.
Any team that receives a bye will get the 3 points for a win and 0 differential.
In the event of a match being partially played that resulted in a forfeit or one team being disqualified before or during the match, then the winning team will receive either the differential allotted during that match so far, or the average differential for all other teams, which ever one is higher. Said differential will be subtracted from the forfeiting/disqualified team.
Once the final schedule for a week is made, no more bye wins can be awarded for that week. If a team drops out, that team's opponent will receive a forfeit win. Schedules may undergo multple revisions after they have been posted, so this only applies to the final schedule for a particular week.
___Null Matches___
In certain cases, the administrators may find it necessary to determine the outcome of a match to be "null". In this situation, a team will receive 0 points and 0 differntial.
XII. Match Times and Rescheduling
___Default Match Times:___ *Eastern Standard Time
TBD
___Late Matches___
All maps must be started by TBDpm EST (unless both teams agree to play later), and any remaining maps have to be rescheduled to start within 100 hours after the scheduled start time of the original match. For this to be able to happen, the match has to have been started on time and at least 2 maps has to have been completed. The admins have to be informed of the new start date of the remaining maps, by both teams, within 6 hours of the original match’s scheduled start time. If the two teams can’t decide on a date and time within those 6 hours, then the remaining maps will start 72 hours after the scheduled start time of the original match. In the event of a holiday, the administrators will make a ruling on the start time if one is not already agreed upon within those first 6 hours by the two teams.
___Initial contact:___
Clans are expected to make contact with each other at least 24 hours prior to game time. During initial contact, server and match time information should be exchanged. Pings should be tested out on the servers chosen by both teams to make sure there are no problems.
___Rescheduling:___
Upon the consent of both clans, a match may be rescheduled to something other than the default day/time. However, all games should ideally be played before the default day has passed. Once a clan accepts a reschedule, any failure to abide by the new mutual agreement is grounds for automatic forfeit.
The administrators must be notified of a rescheduling before 24 hours before the scheduled start of the match by both teams. This is so the administrators can confirm that both teams agree on this time. If this is not done properly then the match is assumed to be starting at the standard time and one or both teams may receive a forfeit loss.
The latest a match can be scheduled to start is 100 hours after the start of the original match. All maps must be played at that time, regardless of the Late Matches rule stated above.
Clans are responsible for having multiple means of contacting teammates, STA administrators, and also other clans. Server downtime for communication mediums such as IRC networks, e-mail, or Instant Messaging must be manageable by clans and their players.
XIII. Game Recordings
All players are required to record and save complete demos from every match. They must save these demos for the entirety of the season, whereby administrators reserve the right to obtain from the player a demo of any match, at any time, and for any reason. Failure to record demos will result in a penalty for the offender's clan. The minimum punishment will be a forfeit loss, with the possibility for additional action depending upon the circumstances at hand.
Demo name format should be like this :
team-a_vsteam-b_date-
*to record demos in hl2dm just type record <demo-name>
XIV. Match Basics
The appropriate STA server config file should be executed prior to each game to ensure appropriate settings
___Minimum Players:___
Seeing as how this is a 2 vs 2 league team will not be able to play 1 vs 2. You will either have to forfiet or reschedule.
___Scoring Basics:___
STA operates on a points-win basis. Each week opponents will play the pre-designated map, listed in the *Schedule area. Both clans must play this map for 20 minutes as each color, with the possibility of a tiebreaker being necessary. Further details available in *Section XVII. Teams must play on the map scheduled for that particular week. Any teams who play on a map other than the one scheduled will receive forfeit losses.
___Server Lag:___
If a server is constantly receiving lag spikes or any other lag in general then another server is to be used. The team that had the choice for that round will pick the new server. If this happens during a match, a timeout is to be called and the procedures in the Server Crashes rules in section *Section XX is to be followed. If the standard server lag bug occurs then a team may call a timeout followed by an rcon pause until the lag from the bug passes. It is recommended that an administrator be contacted during or before the match if both teams do not agree that the server is having lag problems. If no administrator is available, the play either continues on the current server or the team that is fighting to play on a different server must file a dispute. If the administrators later on view the demos and see that there was no noticeable lag or lag spikes then the team fighting to stay on teh server will receive a forfeit win. If the demos show that the server did have lag or lag spikes, then the team fighting to change servers will receive a forfeit win. Obviously a situation like this is not usually required. The best bet for both teams is to settle the dispute between themselves while practicing common sense.
XV. Detailed Pre-Match
The "Home" team is the first clan listed on the schedule page. This team begins the game as Red, and chooses the server for the first map. The "Away" team is the second clan listed on the schedule page. This team begins the game as Blue, and chooses the server for the second map. Teams must swap colors between the first two maps. If TeamA chooses TeamB’s server as the server they would like to play on, TeamB has the right to decline that request.
Clans have 15 minutes after the scheduled match time to join the game server and "ready up". Please refer to the Between Map Time Limits rule in *Section XVIII below for more information.
All clans are expected to be ready to play at the default time. Clans should send a representative to the #sta-hl2dm IRC channel 30 minutes prior to the match, as to avoid disagreements and potential problems.
Finally, both clans should check server settings to verify that they are correct. If no objections are raised during this time, then neither clan may challenge the settings during or after the match. By joining the server and starting the match, you agree to the cvar settings as they stand. In addition, if there is a conflict based on ping differential, i.e. East Coast vs. West Coast, a server in a Central location will be provided upon need. There will be no "forcing" of server selection. If there is a known conflict the use of a central server is required.
XVI. Detailed Match
___Map Start___
1. The proper STA config should be enabled at this time by inputting the following:
exec "stahl2dm.cfg"
2. Load up the map for that week.
map dm_overwatch
3. Once everyone is on the correct team, type the following command, exec "lo3.cfg" .
4. During the map warmup, the team captains are required to take a screenshot of all players' SteamID's and save them for the entire season.
status
screenshot
5. During the map warmup, the team captain who has rcon access to the server must also take a screenshot of all players' IPs and save them for the entire season.
status
screenshot
___Color Swapping___
After the first map is completed, teams must swap colors for the next map.
___Overtime___
Should an overtime map be necessary after the first two maps have been completed, then the team with the most cumulative rounds or kills chooses their preferred color or server for the final map. The team with fewer cumulative rounds receives the privilege of whichever category the winning team opted out of. In the unlikely event that the total rounds of each team are equal, then the "Home" team, who by default is the higher seed, gets first pick. All of the previous rules stated in *Section XVII still apply to this 3rd map, including the rule where "If TeamA chooses TeamB’s server as the server they would like to play on, TeamB has the right to decline that request." If a situation occurs where a team captain picks either server or color, and then that captain changes his or her mind, then that captain has the right to do so as long as the map has not begun and 10 minutes has not passed since the end of the 2nd map. This leaves 5 minutes to swap servers if neccessary before the 15 minute timelimit between maps expires.
To begin the overtime round, please exec the following command, exec "lo3_ot.cfg" .
___Between Map Time Limits___
Clans have 15 minutes after the scheduled match time and in between maps to join the game server and "ready up". Failure to comply will cost the offending clan a forfeit and an administrator should be notified once this happens. Please also record demos and do condumps of the time leading up to 15 minutes after the scheduled time the map was supposed to start (use this evidence in a dispute report). Under extraordinary circumstances, such as major connection problems for multiple players, STA-HL2DM may allow an exception. If this is the situation, the administrators must be contacted immediately. If server problems are preventing the map from starting within the 15 minutes, the team who has picked the server will forfeit their server choice and the map must be played on the other team's choice. From this point the map has 10 minutes to start, otherwise the "non-readied" team will receive a forfeit loss. Please note that if a team has forfeited their server choice for map1, they do not receive server choice in map2.
___Server Settings Regulations___
Server settings are not allowed to be changed during mid-map. If a variable is found to be incorrect (such as the timelimit), then the server admin may perform an rcon pause to stop the match, alert the other team, and change the setting. No settings will be allowed to be changed without this procedure. No substitutions can be made during this time. This is strictly for a server settings change.
XVII. Detailed Post-Match
___Screenshots___
Both teams are required to take a screenshot of the score board which displays the final outcome of each map after time has expired.
bind F12 screenshot
Then press F12 (or whatever your bind is) when you want to take a screenshot.
___Score Reporting___
Scores must be reported within 6 hours of the scheduled match time, by both teams, unless a dispute is filed. We recommend you submit score reports immediately after the match is completed. A list of the players who have played in that particular match for a team (not subs) must be submitted in the comments section when submitting scores. If rosters are not submitted, there will be a 15 point or 15% differential deduction (which ever is higher) for the offending team.
___Dispute Reporting___
Please see *Section X above for dispute information.
XVIII. Miscellaneous
___Spectators___
The only spectators allowed in matches are live broadcasting representatives, a team's designated substitute, or a league administrator. A spectator can not be on the roster of either team, be it a league administrator, Source:TV, or Shoutcaster.
___Map Exploits___
Abusing map exploits is not allowed. Map exploits are loosely defined as the following: (1) areas accessible on the map which the mapper did not intend to be reachable, (2) performing a certain action on a map that was not intended by the mapper, such as throwing grenades over or through certain parts of a map, and (3) areas that are not accessible without the use of boosting, unless otherwise stated. Additionally, for these areas to be considered illegal, the spot must show a potential advantage for a player if a player is to abuse said area. This is a decision which is at the sole discretion of the ruling administrator either before, during, or after a match. We will try to specifically address known exploits for maps each week in the news, so be sure to check the STA news page right before your match starts. If a player feels accessing a given location on a map is unintended or wrong, he/she is encouraged to stay away from this location during the match. If such a location is found prior to a match, please ask an administrator.
___Live Broadcasting___
By playing in STA, you automatically consent to allowing live broadcasts of your game via Shoutcasting or Source:TV.
___Game Version___
Unless otherwise stated by the administrators, clans are obligated to use the newest version of HL2DM no later than 5 days after it's release, to use the specified version of each map.
___Server Crashes___
In the event of a server crash, both teams may agree to restart the map if they feel that would be the easiest solution. If the teams do not agree on that, the map will be restarted with a time limit that was equal to the amount of time remaining when the crash occurred (rounded up to the nearest minute). At the end of that map, that score will be added to the score of the map when the server crashed to determine the map winner. If this ends up in a tie, the map will be restarted again with the standard sta2.cfg server settings but with a fraglimit of 1, and a timelimit of 0 for both. Which ever team wins this, wins the map.
If the teams can not agree on the scores and time left at the time of the crash, an administrator isn’t readily available to make a ruling, the map (and all remaining maps) may be postponed in accordance with rule XIII, section “Late Matches”. Obviously, an administrator must be notified if this situation happens.
If the server can not be brought back up, and no replacement server can be found for that team, then the team whom didn’t have server choice for that map gets to pick the server, in addition to the map where they normally have choice. If no servers can be found by either team, the remaining maps may be postponed in accordance with *Section XIII, section “Late Matches”. Obviously, an administrator must be notified if this situation happens.
___Server Specific Bans___
If a player is banned on a server, that player has to be unbanned for the match on that server. The only reason a ban may be in place for STA matches is if STA has officially banned that player. Bans from other leagues, master ban lists, pubs, and for any other reasons outside of STA have to be lifted so all players eligible to play in that match are able to.
If a team refuses to lift a ban on an opposing player, the team refusing to lift the ban will receive a forfeit loss.
XIX. Team Inactivity
A clan is marked for inactive status if any of the following conditions occur:
1. Clan has requested inactivity.
2. Clan has forfeited matches for two consecutive play weeks.
3. Clan has repeatedly not had the full amount of players available for matches.
Inactive clans are not scheduled for play. For a clan to become active again, it must meet the same criteria as those clans wishing to join the league anew.
| Last Updated on August 28, 2006 |
|
|
|