Editing Prolander

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help pages.

Latest revision Your text
Line 18: Line 18:
 
With its team sizes of 7 and class limits of 1, the primary strategy of play revolves around the support and pick classes chosen by each team. Classes can be changed in game at any time, as long as there are no more than one of each class outside the spawn at any given time. As with other competitive formats, there is a combo consisting typically of a Medic and a Demo, with other classes such as Heavy and/or Pyro often joining them.
 
With its team sizes of 7 and class limits of 1, the primary strategy of play revolves around the support and pick classes chosen by each team. Classes can be changed in game at any time, as long as there are no more than one of each class outside the spawn at any given time. As with other competitive formats, there is a combo consisting typically of a Medic and a Demo, with other classes such as Heavy and/or Pyro often joining them.
 
=== Strategy ===
 
=== Strategy ===
The combinations of the classes possible creates a variety of gameplay options, for example the defensive team on a Payload map may choose to use a Medic, Demo, Pyro, Heavy, Engineer, Soldier, and Sniper which would be a very combo heavy, defensive composition. The attacking team may run a Medic, Demo, Pyro, Sniper, Soldier, Scout and Spy, which is very flank/pick intensive composition which could be used to counter the other teams defenses and exploit lightly held flank routes. The format revolves around shifting classes in response to the other team, for example if BLU struggles to deal with a RED Engineer they may run a Spy. If a RED Sniper then changes Pyro to counter this Spy, then that leaves RED open to a BLU counter Sniper and so on.
+
The combinations of the classes possible creates a variety of gameplay options, for example the defensive team on a Payload map may choose to use a Medic, Demo, Pyro, Heavy, Engineer, Solider, and Sniper which would be a very combo heavy, defensive composition. The attacking team may run a Medic, Demo, Pyro, Sniper, Solider, Scout and Spy, which is very flank/pick intensive composition which could be used to counter the other teams defenses and exploit lightly held flank routes. The format revolves around shifting classes in response to the other team, for example if BLU struggles to deal with a RED Engineer they may run a Spy. If a RED Sniper then changes Pyro to counter this Spy, then that leaves RED open to a BLU counter Sniper and so on.
 +
 
  
 
== Organizations ==
 
== Organizations ==

Please note that all contributions to comp.tf may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see comp.tf:Copyrights for details). Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)