Don't like ads? PRO users don't see any ads ;-)
Guest

Untitled

By: a guest on Apr 25th, 2012  |  syntax: None  |  size: 17.28 KB  |  hits: 15  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. [b]GENERAL T:A RULES/CONFIGURATIONS (ladder/league)[/b]
  2.  
  3. [b]Team Size and Punctuality[/b]
  4.  
  5.  
  6. Tribes Ascend 7-Man CTF is played with both teams having 7 players. If both teams agree to play with more, they are allowed to do so, as long as the server(s) offered by both teams can support the agreed upon number. If both teams agree to play with less than the minimum required number of players per team, then the TeamWarfare Staff sees this as an agreement between teams and therefore acceptable.
  7.  
  8. Both parties must have at least 5 eligible players on the server by 15 minutes after the scheduled start time. Failure to meet this requirement will result in an immediate forfeit against the non-compliant party, unless the violating team and their opponent make an informal ¡°Substitute Players¡± agreement (see section below). If no such agreement is reached, the offending team is still permitted to play 5v7 or 6v7. If both teams agree to postpone due to roster issues please either contact a TeamWarfare Admin immediately to inform them of the situation and the new scheduled time or, alternatively, post this information in Match Comms. Be sure to read the General Rules area pertaining to Reschedules and abide by its terms.
  9.  
  10. Please note, that not every match's situation and circumstances can be determined by a cut and dry reading of the rules. TWL Admins at their discretion have the ability to determine whether a forfeit is necessary. Many factors not listed above will be considered if there is a dispute between two teams.
  11.  
  12.  
  13. [b]T:A Server Configuration[/b]
  14.  
  15. For TWL Matches, edit your server configuration as follows:
  16.  
  17.             *Region*
  18.  
  19. North America - East
  20.  
  21.       (Note: If both teams agree in match communications, the server location may be changed.)
  22.  
  23. *Gametype and Maps*
  24.  
  25.         Gametype: CTF
  26.    Rotation Type: Single
  27.     Map Rotation: Maps for the match (in order)
  28.  
  29. *Gameplay Settings*
  30.  
  31.    -*Time Settings*
  32.  
  33.         Warmup Time: 300 seconds
  34.      Gametime Limit: 25 minutes
  35.      Overtime Limit: 60 minutes
  36.       Respawn Timer: 5 seconds
  37.  
  38.    -*Score Settings*
  39.  
  40.        Score To Win: 5 captures
  41.  
  42.    -*Player Settings*
  43.  
  44.        Allowed Classes: 1 Sentinel, 2 Raider. Rest = all
  45.            Spawn Naked: Disabled
  46.          Minimum Level: None
  47.          Maximum Level: None
  48.  
  49.     -*Team Settings*
  50.  
  51.            Max Players: 32
  52.         Team Join Type: Unbalanced
  53.    Autobalance in game: Disabled
  54.  Base Destruction req : Off
  55.      Pool Team Credits: On
  56.  
  57.     -*Base Settings*
  58.          
  59.        Base Objectives: Enabled
  60.          Base Upgrades: Disabled
  61.        Generator Regen: Disabled
  62.  Generator Destroyable: Enabled
  63.    Powered Deployables: Enabled
  64.  
  65.     -*Vehicle Settings*
  66.  
  67.      Health Multiplier: 1.0
  68.       Grav Cycle Limit: 2
  69.       Grav Cycle Price: 1200
  70.          Beowulf Limit: 1
  71.          Beowulf Price: 6000
  72.           Shrike Limit: 1
  73.           Shrike Price: 9000
  74.  
  75.      -*Call-in Settings*
  76.  
  77.       Powered Call-ins: Disabled
  78.       Tactical Strikes: Disabled
  79.        Orbital Strikes: Disabled
  80.            Supply Drop: Active, 2000 credits, 30s cd, 2s buildup, ammo only disabled.
  81.  
  82.    
  83.      -*Friendly Fire Settings*
  84.  
  85.             Friendly Fire: Enabled
  86.             FF Multiplier: 1.0
  87.         FF on Deployables: Enabled
  88.         FF on Base Assets: Enabled
  89.                Kill Limit: Off
  90.              Damage Limit: Off
  91.  
  92. [b]Map Selection[/b]
  93.  
  94. All CTF maps with the exception of Temple Ruins are considered part of TWL's ladder and league rotations (as of 4/25/2012).    
  95.  
  96. [b]Additional Rules/Bans[/b]
  97.  
  98. Currently, the following weapons are not allowed in TWL matches. As there is no server setting, it is mandatory that players observe these rules and not use banned weapons in match play. Failure to adhere to this may result in a match forfeit upon review by an admin.
  99.  
  100. Infiltrator:
  101.  
  102.    Jackal, Smoke Grenades
  103.  
  104. Raider:
  105.  
  106.    Plasma Gun, NJ5-B
  107.  
  108. [b]Server Selection Etiquette[/b]
  109.  
  110. Currently, all servers for T:A in the NA:E region run off the same hardware, therefore there is little reason for teams to squabble over which server to use. In the case of a dispute of which server to use, it would be the defending team's choice - but please, do your admins a favor and don't fight over something so meaningless. In the unlikely event that neither team has access to a T:A server, teams are urged to seek help either on the forums or from one of the admins - we can usually help you out.
  111.  
  112. [b]Match Starting Etiquette[/b]
  113.  
  114. A match is not considered official until both teams are on the server, and indicate they are ready to play to each other via readily known terms (ie: "we're ready, live, etc.) Teams must indicate that they are ready to each other with at least 30 seconds remaining on the warm-up time. This is to avoid confusion between teams as to whether or not their match has started. This is also the reason as to why at 300 second warmup time is indicated on the server settings (to give teams plenty of time to indicate their readiness, and to adjust between maps).
  115.  
  116.  
  117. [b]Overtime Considerations[/b]
  118.  
  119. While it is exceedingly unlikely that a match will last long enough to stalemate out a one hour overtime, a stalemate is not considered an acceptable outcome to a map on TWL. Should a match be stalemated, both teams will replay the map under Sudden Death rules. First team to get a cap on the replay wins, even if the map itself is not on a game-based overtime.
  120.  
  121. [b]Server Crashes[/b]
  122.  
  123. In the event of a server crash, if both teams can agree upon the remaining time and score, the map will be restarted with the remaining time and score intact. In the event of a dispute, an admin will look at evidence provided by both teams in order to determine the remaining time/score on a restart. If neither team can provide the admin with any evidence, the map will be replayed from the start. In the event that a team loses a player due to connectivity issues,the team may substitute the player immediately with someone from their roster. Substitute players, brought in during match, that are not eligible players, will force an immediate forfeiture on the part of the team they were playing for.
  124.  
  125.  
  126. [b]Substitute Players[/b]
  127.  
  128. TeamWarfare acknowledges that some teams may still wish to play a match even if their opponent does not have 7 eligible players available. In such a case, an informal agreement may be reached regarding the use of substitutes, whereupon the violating party should offer a list of available candidates who might fill the role. These candidates must be registered TeamWarfare players who are not currently banned or suspended from competition, and must meet with the approval of the opposing team. The non-offending team is allowed to bar the use of any player as a sub for [b]any[/b] reason, as long as they do so prior to the beginning of a map. Please note that if such an agreement is reached and the non-offending team then loses, they are still required to report the results of the match.
  129.  
  130.  
  131. [b]Legal Player Names[/b]
  132.  
  133. All members registered to play on Tribes Ascend ladders/leagues must be registered under a recognizable name in Tribes Ascend proper. Slight variations in the name (such as dashes or stars) are permitted, as some names may have been taken by players not participating on the ladders.
  134.  
  135. [b]TWL Match Observers[/b]
  136.  
  137. TWL admins reserve the right to spectate any TWL sanctioned match. Failure to cooperate with an admin (providing server info, password, etc) on request may result in penalties to the offending team per the admin's discretion.
  138.  
  139.  
  140. [b]Sportsmanship[/b]
  141.  
  142. Teams are expected to be straight forward in regards to match communications and setting up the logistics of any TWL match. While TWL will generally not take action against garden variety "trash talk" that might occur in a heated match, TWL reserves the right to penalize a team in the following circumstances:
  143.  
  144. Extremely excessive spam that blocks communications/audio
  145.  
  146. Racist/sexist remarks clearly borne out of malice
  147.  
  148. Malicious/Severe disrespect that goes well beyond the norm (even for the Tribes community) in the discretion of a presiding admin.
  149.  
  150.  
  151. [b]Cheating (Team Reporting Section)[/b]
  152.  
  153. In the event that a team believes their opponent has cheated, the match should be completed and the TeamWarfare Staff should be notified immediately afterwards (in accordance with the Match Results and Disputes clause) so that a judgment can be made. Failing to submit a dispute or contact a member of TeamWarfare Staff within an hour of the match¡¯s completion will be regarded as waiving any right to protest. If the protesting team is the losing team, they should not report the loss until a ruling is made. By reporting a loss, the losing team likewise waives all rights to protest. When it is known that a team is going to protest, both teams should submit evidence to support their side of the story to the TeamWarfare Admin handling the issue. Submitting VODs and other information will help the staff involved in ruling on the matter. Not providing all pertinent information could limit the scope of the evaluation and hurt rather than help a team, so both should participate as best they are able.
  154.  
  155. All bugs and tactics are not considered cheats. The TeamWarfare Staff acknowledges some of the unintended effects of bugs are an acceptable part of the game, and we will take this into consideration when determining if a bug is so extreme that it warrants disciplinary action against the offending team. If it is shown that the bug is of such a degree as to constitute a cheat, the TeamWarfare rules will be updated and disciplinary actions could be taken against the team in question.
  156.  
  157.  
  158. [b]Cheating (Player Accountability Section)[/b]
  159.  
  160.  
  161. TWL has a ZERO tolerance policy regarding game hacking. This rule covers players who use code to manipulate a particular game for the purpose of gaining an unfair advantage over other teams and players. wallhacks, speedhacks and aimbots are just examples of the types of cheats covered by this rule.
  162.  
  163. "Testing" or "trying out" hack programs will not be accepted excuses.
  164.  
  165. Ladders:
  166.  
  167.  
  168. 1. Hacker caught in TWL Match:
  169.  
  170. - Forfeiture of the existing game
  171. - Player Permanently banned from TWL.
  172.  
  173.  
  174. 2. Hacker Caught in Match outside of the ladder (League match) or in a match outside of TWL:
  175.  
  176. - Player Permanently banned from TWL.
  177.  
  178.  
  179.  
  180. 3. Hacker caught in a Pub/Scrim :
  181.  
  182. - Player banned from TWL for 1 yr.
  183. - 2nd Offense Perma Banned.  A pub ban on two separate games equals two offenses.
  184.  
  185.  
  186. Based on the circumstances of the ban, additional penalties may be levied on the team that harbored the cheater. This will be discretionary and handled on a case by case basis.
  187.  
  188.  
  189. Circumventing your ban, either by creating new accounts, or smurfing as another player will result in the player(s) being [b]permanently banned from TWL.[/b]
  190.  
  191.  
  192. ***NOTE- Each individual game has the option of preventing a person from participating in their specific game that has been caught cheating on the pubs, regardless of how long ago the violation has occurred. This will affect that game only. The player will not be site banned/suspended or prevented from playing another game that allows them to, if the violation is over one year old.
  193.  
  194.  
  195. Admin Notes:
  196. - TWL will continue to support teams who Police themselves of hackers and cheaters. In the case where a team Purges a hacker from their ranks and brings it to the attention of TWL staff. TWL will (waive the Drop in ladder rungs)
  197.  
  198.  
  199. [b]Smurf Policy[/b]
  200.  
  201. Smurfing is signing up for more than one team (or the same team) on the same ladder, 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.
  202.  
  203. Playing for a team you are not registered to play for is prohibited. Playing on more than one team per ladder is also prohibited, as is registering multiple accounts for use on the same team or ladder.
  204.  
  205. Minimum punishment for the violation of this paragraph is as follows but not limited to : (It will ultimately remain sole discretion of Teamwarfare Staff)
  206.  
  207.  
  208.     The team that the smurf joined or played for most recently will be deleted.
  209.  
  210.     The smurf's original team will be dropped 33% of the ladder.
  211.  
  212.     The smurf's account(s) on, and possibly access rights to, TWL will be revoked.
  213.  
  214.  
  215. ---
  216.  
  217. [b]Ladder Specific Rules[/b]
  218.  
  219. [b]Ladder Movement[/b]
  220.  
  221. You can challenge anyone above you 10 slots or 50% of the remaining ladder from your current rank - whichever is higher. (Ex: Rung 100 can challenge rung 50. Rung 48 can challenge to rung 24. Rung 15 can challenge to rung 5).
  222.  
  223. On some of the smaller ladders, the challenge slots is 5 slots or 50% of the remaining ladder. Check the ladder's specific rules to be sure.
  224.  
  225.  
  226. [b]Ladder Concept[/b]
  227.  
  228. The Ladder is based on a ¡°best 2 out of 3¡± maps scenario. Map selection is random for the first and second maps. The "Defending" team selects the third (tiebreaker) map. The "Defending" team chooses map sides and order for the first two maps (order should be stated in Match Comms within 24 hours of finalization of match). By choosing the order, the "Defending" team also chooses what map is to be played on the defender's server of choice. The "Attacking" team picks the tiebreaker map¡¯s sides. Once a match has been played, you may not attack the same team for 7 days after its conclusion.
  229.  
  230. [b]Team Roster Management[/b]
  231.  
  232. Ladder members join teams per ladder and may only be a member of one team per ladder. Roster changes may be made on any day. In order for a player to be considered 'eligible' for a match, he must be on his team's roster before the Defender accepts the challenge and remain on the team until the match is completed. If a player drops from a team after a challenge is accepted and rejoins he will only be allowed to legally play if the other team agrees to it in match comms. Leniency is given for people that sign up on the same day match is accepted.
  233.  
  234.  
  235. [b]Team Management[/b]
  236.  
  237. Teams have one (1) Owner and any number of Captains. Captains are assigned at a ladder level. Owners are captains on all ladders. The team Owner should determine who should be in charge of issuing challenges per ladder and maintaining the team information. Multiple team captains can be assigned to perform such duties.
  238.  
  239. *There are only to be a maximum of 2 captains assigned to any ladder match.
  240.  
  241. You can only issue a challenge by making it in your Team's Admin Console on your ladder control panel on any day of the week. Access to the Team Admin Console is available to all Captains¡­¡­¡­¡­ NOTE - You must login to the ladder in order to administer your team.
  242.  
  243.  
  244. [b]Challenge and Match Date Acceptance[/b]
  245.  
  246. All ladders have a time limitation for match responses. This includes Acceptance of a Challenge and/or Date Acceptance. The Present time frame is 48 hours. At that time a "Flag" is created for the Ladder Admins to address the next time they login to their Admin Console. If the problem is resolved by that team prior to the Admin logging in then the match continues as before. If the Admin logs in first the appropriate action will be taken. In this case forfeits will be granted and rungs dropped.
  247.  
  248. It is the each team's responsibility before the match starts to see that all players are legally registered on each teams roster. After match start or completion, roster disputes are not valid justification for forfeiture or admin intervention. Substitute players, brought in during match, that are not eligible players by the above criteria, will force an immediate forfeiture on the part of the team they were playing for.
  249.  
  250.  
  251. [b]Match Results Reporting and Disputes[/b]
  252.  
  253. Once a match has started, it is understood that both teams agree to the terms of the match (number of players, time limit, rosters, etc). If there is a disagreement of match terms AFTER match completion, the disagreement will be thrown out.
  254.  
  255. Match results are to be reported as a loss in your team admin panel or if you are disputing the loss you must login to your team admin panel and select the "Dispute Match Results" link within 1 hour of match end. If disputed it will send an automatic email to your ladder admin. If a team fails to report or dispute the team needs to notify the ladder admin immediately. Failure to do either within 1 hour of match end will result in :
  256.  
  257.    1. First Offense : Dropped a percentage of total rungs on ladder.
  258.    2. Second Offense : Removed from ladder.
  259.  
  260. By reporting the results, teams waive their rights to protest (ultimately decided by TeamWarfare Staff). It is also to be known that once a match has been played / reported neither team can attack each other for 7 days.
  261.  
  262. If match results are being protested, a ladder admin and the opposing team captains must be made aware of the protest within one hour from the completion of the match via the "Dispute Results" link in your admin panel AS WELL AS through match comms. Failure to do BOTH may result in an admin reporting the match.
  263.  
  264. After a protest has been initiated, both teams have 24 hours to gather evidence. In this time the team being protested against may issue a counter-protest.
  265.  
  266. ALL match issues should be resolved within 48 hours from match completion.
  267.  
  268. [b]Challenge Cancellation[/b]
  269.  
  270. On the TWL there is no availability for the team Captains or Founders to cancel a challenge. All Cancellations must be coordinated through a Ladder Admin. Cancellations are not always guaranteed.