| STA DC Rules |
I. Introduction
II. Clan Entrance
III. General Protocals
IV. Season Format
V. General Gameplay
VI. Ties
VII. STA-DC Map List
VIII. Server settings
IX. Servers
X. Scheduling
XI. PLayer Conduct
XII. Expectations
XIII. Clan Placement and Ranking
XIV. Multi-Clanning and Ringers
XV. Foreign Clans & Multi-Team Clans
XVI. Cheating
XVII. Map Exploits, Bugs and External Communications
XVIII. Disputes
XIX. Inactivity and Expulsions
XX. Punishment
I. Introduction
STA-DC was created for the enjoyment of playing competitive online gaming with the clans in mind. Please keep in mind that the administrators do this for pure enjoyment and should be treated with the utmost respect at all times as well as all players. STA is NOT a ladder, this is a league. This league is for BattleField 1942 Desert Combat, Conquest style.
II. Clan Entrance
For clans to be considered for entrance to STA-DC they should meet the following requirements:
1. Clans should have a FINISHED and professional looking website that INCLUDES a roster.
2. They should have no less then 10 members posted on their site rosters.
3. All STA-DC clans will be REQUIRED to maintain a REGISTERED channel on Gamesnet.net for their prospective clan.
4. Clans without league experience should have references from current, active, STA-DC clans.
5. ALL clan members should read thoroughly and understand ALL of the rules in STA-DC and WILL be expected to abide by all said rules.
III. General Protocals
Very simply, STA is a system of organized leagues, all run by individual administrators who have, in many cases, little contact with each other. That being said, all STA leagues operate under the same basic tenets of order, logic, equality and fairness.
And while STA is a service to clans, and the league does not profit in any way by clan participation, clans (and their members) in the STA Desert Combat league do reserve certain liberties.
1. All STA-DC league administrators, regardless of official capacity, are expected to make themselves available to clans.
For clan leaders: League administrators are required to make themselves available to clan leaders in a timely fashion and address any and all concerns, disputes and queries promptly and seriously.
For clan members: If any member of a clan (who is not in a position of leadership) within STA-DC requires contact regarding personal issues they may contact an administrator directly. All other operations, including official clan business, should be channeled appropriately through the team's listed clan leader or contact. Administrators reserve the right to deny communication with clan members if the capacity of the contact is related to official clan operations.
2. All forms of dispute must be accompanied with appropriate proof or evidence.
Any and all disputes and charges against other STA-DC clans must be accompanied with appropriate forms of proof or evidence, such as screenshots, demos and logs. Claims and accusations that are lacking in sufficient evidence will be discarded immediately.
3. Clans, clan leaders and clan members have the right to a fair and just decision.
Under any circumstances that require a ruling by an STA-DC official, clans, clan leaders and clan members have the right to a fair and just decision. If any person feels this right is violated, they should contact the Head Administrator with a full and detailed account of the proceedings.
4. Clans, clan leaders and clan members have the right to request an impartial ruling.
Under any circumstances that require a ruling by an STA-DC official, clans, clan leaders and clan members have the right to request the decision be ruled by more than one administrator in the name of impartiality. They do not have the right to choose which administrator(s) will be called in for additional counsel, nor can they appeal the decision once judgement has been passed.
5. All rulings are final, and failure to adhere to any aspect of a ruling is grounds for expulsion.
IV. Season Format
STA-DC is currently run in a Traditional "King of the Hill" format. Its setup is structured to provide competitive matches and rewards the most capable clans. Current map lists will be kept posted on the STA-DC website and will be updated from time to time. Title match/shot opportunities will be chosen by clans +/- win streak, current rank and total record in STA-DC. Non-Title or Title Shot matches may not be strictly chosen on the above criteria if teams have recently played eachother.
V. General Gameplay
Clans are expected to have a valid UPDATED roster on their website with at least 10 members who are active. They are also expected to keep a current active roster with STA-DC through the Operations link on the main page. As of 8/10/04 the rosters are also required to be updated with Punkbuster GUID numbers. These numbers are an ID assigned by Punkbuster and are calculated using a players CD Key. This means these ID's are unique to that player and can serve to identify a player in the event of cheating or accusations of ringers. Rosters will be LOCKED 24 hours prior to match night to prevent ringers/clan hoppers.
To find out a players GUID, have them join a Punkbuster enabled server, bring up the console (~ key) and type the following:
pb_plist
This will bring up a list of all the Punkbuster ID's for everyone on the server. We only require the last 9 digits of the GUID to be entered into the Roster. If you are a server administrator, you can also pull your clan's GUID's out of the log files in your /bf1942/pb/svlogs folder.
Type of Game play: Conquest
Number of Maps: 1 (Highest ticket count after 30mins and/or before time limit runs out wins)
Number of Squads: 2
Members per Squad: 10 (no less then 8)
Time Limit: 30 minutes per round, 2 rounds per map.
Friendly Fire: On (No Exceptions)
Rounds: 2
Mods: Desert Combat - Most current version (to be determined by STA-DC admins)
Map Selection: Random maps played weekly by entire league
Side Selection: Both
Map Play Order: Home team w/choice of side first OR server first.
With the latest release of BF1942, Punkbuster is now REQUIRED to be enabled and up to date on all match servers. Punkbuster is our first line of defense against cheats and should help prevent the majority of common hacks and cheats from occuring during gameplay. It is not perfect and we still suggest screenshots be taken of any questionable behavior that Punkbuster may not catch. Accusations of cheating will not even be considered if Punkbuster is not enabled on the server the match is being played on.
These are considered general guidelines for gameplay. STA-DC has no control over matchplay if BOTH clans agree to different terms BUT the STA-DC server config MUST still be used. If there is a problem with the agreement, clans should submit evidence of the agreement in the form of SS, IRC Logs or emails. If there is no evidence of any agreement, STA-DC shall assume standard gameplay rules are in effect and rule accordingly.
VI. Ties
There can be NO TIES in STA-DC. A tie shall be when the SUM of the ticket count of BOTH rounds is equal. In the instance of a tie, the team with the HIGHER team score, (most kills), shall be determined the winner. If the ticket count AND the team score are equal then the clans will go to a overtime round. Clans will play BOTH sides of the map, with the timelimit set to 15 mins. per round. The HIGHER ranked clan will have choice of the side OR server. The lower ranked clan gets choice of the other.
VII. STA-DC Map List
Current Maps considered for play (DC.7 and DC Final:
El_Alamein
El_Alamein Day 2 & 3
Gazala
Lost Village and LostVillage Nopara
Weapons Bunkers
Basrahs Edge
Basrah Nights
Stalingrad
Desert Shield
No Fly Zone Day 2
Berlin
Bocage
Kharkov
73 Eastings
Wake Island
Guadalcanal
Oil Fields
Aberdeen
Al Nas Day 1 & 2
Bridge
Cornered
Dustbowl
Twin Rivers
First Light
Maps NOT currently played:
Tobruk (Gameplay Issues)
Bocage_Day2 (Gameplay Issues)
Omaha Beach (Gameplay Issues)
Kursk (Gameplay Issues)
Iwo Jima (Gameplay Issues)
BattleAxe (Gameplay Issues)
Ishallah Valley (Gameplay Issues - Cap Points)
Battle of the Bulge (Gameplay Issues)
Al_Khafj_Docks (Gameplay Issues/Crash Problems)
Coral Sea (Gameplay Issues/Crash Problems)
Market Garden (Crash Problems)
Midway (Gameplay Issues)
Medina Ridge (Game format not compatible with STA-DC)
Operation Bragg (Vehicle Bugs)
Urban Siege (Lag issues)
Coastal Hammer (Lag issues)
VIII. Server settings
This server config will be used for ALL STA matches, NO EXCEPTIONS.
game.serverName "STA-DC Match in Progress"
game.serverPassword "putyourpasswordhere"
game.serverDedicated 1
game.serverGamePlayMode GPM_CQ
game.serverMaxPlayers 25
game.setServerTKPunishMode 1
game.serverScoreLimit 0
game.serverInternet 1
game.serverNumberOfRounds 2
game.serverSpawnTime 5
game.serverSpawnDelay 5
game.serverGameStartDelay 60
game.serverSoldierFriendlyFire 100
game.serverVehicleFriendlyFire 100
game.serverSoldierFriendlyFireOnSplash 100
game.serverVehicleFriendlyFireOnSplash 100
game.serverTicketRatio 200
game.serverGameTime 30
game.serverAlliedTeamRatio 1
game.serverAxisTeamRatio 1
game.serverCoopAiSkill 75
game.serverCoopCpu 20
game.ServerBandwidthChokeLimit 0
game.ServerAllowNoseCam 1
game.ServerFreeCamera 0
game.ServerExternalViews 1
game.ServerAutoBalanceTeams 0
game.ServerNameTagDistance 150
game.ServerNameTagDistanceScope 150
game.ServerKickBack 0
game.ServerKickBackOnSplash 0
game.serverHitIndication 1
game.ServerContentCheck 0
game.ServerDeathCameraType 0
game.serverEventLogging 1
game.serverEventLogCompression 1
game.serverPunkBuster 1
//STA Server Config edited by Crimson 2/8/04
IX. Servers
Each clan will have a choice of their own server for one set. Servers must be in the United States or Canada unless both clans agree to a foreign server. Cable Modem and DSL servers are not acceptable. Any server used to house STA-DC matches must be on a T1 or better line.
All servers must have the correct map version for the map assigned. Use of the STA-DC configuration file or settings are mandatory.(see section V). Servers must NOT be upgraded to the latest release of DC until we explicitly allow it with an announcement on the site. This way we can verify there are no game affecting bugs in new releases before using them.
All servers must be dedicated PURE BF42-Desert Combat servers. Listen servers are not acceptable under any circumstances. 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.
Should a match have already begun and the visiting clan recognizes that there is a problem with any server setting, they are still committed to playing the match. Server settings should be checked during prematch. When you join a server and begin playing, you are agreeing to the settings as they stand.
Server Crashes:
If a server crashes before 15 minutes have been completed, the server must be restarted and the game's score is reset to default ticket numbers for the map played. If the server crashes after 15 minutes have completed, this is considered a COMPLETE GAME and score stands. IF there is a crash, BOTH teams are encouraged to get screen shots of the outcome. If the server crashes a 3rd time, it is STRONGLY suggested that the teams move to a secondary server and try to replay the match. If there is no secondary server available, the teams should go to Gamesnet #STA-DC and seek help from the STA-DC admins.
Ping Imbalance:
There are certain times when there may be ping issues out of a clan's control. Things such as poor routing are problems that are non-fixable by players. Therefore, if a server is either giving high PL 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 asked for. If a clan refuses to provide another server, an STA-DC official may be called in to make a ruling on the server. If the STA-DC official deems the server unplayable, that clan must either provide another server or play on the opposing team's server.
Screenshots should be taken so that the STA admins can make a decision regarding pings.
X. Scheduling
Initial contact: Clans are expected to make contact at least 24 hours prior to game time. At this time, server information can be exchanged and any map details may be decided.
Starting Times:
Clans must be ready to play and on the server at the 9PM EST Tuesday nights. Clans that are short have a 15 minute grace period after the scheduled starting time to come up with a sufficient number of players to begin the match( minimum 10). If a clan has not entered the server with at least 10 players or more after 15 minutes past the scheduled starting time, the team that is ready to play may call for a forfeit. An STA-DC Admin MUST be made aware of the call for forfeit, and clans should NOT assume that just because 15 minutes has passed they automatically get a forfeit. Once a round is forfeited the match is over and the team that had a sufficient roster is the winner. Should both teams have insufficient numbers the match will be declared no match and the records will reflect forfeits by both teams.
Rescheduling: Clans may reschedule the time and day of their match if they BOTH agree. You MUST reschedule your match in the SAME week, BEFORE THURSDAY. 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. Clans may not reschedule matches later than Thursday night (see Postponements section below).
Postponement: Clans may postpone matches to Thursday of the same week. Postponed matches must be played by 11:59pm EST on THURSDAY. No exceptions and a STA-DC Admin WILL BE notifyed of the postponement.
If asked to reschedule by a clan, you must give that clan a response at least 24 hours before the match. 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 clan 24 hours to answer.
If a match is rescheduled and a clan reaches forfeit conditions (see below) due to absence of members, then that clan does not get the option of rescheduling the match again; hence that clan will receive a forfeit.
Clan matches are scheduled based on the following factors:
1. Current win/loss streak.
2. Current rank (win/loss record).
3. Previous opponents. STA-DC will endeavor to schedule clans against opponents that they have not played in at least two weeks.
More specifically, scheduling is done on a per-division basis as follows:
(-) Home/away team status is determined by previous home/away team status. Ideally all teams would alternate between home and away from week to week, but in practice this does not always work. Where it fails, we instead ht (see Postponements section below).
Postponement: Clans may postpone matches to Thursday of the same week. Postponed matches must be played by 11:59pm EST on THURSDAY. No exceptions and a STA-DC Admin WILL BE notifyed of the postponement.
If asked to reschedule by a clan, you must give that clan a response at least 24 hours before the match. 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 clan 24 hours to answer.
If a match is rescheduled and a clan reaches forfeit conditions (see below) due to absence of members, then that clan does not get the option of rescheduling the match again; hence that clan will receive a forfeit.
Clan matches are scheduled based on the following factors:
1. Current win/loss streak.
2. Current rank (win/loss record).
3. Previous opponents. STA-DC will endeavor to schedule clans against opponents that they have not played in at least two weeks.
More specifically, scheduling is done on a per-division basis as follows:
(-) Home/away team status is determined by previous home/away team status. Ideally all teams would alternate between home and away from week to week, but in practice this does not always work. Where it fails, we instead strive to maintain as close to a 50/50 home/away ratio for each clan as possible. (Home team is listed on the LEFT side of the schedule, away is on the RIGHT)
(-) Match-ups that have already occurred in the past two to four weeks (depending on the number of clans in the division) are unconditionally avoided.
(-) Naturally, due to odd numbers of clans in some of these categories, it is sometimes impossible to implement this scheduling method exactly as described. When an exception must be made, clans are matched up as "closely" as possible, in the sense of the determinants above. For example, if we have an odd number of 1L streak clans and an odd number of 1W streak clans (whereas the rest of them match up according to the scheme above with no extras), then a 1W clan must face a 1L clan. To determine this match, we choose the lowest performer of the 1W clans, and the highest performer of the 1L clans, relative to the determinants above.
At the conclusion of the match, BOTH teams are encouraged to report scores.
XI. PLayer Conduct
Clans and members that do not display proper sportsmanship towards other clans will be considered for expulsion. Activities that would warrant this consideration include excessive mm1 spamming and abuse(in-game), Taunts (in-game) and public defilement of other clans. Any abusive, racist or vulgar remarks used in mm1 during matches are grounds for expulsion by STA-DC. Screenshots and demos must be provided as proof.
This rule applies to any electronic communication and through any medium that involves a member of STA-BF42 and any other member of STA-DC or its Administrators.
Clan leaders are held directly responsible for the actions of their clan members. If a member of their clan is found to be guilty of a violation of sportsmanship the STA-DC will deal directly with that clan's representative, who is expected to immediately confront his/her player about the incident.
XII. Expectations
One of the main tenets of the Stronger Than All league is to provide clans and their players with a professional, logical, systematic approach to online gaming.
STA recognizes the wide spectrum of players that play under it's 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 clan leaders themselves.
STA Clan leaders have certain responsibilities that must be fulfilled in order for the STA league to remain functional. The bulk of these responsibilities is organizational and are as follows:
1. It is expected that all clan leaders are fully familiar with the rules. Much like 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 and/or ICQ.
3. Clan leaders are expected to keep current on changes to the website including; news updates, rule updates and schedules. Most crucial information will also be emailed.
4. Clan leaders are responsible for the conduct of their clan. Clan leaders may be held accountable for the actions of their individual clan members. Furthermore, leaders are responsible for educating their clan members on the STA rules of conduct and any other pertinent information.
5. Clans are expected AND REQUIRED TO maintain a IRC channel on gamesurge.net for ease of contact and should checkin on match nights in #STA-DC before their prospective matches.
Because of these responsibilities, Clan leaders are also acknowledged as worthy of respect and shall always be dealt with in an appropriate, respectful manner.
XIII. Clan Placement and Ranking
Initial placement:
Clans will be assigned a division based on their previous experience in organized BF or DC leagues, or non-league matches. Scrims will not be considered. Clans without any previous league or non-league match experience will be assigned to the Silver division. Clans that are reformations of other clans that have had experience under other names will be considered to start at a higher level. They need to email the division coordinator to ask for this change.
Evaluation period for new clans:
When a new clan is placed in their initial division, there will be a 2 match evaluation period. At the end of the evaluation period, the new clan liaison together with the corresponding division administrator can re-evaluate the placement of the clan and move them, if need be, to a more suitable division.
Movement to other divisions:
The STA encourages clans to strive to reach the next level. Consistent practice and devotion to the game can produce tremendous results. Therefore, division assignments are not static. Clans may move to a new division based on certain factors listed below. If a clan changes division, it keeps its win/loss record for STA, but has a separate record for the new division.
Movement to a higher division: By winning the title for the division and defending it for (1) one week OR attaining a +10 +/- for the current division requires the clan a move up to a higher division.
Movement to a lower division: A clan may ask to be moved to a lower division. The STA admins will consider the request and, for the most part, the request will be granted. 2 games will be required to be played in the new division before a move request is considered.
To ensure that the divisions are balanced, when a clan retires from competition or moves up/down from one division to another, the title holder from the lower division will be invited to replace them. If the title holder declines the invitation, the next ranked clan will be invited in their place. If there is no title holder currently from the lower division, then the next title match will not only determine the title holder but also who will move up to the upper division.
Administrators from time to time will move clans from one division to another to balance the divisions. These movements will be based upon their STA record (i.e. division ranking, win streak, overall record, etc.). Clan representatives will be contacted of the move and must agree/disagree to the changes before it is made official. While these changes are sometimes necessary, the STA will strive to make these types of movements to a minimum and will only be announced with at least 10 days notice. Included in this notice will outline what divk OR attaining a +10 +/- for the current division requires the clan a move up to a higher division.
Movement to a lower division: A clan may ask to be moved to a lower division. The STA admins will consider the request and, for the most part, the request will be granted. 2 games will be required to be played in the new division before a move request is considered.
To ensure that the divisions are balanced, when a clan retires from competition or moves up/down from one division to another, the title holder from the lower division will be invited to replace them. If the title holder declines the invitation, the next ranked clan will be invited in their place. If there is no title holder currently from the lower division, then the next title match will not only determine the title holder but also who will move up to the upper division.
Administrators from time to time will move clans from one division to another to balance the divisions. These movements will be based upon their STA record (i.e. division ranking, win streak, overall record, etc.). Clan representatives will be contacted of the move and must agree/disagree to the changes before it is made official. While these changes are sometimes necessary, the STA will strive to make these types of movements to a minimum and will only be announced with at least 10 days notice. Included in this notice will outline what divk OR attaining a +10 +/- for the current division requires the clan a move up to a higher division.
XIV. Multi-Clanning and Ringers
STA-DC will not tolerate ringers or multi-clanners. A ringer is any person playing for a Desert Combat clan they are not currently a member or recruit of. A multi-clanner is any player currently in a Desert Combat OR Battlefield 1942 clan participating in STA-DC who belongs to another BF42 or Desert Combat clan, whether or not that BF42/DC clan is currently participating in STA-DC.
STA-DC strictly prohibits clans from using players that are a member of two active clans at the same time, whether in STA-DC, or any other league. Punishment will start with a forfeit loss for the offending clan, and that clan will be considered for immediate expulsion from STA-DC.
XV. Foreign Clans & Multi-Team Clans
Foreign clans are welcome in STA-DC as long as they adhere to our 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 clan and an STA-DC administrator. No exceptions. In addition, it is understood that foreign players'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 clan will in general be disregarded.
Multiple teams from a single clan will be allowed on a case by case basis and can be revoked by the Admins at any time. If a team's roster is large enough that they feel they can field more than one team per week, they can request a second team be added. If accepted, Rosters must be SPLIT between the two teams. One team will be assigned as the main team, and the other as the secondary team.
Movement of members between teams will only be allowed in one direction, from secondary to main, to prevent players from the main team from being brought in on the secondary team's matches. The 24 hour roster lock will also still apply. Violation of the roster rules could result in the expulsion of BOTH teams from the league.
XVI. 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 clan in STA-DC cheats. Cheats include, but are not limited to:
Using Aim Bots to increase accuracy of your guns. Using different models that originally came with the game to give you an advantage over the opponents.
The Blood patch is allowed for use during STA matches
Precautions that can be taken by an STA-DC Coordinator if individuals in a clan have been suspected of cheating are:
1. An STA-DC Coordinator must be given rcon to check IP addresses during a match if it is deemed necessary by the Coordinator.
2. Both sides may be asked to submit in-game screenshots during the match or at any time the STA-DC Coordinator feels suitable.
If it is somehow determined that a clan is cheating in league play, that clan will be removed from the league immediately and permanently. Adequate proof in the form of screenshots, demos, and logs must be provided to the STA-DC before a ruling is made.
If it is found that cheating occurs, notify an STA-DC official with proof and the offending clan will be considered for expulsion. 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.
XVII. Map Exploits, Bugs and External Communications
Voice communication is allowed and encouraged in STA-DC and is not considered an Exploit.
Map exploits are never, under any circumstance, acceptable. Map exploits include, but are not limited to: Map bugs, speed hacks, explosion and weapon bugs, Superman bug, using walls, floors, ceilings or other inanimate objects to gain a advantage on your opponent, (this does NOT include parachuting onto a roof to capture a point), etc... Submerging completely underwater is NO LONGER allowed AT ANY TIME. Please do not do it.
Any act to change the structure and/or goals of a map or the engine of the game are considered illegal for STA match play. Proof can include screenshots and/or demos, if clans are found using them by the STA intentionally they will forfeit the match and suspensions/bans will be handed out to guilty person(s).
Uncommonly known exploits are NOT allowed, and instances of these exploits should be recorded and submitted to the league for review. These exploits and bugs will be dealt with on a case by case basis and IF there is a question about them it is best to ask a admin about it before trying it in a match. Any such exploit used in a match that grants one player/team an unfair advantage may be considered cheating.
XVIII. Disputes
In the event of a dispute, both clans involved must submit a claim package to the STA-DC administrators for review, WITHIN 24 hours of the completion of the match. 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 screenshots
- in-game demos
For dispute handling, it is best to go to your STA-DC administrators first. However, in the event that your administrator is not there, one of the other administrators listed on the contacts page may be used. Note that once you talk to someone about a dispute, you will deal ONLY with that staff member, and once he has made a ruling, the decision is final and may not be appealed to another dispute handler.
Also, any agreement that is made outside of the default STA-DC rules is not subject to STA/STA-DC jurisdiction. What this means is that if you make an agreement to, say, play a clan on a different day but they say you didn't, and you have no proof of that agreement, then the STA-DC official will assume the default settings were agreed upon.
Disputes may end in one of the following manners:
- Technical forfeit
Neither clan earns a win or loss
- Forfeit by dispute
One of the two clans involved will earn a win by forfeit; the other will earn a corresponding loss
The transgressing clan (only in forfeit by dispute case) may be expelled if the STA-DC administrators deem it appropriate due to the situation at hand.
-Real-Time Dispute Handling-
If a dispute must be handled immediately, the disputing clans should send representatives, and only representatives, to IRC channel #STA-DC on irc.gamesnet.net. There they may contact the STA-DC administrators or disputes handler, as listed on the STA-DC contacts pages. If there is no STA-DC official able to handle the dispute at the time, clans should follow the outline given above. Note that for all disputes, clans are encouraged to find mutually acceptable solutions without the aid of an STA-DC official.
-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-DC 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.
XIX. Inactivity and Expulsions
A clan is marked as inactive if any of the following conditions occur:
1.Clan is going inactive and has requested the suspension
-or-
2.Clan has forfeited matches for two consecutive play weeks
Inactive clans are not scheduled for play. STA-DC administrators may deny a clan's request for inactivity.
A clan is expelled from the STA-DC if any of the following conditions occur:
1. STA-DC has a ZERO TOLLERANCE policy for forfeits. If you don't have the players, don't join the league. It is not fair to punish other clans because your clan cannot field a full team.
It is STRONGLY suggested that the clan request a bye or to be moved to inactive status if they think there may be a problem fielding a team.
2.Clan has not contacted the STA-DC admins after having been inactive for at least one week due to double-forfeit rule.
3. Clan has violated rules and the STA-DC admins have agreed to ejection.
STA-DC Admins may agree on suspending or ejecting a clan for reasons not outlined in this document.
XX. Punishment
Punishment:
STA-DC follows a 3 strikes and your out policy. Clans should be reminded that they WILL be held accountable for actions of ONE member and/or ALL members.
Punishment will be handed out on a case by case basis. For major offenses, removal from the league may be in order. The general penalties are as follows:
· First Strike
You will be given a STRONG VERBAL WARNING and/or forfeit said match the rules violation took place in and/or given a one week suspension from league play.
· Second Strike
You will be suspended from STA match play for two weeks and/or forfeit said match the violation took place in.
· Third Strike
You will be removed from STA for continually being unable to follow the rules given.
| Last Updated on June 1, 2006 |
|
|
|