Editing Swiftwater

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 5: Line 5:
  
 
|maptype=pl
 
|maptype=pl
|filename=pl_swiftwater_final1
+
|filename=pl_swiftwater
 
|version=Official Release
 
|version=Official Release
|author1=Aaron "Schwa" McCallen
+
|download=<!--http://downloads.tf2.mooh.org/maps/pl_swiftwater_final_rc.bsp.bz2-->
|author1steam=76561197967274957
+
|creator1=Schwa
|author2=
+
|creator1steam=76561197967274957
|author2steam=
+
|creator2=
|author3=
+
|creator2steam=
|author3steam=
+
|creator3=
|released=19 May 2009
+
|creator3steam=
|updated=7 July 2016
+
|released=19 May, 2009
 +
|updated=23 August, 2011
 
|official=1
 
|official=1
  
Line 20: Line 21:
 
|gamemode2=
 
|gamemode2=
 
|gamemode3=
 
|gamemode3=
|adapted=
+
|proof=
 
|pro=Swiftwater UGC
 
|pro=Swiftwater UGC
 
|popularity=moderate
 
|popularity=moderate
 
|lpleague=
 
|lpleague=
 
|lpseason=
 
|lpseason=
 +
|lpdate=
  
|download=http://fakkelbrigade.eu/maps/pl_swiftwater_final1.bsp
 
 
|workshop=473210550
 
|workshop=473210550
 
|tf2maps=6749
 
|tf2maps=6749
Line 40: Line 41:
 
}}
 
}}
  
