| STA WOLF Rules |
I. Introduction
II. League Administrators (Admins)
III. STA-RTCW Protocols
IV. Entrance Requirements
V. Foreign Teams
VI. Member Expectations
VII. Team Captains/Contacts Expectations
VIII. Player Expectations
IX. Season Format
X. Scheduling
XI. Rescheduling
XII. Servers
XIII. Server Configuration
XIV. Regular Season Matches
XV. Match Format
XVI. Pre-Match Responsibilities
XVII. Breaks/Halftime
XVIII. Scoring
XIX. Voice Communication
XX. Demos/Screenshots
XXI. Ping Imbalance
XXII. Server Crashes
XXIII. Post-Match, Match Reporting
XXIV. Player Conduct
XXV. Double-Clanning & Ringers
XXVI. GUIDs
XXVII. Cheating
XXVIII. Bug, Map, Class, & Game Exploits
XXIX. Disputes
XXX. Real-Time Disputes
XXXI. Wildcard Rule
XXXII. Inactivity, Team Expulsions, and Player Bans
XXXIII. Inter-Team Matches
XXXIV. ProBowls
XXXV. 10v10 Inter-Team
XXXVI. Rule Amendments
I. Introduction
STA is a system of organized leagues, all run by individual administrators. All STA leagues operate under the same basic tenets of order, logic, equality and fairness. STA does not profit in any way by clan participation.
The STA-RTCW league was created for teams to come together and play Return to Castle Wolfenstein competitively. If your team desires a venue where they can storm the beach and defend the objective in a fun and community-oriented environment, STA-RTCW is the place for you.
STA-RTCW currently consists of an unlimited lives OSP division. Other RTCW divisions can be created based on community feedback. Requests should be made to the STA-RTCW administrators.
Disclaimer
STA reserves the right to modify the following rules as necessary. Teams should check the rules on a regular basis and prior to every match to ensure they are in complete compliance. Rules are marked with an update date and log of changes to assist in this capacity. These rules are guidelines by which the league operates to ensure a fun and even playing field for all teams. At all times, these rules are subject to interpretation by STA-RTCW admins. While STA strives to provide the most comprehensive rules possible, not every scenario can be anticipated. Those matters are left to admin discretion based on the spirit of these rules.
II. League Administrators (Admins)
A lot of time and effort goes into administering and maintaining this league. STA-RTCW admins do this for their enjoyment and for the benefit the league experience for all participants. They spend their free time presenting this league without any monetary compensation.
Admins are expected and required to do the following:
1. Provide a fun, competitive, and fair atmosphere for teams.
2. Act in a professional, neutral, and unbiased manner at all times on matters associated with the league.
3. Remove themselves if a dispute arises involving or potentially impacting their team. Other admins must resolve the issue.
4. Be available on league nights to assist teams with their matches. Admins are available on Internet Relay Chat (IRC) in #sta-wolf on gamesurge.net approximately 30-45 minutes before default match time. Admins on duty on match nights wear an "OnDuty" tag on their nickname. Admins are also available on non-match nights on a time-available basis.
5. Monitor matches when requested by teams. At least two admins are required to monitor STA playoff finals.
In addition to IRC, admins can also be contacted in the following manner:
Trinners
• Email: trinners@sta-league.org
• AIM: tr1nn3rs
• ICQ: 231432619
• MSN: trinners@hotmail.com
• Xfire: tr1nn3rs
III. STA-RTCW Protocols
Team and Member Bill of Rights
All teams and members have the following inherent rights:
1. To be treated with respect by all members of the STA-RTCW community. This includes by other teams (including team captains, representatives, and individual members) and by administrators.
2. To challenge a match to an admin. All forms of dispute must be accompanied with appropriate proof or evidence. (See Section XXIX (Disputes))
3. To request that a league admin monitor their match.
4. To a fair and just decision by league admins.
5. To have their queries, concerns, and disputes handled by league admins in a timely fashion.
Violation of Rights Procedures
• If any person feels his/her individual or team rights have been violated by another team should immediately contact an admin with a full and detailed account of the proceedings. Individual team members should go through their captain/contact first before contacting an admin directly.
• If a team feels that a member’s individual or team rights have been violated by an administrator, the team captain should immediately contact the head STA-RTCW administrator with a full and detailed account of the proceedings.
IV. Entrance Requirements
To be admitted into STA-RTCW, teams are required to complete the STA-RTCW application form, which can be found off the Web site (http://wolf.sta-league.org). When joining, teams must have the following minimum requirements:
1. At least 5 members on the roster.
2. A team name and tag.
3. At least 2 forms of communication (e.g. Web site, IRC channel, ICQ, email). IRC and a team Web site are preferred.
4. Team captain/contact must supply a valid e-mail address that is checked daily.
Once admitted into the league, teams must maintain the above minimum requirements to maintain eligibility. Teams that are unable to meet these minimum requirements will be marked as inactive until met. In addition, teams must have 6 active members in order to be scheduled for match play. Players are eligible if their name and 8-digit pbguid (guid) are listed on their team’s STA-RTCW roster.
STA reserves the right to refuse or remove any team from this league at any time. Registration is closed after a predetermined number of weeks of regular play. To be eligible for playoffs, teams must participate in 60% of an 8-week regular season and 70% of a 10-week regular season.
V. Foreign Teams
Foreign teams are welcome to join STA-RTCW as long as they adhere to league rules. All matches must be played on North American servers. Match times are still to be played at default times unless other arrangements have been made with the opposing team and an STA-RTCW admin. No exceptions.
In addition, it is understood that foreign player’s pings on North American servers may be rather high, and they accept this as a consequence of participating in this league. Disputes with regard to ping imbalance from a foreign team will in general be disregarded.
VI. Member Expectations
One of the main tenets of STA and STA-RTCW is to provide teams and their players with a professional, logical, systematic approach to online gaming.
STA recognizes the wide spectrum of players that play under its banner and we understand that there can be conflicts between players of varying levels of maturity and intellectual development. It would be a grossly inappropriate and inaccurate to apply stereotypical filters to membership (such as age), so the only filters we have, as administrators, are the team leaders themselves.
With that said, the following are expectations for team captains/contact and players:
VII. Team Captains/Contacts Expectations
Each team must have at least 1 team captain/contact. The maximum number is 2. Team captains/contacts must:
1. Be fully familiar with all STA-RTCW rules. Much like in real life, ignorance is not an excuse.
2. Be easily accessible not only to other team leaders but also to STA-RTCW admins. Team captains/contacts are required to have a valid email address that is checked regularly. Contact must also be possible through IRC—either through the team’s IRC channel or by idling on IRC in #sta-wolf on gamesurge.net.
3. Keep current on issues as provided by the STA-RTCW Web site (http://wolf.sta-league.org). This includes news features, rule changes/updates, and schedules.
4. Be responsible for the conduct of their team. Team leaders may be held accountable for the actions of their individual team members. Furthermore, leaders are responsible for educating their team members on the STA rules of conduct and any other pertinent information.
5. Team leaders are responsible for keeping their rosters as listed on the STA-RTCW Web site up-to-date. (e.g. team contact information and player names/guids).
Because of these responsibilities, team captains/contacts are also acknowledged as worthy of respect and shall always be dealt with in an appropriate, respectful manner throughout the STA-RTCW community.
VIII. Player Expectations
All players must play under the name and guid as listed on their team’s roster on the STA-RTCW Web site. To obtain your pbuid, enter /pb_myguid in the RTCW console.
In the case a player has multiple guids, all guids must be listed on his/her team's STA-RTCW roster. If, at any time, there is potential for a guid to be used by another player (other then the player listed on the STA roster) league admins must be notified immediately.
It is the responsibility of players to inform their captain of any name/guid changes. Moreover, it is the responsibility of the team captain to keep his/her STA-RTCW team roster up-to-date.
IX. Season Format
STA-RTCW seasons consist of an 8 or 10-week season, which is decided at the discretion of the admins prior to the start of the season. Rosters are locked after the fifth week of an 8-week season and after week six of a 10-week season. Teams may add players to their rosters prior to the season lockdown, except for on match days.
The top teams within each division will compete in a playoff format following the regular season. Teams that do not make the playoffs will be scheduled for exhibition matches during that time (except the night of the finals).
X. Scheduling
Regular season match-ups are scheduled based on an algorithm to create arbitrary match-ups based on a round-robin format. There may be admin discretion in some circumstances (e.g. a team joins/leaves the league during the regular season, team suspensions, and extenuating circumstances).
Each team is assigned a home and away status. The first team listed on the "Schedules" page is the home team. Ideally teams will alternate between home and away status from week to week, but this does not always work in practice. STA-RTCW admins strive to maintain as close to a 50/50 home/away ration for each team as possible.
STA-RTCW strives to post scheduled match-ups on the STA Web site for the upcoming week no later than the previous Wednesday.
XI. Rescheduling
Teams may reschedule a match for anytime between the day on which the schedule has been posted, and the day after the scheduled default day of match (TBD), so long as both teams agree to it and an admin consents. Once a match is rescheduled, it may not be rescheduled again. If no agreement is made, matches are to take place on the default day at the default time (21:30 EST (9:30PM)). Teams may not reschedule matches later than Friday night unless express consent has been given by a STA admin.
If asked to reschedule by a team, you must give that team a response at least 24 hours before the default match time. In particular, the response may not be on the day of the match. This also means that reschedule requests cannot be made on the day of or the day before the match so as to allow the other team 24 hours to answer.
If a match is rescheduled and a team reaches forfeit conditions such as due to absence of members et cetera, then that team does not get the option of rescheduling the match again and the offending team receives a forfeit loss.
XII. Servers
Matches must be played on servers that are located in the United States or Canada unless both teams agree to a foreign server. Servers must be hosted on a T1 line or better. Servers hosted over a cable modem or d DSL connection are not acceptable. Also, all servers must be dedicated PURE RTCW servers. Listen servers are not acceptable under any circumstances. If neither team is able to provide a server, contact an admin for assistance.
XIII. Server Configuration
The following are mandatory server requirements that must be executed prior to the start of a match. Teams are responsible for checking the STA-RTCW Web site on a regular basis and ensuring that their server settings comply.
1. Current STA-RTCW match config file, which can be downloaded from the STA-RTCW Web site (http://wolf.sta-league.org) from the "Files" section on the left navigation bar.
2. Shrub mod as permitted by STA. Current acceptable versions of each are posted on the STA-RTCW Shrub Web site.
3. All matches must be played in Stopwatch mode (SW)—Gametype 6.
4. Friendly fire is ON. No exception.
5. Punkbuster must be enabled and servers must capture PBSS.
6. Correct map version for the map assigned.
Servers must NOT be upgraded to the latest release of RTCW or Shrub until STA-RTCW explicitly allows it with an announcement on the Web site or directly allowed by an admin. STA-RTCW will verify that there are no game-affecting bugs in new releases before implementation and give reasonable notice to teams of any changes before making them mandatory. In addition, other server modifications/versions such as the Shrub mod are not allowed under any circumstances.
Both teams should check the server's settings to verify that they are correct. If no objections are made, no team may challenge the settings during or after play. If an objection is made prior to the match commencing and the server settings do not match those required by the league, the settings must be fixed within 15 minutes of the start of the round or a change of venue must be made.
If issues arise after a match has been started (e.g. ping spikes, disconnects) that were not present before match play, teams should attempt to agree on a server change and/or an admin should be contacted to make a ruling. Any rounds previously played will be counted in match outcome.
XIV. Regular Season Matches
Matches are played on either Mondays or Tuesdays (TBD) at 21:30 EST (9:30PM) using the Shrub mod based on the server config file as provided by STA-RTCW. Teams must play the scheduled week’s map. Violations result in both teams receiving a forfeit loss on their record for the week’s match.
Teams have 15 minutes after the default time, or the mutually agreed-to time (See Section XI (Rescheduling)) to start the match. Failure to comply will cost the offending team a forfeit loss. Under extraordinary circumstances, such as connection problems, STA-RTCW admins may allow an exception. In the event of connection problems, contact an admin immediately.
Team Format
The default match format is 6v6 with one panzer and unlimited lives. Matches may be played with more than 6 if both teams agree and the server can support it.
Each team must have at least 5 to play. Teams are prohibited from playing 1-man down if both teams have 6 able players present. A team purposely playing a man down is considered unsportsmanlike.
Failure to play with at least 5 players results in the offending team's forfeiture of the match.
Spectators
Due to limitations of the Shrub mod, spectators are not permitted.
Timeouts and Mid-Match Issues
Since Shrub does not have a /pause function any issues must wait until the end of the round. Any connection issues or dropped players are a consequence of the mod. If players drop unexpectedly in the middle of a round, they may rejoin the server but must rejoin their team promptly due to the spectator limitation.
XV. Match Format
There will be (at minium) 3 rounds of stopwatch (SW) on the same map playing in an AB/BA format. The home team chooses either server or starting side (Axis or Allies). The away team decides on the remaining option. Sets and rounds are defined as the following:
Round 1:
Team A attacks and sets the time.
Team B attacks and tries to beat the time.
Round 2:
Team B attacks and sets the time.
Team A attacks tries to beat the time.
HALFTIME
Round 3:
Team A attacks and sets the time.
Team B attacks and tries to beat the time.
XVI. Pre-Match Responsibilities
Team Coordination
Teams are expected to make contact at least 24 hours prior to game time via the STA-RTCW Captains forums so there is written documentation of the match agreed upon details. At this time, server information can be exchanged and any other details may be decided.
The designated home team decides EITHER:
• Where the first set will be played.
• Which side it will play first (Axis or Allies).
The away team decides upon the remaining option. The teams must switch sides after the first set, thus, the team that attacked first in set one will defend first in the second set (See Section XV (Match Format)).
IRC
On the night of the match, teams must send at least one team captain/contact to idle on IRC in #sta-wolf on gamesurge.net at least 30 minutes before match time. The team captain/contact must wear his/her team tag and his/her name. This is to avoid disagreements and potential problems. Failure to have a representative in #sta-wolf should a problem arise will result in a warning from the STA-RTCW admins.
Server
In addition, on the night of the match, the server hosting the match must be in compliance with Sections XII (Servers) and XIII (Server Configuration) prior to the start of the match. It is the responsibility of the team selecting the server to ensure the server is ready prior to the match.
Once both teams have gathered on the match server, teams are responsible to:
1. Check team rosters/guids. Teams can obtain all players' guids by entering /pb_power in the console. A screenshot of the roster/guids prior to the match is required.
2. Make sure members are on the correct teams, teams are on the correct sides, and that the server is in round 1 of stopwatch mode.
3. Remove any spectators. Due to the /follow command, specs are forbidden in Shrub. Specs will not be locked in case an admin needs to log onto the server.
The match must start within 15 minutes of the default start time. To begin the match, teams ready up to start the round. Individual players must /ready. Once the round starts play is considered "LIVE".
NOTE: Due to limitations of the /ready command in Shrub, damage as been disabled during warmup.
Once a match begins, only ONE designated representative from each team (team captain/contact or designated player) is allowed to use mm1 (messagemode1, public talk) during a match. (See Section VII (Team Captains/Contacts Expectations)).
All players are required to take demos of each round and screenshots at the end of each round. (See Section XX (Demos/Screenshots))
XVII. Breaks/Halftime
There should be no more than 5 minutes of downtime between rounds with exception to the allowed 10 minute break at halftime (between rounds 2 and 3). Any delays beyond this not expressly agreed upon by both teams may result in the transgressing team's forfeiture of the match. (See Section XXIX (Disputes))
XVIII. Scoring
One point is awarded to the team with the lowest time in a single round. The first team to score 3 points wins the match. If both clans fail to achieve the objective in a single round, the round is considered a tie and neither clan is awarded a point.
Teams must play until 3 points are achieved by one team. In case of a 3-3 tie, teams will continue to play the same ABBA pattern until one team achieves victory.
STA-RTCW admins recognize that late matches can be a problem for teams. If a match goes into overtime and time becomes a factor for one/both teams, contact an admin for assistance.
XIX. Voice Communication
Use of communication programs such as the in-game voice communication (e.g. Ventrilo, Teamspeak, Roger Wilco) is acceptable and encouraged in STA-RTCW.
XX. Demos/Screenshots
All players are required to take demos of each round. These demos must also be available in the event an admin requests copies. Failure to provide these items immediately to an admin will result in a suspension.
XXI. Ping Imbalance
Pings and conditions should be playable for both teams and there should not be a huge discrepancy between teams. It is expected that a hosting team may have a "home-field advantage" to some degree. The difference between the two team's average pings on the match server should be no greater than 35 milliseconds (ms). If the difference between the average pings is less than 35 ms, the server is acceptable for play.
While the networking in RTCW is certainly better than almost any game out there, and while it is more HPB-friendly, there are certain times when there may be ping issues outside of a team’s control. Things such as poor routing are problems that are unfixable by teams/players. Pings must be confirmed in-game and teams should check for packet loss and playability.
If a server is either giving high pings to everyone on the server, or if the majority of the members of a team have unplayable pings (generally above 200 ms), a change of server may be requested. If the host team refuses to provide another server, an STA-RTCW admin may be called in to make a ruling on the server. If the STA-RTCW admin deems the server unplayable, the host team must either provide another server or play on the opposing team's server.
XXII. Server Crashes
If a server crashes during the middle of a stopwatch round, the server must be restarted and the half round will be reset. Any previous set/round scores are maintained. If the server should crash a second time, a change of server may be requested. If the host team refuses to provide another server, an STA-RTCW admin may be called in to make a ruling on the server. If the STA-RTCW admin deems the server unplayable, the host team must either provide another server or play on the opposing team's server.
XXIII. Post-Match, Match Reporting
At the conclusion of each match, BOTH teams are responsible for reporting the match’s scores and MVPs (one MVP for their team and 2 for the opposing team). Only team captains/contacts may submit scores and MVPs. The method of MVP selections is at the discretion of the team’s captain/contact.
MVPs are collected from each regular-season match and used to determine ProBowl candidates. The votes are tallied prior to the ProBowl match. The players with the most votes will be asked to compete in the ProBowl (See Section XXXIV (ProBowls)).
If there are disputes or problems with the match, they must be reported immediately to an STA-RTCW admin per Section XXIX (Disputes). In order to keep the league functioning smoothly, match scores must be submitted the night of the match Delays in reporting match results delay posting schedules for the next week.
XXIV. Player Conduct
STA-RTCW strives to provide a venue for fun yet competitive play and prizes sportsmanship above all else. Teams and members that do not display proper sportsmanship towards other teams will be considered for expulsion. Activities that would warrant this consideration include excessive mm1 spamming and abuse (in-game), and public defilement of other teams. Any abusive, racist or vulgar remarks used in mm1 during matches are grounds for expulsion by STA-Wolf. Screenshots and demos must be provided as proof.
This rule may apply to any electronic communication and through any medium that involves a member of STA-RTCW and any other member of STA-RTCW or its admins. This is, except in the most extreme circumstances, restricted purely to official league business. Official league business includes administrative duties and matches, and encompasses pre-match, match, and immediate post-match communications. Most other activities will fall outside the jurisdiction of STA-RTCW.
STA-RTCW forums are also held to these standards. Forums are a place to share information, opinions and interact socially. Accusatory and inflammatory remarks will not be tolerated. Inappropriate posts will be deleted, edited and or locked. Further disciplinary action may be taken for frequent offenders which may ultimately affect their respective team’s status.
Team leaders are held DIRECTLY RESPONSIBLE for the actions of their team members. If a member of their team is found to be guilty of a violation of sportsmanship STA-RTCW admins will deal directly with that team’s representative, who is expected to immediately meet with his/her player about the incident.
XXV. Double-Clanning & Ringers
STA-RTCW will not tolerate ringers/smurfs/double-clanning. This includes any person playing for an RTCW team for which they are not registered, signing up for more than one team (or the same team) in the same league, either under the same name, or a different name. It is also the act of playing for a team for which you are not registered under a false identity.
STA-RTCW strictly prohibits teams from using a player who is a member of two active STA-RTCW teams under any circumstances, within STA-Wolf or in another league. It is acceptable for a player to multi-clan with a team enrolled in another league as long as that team is not also active in STA. This is to avoid the appearance of conflicts in interest and/or the possibility of such conflicts. Any attempts to subvert this rule (e.g. pseudo names) are prohibited.
Consequences start with a forfeit loss for the offending team, and that team will be considered for immediate expulsion from STA-RTCW. The player caught ringing/smurfing/double-clanning will be expelled from the league and may be banned from all STA leagues. RTCW admins in other leagues will also be notified of the offense. Second offenses by members of the same team will result in the team or teams involved being removed from the league and forfeit of all matches played during that season.
Team rosters as listed on the STA-RTCW Web site will be used for primary determination of whether players are ringers, smurfs, et cetera. If there is doubt beyond site roster, STA-RTCW will resort to checking IP addresses, guids, and any other means deemed necessary.
XXVI. GUIDs
Each player is responsible for his/her guid. That includes keeping your guid information up-to-date on the STA-RTCW Web site and not distributing your guid to others. If you share your guid you do so at your own risk. So, for example, if Person A shares his/her guid with Person B and Person B is caught hacking, Person A is responsible for the consequences.
In the case a player has multiple guids, all guids must be listed on his/her team's STA-RTCW roster. If, at any time, there is potential for a guid to be used by another player (other then the player listed on the STA roster) league admins must be notified immediately.
Teams or individuals playing at LAN centers need to have the LAN center E-mail the an STA-RTCW admin with the following information: LAN Center name, Location, Public IP Address range, and ALL GUIDs for their center.
XXVII. Cheating
Internet gaming is plagued by an enormous population of irresponsible and value-less individuals who do not see the harm in introducing cheats, hacks, and spam into the community's consciousness. It is expected that no team in STA-RTCW cheats. Cheats include, but are not limited to:
1. Transparent texture override (a.k.a. hacked maps).
2. Models that extend beyond reasonable bounds.
3. Any mechanism by which information that is not normally available to the player is obtained (e.g. aim proxy, RW eavesdropping, spec cheating, and observing LAN players).
4. Nuking, channel takeovers, spamming, crashing a match server, or any other form of denial of service (DoS) are also considered cheating.
5. Any setting within the game that exploits that is not common knowledge and would give an unfair advantage.
6. Any script that is used to change game/player settings in attempts to subvert equal and fair play (e.g. scripts that rapidly change timenudge settings)
NOTE: While STA does not endorse the use of spawn timers, due to limitations in the coding of RTCW, the STA-RTCW league permits the use of spawn timers so that all clans can have an equal opportunity and playing field since there is no efficient way of regulating the use of them.
Precautions that can be taken by an STA-RTCW admin if individuals in a team have been suspected of cheating are:
1. Require rcon to check a server and players during a match.
2. Require both sides to submit in-game screenshots, demos, server logs, pbss, and ftp access during the match or at any time the STA-RTCW admins feel suitable.
3. STA-RTCW admins may request a copy of a cfg being used by a player.
4. STA-RTCW admins may also request a match is played or continued on a server of their choice where the admin has access to all these tools as well. Failure to cooperate will result in forfeit of the match.
If it is suspected that cheating occurs, notify an STA-RTCW admin with proof and the offending player(s)/team will be considered for expulsion. Proof may include demos, console logs and any other pertinent information and must be submitted within 48 hours of the incident. If a team claims that another team has cheated and cannot supply enough evidence to substantiate the claim the claim will be discarded. Spurious accusations of cheating will be considered a violation of proper conduct and action can be taken against the accusing team.
STA does not tolerate cheaters of any kind. Players found guilty of cheating will be banned (See XXXII, Inactivity, Team Expulsions, and Player Bans).
XXVIII. Bug, Map, Class, & Game Exploits
Map exploits are never, under any circumstance, acceptable. Map exploits include, but are not limited to:
Boosting
Boosting is defined as standing on top of another player in order to reach higher ground, such as boosting over the sea wall on mp_beach. The following are boosting restrictions:
1. Boosting more than 2 people high in a stack.
2. Boosting into areas that are "not intended" for players is prohibited. Most RTCW maps are clipped in areas that are unintended for play. However, if there is questionable areas contact an STA-RTCW Shrub admin immediately. In Shrub there is a map exploit on the sea wall in Beach that allows for a solo boost over the wall. It should not be used.
3. Grenades and airstrikes cannot be used to exploit the invulnerability time that a player has after respawn or after being revived to intentionally be "launched" across the map or into places players cannot normally access with a boost or jump.
Class Exploits
• Flamethrower Exploit: A flamethrower cannot be used to allow the flame to bounce off a solid object (wall, box, door). Doing so is an exploit that causes the flame becomes invisible to your opponent.
• Sniper Recoil: Snipers cannot set their map fps below 40. Doing so is an exploit that negates the sniper recoil. STA-RTCW match configs use PB settings that prevent this cheat. For the record, however, it is an exploit and illegal.
• Sniper Unscoped: Using an unscoped mauser is prohibited. It is possible for player to use an unscoped mauser. To others it will appear to be a scoped mauser. If killed by an unscoped mauser, the console would state, "WolfPlayer killed by SniperMan's Sniper Rifle" instead of Mauser.
Other Exploits
• Gold/Objective Passing: Players may not pass gold, documents, and other objectives through gates areas, which are intended to be closed off.
Uncommonly known exploits are NOT allowed, and instances of these exploits should be recorded and submitted to the league for review. Any such exploit used in a match that grants one player/team an unfair advantage may be considered cheating.
Common sense clause
If you have a question towards the legality of a possible exploit contact an admin as soon as possible to avoid being hit with infractions in the future. If a person is found to have used an exploit that gained them a large advantage they will not be able to hide behind "It wasn't stated as being an exploit in the rules", "I didn't know" or "other players are doing it". Spending hours upon hours searching for the next undocumented exploit that will gain you or your team an advantage in a match will no longer be a viable option. Players and teams will be held responsible for your actions when the exploit is found and a ruling is made on it. Punishment could vary and is completely at the admin’s discretion.
XXIX. Disputes
Teams are encouraged to find mutually acceptable solutions between team each team's representatives without the aid of an STA-RTCW admin. There are cases, however, in which an admin is needed.
In the event of a dispute, both teams must submit a claim package to the STA-RTCW admins for review as soon as possible. A claim package is a precise representation of a team’s claim that the opposing team’s actions warrant a forfeit loss for that team. Claim packages must include:
1. The rule violated by the opposing team, as quoted from this document.
2. How the rule was violated by the opposing team.
3. Proof that the rule was violated. Proof may be in the form of server logs, e-mails, ICQ logs, IRC logs, in-game screenshots, in-game demos, et cetera.
Once a claim packages has been received, STA-RTCW admins will handle all disputes in a timely, neutral, and unbiased manner. If the "accusing" team improperly handled the dispute procedure (e.g. flaming the accused team/admins or insufficient evidence) the dispute may be thrown out at the discretion of the admin staff. All rulings are final, and failure to adhere to any aspect of a ruling is grounds for expulsion.
Disputes may end in one of the following manners:
• Technical forfeit: Neither team earns a win or loss
• Forfeit by dispute: One of the two teams involved will earn a win by forfeit; the other will earn a corresponding loss.
Once a team captain/contact has contacted an admin about a dispute, interaction will ONLY be made with that admin unless otherwise notified. Decisions may not be appealed to another dispute handler.
In the case where another admin has been brought in for additional counsel, teams may not choose which administrator(s) will be called, nor can they appeal the decision once judgment has been passed.
Note: Any agreement that is made outside of the default STA-RTCW rules is not subject to STA-RTCW jurisdiction. Therefore, if a team makes an agreement to, for example, play an opposing team on a different day but the opposing team claims there is no proof of that agreement, then the STA-RTCW admin will assume the default settings were agreed upon.
If the case should arise that no STA-RTCW admins are available, another STA admin may be contacted. Contact information for STA admins can be found on the "staff contacts" link on the STA-RTCW Web site (http://wolf.sta-league.org).
XXX. Real-Time Disputes
If a dispute arises during gameplay and must be handled immediately, the disputing teams should send one representatives (preferably the team’s captain/contact) to IRC #sta-wolf on gamesurge.net. There they may contact an STA-RTCW admin. In the event that admins are unavailable, leave a personal message with an admin including IP, password, and brief description of the dispute.
XXXI. Wildcard Rule
Any dispute that will affect the outcome of a particular round should be addressed immediately. Play should be halted. A team with a legitimate claim should have its players drop to specs while a league admin is contacted to resolve the issue. Admins can be located on IRC in #sta-wolf on gamesurge.net. Demos and screenshots will be used to resolve the dispute and reset game clocks (if necessary). If a claimed dispute is not found to be legitimate, the disputing team may lose that round (not necessarily the match) based on admin’s discretion. Most disputes, legitimate or not, will not be honored if the disputing team waits until the end of the match to report. Disputes are not to be used as "get out of loss free" cards.
Note: Valid issues do not include player drops/pinging out etc unless it is determined to be an ongoing server issue.
XXXII. Inactivity, Team Expulsions, and Player Bans
Inactivity
Inactive teams are not scheduled for play. A team will be marked as inactive if any of the following conditions occur:
1. A team requests inactive status due to team-related issues. STA-RTCW admins may deny a team’s request for inactivity.
2. A team has forfeited matches for two consecutive play weeks.
Team Explusions
Teams may be expelled from the league if any of the following conditions occur:
1. A team as not contacted the STA-RTCW admins after having been inactive for at least one week due to double-forfeit rule (see above).
2. A team has violated rules and the STA-RTCW admins have agreed to ejection.
Player Bans
STA does not tolerate cheating of any kind. All allegations of cheating must be accompanied by proof to STA-RTCW admins within 48 hours of the incident (See Section XXVII, Cheating). The following are consequences for cheating:
1. During an STA-RTCW match: The offending player will be permanently banned from STA-RTCW and all STA leagues, the offending team will forfeit the match and all matches in which that player particpated during that season. In addition, STA-RTCW will announce publicly all pertinent facts to the community regarding the league's findings. RTCW admins in other leagues will also be notified of the offense.
2. During a non-STA-RTCW match: The offending player will be permanently banned from STA-RTCW and all STA leagues and the offending player's STA-RTCW team will forfeit all matches in which that player particpated during that season.
3. During a scrim or while pubbing: The offending player will be banned from STA-RTCW and all STA leagues for one year. Any repeat offense during the ban or thereafter will result in a permanent ban.
NOTE: Leniency will be given to teams that report hackers and cheaters within their own team to STA-RTCW admins. If a team reports the hacker/cheater and purges him/her from their roster, STA will waive the forfeiting of matches prior to the incident.
STA-RTCW admins may agree on suspending, ejecting a team, or banning a player(s) for reasons not outlined in this document.
XXXIII. Inter-Team Matches
STA-RTCW is a community-centric league and provides various venues for teams to get to know outside of their weekly matches. The following are the various types of inter-team matches that are organized by STA-RTCW admins:
XXXIV. ProBowls
ProBowls are exhibition matches for the purpose of community camaraderie as well as showing off some of each team's most talented players. Up to 2 ProBowl matches may be played in a season. MVP candidates are announced at least 2 weeks prior to the ProBowl match to allow for players to make schedule adjustments (if any).
ProBowlers are selected based on weekly MVP selections that are made by team captains/contact when they submit their scores. Team captains/contacts are required to submit their choice of MVP for their team and 2 MVPs from the opposing team. STA-RTCW admins review the submissions and tally votes per individual. Those that received the most from each team (2 per team) are selected for the ProBowl.
It is up to the individual team’s captain/contact how he or she selects the MVPs. Some go strictly by stats, others by game performance, but it is ultimately up to the captain to decide. Once the list is compiled, teammates are divided to allow teams to get to know their fellow STA Wolfers.
ProBowl matches consist of two team—Red and Blue. Captains for a Blue Team and a Red Team may be selected by STA-RTCW admins, though MVP candidates are encouraged to volunteer. All participants are required to wear their team's tag with their corresponding team color (Red or Blue). STA will provide game and voice servers for the event. Teams are prohibited from practicing more than once for this event as it may present an unfair advantage for a team without the same resources/time.
Regular season rules apply in ProBowl matches and maps are generally chosen that night by the ProBowlers from a limited list as determined by STA-RTCW admins. Moreover, admins will have the match broadcast on WolfTV or Shoutcast if possible.
XXXV. 10v10 Inter-Team
10v10 matches are scheduled based on the number of teams participating in any given season. In the case of a 10v10 match, 2 teams are paired and scheduled to face off against 2 other teams in a 10v10 match. Team pairings and matches are based on season records in attempt to provide balanced match play. Special requests for pairings will be considered as well.
Regular season rules apply in 10v10 matches. Teams are encouraged to coordinate voice communications and other matters so the paired teams may work together cohesively. Map is chosen by the league. These are exhibition matches for the purpose of community camaraderie and fun. They do not affect a team's record or status.
XXXVI. Rule Amendments
06/22/05 - Rules revamped for a ULTL Shrub league.
03/15/05 - Player Conduct section updated. Amended to provide further clarification of rule scope.
12/28/04 - Rules were revamped to elaborate on gray areas and update for functionality. Notable additions/changes include: (1) All match servers must capture PBSS, (2) Player ban specifications, (3) Match start time requirements, (4) Player GUID responsibilities, and (5) Demo/Screenshot specifications (e.g. seta cg_autoAction "7").
11/13/04 - Rules were corrected for spelling, minor grammar, and duplication.
06/30/04 - Rules on roster locks clarified. 8 week season (locked after week #5), 10 week season (locked after week#6)
-ProBowl games will be played the week after Final's match of playoffs.
-Pbguid rule updated- If at any time there is potential for a pbguid to be used by any other player/gamer other then the player listed on the STA roster STA admin's must be notified.
02-9-04 - The default format for match play is 6 vs 6 (min. players per team: 5) with a limit of 1 Panzer per side. If BOTH teams agree (before the start of a match) the match may be played 7 vs 7.
07/02/03 - Rosters are now on the STA site along with GUIDs and are required for a player to be eligible and will be locked every week on Sundays and Mondays.
11/07/02 - Exploits section updated.
10/02/02 - Inclusion of OSP & shrub information in servers section.
10/01/02 - Postponements. Matches may now be postponed to Tuesday night.
10/01/02 - Season Format section updated.
06/27/02 - Ascension matches section added.
05/06/02 - Server section: version rule updated. Servers are NOT to be updated with new patches until we clear them.
04/18/03 - Roster section updated: we actually use site rosters for initial determination of whether players are ringers/multi-clanners.
03/17/02 - Wildcard Rule
Almost all disputes should be reported immediately after the disputed incident occurs. That means the match should be halted and the disputing clan should contact an STA admin (found in #sta-wolf on irc.gamesnet.net). Most disputes, legitimate or not, will not be honored if the disputing clan waits until the end of the match to report. Disputes are not to be used as "get out of loss free" cards.
03/07/02 - Season format section completed; scheduling method added to scheduling section.
02/20/02 - "No Fullbright Command" removed from cheats section. It is okay to change any type of in-game variables to achieve better performance.
| Last Updated on September 30, 2008 |
|
|
|