Battlefield 2142 NA Ladders
|
Navigation Supported Gametypes and Rulesets -Gametype Specifications and Concept:
Battlefield 2142 5v5 Infantry Ladder -Format: Current Patch: 1.5 Type of Gameplay: Conquest Number of Maps: 1 Number of Teams: 2 Members per Team: 5 (4 Minimum) Time Limit: 15 minutes Friendly Fire: Yes Rounds: 3 (Best 2 out of 3) Map Selection: Random Mods: None Unlocks: Yes Side Selection: Visitor Server Selection: Home Server Hosting: Both teams are required to list their server information if available. Demo Recording: On -Commander Mode:
-Vehicles/Stationary Guns:
-Map List:
-Server Settings: rem *** TWL BF2142 5v5 Ladder Match Config rem *** Last Updated December 1st, 2006 rem *** TeamWarfare rem *** http://www.teamwarfare.com rem *** Questions or Issues: rem *** Email BF2142NALadders@teamwarfare.com rem *** IRC: irc://irc.gamesurge.net/twl_bf rem *** Server Settings - Modify as Needed sv.serverName "(Clan Tag) vs. (Clan Tag) - TWL 5v5 Inf Ladder Match" sv.password "Your Password Here" sv.serverIP "Your Server IP Here" sv.serverPort 16567 sv.welcomeMessage "TWL 5v5 Infantry Match in Progress" sv.sponsorText "" sv.sponsorLogoURL "" sv.communityLogoURL "" rem *** NAT Settings - Modify as Needed sv.allowNATNegotiation 0 sv.interfaceIP "" rem *** TWL Match Settings - DO NOT MODIFY sv.bandwidthChoke 0 sv.internet 1 sv.punkBuster 1 sv.allowFreeCam 0 sv.allowExternalViews 1 sv.allowNoseCam 1 sv.hitIndicator 1 sv.maxPlayers 12 sv.numPlayersNeededToStart 2 sv.notEnoughPlayersRestartDelay 15 sv.startDelay 15 sv.endDelay 15 sv.spawnTime 10 sv.manDownTime 10 sv.endOfRoundDelay 15 sv.ticketRatio 100 sv.roundsPerMap 3 sv.timeLimit 1500 sv.scoreLimit 0 sv.soldierFriendlyFire 100 sv.vehicleFriendlyFire 100 sv.soldierSplashFriendlyFire 100 sv.vehicleSplashFriendlyFire 100 sv.tkPunishEnabled 0 sv.tkNumPunishToKick 0 sv.tkPunishByDefault 0 sv.votingEnabled 0 sv.voteTime 0 sv.minPlayersForVoting 2 sv.gameSpyPort 29900 sv.adminScript "default" sv.timeBeforeRestartMap 30 sv.autoBalanceTeam 0 sv.teamRatioPercent 100 sv.radioSpamInterval 6 sv.radioMaxSpamFlagCount 9999 sv.radioBlockedDurationTime 30 sv.friendlyFireWithMines 1 sv.maxRank 0 rem *** Global unlocks (Enabled) sv.useGlobalRank 1 sv.useGlobalUnlocks 1 rem *** Demo Recordings (Enabled) sv.autoRecord 1 sv.demoIndexURL http:// sv.demoDownloadURL http:// sv.autoDemoHook "adminutils/demo/rotate_demo.exe" sv.demoQuality 1 rem *** Voice over IP Settings (disabled) sv.voipEnabled 0 sv.voipQuality 3 sv.voipServerRemote 0 sv.voipServerRemoteIP "" sv.voipServerPort 55125 sv.voipBFClientPort 55123 sv.voipBFServerPort 55124 sv.voipSharedPassword "" Download Config -Overview: This is an 5v5 Conquest mode "Infantry Only" ladder. The match is played best of three rounds where the winner of each round is determined by which team has tickets remaining. All Ladder rules will supercede normal TWL rules, both general and game specific. -Map Rotation: Only one map will be played per match chosen randomly by your admin panel. The Home team gets server selection and the Visiting team gets side selection. To ensure fairness, each team will play one round on each side of the map. If each team has won a round a third round will be played, the team with the highest total ticket amount from the previous rounds gets side choice for the OT round. -Infantry only specific rules: Commander mode can be utilized legally with the exception of Orbital Strike. It is illegal to use Orbital Strike at any time during 'live' matchplay. Dropping Orbital Strike is a forfeit-able offense for that round only. Forfeits are given at the other teams discretion, the forfeit must be called immediately, if you finish the round you lose the right to make the violating team forfeit the round. Teams are urged to play through an accidental Strike in the interest of fair play provided the Strike did not impact the match, please play fair and remember mistakes can happen to any team. SAT-TRACK, UAV, EMP Strike & Supplies are all legal. In the event of a forfeit round, the forfeit round will not count towards the violating teams total ticket count for any tie-breaker rounds. Meaning, if Team A wins with 75 tickets left in round one, and Team B drops Orbital Strike in the second round, Team B would have 0 total tickets and would lose side choice for the third round. -Team Size/Match Roster & GUID's: Each team is to fill a maximum of 5 positions. Teams are required to be "Match Ready" within 15 minutes of posted start time regardless of how many players they have in the server. The match will be started with the available players. Time extensions are at the discretion of the other team. If players become available during the match, they are allowed to join the match in progress provided they are on the teams roster with a valid GUID. You can add players until you have 5 regardless of the number of players the opposing team has. If a player joins a server at any time during live match play that is either not on the roster or does not have a valid GUID the team they are playing for will forfeit the entire match and are subject to disqualification from the ladder. Your PID (Player Identification Number) is NOT your GUID and should NOT be entered in it's place. PID is for stats tracking only and has nothing to do with your Punkbuster GUID Instructions on obtaining your GUID are listed below in the Punkbuster and GUID's section of the rules.
Battlefield 2142 8v8 Infantry Ladder -Format: Current Patch: 1.5 Type of Gameplay: Conquest Number of Maps: 1 Number of Teams: 2 Members per Team: 8 (6 Minimum) Time Limit: 25 minutes Friendly Fire: Yes Rounds: 3 (Best 2 out of 3) Map Selection: Random Mods: None Unlocks: Yes Side Selection: Visitor Server Selection: Home Server Hosting: Both teams are required to list their server information if available. Demo Recording: On -Commander Mode:
-Vehicles/Stationary Guns:
-Map List:
-Server Settings: rem *** TWL BF2142 8v8 Ladder Match Config rem *** Last Updated May 5th, 2007 rem *** TeamWarfare rem *** http://www.teamwarfare.com rem *** Questions or Issues: rem *** Email BF2142NALadders@teamwarfare.com rem *** IRC: irc://irc.gamesurge.net/twl_bf rem *** Server Settings - Modify as Needed sv.serverName "(Clan Tag) vs. (Clan Tag) - TWL 8v8 Inf Ladder Match" sv.password "Your Password Here" sv.serverIP "Your Server IP Here" sv.serverPort 16567 sv.welcomeMessage "TWL 8v8 Infantry Match in Progress" sv.sponsorText "" sv.sponsorLogoURL "" sv.communityLogoURL "" rem *** NAT Settings - Modify as Needed sv.allowNATNegotiation 0 sv.interfaceIP "" rem *** TWL Match Settings - DO NOT MODIFY sv.bandwidthChoke 0 sv.internet 1 sv.punkBuster 1 sv.allowFreeCam 0 sv.allowExternalViews 1 sv.allowNoseCam 1 sv.hitIndicator 1 sv.maxPlayers 18 sv.numPlayersNeededToStart 2 sv.notEnoughPlayersRestartDelay 15 sv.startDelay 15 sv.endDelay 15 sv.spawnTime 10 sv.manDownTime 10 sv.endOfRoundDelay 15 sv.ticketRatio 100 sv.roundsPerMap 3 sv.timeLimit 1500 sv.scoreLimit 0 sv.soldierFriendlyFire 100 sv.vehicleFriendlyFire 100 sv.soldierSplashFriendlyFire 100 sv.vehicleSplashFriendlyFire 100 sv.tkPunishEnabled 0 sv.tkNumPunishToKick 0 sv.tkPunishByDefault 0 sv.votingEnabled 0 sv.voteTime 0 sv.minPlayersForVoting 2 sv.gameSpyPort 29900 sv.adminScript "default" sv.timeBeforeRestartMap 30 sv.autoBalanceTeam 0 sv.teamRatioPercent 100 sv.radioSpamInterval 6 sv.radioMaxSpamFlagCount 9999 sv.radioBlockedDurationTime 30 sv.friendlyFireWithMines 1 sv.maxRank 0 rem *** Global unlocks (Enabled) sv.useGlobalRank 1 sv.useGlobalUnlocks 1 rem *** Demo Recordings (Enabled) sv.autoRecord 1 sv.demoIndexURL http:// sv.demoDownloadURL http:// sv.autoDemoHook "adminutils/demo/rotate_demo.exe" sv.demoQuality 1 rem *** Voice over IP Settings (disabled) sv.voipEnabled 0 sv.voipQuality 3 sv.voipServerRemote 0 sv.voipServerRemoteIP "" sv.voipServerPort 55125 sv.voipBFClientPort 55123 sv.voipBFServerPort 55124 sv.voipSharedPassword "" Download Config -Overview: This is an 8v8 Conquest mode "Infantry Only" ladder. The match is played best of three rounds where the winner of each round is determined by which team has tickets remaining. All Ladder rules will supercede normal TWL rules, both general and game specific. -Map Rotation: Only one map will be played per match chosen randomly by your admin panel. The Home team gets server selection and the Visiting team gets side selection. To ensure fairness, each team will play one round on each side of the map. If each team has won a round a third round will be played, the team with the highest total ticket amount from the previous rounds gets side choice for the OT round. -Infantry only specific rules: Commander mode can be utilized legally with the exception of Orbital Strike. It is illegal to use Orbital Strike at any time during 'live' matchplay. Dropping Orbital Strike is a forfeit-able offense for that round only. Forfeits are given at the other teams discretion, the forfeit must be called immediately, if you finish the round you lose the right to make the violating team forfeit the round. Teams are urged to play through an accidental Strike in the interest of fair play provided the Strike did not impact the match, please play fair and remember mistakes can happen to any team. SAT-TRACK, UAV, EMP Strike & Supplies are all legal. In the event of a forfeit round, the forfeit round will not count towards the violating teams total ticket count for any tie-breaker rounds. Meaning, if Team A wins with 75 tickets left in round one, and Team B drops Orbital Strike in the second round, Team B would have 0 total tickets and would lose side choice for the third round. -Team Size/Match Roster & GUID's: Each team is to fill a maximum of 8 positions during a match with a maximum of 24 players on the entire team. Teams are required to be "Match Ready" within 15 minutes of posted start time regardless of how many players they have in the server. The match will be started with the available players. Time extensions are at the discretion of the other team. If players become available during the match, they are allowed to join the match in progress provided they are on the teams roster with a valid GUID. You can add players until you have 8 regardless of the number of players the opposing team has. If a player joins a server at any time during live match play that is either not on the roster or does not have a valid GUID the team they are playing for will forfeit the entire match and are subject to disqualification from the ladder. Your PID (Player Identification Number) is NOT your GUID and should NOT be entered in it's place. PID is for stats tracking only and has nothing to do with your Punkbuster GUID Instructions on obtaining your GUID are listed below in the Punkbuster and GUID's section of the rules.
Battlefield 2142 8v8 Conquest Ladder -Format: Current Patch: 1.5 Type of Gameplay: Conquest Unlocks: Yes Vehicles: Yes Number of Maps: 1 Number of Teams: 2 Members per Team: 8 (6 Minimum) Time Limit: 25 Minutes Friendly Fire: Yes Friendly Fire Mines: Yes Rounds: 3 (Best 2 out of 3) Map Selection: Random Mods: None Battlerecorder: Yes Server Selection: Home Side Selection: Visitor Server Hosting: Both teams are required to list their server information if available. -Commander Mode: All Commander mode assets are legal -Map List:
-Server Settings rem *** TWL BF2142 8v8 Conquest Ladder Config rem *** Last Updated October 29th, 2006 rem *** TeamWarfare rem *** http://www.teamwarfare.com rem *** Questions or Issues: rem *** Email BF2142naladders@teamwarfare.com rem *** IRC: irc://irc.gamesurge.net/twl_bf rem *** Server Settings - Modify as Needed sv.serverName "(Tag) V. (Tag) - TWL BF2142 8v8 Conquest Match" sv.password "Your Password Here" sv.serverIP "Your Server IP Here" sv.serverPort 16567 sv.welcomeMessage "TWL BF2142 8v8 Conquest Match in progress" sv.sponsorText "" sv.sponsorLogoURL "" sv.communityLogoURL "" rem *** NAT Settings - Modify as Needed sv.allowNATNegotiation 0 sv.interfaceIP "" rem *** TWL Match Settings - DO NOT MODIFY sv.bandwidthChoke 0 sv.internet 1 sv.punkBuster 1 sv.allowFreeCam 0 sv.allowExternalViews 1 sv.allowNoseCam 1 sv.hitIndicator 1 sv.maxPlayers 18 sv.numPlayersNeededToStart 2 sv.notEnoughPlayersRestartDelay 15 sv.startDelay 15 sv.endDelay 15 sv.spawnTime 15 sv.manDownTime 15 sv.endOfRoundDelay 15 sv.ticketRatio 100 sv.roundsPerMap 3 sv.timeLimit 1500 sv.scoreLimit 0 sv.soldierFriendlyFire 100 sv.vehicleFriendlyFire 100 sv.soldierSplashFriendlyFire 100 sv.vehicleSplashFriendlyFire 100 sv.tkPunishEnabled 0 sv.tkNumPunishToKick 0 sv.tkPunishByDefault 0 sv.votingEnabled 0 sv.voteTime 0 sv.minPlayersForVoting 2 sv.gameSpyPort 29900 sv.adminScript "default" sv.timeBeforeRestartMap 30 sv.autoBalanceTeam 0 sv.teamRatioPercent 100 sv.radioSpamInterval 6 sv.radioMaxSpamFlagCount 9999 sv.radioBlockedDurationTime 30 sv.friendlyFireWithMines 1 sv.maxRank 0 rem *** Global unlocks (Enabled) sv.useGlobalRank 1 sv.useGlobalUnlocks 1 rem *** Demo Recordings (Enabled) sv.autoRecord 1 sv.demoIndexURL http:// sv.demoDownloadURL http:// sv.autoDemoHook "adminutils/demo/rotate_demo.exe" sv.demoQuality 1 rem *** Voice over IP Settings (disabled) sv.voipEnabled 0 sv.voipQuality 3 sv.voipServerRemote 0 sv.voipServerRemoteIP "" sv.voipServerPort 55125 sv.voipBFClientPort 55123 sv.voipBFServerPort 55124 sv.voipSharedPassword "" Download Config -Overview: This is an 8v8 Conquest mode ladder. The match is played best of three rounds where the winner of each round is determined by which team has tickets remaining. All Ladder rules will supercede normal TWL rules, both general and game specific. -Map Rotation: Only one map will be played per match chosen randomly by your admin panel. The Home team gets server selection and the Visiting team gets side selection. To ensure fairness, each team will play one round on each side of the map. If each team has won a round a third round will be played, the team with the highest total ticket amount from the previous rounds gets side choice for the OT round. -Team Size/Match Roster & GUID's: Each team is to fill a maximum of 8 positions during a match with a maximum of 24 players on the entire team. Teams are required to be "Match Ready" within 15 minutes of posted start time regardless of how many players they have in the server. The match will be started with the available players. Time extensions are at the discretion of the other team. If players become available during the match, they are allowed to join the match in progress provided they are on the teams roster with a valid GUID. You can add players until you have 8 regardless of the number of players the opposing team has. If a player joins a server at any time during live match play that is either not on the roster or does not have a valid GUID the team they are playing for will forfeit the entire match and are subject to disqualification from the ladder. Your PID (Player Identification Number) is NOT your GUID and should NOT be entered in it's place. PID is for stats tracking only and has nothing to do with your Punkbuster GUID Instructions on obtaining your GUID are listed below in the Punkbuster and GUID's section of the rules.
Battlefield 2142 2v2 Gunship Ladder -Format: Current Patch: 1.5 Type of Gameplay: Titan Number of Maps: 1 Number of Teams: 2 Members per Team: 2 (2 minimum, 5 maximum) Time Limit: None Rounds: First team to win 7 rounds (Maximum 13 rounds, not including OT) Map Selection: Random Selected Mods: None Unlocks: No Vehicles: Gunships only Side Selection: Attacker Server Selection: Defender Server Hosting: Both teams are required to list their server information if available. Demo Recording: On -Commander Mode:
Rounds: First team to win 7 rounds (Maximum 13 rounds, not including OT) -Map List:
-Server Settings: rem *** TWL BF2142142 2v2 Gunship Ladder Match Config rem *** Last Updated 6/6/07 rem *** TeamWarfare rem *** http://www.teamwarfare.com rem *** Questions or Issues: rem *** Email BF2142NALadders@teamwarfare.com rem *** IRC: irc://irc.gamesurge.net/twl_bf rem *** Server Settings - Modify as Needed sv.serverName "(Clan Tag) vs. (Clan Tag) - TWL 5v5 Inf Ladder Match" sv.password "Your Password Here" sv.serverIP "Your Server IP Here" sv.serverPort 16567 sv.welcomeMessage "TWL 2v2 Gunship Match in Progress" sv.sponsorText "" sv.sponsorLogoURL "" sv.communityLogoURL "" rem *** NAT Settings - Modify as Needed sv.allowNATNegotiation 0 sv.interfaceIP "" rem *** TWL Match Settings - DO NOT MODIFY sv.bandwidthChoke 0 sv.internet 1 sv.punkBuster 1 sv.allowFreeCam 0 sv.allowExternalViews 1 sv.allowNoseCam 1 sv.hitIndicator 1 sv.maxPlayers 5 sv.numPlayersNeededToStart 2 sv.notEnoughPlayersRestartDelay 15 sv.startDelay 15 sv.endDelay 15 sv.spawnTime 5 sv.manDownTime 5 sv.endOfRoundDelay 15 sv.ticketRatio 1000 sv.roundsPerMap 3 sv.timeLimit 0 sv.scoreLimit 0 sv.soldierFriendlyFire 100 sv.vehicleFriendlyFire 100 sv.soldierSplashFriendlyFire 100 sv.vehicleSplashFriendlyFire 100 sv.tkPunishEnabled 0 sv.tkNumPunishToKick 0 sv.tkPunishByDefault 0 sv.votingEnabled 0 sv.voteTime 0 sv.minPlayersForVoting 2 sv.gameSpyPort 29900 sv.adminScript "default" sv.timeBeforeRestartMap 30 sv.autoBalanceTeam 0 sv.teamRatioPercent 100 sv.radioSpamInterval 6 sv.radioMaxSpamFlagCount 9999 sv.radioBlockedDurationTime 30 sv.friendlyFireWithMines 1 sv.maxRank 0 rem *** Global unlocks (Enabled) sv.useGlobalRank 0 sv.useGlobalUnlocks 0 rem *** Demo Recordings (Enabled) sv.autoRecord 1 sv.demoIndexURL http:// sv.demoDownloadURL http:// sv.autoDemoHook "adminutils/demo/rotate_demo.exe" sv.demoQuality 1 rem *** Voice over IP Settings (disabled) sv.voipEnabled 0 sv.voipQuality 3 sv.voipServerRemote 0 sv.voipServerRemoteIP "" sv.voipServerPort 55125 sv.voipBFClientPort 55123 sv.voipBFServerPort 55124 sv.voipSharedPassword "" -Ladder Outline: This is a 2 vs. 2 Gunship ladder. Each team will consist of one pilot and one gunner. Only one Gunship is to be in the air per team at any given time during live match play. -How You Win: A match will be the first team to score 7 "kills", valid kills are defined below. -Map Rotation: Only one map will be played per match. -Team Size: This is a 2 vs. 2 ladder, each team must have 2 eligible players to begin the match. If a squad is unable to meet this requirement, the offending squad must forfeit the match unless the other team is willing to reschedule to a later date. If neither team is able to fill 2 positions at the start of the match, the match will be nullified unless both squads choose to play the match with less than the number of required players or they choose to reschedule. "Sologuiding" is allowed only with expressed permission from the opposing team in match comms at least 24 hours prior to match start time. If you do not get permission before match start time and show up expecting to "sologuide" you are subject to a forfeit at the opposing teams discretion. -Side Selection and Side Switching: The defending team gets server selection and the attacking team gets side selection for the first 3 rounds. The attacking team must announce their side choice at least 24 hours prior to match time in match comms. Failure to announce side choice will result in loss of side choice. The same rule applies to server choice, if the Defender fails to announce what server they choose to play the match on, side choice will be given to the attacker. You will play 3 rounds on your given sides, then both teams will switch sides every 3 rounds to finish the match. In the event of a tie, 6-6, the teams will finish out the remaining round on the side they are currently on. -Start Procedure: Both teams will enter their respective Gunship, however both teams must remain at their Titan (Can be verified using command HUD). When both teams have entered their Gunship and are ready to take off they must globally announce "Ready", Home team will than globally announce the match score and give the "Go" command, after the "Go" command is given both teams may take off. Example: Visiting Team: We are ready Home Team: Ready, Match score is 4-1 Team X Home Team: "Go" -Round Procedure: At any time you may return to your Titan to repair/reload, however you may not "idle" under the protection of your shield, excessive "idling" at your Titan may constitute a round forfeit. Once BF2142 registers a winner, the round is over, after a team destroys the other teams Gunship they must return to their Titan as fast as possible to expedite the start of the next round. Any events that happen after or during BF2142 announcing a kill are considered non-events, This includes a ram/collision event. In the event of a ram, whoever BF2142 deems as "getting the kill" is considered the Round winner, regardless of all other events. -Bailing Out or Killed Inside the Gunship: If for some reason, accidental or otherwise, a team member should bail out of the Gunship, there is no penalty provided they don't do anything to alter the match, for instance fire on the enemy Gunship. You may respawn back into the Gunship if its available. If you are "shot" out of the Gunship, you may respawn back into the Gunship if its still available. -What Constitutes a Kill: Missile kills, both TV and pilot, mounted gun kills, and rams will be counted. Round winner will be decided by who BF2142 registers as the winner. A "kill" is considered the death of the Gunship by any means under any legal circumstances, including pilot error, ie; flying into a mountain, the ground, etc… A ram is not the same as a "Double K.O.", if both Gunships kill each other at the same time, (TV guided kill, missile kill, gun kill, etc...), this will count as a point for each team, if the match is tied and this happens in the last round, an additional round will be played. -Match Scoring: Only a Gunship "kill" wins you the round. Home team must globally type in the current match score i.e. 2-1 Team X 4-0 Team X ect ect, Team X being whoever is ahead in kills. If both teams are tied, simply announce kills and say All/both/each teams/Tied ect. A screenshot must be taken of each round score being by both teams and held for 1 week. Please be aware, live player chat cannot be seen by dead players, so wait to give score until the other team says ready. -Commander Mode and Command HUD: Command HUD usage is legal. If EMP or Orbital Strike goes off and no one is hurt there is no penalty. Any deliberate EMP Strike or Orbital Strike, for instance on the enemy’s Titan, is a round forfeit, more than once during one match is an immediate match disqualification. Any “accidental” EMP or Orbital Strikes in live match play that result in the damage or destruction of the enemy Gunship will constitute a forfeit of the current round by the offending team. If this happens more than once by the offending team in a match, the offending team is subject to a match disqualification. UAV, Supply Drops, Orbital Strike, and EMP Strike are illegal for live match play. The Titan should not be moved unless agreed upon by both teams to expedite the match. If you are found excessively moving the titan out of it's starting position you may be subject to a forfeit of the round in question. -Outside Weapon Use and Map Flags: Firing on the enemy’s Gunship with any weapon not attached to the Gunship will constitute a match disqualification. ***This rule in non-debatable and overrides all other rules on this ladder*** If it's not attached to the Gunship you risk disqualification of the entire match, we are instituting a "No Tolerance Policy" on this rule, please use common sense. The offending team will forfeit the entire match, and be moved to the bottom of the ladder. This includes any hand held weaponry, ground based weaponry, land vehicle based weaponry, jet based weaponry and Commander assets. The deliberate taking of any Silo will constitute a forfeit of the current round by the offending team. If this happens more than once by the offending team in a match, the offending team is subject to a match disqualification. Repeat offenders of either the weapon use or Silo capture rules will be removed from the ladder completely. -Titan Ladders - *CLICK TO EXPAND*
Battlefield 2142 12v12 Titan Ladder -Format: Current Patch: 1.5 Type of Gameplay: Titan Unlocks: Yes Vehicles: Yes Number of Maps: 1 Number of Teams: 2 Members per Team: 12 (10 Minimum) Time Limit: None Friendly Fire: Yes Friendly Fire Mines: Yes Rounds: One - Winner takes all Map Selection: Random Mods: None Battlerecorder: Yes Server Selection: Home Side Selection: Visitor Server Hosting: Both teams are required to list their server information if available. -Commander Mode: All Commander mode assets are legal -Map List:
-Server Settings rem *** TWL BF2142 12v12 Titan Ladder Config rem *** Last Updated November 3rd, 2006 rem *** TeamWarfare rem *** http://www.teamwarfare.com rem *** Questions or Issues: rem *** Email BF2142naladders@teamwarfare.com rem *** IRC: irc://irc.gamesurge.net/twl_bf rem *** Server Settings - Modify as Needed sv.serverName "(Tag) V. (Tag) - TWL BF2142 12v12 Titan Match" sv.password "Your Password Here" sv.serverIP "Your Server IP Here" sv.serverPort 16567 sv.welcomeMessage "TWL BF2142 12v12 Titan Match in progress" sv.sponsorText "" sv.sponsorLogoURL "" sv.communityLogoURL "" rem *** NAT Settings - Modify as Needed sv.allowNATNegotiation 0 sv.interfaceIP "" rem *** TWL Match Settings - DO NOT MODIFY sv.bandwidthChoke 0 sv.internet 1 sv.punkBuster 1 sv.allowFreeCam 0 sv.allowExternalViews 1 sv.allowNoseCam 1 sv.hitIndicator 1 sv.maxPlayers 26 sv.numPlayersNeededToStart 2 sv.notEnoughPlayersRestartDelay 15 sv.startDelay 15 sv.endDelay 15 sv.spawnTime 15 sv.manDownTime 15 sv.endOfRoundDelay 15 sv.ticketRatio 100 sv.roundsPerMap 1 sv.timeLimit 0 sv.scoreLimit 0 sv.soldierFriendlyFire 100 sv.vehicleFriendlyFire 100 sv.soldierSplashFriendlyFire 100 sv.vehicleSplashFriendlyFire 100 sv.tkPunishEnabled 0 sv.tkNumPunishToKick 0 sv.tkPunishByDefault 0 sv.votingEnabled 0 sv.voteTime 0 sv.minPlayersForVoting 2 sv.gameSpyPort 29900 sv.adminScript "default" sv.timeBeforeRestartMap 30 sv.autoBalanceTeam 0 sv.teamRatioPercent 100 sv.radioSpamInterval 6 sv.radioMaxSpamFlagCount 9999 sv.radioBlockedDurationTime 30 sv.friendlyFireWithMines 1 sv.maxRank 0 rem *** Global unlocks (Enabled) sv.useGlobalRank 1 sv.useGlobalUnlocks 1 rem *** Titan Movement (Enabled) sv.AllowTitanMovement 1 rem *** Demo Recordings (Enabled) sv.autoRecord 1 sv.demoIndexURL http:// sv.demoDownloadURL http:// sv.autoDemoHook "adminutils/demo/rotate_demo.exe" sv.demoQuality 1 rem *** Voice over IP Settings (disabled) sv.voipEnabled 0 sv.voipQuality 3 sv.voipServerRemote 0 sv.voipServerRemoteIP "" sv.voipServerPort 55125 sv.voipBFClientPort 55123 sv.voipBFServerPort 55124 sv.voipSharedPassword "" Download Config -Overview: This is an 12v12 Titan mode ladder. The match is played best of one round where the winner is determined by which team destroys the other teams Titan first. All Ladder rules will supercede normal TWL rules, both general and game specific. -Map Rotation: Only one map will be played per match chosen randomly by your admin panel. The Home team gets server selection and the Visiting team gets side selection. -Titan Specific Bugs/Exploits There is still a significant number of bugs in Titan mode applying directly to the Titans themselves, thankfully many of these bugs are uncommon. This being said, it's essential that demos be on and recording on this ladder. Any teams found intentionally exploiting any of these bugs will be punished at the admins discretion, repeat offenders risk being permanently removed from the ladder. -Team Size/Match Roster & GUID's: Each team is to fill a maximum of 12 positions. Teams are required to be "Match Ready" within 15 minutes of posted start time regardless of how many players they have in the server. The match will be started with the available players. Time extensions are at the discretion of the other team. If players become available during the match, they are allowed to join the match in progress provided they are on the teams roster with a valid GUID. You can add players until you have 12 regardless of the number of players the opposing team has. If a player joins a server at any time during live match play that is either not on the roster or does not have a valid GUID the team they are playing for will forfeit the entire match and are subject to disqualification from the ladder. Your PID (Player Identification Number) is NOT your GUID and should NOT be entered in it's place. PID is for stats tracking only and has nothing to do with your Punkbuster GUID Instructions on obtaining your GUID are listed below in the Punkbuster and GUID's section of the rules. -Draws/Overtime: Each side of the map is to be played before any OT periods. In the event of a tied match (each team has won a single round, or tied on round 1 and/or 2), a third round on the same map will be played. The team that had the highest amount of tickets remaining from the won round is allowed to choose which side they would like to play on round 3. If both teams are tied in tickets, the defender will have their side choice for round 3. If by chance the 3rd round is a tie, the opposite team will be given side choice. Side selection will alternate per OT until a winner is determined. -Match Sportsmanship All members of all teams are responsible for treating each other with respect during the match. Due to the lack of a language filter, please respect those in the server at all times and please don't be careless with your language. The server, as well as all members of each team, should be running the latest patch approved by TWL. -Battlerecorder/Demo Recording: All matches must be recorded. You must ask for the demo in match comms 24 hours prior to match to have a valid demo claim. Further details in the demo recording section. -Voice Over IP (voIP): voIP will be not be required to be enabled on match servers. Both teams may agree to use voIP but only by both parties consenting in 'match comms'. TeamWarfare will not rule on disputes that involve voIP. -Qualified Servers: A server capable of handling the maximum required number of players and 2 reserve spots is necessary for every match. The server must be located in North America. The server must be running in dedicated mode and following all of the necessary rules specified under General Gameplay Info. If each team has a server, the defending team chooses the server. Please ensure the server's stability and capability to withstand the required amount of players from across North America before the match begins. In the event of excessive lag, another server may be chosen or the match may be re-scheduled. The IP of the server should be provided to each team captain. In addition, the server must be listed on the master list. Please be sure to pay attention to the score in case of a difficulty of the server. It is important to prevent disputes by being aware. -Server Crashes: In the event of a server crash during a round said round will be replayed. Teams will begin this replay round with the flags they had when the server crashed. Any grey flags will be taken to that state and players will move totally away from them until play resumes. All players should remain by their own flags. 1 player from the required side will move to the flag that should be grey and take it to that state. Then that player will go back to a flag he holds and play will then begin from that point. In the case the server crashes again, the score at that point will stand and the match must be played on a different server. All previous round results will stand. Game Version and Server Information -Server and Client Sides: -Special note regarding new patches: DO NOT install new patches as soon as they are released. TWL uses a "patch approval process" for every new patch. This process is in place to ensure the new patch is compatible with match play. Some of the things the admins check for - Check the Ladder forums for more information when a new patch is released. -Server Types: -Ping Discrepancy: In the event of a major ping discrepancy, (+/- 50ms Average difference between teams) a neutral server must be used unless both Teams agree that the match should proceed. -Punkbuster Configuration Requirement: The team that is hosting the match server is responsible for the server being fully setup with the TWL punkbuster configurations including streaming to PsB. If the visiting team would like a copy of the PB logs once the match is completed, this request must be made in match comms prior to the start of the match. The validity of the logs can be verified by an admin upon request via email or IRC. The purpose of streaming is to backup any claim or evidence of a rules violation during the match and to enforce the TWL MBL. If a dispute is filed and the admins find the server has not been streaming to PsB or has been running incorrect/modified configurations the following punishments will apply: If the server is found not to be streaming during a match (i.e. when a dispute is not involved) the match will be thrown out and voided. Both teams should make sure they check the server's streaming status prior to starting the match to make sure this is not an issue. Please use the links below to check a server's status: PunksBusted If you need help with setting your server up or have a question about streaming please visit our forums. Note 1: The only grounds for not being able to stream to PsB is technical problems on the receiving side (i.e. PsB server problems). Note 2: Failure to produce punkbuster logs to the opposing team is not a disputable offense. Instead, the guilty team founder will be suspended for unsportsmanlike conduct. Note 3: If the team is found to be editing logs then the founder will be severely penalized and suspended. Unlocks, Commander Mode, Squad System, & Pods -Unlocks, Commander Mode, & Squad System: ILLEGAL: Active unlocks This includes: All Squad Leader assets are legal and can be utilized to their full potential. Check each individual ladders settings for any limitations on Commander mode. There are no limits on player classes or how many of a certain player class can be used by a squad. -Recommended Unlocks: In no particular order: These are recommended unlocks from our ladder staff, they are purely the opinion of our ladder staff and are in no way required to play on the BF2142 ladders. -Squad Leader Beacon/APC Pod Rules and Limitations: ***If you believe any of the above rules have been broken during a live match your Founder or Captain's should use global chat to communicate with the other team regarding the matter, a simple "please stop XXXXX" will suffice, remember that the match is live and being recorded you can review the demos after the match is over, it is advised that you never stop playing the match, if you stop the match and you are wrong you risk forfeiting the round. You will not be given a replay of a round for something you "thought" you saw happen.*** Any doubt can easily be verified by watching the demo of the round in question after the match is over, if after you have watched the demo you feel a rule was broken you may follow our dispute filing procedures for filing a dispute and the ladder admins will take it from there. -Out of Bounds "tactics": On several maps there may be ways to use the "Out of Bounds" areas to your advantage, these tactics are legal provided they are not using any exploits, you can be killed, etc... Please use common sense. -PunkBuster Requirement: -PunkBuster updates for Battlefield 2142: Punkbuster offers a free utility called PBSetup which can be used to update any game that uses Punkbuster. Instructions and download can be found here. Manual Punkbuster updates can be found here. -Invalid PB GUID's: If a player or team finds other players who are missing or have invalid GUID's, send an email to BFACTeam@teamwarfare.com. Having a valid GUID helps the community to have a fair and balanced game for all teams. -Master Ban List (AutoMBL): To take a more proactive stance against cheating, the TWL has approved the use of the Punksbusted.com Master Ban List for match play. Please note, however, that TWL does not provide technical support for the Punksbusted.com MBL nor the AutoMBL tool. To find our more information regarding the MBL and or the AutoMBL tool, please visit PunksBusted.com's website by clicking here. NOTE: Use of the MBL is not required for TWL matches. Therefore, teams cannot dispute against any other team who's server does not utilize this system, nor force a match to be played on a server that does use it. -The following is a general guideline on "How to handle GUID issues": -Enter the correct GUID and then email the appropriate Competition Manager to request the incorrect GUID be deleted. -GUID'S will not be removed so that players can still be tracked in case something appears on the MBL. If you buy a copy that is already registered w/ a GUID, return it and get a new copy. Your best bet would not to buy a used copy. -Email the AC team to find out about your ban and what to do next. ***All emails must contain the following information*** Competition Manager's List: Report any current suspected bans/GUID matches to: BF2142NALadders@teamwarfare.com -Demo Requirement: Note 1: Failure to produce a demo does not constitute a disputable offense. Note 2: Demos are to be held no less than 2 weeks after match date. Note 3: Not turning over a demo requested by the opposing team prior to the match will result in a 'Unsportsmanlike Conduct' suspension for the founder. -Joining a Ladder:
-Eligibility for Match: All Players must be registered on their team's roster with their correct (game specific) GUID listed in their profile the day before the match date. This means as long as they are on the roster by 11:59pm the day prior to the match, they are eligible. Exceptions may be agreed upon in Match Comms by the opposing team prior to match start. -Smurfing: Team Hopping or smurfing is not allowed. Players can leave a team and join a new one but switching between numerous teams on a frequent basis is not allowed. Doing so will result in a competition suspension. If you are creating new accounts or using another player's account to play for multiple teams on the same ladder/league you will be subject to the following: Any other violations are at the discretion of the Battlefield Competition Staff. Teams who attempt to use a player without a valid guid by bringing them in mid match will be forced to forfeit that match and could also be subject to other penalties. Smurfing is also defined as playing under a false identity. This means ringers may not change their name to more closely match a rostered player's name. Players must also use the GUID registered in their profile. Using another player's GUID is considered smurfing. If at any point a person is in control of two accounts on the same ladder then both accounts will be suspended. Players should not have more than one account at TeamWarfare anyway, doing so is a bannable offense. -Smurfing Founder Consequences Team founders are responsible for the actions of their team. Therefore, if a player is found to be smurfing on your team during a match, the founder will be subject to the following consequences: -Player Names: Due to the account system in Battlefield 2142 please have your name be similar to that of your Teamwarfare account. Examples: -Substitutions: Due to the nature of the Internet, it is possible for players to be disconnected or dropped from a server. Should this happen, you may substitute an eligible player to fill the spot or allow the dropped player to rejoin. Once connected, the player must join their respective team immediately. Due to the sizes of some teams, it is acceptable to rotate players at the beginning of new maps. However, this should be done in a timely manner that does not hinder the progress of the game. In other words, please have your teammates "waiting in the wings." -Spectators: The only spectators that will be allowed to watch a match are those authorized by TWL. TeamWarfare reserves the right to observe any TWL match without notification or approval. The Admin's identity can be verified by contacting them on IRC during the match in #twl_bf on Gamesurge. Any attempt to impersonate a TeamWarfare admin will result in a permanent site ban. -Account Deletion: If you would like your account removed from TeamWarfare please visit Site Support & Member Services and follow the instruction on this thread here. -Team Name Change: If you would like to request a name change for your team then please visit Site Support & Member Services and follow the instruction on this thread here. -Team Deletion: If you would like your team removed from TeamWarfare please visit Site Support & Member Services and follow the instruction on this thread here. Please note only the founder of the team can make this request. -Match Comms: -Roster PB GUID checks: -Accepting the Match: To challenge a team you must log into your team's Admin panel, also see Ladder Movement. If you are challenging a team you are considered the Attacker of the match. The team being Attacked is referenced as the Defending team. Once attacked the Defending team has 48 hrs to respond to the challenge of the Attackers by selecting two different dates and two different times for the Attacking team to select from. Also note that some Ladders may require additional selections such as maps and/or side selection. Failure to accept the match within 48 hrs will result in the following consequence. Consequence - Defender's forfeit match. Dropped 10 Ladder rungs. Attacker takes Defender's rung. Note: Forfeit will NOT include a loss on the record of the team, nor will the other team gain a win on their record. -Confirming the Match: Once the Defender has offered the dates and times the Attacking team will have 48 hrs to confirm one of the two offers by the Defending team. Also note that some Ladders may require additional selections such as maps and/or side selection. Failure to confirm the match 48 hrs after it was accepted will result in the following consequence. Consequence - Attacker's forfeit match. Dropped 10 Ladder rungs. Note: Forfeit will NOT include a loss on the record of the team, nor will the other team gain a win on their record. Teams that have these consequences applied will be notified by the auto mailer system. The TWL System monitors and flags all matches in violation. A llama is added each time to the team that violates the Match Acceptance process. Teams that receive more than 2 llama's in a row for inactivity will be removed from the Ladder. -Screenshots of the Score: Periodically you may need an Admin to finish the match results. Every Admin must be able to verify the scores in order to report the match as completed. It is the Captains responsibility from both teams to take screenshots at the end of each half so that the score can be verified. Without screenshots, regardless of the match outcome, the match may be canceled. -Reporting Match Results: It is the Team Captain's responsibility of the losing team to accurately report the match results in a timely manner. The Team Captain of the losing team MUST report the match results NO LATER THAN 1 HOUR after completion of the match. Teams who fail to report match results accurately and in a timely manner will be punished in the following manner:
NOTE: It is the winning team's responsibility to ensure that the match score is accurately reported and submitted in a timely manner. If the opposing team fails to report the match score, it is then the winning Team's responsibility to file a dispute indicating the losing team failed to report a loss. -No Shows: Teams that fail to show up in the correct server at match time will forfeit the match and may be dropped 10 rungs, this is NOT a llama. An exception to this is when a team shows up but does not have the required number of players. In that case if the other team does not agree to a reschedule then the team in violation should report the loss immediately, failure to do so may result in the loss of 10 rungs. Teams that are aware that they may not have someone around at match time to play or notify the other team should post in match comms stating the situation. This will then be at the admin's discretion as to whether or not ample notification was provided to waive the drop of 10 rungs. Any team that has 3 consecutive forfeits (No Shows or llamas) is subject to be removed from the ladder. -Match Time: -IRC Channel Info: This is a public channel open to all of the TeamWarfare Battlefield community. TWL_BF Admins are logged in 24 hours a day 7 days a week to help resolve any issues that you may have while competing on the TWL_BF Ladders. The majority of disputes submitted could of been resolved if a member of the team had logged in to IRC and requested an Admin to join the server. This is what we are here for: to help you. -TWL BF Admin Contacts: A current listing of Teamwarfare's BF2142 Admin Staff can be found by clicking here. -TeamWarfare Match Observation TeamWarfare Admins are available for match observation in applicable circumstances. Please be respectful to any TWL Admins assigned to a match. The role of an observer is to: If you would like to request an administrator to observe your match please email BF2142NALadders@teamwarfare.com with the following information. Please send all comments and/or complaints to BF2142NALadders@teamwarfare.com -Disputes for Cheating Format: Take a reasonable amount of time to discuss the issue with your own teammates. Take time to cool off and rationally talk about the issue. You need to have reasonable evidence to file charges. A text file with information regarding times and players involved it a vital piece of information for use in your dispute. If you feel you have reasonable grounds, initiate a dispute. List your concerns over specific instances during your match and include these in your dispute. Example: At x:xx minutes in the X round, player XXXXX did this. At x:xx in the X round, same player XXXXX did this. etc etc. Notify your opponent in Match Comms as soon as you dispute so they can get their evidence ready for review. Keep in mind that a disputed team becomes defensive. If your team has a dispute filed against you, cooperation is your best ally in a dispute. DO NOT use the Match Comms to flame the other team for disputing against you. Unsportsmanlike Conduct in the Match Comms will results in penalties. Counter-Disputes - Please do not submit a counter-dispute against a team that has disputed against you. TeamWarfare's investigation of a dispute includes hearing BOTH sides. You will have your chance to supply the Admin handling the dispute with any information you have. -Examples of Cheating Dispute Format: At approx 7:35 in the first half, |Team|Player3 was able to kill 5 of my team members in a single clip without reloading once in less then 20sec after we all spawned. We suspect symptoms of an Aimbot. {Clan}Player5 was able to come around corners preferring the weapon on several occasions as if we could be seen through the walls. This happened during the first half at 10:20, 6:50, and 3:23. Then it happened again during the second half at 18:43, 12:08, 10:22, and 5:16. During the first half at approx 5:15 left on the clock, a member of the other team was in the capture radius completely submerged. Please consult our screenshot as evidence of this. At approx 1:01 in the third round during the first half, -=Clan=-Member1 had their tank barrel pointing through a wall and was firing on us, we could not kill his tank because he was protected by the wall. Somewhere around 12:34 on the second round [clan]member7 began to use "all-talk" to type racist insults at our team, please consult our server logs and included screenshots for the evidence. -General Procedures: All disputes will be handled by the ladder admin(s). Each and every dispute inevitably involves different aspects and will be dealt with individually. Disputes must be reported to your ladder admin within 1 hour of match end. This is done by clicking on "Dispute Match Results", found in your team admin panel. Disputes must be for a valid and specific reason. Teams must identify 'when and where' the violation occurred. Admins may use their discretion of listening to a dispute that is later then an hour. -Report to Match Comms: In the event of a dispute, teams should check their match comms and team emails often as the admin may request additional information. Once requested, teams have 24 hours to produce the materials (demos, server logs, screenshots etc) that the admins ask for. The Admin will have the final say in judging the disputes. This game is meant to be fun, let’s keep it clean and avoid any unwanted hassles. -Making a Habit of Disputing: Our concern is to have a fun and clean place to play. Although the dispute process is necessary in helping keep a clean match, teams who make it a habit to dispute often with frivolous reasons will subject themselves to possible suspension, rungs lost and/or league points deducted. Teamwarfare has zero tolerance for cheating and cheating accusations without an effort to submit any evidence. -General Info: -Aug 19, 2009 Ladder Movement 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). Ladder Concept 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 tiebreaker map. The "Defending" team chooses map sides and order. The "Attacking" team picks the tiebreaker map sides. Team Roster Management 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. In the case of games with in game identifiers (PunkBuster), this GUID must be entered into the players profile before the defender accepts the challenge for the player to be considered 'eligible'. 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. Team Management 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. Challenge and Match Date Acceptance 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. Failure to Appear For each ladder there is a minimum number of players needed to proceed with a match. Teams should have the minimum number of players on the appropriate server no later than 15 minutes after the scheduled match time. Failure to meet this requirement will result in an immediate forfeit against the non-compliant party. Both teams should be ready to play no later than 30 minutes from the scheduled match time (Unless agreed upon by both parties). Failure to agree to start the match at this time will result in forfeiture by the non-compliant party. A TWL admin should be contacted immediately (mIRC - #teamwarfare) for a ruling to be made. If an admin isn't available then the match should be postponed, and a dispute must be filed. Server Selection Server preference and choices are communicated through the "Match Communication" Portion of your Team Admin Console. All matches must be played on a server that has the ability to be password protected. If a neutral server cannot be agreed upon then the 1st and 3rd maps will be played on the Defender's Choice and the 2nd will be played on the Attacker's choice. All members should be able to connect to the server. Server disputes must be handled before match completion. Disputing a server after a match has been played will result in the dispute being thrown out. Inactivity Teams of the TWL are expected to remain active while on the ladder. Any team showing inactivity for a period of three weeks will be deleted from the appropriate ladder. This time frame of course does not include "Rest" time taken. Challenge Cancelation 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. Sportsmanship and Cheating Un-sportsmanlike conduct during matches will not be tolerated by the TWL. If an admin is called in to resolve an issue regarding un-sportsmanlike conduct the judgment/punishment will be swift, efficient and final. We here at the TWL suggest you conduct yourselves accordingly. See the specific ladder areas by this name for the specifics for that ladder and game. Server Selection Time All servers must be posted in the online match communications 48 hours prior to the match time. If no attempt is made to offer a server for your team, and the opposing team has offered a server, all 3 matches may be played on the opposing team's server per their request. Server Crashes 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. If there is a dispute the entire map will be restarted. In the event that a team loses a player due to connectivity issues, (or his Mom/Dad tells him to get the hell off the PC...LOL) 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. Punctuality Map side choices and order must be relayed to the attacking team no more than 24 hours after the attacker schedules the match. The attacking team also must relay side choice for the Tiebreaker map no later than 24 hours after scheduling the match. Server choice must be communicated in the "Match Communication" section in your team's ladder control panel 48 hours prior to match time. Failure to keep these deadlines may result in your forfeit of these options at the opposing team's (and admin's) discretion. Rescheduling Should a match require rescheduling, the new match time should be within 3 days of the original match time. Matches can only be rescheduled once. Mutual consent via match comms between opponents is required. Smurf Policy 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.
Additionally, team captains and founders can contact your games coordinator (SysAdmin). The list is located here. In each games staff list, at the top, is the SysAdmin for that game. The admins will cooperate fully with team captains and founders in order to combat and prevent smurfing. We will NOT hand out IP's so don't ask but we will be more than happy to check a certain player on your team. ****Ladder Specific rules supercede the corresponding general ladder rule.**** HACKING 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. |
Additional Sponsorship From