'''pl_swiftwater''' is a custom payload map made by [http://steamcommunity.com/id/whatisschwa Schwa] that is exclusively used in [[Highlander]]. The [[Swiftwater UGC|pl_swiftwater_ugc]] variation has been frequently included in the UGC league map list since Season 8. Nearly four years after development on the map had ceased, it was included in the Meet Your Match update in July of 2016.<ref name="TF2 - Meet Your Match">[http://www.teamfortress.com/meetyourmatch/ TF2 - Meet Your Match]</ref>
+
'''pl_swiftwater''' is a custom payload map made by [http://steamcommunity.com/id/whatisschwa What Is Schwa?] that is exclusively used in [[Highlander]]. The [[Swiftwater UGC|pl_swiftwater_ugc]] variation has been frequently included in the UGC league map list since Season 8. Nearly four years after development on the map had ceased, it was included in the Meet Your Match update in July of 2016.<ref name="TF2 - Meet Your Match">[http://www.teamfortress.com/meetyourmatch/ TF2 - Meet Your Match]</ref>
  
 
== Usage in competitive ==
 
== Usage in competitive ==
 
{{Swiftwater/MapLeagueInclusionTable}}
 
{{Swiftwater/MapLeagueInclusionTable}}
 +
==Strategy==
  
==Strategy==
 
 
Attacking times on swiftwater tend to be longer than on other traditional payload maps such as Badwater and Upward. It is a more open map than either of those, with the layout offering a lot of height advantage as well to use for flanking and utility classes.
 
Attacking times on swiftwater tend to be longer than on other traditional payload maps such as Badwater and Upward. It is a more open map than either of those, with the layout offering a lot of height advantage as well to use for flanking and utility classes.
  
 
Defensive strategy can vary quite a lot depending on the team involved, it really is a map where a degree of familiarity and team synchronization is required to play well. At higher levels a top sniper can be a nightmare to play against!
 
Defensive strategy can vary quite a lot depending on the team involved, it really is a map where a degree of familiarity and team synchronization is required to play well. At higher levels a top sniper can be a nightmare to play against!
  
=== First point ===
+
<big>'''1st Point'''</big>
{{Map locations
 
| title = Swiftwater, first point
 
| image = pl_swiftwater A.png
 
| area1 = Platform | x1=155px | y1=190px
 
| area2 = Bar/House | x2=200px | y2=130px
 
| area3 = Perch | x3=250px | y3=50px
 
| area4 = Stream/River | x4=400px | y4=370px
 
| area5 = Shed | x5=750px | y5=280px
 
| area6 = Tunnel/Mine | x6=600px | y6=150px
 
| area7 = Log | x7=510px | y7=310px
 
| area8 = Boxes | x8=20px | y8=200px
 
| area9 = Behind/Maintenance | x9=370px | y9=70px
 
| area10 = Patio/Gates/Connector | x10=490px | y10=55px
 
}}
 
 
 
There is no definitive strategy for the first point hold although the consensus is this can be difficult to hold. If a team does try to hold they will typically be on the ledge in-front of the house. This can be vulnerable to spam and you run the risk of getting cut off if you lose your flank by the tunnel exit. Consequently many teams do not commit important classes to the defense of first at all, setting up in the tunnel. There can be interesting strategies to try and catch the attacking medic unawares and generally stall the push before 2nd.
 
  
 
<gallery>
 
<gallery>
Line 73: Line 58:
 
</gallery>
 
</gallery>
  
=== Second point ===
+
There is no definitive strategy for the first point hold although the consensus is this can be difficult to hold. If a team does try to hold they will typically be on the ledge in-front of the house. This can be vulnerable to spam and you run the risk of getting cut off if you lose your flank by the tunnel exit. Consequently many teams do not commit important classes to the defense of first at all, setting up in the tunnel. There can be interesting strategies to try and catch the attacking medic unawares and generally stall the push before 2nd.
{{Map locations
 
| title = Swiftwater, tunnel area
 
| image = pl_swiftwater Tunnel.png
 
| area1 = Arm | x1=510px | y1=175px
 
| area2 = Pallet | x2=330px | y2=160px
 
}}
 
  
{{Map locations
+
<big>'''2nd Point and 3rd Point'''</big>
| title = Swiftwater, second point
 
| image = pl_swiftwater B.png
 
| area1 = Catwalk | x1=470px | y1=100px
 
| area2 = Banana | x2=410px | y2=145px
 
| area3 = Attic | x3=700px | y3=110px
 
| area4 = Basement | x4=660px | y4=210px
 
| area5 = Long | x5=675px | y5=415px
 
| area6 = Lightbulb | x6=225px | y6=115px
 
| area7 = Mansion | x7=180px | y7=10px
 
| area8 = Truck | x8=475px | y8=325px
 
| area9 = Tires | x9=445px | y9=160px
 
}}
 
 
 
The bomb goes through the tunnel (2nd point is at the end of the tunnel) and a good defense here can be tough to break through without an uber, key picks by the spy or effective use of the top flank. I refer to the top flank, this is a one-way door (beware!) on the top right of the first point which grants access to a top corridor which leads onto a balcony overlooking the third point and red spawn. Control of this area can be important for both teams for the 2nd point due to the substantial height advantage it offers. Defending, you should always be aware of who is up there at the very least. Teams can also place sentry guns and keep other players on the opposite side to the first point flank.
 
  
 
<gallery>
 
<gallery>
File:Tunnel.jpg|Tunnel leading to the 2nd capture point
+
File:Tunnel.jpg|Tunnel leading to 2nd and 3rd capture points
File:3rd Point.jpg|2nd from Attack's POV
+
File:3rd Point.jpg|3rd from Attack's POV
File:3rd Point 2.jpg|2nd from Defense's POV
+
File:3rd Point 2.jpg|3rd from Defense's POV
 
</gallery>
 
</gallery>
  
=== Third point ===
+
The bomb goes through the tunnel (2nd point is at the end of the tunnel) and a good defense here can be tough to break through without an uber, key picks by the spy or effective use of the top flank. I refer to the top flank, this is a one-way door (beware!) on the top right of the first point which grants access to a top corridor which leads onto a balcony overlooking the third point and red spawn. Control of this area can be important for both teams for the 3rd (and 2nd) points due to the substantial height advantage it offers. Defending, you should always be aware of who is up there at the very least. The 3rd point is traditionally one of the hardest points to attack in the map (along with the 4th and 5th). Teams can also place sentry guns and keep other players on the opposite side to the first point flank.
{{Map locations
 
| title = Swiftwater, third point
 
| image = pl_swiftwater C.png
 
| area1 = Attic | x1=345px | y1=60px
 
| area2 = Tanks/Storage | x2=515px | y2=70px
 
| area3 = Silos/Trio | x3=380px | y3=90px
 
| area4 = Choke | x4=525px | y4=175px
 
| area5 = Balcony | x5=540px | y5=265px
 
| area6 = Einstein | x6=175px | y6=285px
 
| area7 = Speakers | x7=100px | y7=200px
 
| area8 = Connector | x8=235px | y8=70px
 
| area9 = Dropdown/Basement | x9=305px | y9=130px
 
}}
 
  
Because the attack can go a number of different routes this can be an unusual point to defend. The sentry overlooks the cart in some position, and all other classes positioning can vary heavily you do see the combo near he sentry more often than not). Soldiers tend to roam on the far side to the spawn looking for drops on the medic or vulnerable people walking through the doors, and scouts get out onto the left (3rd point) if they can. Once the attacking team take this point the spawn doors behind the defense close and they essentially get trapped (blue spawn changes to directly in front of you too). Not getting caught here is often the key to a good 5th point defense.
+
<big>'''4th Point'''</big>
  
 
<gallery>
 
<gallery>
File:4th point.jpg|3rd Point coming from 2nd, poor picture
+
File:4th point.jpg|4th Point coming from 3rd, poor picture
 
</gallery>
 
</gallery>
  
=== Fourth point ===
+
Because the attack can go a number of different routes this can be an unusual point to defend. The sentry overlooks the cart in some position, and all other classes positioning can vary heavily you do see the combo near he sentry more often than not). Soldiers tend to roam on the far side to the spawn looking for drops on the medic or vulnerable people walking through the doors, and scouts get out onto the left (3rd point) if they can. Once the attacking team take this point the spawn doors behind the defense close and they essentially get trapped (blue spawn changes to directly in front of you too). Not getting caught here is often the key to a good 5th point defense.
{{Map locations
 
| title = Swiftwater, fourth point
 
| image = pl_swiftwater D.png
 
| area1 = View | x1=740px | y1=105px
 
| area2 = Garage | x2=735px | y2=205px
 
| area3 = Porch | x3=715px | y3=355px
 
| area4 = Slope | x4=405px | y4=280px
 
| area5 = House/Station | x5=200px | y5=295px
 
| area6 = Behind | x6=50px | y6=310px
 
| area7 = Barn | x7=90px | y7=155px
 
| area8 = Gate | x8=165px | y8=50px
 
| area9 = Vent | x9=220px | y9=80px
 
| area10 = Lockers | x10=310px | y10=25px
 
| area11 = Under/Ballpit | x11=310px | y11=70px
 
| area12 = Hold | x12=390px | y12=95px
 
| area13 = Shack | x13=525px | y13=60px
 
}}
 
  
A long and potentially bloody attack up a hill for the 4th point, where the cart has to go a long way to go. The combo typically sets up on the ledge above the first section of uphill along with the engineer which allows them to shoot down onto the hill/and cart at first. Flank classes (defense, I am thinking solly and scout), if they can try, to get into the house on the far right (from the defense's perspective). The two teams snipers are often the deciding factors here, on defense the sniper can be a long way back. For the attacking team the key is speed. If they can catch some players out on 3rd and prevent this ideal defense being set-up that saves valuable time.
+
<big>'''5th Point'''</big>
  
 
<gallery>
 
<gallery>
File:5th point.jpg|4th point from defence, Sniper spot!
+
File:5th point.jpg|5th Point from defence, Sniper spot!
File:5th Point 2.jpg|4th point in-game example
+
File:5th Point 2.jpg|5th Point in-game example
 
</gallery>
 
</gallery>
  
=== Fifth point ===
+
A long and potentially bloody attack up a hill for the 5th point, where the cart has to go a long way to go. The combo typically sets up on the ledge above the first section of uphill along with the engineer which allows them to shoot down onto the hill/and cart at first. Flank classes (defense, I am thinking solly and scout), if they can try, to get into the house on the far right (from the defense's perspective). The two teams snipers are often the deciding factors here, on defense the sniper can be a long way back. For the attacking team the key is speed. If they can catch some players out on 4th and prevent this ideal defense being set-up that saves valuable time.
{{Map locations
+
 
| title = Swiftwater, fifth point
+
<big>'''Last Point'''</big>
| image = pl_swiftwater E.png
 
| area1 = RPC | x1=770px | y1=110px
 
| area2 = Box | x2=745px | y2=190px
 
| area3 = Grass | x3=550px | y3=200px
 
| area4 = Stairs | x4=5px | y4=350px
 
| area5 = Pumps | x5=310px | y5=170px
 
| area6 = Bridge/Windows | x6=280px | y6=70px
 
| area7 = Map/IT | x7=435px | y7=45px
 
| area8 = Secret | x8=500px | y8=10px
 
}}
 
  
 
A sentry gun is typically overlooking the cart. Power classes from both sides tend to contest the upper lobby overlooking this gun position. Whilst there are flanks available to try and get behind the attacking teams players the defensive team has to balance this potential threat they can cause with the need for players stop to the cart. This balance may depend on the amount of pressure on it (number of attacking players pushing cart, how close it is etc.).
 
A sentry gun is typically overlooking the cart. Power classes from both sides tend to contest the upper lobby overlooking this gun position. Whilst there are flanks available to try and get behind the attacking teams players the defensive team has to balance this potential threat they can cause with the need for players stop to the cart. This balance may depend on the amount of pressure on it (number of attacking players pushing cart, how close it is etc.).
Line 169: Line 94:
 
{{reflist}}
 
{{reflist}}
  
{{Active Maps Navbox}}{{All Maps Navbox|y}}
+
{{Maps navbox}}
 +
[[Category:Maps]]
 +
‏[[Category:Payload maps]]

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)