| STA BF2 Rules |
I. Introduction
II. Team Entrance
III. General Protocols
IV. Season Format
V. General Gameplay
VI. Match Process
VII. Substitutions
VIII. Ties
IX. Servers
X. STA-PoE:2 Map List
XI. Match Config
XII. Punkbuster Server Settings
XIII. Server Crashes
XIV. Voice Communication
XV. Demo Recording
XVI. Scheduling
XVII. Player Conduct
XVIII. Expectations
XIX. Foreign Teams & Multi-Team Teams
XX. Multi-Teamning and Ringers
XXI. Team Placement and Ranking
XXII. Cheating
XXIII. Map Exploits and Bugs
XXIV. Disputes
XXV. Inactivity and Expulsions
XXVI. Punishment
XXVII. Rule updates
I. Introduction
Introduction
STA-PoE:2 was created for the enjoyment of playing competitive online gaming with Teams 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 2 Point of Existence, Playing Conquest, Frontline and Objective style games.
II. Team Entrance
Team Entrance
For Teams to be considered for entrance to STA-PoE:2 they should meet the following requirements:
1. Teams should have a FINISHED and professional looking website that INCLUDES a roster.
2. They should have no less then 12 members posted on their site rostersfor the 12v12 league & 8 for the 8v8 league.
3. All STA-PoE:2 Teams will be REQUIRED to maintain a REGISTERED channel on GameSurge.net for their prospective Team.
4. Teams without league experience should have references from current, active, STA-PoE:2 Teams.
5. ALL Team members should read thoroughly and understand ALL of the rules in STA-PoE:2 and WILL be expected to abide by all said rules.
III. General Protocols
General Protocols
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 Teams, and the league does not profit in any way by Team participation, Teams (and their members) in the STA Battlefield 2 PoE:2 league do reserve certain liberties.
1. All STA-PoE:2 league administrators, regardless of official capacity, are expected to make themselves available to Teams.
For Team leaders: League administrators are required to make themselves available to Team leaders in a timely fashion and address any and all concerns, disputes and queries promptly and seriously.
For Team members: If any member of a Team (who is not in a position of leadership) within STA-PoE:2 requires contact regarding personal issues they may contact an administrator directly. All other operations, including official Team business, should be channeled appropriately through the team's listed Team leader or contact. Administrators reserve the right to deny communication with Team members if the capacity of the contact is related to official Team operations.
2. All forms of dispute must be accompanied with appropriate proof or evidence.
Any and all disputes and charges against other STA-PoE:2 Teams 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. Teams, Team leaders and Team members have the right to a fair and just decision.
Under any circumstances that require a ruling by an STA official, Teams, Team leaders and Team 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. Teams, Team leaders and Team members have the right to request an impartial ruling.
Under any circumstances that require a ruling by an STA official, Teams, Team leaders and Team 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 judgment 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
Season Format
STA-PoE:2 is currently run in a Traditional "King of the Hill" format. Its setup is structured to provide competitive matches and rewards the most capable Teams. Current map lists will be kept posted on the STA-PoE:2 website and will be updated from time to time. Title match/shot opportunities will be chosen by Teams +/- win streak, current rank and total record in STA-BF2. Non-Title or Title Shot matches may not be strictly chosen on the above criteria if teams have recently played each other.
V. General Gameplay
General Gameplay
Teams are expected to have a valid UPDATED roster on their website with at least 12 members for the Gold Division and 8 for the Silver Division, who are active.
They are also expected to keep a current active roster with STA-PoE:2 through the Operations link on the main page. The rosters are also required to be updated with Punkbuster GUID numbers (last 8 charters).
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/Team 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 Team's GUID's out of the log files in your Battlefield2/pb/svlogs folder.
GOLD DIVISION:
Type of Game play: Conquest - Frontline - Nuke
Number of Maps: 1
After both teams have played both sides, the team with the highest ticket total is determined to be the winner of the match.
Number of Teams: 2
Members per Squad: 12 (no less then 10) The default team size is 12, but larger matches are more favorable to Point of Existence any number over the default size must be agreed to. Teams unable to field 12 players may play with 10, but the other team may still play with 12.
Time Limit: None, 2 rounds per map.
Friendly Fire: On (No Exceptions)
Ticket Settings: TBD
Rounds: 2
Map Size: 32
Map Selection: Random maps played weekly by entire league and will be posted on the site.
Side Selection: Both
Map Play Order: Home team w/choice of side first OR server first.
There will be a standard 5 min break between rounds unless teams agree to play without the break.
SILVER DIVISION:
Type of Game play: Conquest - Frontline - Nuke
Number of Maps: 1
After both teams have played both sides, the team with the highest ticket total is determined to be the winner of the match.
Number of Teams: 2
Members per Squad: 8 (no less then 6) The default team size is 8, but larger matches are more favorable to Point of Existence any number over the default size must be agreed to. Teams unable to field 8 players may play with 6, but the other team may still play with 8.
Time Limit: None, 2 rounds per map.
Friendly Fire: On (No Exceptions)
Rounds: 2
Map Size: 16
Ticket Settings: TBD
Map Selection: Random maps played weekly by entire league and pposted on the website.
Side Selection: Both
Map Play Order: Home team w/choice of side first OR server first.
There will be a standard 5 min break between rounds unless teams agree to play without the break.
Punkbuster is 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 occurring 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 has no control over match play if BOTH Teams agree to different terms BUT the STA-PoE:2 server config MUST still be used.
If there is a problem with the agreement, Teams should submit evidence of the agreement in the form of SS, IRC Logs or emails. If there is no evidence of any agreement, STA shall assume standard gameplay rules are in effect and rule accordingly.
After the completion of the match the both teams are required to immediately report the results, regardless if a dispute is going to be filed.
If there is a dispute the results can be altered accordingly. The scores are to be posted as the ticket count of each round. (Example: 115-0 or 72-26). Teams will have until 11:59 PM (EST)on match night (Tuesday or Thursday depending on your division) to submit results. If no results are submitted both teams will receive a Technical Forfeit.
VI. Match Process
Both teams must be ready to start the match 15 minutes after the agreed upon (or default) match time. During this 15 minute period, teams should confirm that their opponent's roster is accurate and legal, and that the server settings are correct. This must take place BEFORE the match begins. Any player who is not on the roster with a matching GUID is considered ineligible and can be asked to leave the server. If the 15 minutes pass and there are no complaints from either team about roster or server settings, the match will proceed and all players ON THE SERVER will be considered valid. STA Admins will not accept disputes over a roster or settings issue after the match has been played, unless an illegal substitute player from outside the server was used in the middle of a match. Once the match begins both teams agree that the server settings and rosters are in order.
Teams will be allowed to take a small break between rounds, this should last no longer than 5 minutes.
VII. Substitutions
Substitutions may be made at any time during the Match. In the case of a substitution, the member that is being subbed OUT must leave the game PRIOR to when the member subbing IN arrives into the game. This prevents unbalanced teams during a substitution.
VIII. Ties
Ties
There can be NO TIES in STA-BF2. A tie shall be when the SUM of the ticket count of BOTH rounds is equal. In the instance of a tie, a 2 round winner take all sudden death will be played. The Home Team will have choice of the side OR server. The visiting Team gets choice of the other. Teams will play EACH side of the map, with the time limit set to 15 mins. per round.
The Standard 5 min break between rounds will apply
IX. Servers
Server
Each Team will have a choice of their own server for one set. Servers must be in the United States or Canada unless both Teams agree to a foreign server. Cable Modem and DSL servers are not acceptable. Any server used to house STA 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-PoE:2 configuration file or settings are mandatory.(see section V). Servers must NOT be upgraded to the latest release of BF2 or PoE:2 until we explicitly allow it with an announcement on the site. This way we can verify there is no game affecting bugs in new releases before using them and that all teams have an opportunity to get servers updated.
Listen servers are not acceptable under any circumstances. If any of these settings are not correct, the opposing Team 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 Team.
Should a match have already begun and the visiting Team recognizes that there is a problem with any server settings, they are still committed to playing the match. Server settings should be checked during pre-match. When you join a server and begin playing, you are agreeing to the settings as they stand. Once the Match has started you have agreed the setting are correct.
X. STA-PoE:2 Map List
STA-PoE:2 Map List (Not in Scheduling order)
Battle of Sambir: Conquest
Carpathian Mountains: Conquest/Nuke
Dnipiro Sunrise: Conquest/Frontline
Dnister River Valley: Conquest/Frontline
Fallen: Conquest
First Snow: Conquest/Frontline
Guardian: Conquest/Frontline
Highway to Hell: Conquest/Frontline
Lutsk: Conquest/Frontline
Orel: Conquest/Frontline
Rivne: Conquest/Frontline
Rolling Thunder: Conquest
Zhytomyr: Conquest/Frontline
XI. Match Config
Server settings
Match Config:
Currently under Development
Map Rotation:
The only map in rotation should be the map that is being played. All maps in the BF2-STA League will be 32 player Maps for the Gold Division and 16 player maps for the Silver Division.
XII. Punkbuster Server Settings
Punkbuster Server Settings
File Name: pbsv.cfg
Under Development
XIII. 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 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.
In the event of a third crash, the game must be cancelled and team captains must contact an admin (IRC GameSurge #STA). An admin may assign a server and have the match restarted, or allow for a reschedule of the remaining rounds to be played.
XIV. Voice Communication
The use of voice communication programs (such as Teamspeak or Ventrilo) in STA matches is completely acceptable. VOIP within BF2 May be used if the server is configured for it. If not it will be the responsibility of each team to provide their own communications systems.
XV. Demo Recording
Demo Recording
Teams are now required to demo every match for the entire duration of the match. These demos are to be handed over to a STA Admin upon request, where they will be subject to review by multiple STA Admins. Demos are to be held no less than 1 week after match date. There are consequences for not producing demos when asked.
• 1st Offense – Team forfeits match.
• 2nd Offense – 2 match suspension
• 3rd Offense – Removed from league.
Teams will not be required to hand over demos to other teams unless a dispute is filed.
If some form of conduct is being questioned, Teams maybe required to forward them to an STA Admin.
XVI. Scheduling
Scheduling
Initial contact: Teams 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:
Teams must be ready to play and on the server at 9:00 PM eastern on Tuesday nights or 9:00 PM eastern Thursday nights (Depending on your Division). Teams 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 for Gold & 6 for Silver). If a Team has not entered the server with at least the above mentioned 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-PoE:2 Admin MUST be made aware of the call for forfeit, and Teams 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: Teams may reschedule the time and day of their match if they BOTH agree. You MUST reschedule your match in the SAME week, BEFORE THURSDAY (for the Gold Division) or before Saturday (for the Silver Division). 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. Teams may not reschedule matches later than Thursday or Sarurday night depending on your division (see Postponements section below).
Postponement: Teams may postpone matches to Thursday of the same week or Saturday (Depending on your Division). Postponed matches must be played by 11:59pm EST on THURSDAY or Saturday. No exceptions and a STA-PoE:2 Admin WILL BE notified of the postponement.
If asked to reschedule by a Team, you must give that Team 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 Team 24 hours to answer.
If a match is rescheduled and a Team reaches forfeit conditions (see below) due to absence of members, then that Team does not get the option of rescheduling the match again; hence that Team will receive a forfeit.
Team matches are scheduled based on the following factors:
1. Current win/loss streak.
2. Current rank (win/loss record).
3. Previous opponents. STA-PoE:2 will endeavor to schedule Teams 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 will make every effort to keep all things equal.
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 Team 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 Teams in the division) are unconditionally avoided.
(-) Naturally, due to odd numbers of Teams in some of these categories, it is sometimes impossible to implement this scheduling method exactly as described. When an exception must be made, Teams 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 Teams and an odd number of 1W streak Teams (whereas the rest of them match up according to the scheme above with no extras), then a 1W Team must face a 1L Team. To determine this match, we choose the lowest performer of the 1W Teams, and the highest performer of the 1L Teams, relative to the determinants above.
At the conclusion of the match, BOTH teams are required to report scores.
XVII. Player Conduct
Player Conduct
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), Taunts (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-BF2. 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-PoE:2 and any other member of STA-BF2 or its Administrators.
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 the STA will deal directly with that Team's representative, who is expected to immediately confront his/her player about the incident.
XVIII. Expectations
Expectations
One of the main tenets of the Stronger Than All league 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 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 Team leaders themselves.
STA Team 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 Team leaders are fully familiar with the rules. Much like in real life, ignorance is not an excuse.
2. Team leaders must be easily accessible. Email must be working and checked regularly. Contact must also be possible through IRC and/or ICQ & X-Fire.
3. Team 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. Team leaders are 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. Teams are expected AND REQUIRED TO maintain a IRC channel on gamesurge.net for ease of contact and should check in on match nights in #STA-BF2 before their prospective matches.
Because of these responsibilities, Team leaders are also acknowledged as worthy of respect and shall always be dealt with in an appropriate, respectful manner.
XIX. Foreign Teams & Multi-Team Teams
Foreign Teams & Multi-Team Teams
Foreign Teams are welcome in STA-PoE:2 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 Team and an STA-PoE:2 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 Team will in general be disregarded.
Multiple teams from a single Team 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.
XX. Multi-Teamning and Ringers
Multi-Teamning and Ringers
STA-BF2 will not tolerate Smurfing/Ringing/Double Clanning. Double Clanning is 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 you are not registered to play for, under a false identity.
A player is allowed to play on only 1 team within the Game. There will be no crossover from 1 league to the other within a GAME. Players Caught playing on more then 1 league team will be suspended and the team will at the discursion of the admin receive either a forfeiture, suspension or removal of the league.
Playing for a team you are not registered to play for is prohibited. Playing on more than one team per league is also prohibited, as is registering multiple accounts for use on the same team or ladder.
Any player caught Smurfing will be Suspended or expelled from the League and may be banned from STA. Second offenses will result in the team or teams involved being remove from the League. Teams are also subject to receiving forfeit losses of there match if found to have Played Smurfs.
XXI. Team Placement and Ranking
Team Placement and Ranking
Initial placement:
The STA encourages Teams to strive to reach the next level. Consistent practice and devotion to the game can produce tremendous results. Therefore, division assignments are not static. Teams may move to a new division based on certain factors listed below. If a Team 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 Team a move up to a higher division.
Movement to a lower division: A Team 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 Team 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 Team 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 Teams 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.). Team 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 Team a move up to a higher division.
Movement to a lower division: A Team 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.
XXII. Cheating
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-PoE:2 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.
Precautions that can be taken by an STA-PoE:2 Coordinator if individuals in a Team have been suspected of cheating are:
1. An STA 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 Coordinator feels suitable.
If it is somehow determined that a Team is cheating in league play, that Team 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 before a ruling is made.
If it is found that cheating occurs, notify an STA-PoE:2 official with proof and the offending Team will be considered for expulsion. Proof may include demos and console logs. If your Team claims that another Team 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 Team.
XXIII. Map Exploits and Bugs
Map Exploits, Bugs and External Communications
Voice communication is allowed and encouraged in STA-PoE:2 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...
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 Teams 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.
XXIV. Disputes
Disputes
In the event of a dispute, both Teams involved must submit a claim package to the STA-PoE:2 administrators for review, WITHIN 24 hours of the completion of the match. 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:
- rule violated by opposing Team, as quoted from this document
- how the rule was violated by the opposing Team
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-PoE:2 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-BF2 rules is not subject to STA/STA-PoE:2 jurisdiction. What this means is that if you make an agreement to, say, play a Team on a different day but they say you didn't, and you have no proof of that agreement, then the STA official will assume the default settings were agreed upon.
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
The transgressing Team (only in forfeit by dispute case) may be expelled if the STA-BF2 administrators deem it appropriate due to the situation at hand.
-Real-Time Dispute Handling-
If a dispute must be handled immediately; the disputing Teams should send representatives, and only representatives, to IRC channel #STA-BF2 on irc.gamesnet.net. There they may contact the STA-BF2 administrators or disputes handler, as listed on the STA-PoE:2 contacts pages. If there is no STA-PoE:2 official able to handle the dispute at the time, Teams should follow the outline given above. Note that for all disputes, Teams are encouraged to find mutually acceptable solutions without the aid of an STA 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 Team should contact an STA admin (found in #STA on irc.gamesurge.net). 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.
XXV. Inactivity and Expulsions
Inactivity and Expulsions
A Team is marked as inactive if any of the following conditions occur:
1.Team is going inactive and has requested the suspension
-or-
2.Team has forfeited matches for two consecutive play weeks
Inactive Teams are not scheduled for play. STA-BF2 administrators may deny a Team's request for inactivity.
A Team is expelled from the STA-PoE:2 if any of the following conditions occur:
1. STA-PoE:2 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 Teams because your Team cannot field a full team.
It is STRONGLY suggested that the Team request a bye or to be moved to inactive status if they think there may be a problem fielding a team.
2.Team has not contacted the STA-PoE:2 admins after having been inactive for at least one week due to double-forfeit rule.
3. Team has violated rules and the STA-PoE:2 admins have agreed to ejection.
STA-PoE:2 Admins may agree on suspending or ejecting a Team for reasons not outlined in this document.
XXVI. Punishment
Punishment
Punishment:
STA-PoE:2 follows a 3 strikes and your out policy. Teams 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.
XXVII. Rule updates
Rule updates
STA-PoE:2 admins reserve the right to update or modify these rules as more information becomes available. Notice will be placed on the main STA-PoE:2 website if modifications are made.
Rules last updated 8/14/2006
| Last Updated on October 4, 2006 |
|
|
|