STA Battlefield 2142 - Rules

STA POE Rules I. Introduction II. Team Entrance III. General Protocal IV. Season Format V. General Gameplay VI. Ties VII. STA-SCEP Map List VIII. Server settings IX. Servers X. Scheduling XI. Player Conduct XII. Expectations XIII. Team Placement and Ranking XIV. Multi-Teamning and Ringers XV. Foreign Teams & Multi-Team Teams XVI. Cheating XVII. Map Exploits, Bugs and External Communications XVIII. Disputes XIX. Inactivity and Expulsions XX. Punishment XXI. Attachement #1 I. Introduction STA-SCEP Testing 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 2142, Titan Mode. This league will be centered around competitive gaming, but teams will be expected to provide feedback to DICE for further development of Battlefield 2142. II. Team Entrance The is an invite only league, for Teams to be considered for entrance to STA-SCEP they should meet the following requirements: 1. Teams will be required to be approved by the provider (DICE). 2. They should have no less then 16 members posted on their site rosters. 3. ALL Team members should read thoroughly and understand ALL of the rules in STA-SCEP and WILL be expected to abide by all said rules. III. General Protocal 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 Point of Existence league do reserve certain liberties. 1. All STA-SCEP 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-SCEP 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-SCEP 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-SCEP 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-SCEP 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 STA-SCEP 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-SCEP 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-SCEP. 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 Type of Game play: Titan Game Mode Number of Maps: 1 Number of Teams: 2 Members per Squad: 18 (no less then 16) The default team size is 16, but a 18vs18 is more favorable to the SCEP Battlefield. Teams are encouraged to play 18 vs 18 or more but it is not required! Time Limit: None, 3 rounds per map. Friendly Fire: On (No Exceptions) Rounds: Best 2 out of 3 (No Time Limit) Mods: None Map Selection: Beta Map Side Selection: Home team will also start on PAC. If at the end of 2 rounds and each team has 1 titan kill, the home team will get side choice. Winning Team is determined by the first team to destroy the enemy's Titan will be awarded the win for that round. A Match is made up of 3 rounds; first team to get 2 Titan kills wins the match. Server will be provided by management and configured per DICE. VI. Ties There can be NO TIES in STA-SCEP. VII. STA-SCEP Map List Current Maps considered for play: Verdan VIII. Server settings To be configured by DICE. IX. Servers DICE will provide Servers for the matches. Team leaders will be given rcon to restart maps or DICE will provide an individual with admin access. X. Scheduling Initial contact: Teams are expected to make contact at least 24 hours prior to game time. Starting Times: Will very, over the 3-4 week period of the SCEP teams will be scheduled 2-3 matches per week. Teams maybe scheduled double matches on the weekends to ensure all scheduled matches are completed Rescheduling: Teams may reschedule the time and day of their match if they BOTH agree. But matches must be completed in a timely fashion. 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-SCEP 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 ht (see Postponements section below). 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. (-) 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 encouraged to report scores. Scores will be reported but the number of titan kills i.e. 2-1, 2-0. XI. 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-SCEP. 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-SCEP and any other member of STA-SCEP 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-SCEP will deal directly with that Team'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 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. 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 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. XIII. 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. 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. XIV. Multi-Teamning and Ringers During this beta testing this rule will be suspended XV. Foreign Teams & Multi-Team Teams Foreign Teams are welcome in STA-SCEP 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-SCEP 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. 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 Team in STA-SCEP 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-SCEP Coordinator if individuals in a Team have been suspected of cheating are: 1. An STA-SCEP 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-SCEP 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-SCEP before a ruling is made. If it is found that cheating occurs, notify an STA-SCEP 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. XVII. Map Exploits, Bugs and External Communications Voice communication is allowed and encouraged in STA-SCEP 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. All So See Attachment #1 Identified Exploits. 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. SCEP Rule: Screenshots or demos should be used to point out issues to the management. XVIII. Disputes In the event of a dispute, both Teams involved must submit a claim package to the STA-SCEP 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-SCEP 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-SCEP rules is not subject to STA 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-SCEP 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-SCEP 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-SCEP on irc.gamesnet.net. There they may contact the STA-SCEP administrators or disputes handler, as listed on the STA-SCEP contacts pages. If there is no STA-SCEP 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-SCEP official. -WilSCEPard 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-SCEP on irc.gamesnet.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. XIX. 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 matches Inactive Teams are not scheduled for play. STA-SCEP administrators may deny a Team's request for inactivity. A Team is expelled from the STA-SCEP if any of the following conditions occur: 1. STA-SCEP 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-SCEP admins after having been inactive for at least one week due to double-forfeit rule. 3. Team has violated rules and the STA-SCEP admins have agreed to ejection. STA-SCEP Admins may agree on suspending or ejecting a Team for reasons not outlined in this document. If your team is expelled your CD keys will be removed. XX. Punishment Punishment: STA-SCEP 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. XXI. Attachement #1 Identified Explotes: The use of any of the below tactic's would result in your team being disqualified. Please ensure you understand what they are and how not to use them. Any player by accident that would end up in the Hanger bey or the titan core without the blast doors being opened should immediately suicide. Below you will find a list of the exploits that would be considered a violation of the rules for this league. Any team found using them would be DQ'ed Master Exploit List: Tested exploits that SHOULD NOT BE USED ----------------------------------------------------------- 1. Stat padding - Repeated killing and reviving of a player in order to gain points. I am sure everyone knows this.. ----------------------------------------------------------- 2. Core glitching - There is a way to fall through a door into the core room when approaching the the door at a angle. Then the ship can be destroyed from inside without destroying the panels. Another door (furthest away from stairs) when inside you can shoot through but not move through. http://img241.imageshack.us/img241/3965/screen000rf4.jpg http://img152.imageshack.us/img152/4468/screen001sj9.jpg ----------------------------------------------------------- 3. The large rear door on the back of the titan you can see AND shoot through into the titans. http://img520.imageshack.us/img520/9207/screen004uo5.jpg http://img157.imageshack.us/img157/5152/screen005sl2.jpg ----------------------------------------------------------- 4. The staircase wall on the both titans you can glitch into and see the inside of the titan from stairwells and surrounding areas. Occasionally you get warped back to the spawn point on the titan for doing this. http://home.nyc.rr.com/mtmmp/2142bugs/screen002.jpg http://img247.imageshack.us/img247/6543/screen002jb6.jpg http://img134.imageshack.us/img134/1013/screen003wf5.jpg http://img68.imageshack.us/img68/6376/screen009nd0.jpg http://img241.imageshack.us/img241/2240/screen008er1.jpg http://img291.imageshack.us/img291/7315/screen007ua0.jpg http://img242.imageshack.us/img242/9457/screen011mg5.jpg ----------------------------------------------------------- 5. Titan shield glitching - I is possible to glitch through the shield when the standing on the shield above a vehicle when it spawns, allowing you to fall through. http://img96.imageshack.us/img96/3418/screen007le7.jpg ----------------------------------------------------------- 6. Viewing holes in doors. where there should be a door lock or something it is not rendered and results in a viewing hole. There a several doors that have this and all of them should be checked. http://img242.imageshack.us/img242/4161/screen009za9.jpg http://img242.imageshack.us/img242/2223/screen010vk6.jpg ----------------------------------------------------------- 7. Corridor shield exploitation. It is possible to wedge yourself in between a shield and be near invulnerable. Using a medic kit makes this worse. if the correct position you may only be hit by the bottom elbow. http://img101.imageshack.us/img101/9047/screen008ra0.jpg ----------------------------------------------------------- 8. When killed you may switch kits and repspawn will full ammo and stats, allowing for players to restock on ammo and switch kits without respawning. http://img431.imageshack.us/img431/7519/screen011oo5.jpg http://img20.imageshack.us/img20/4854/screen012wg2.jpg ----------------------------------------------------------- Last Updated on October 4, 2006

Copyright © 2000-2001 Stronger Than All. All rights reserved. Any unauthorized copying, redistribution, or transfer of any information contained herein is prohibited.