Difference between revisions of "Mannhattan"
(The gate glitch wasn't fixed, just altered... (Added the bug, However, it's very likely in need of a re-write.) :/ Plus: Removed the template "W", as the template article wants people to remove every instance of it that one finds.) |
(I think this bug was fixed.) |
||
Line 28: | Line 28: | ||
When updated with content, the [[Mannhattan Community Strategy]] page will contain some strategic points. | When updated with content, the [[Mannhattan Community Strategy]] page will contain some strategic points. | ||
− | == Bugs == | + | <!--== Bugs == |
− | * If the gatebots manage to capture gate A and B, and the mercs beat the wave, the mercs have to be extra careful; If the gatebots capture gate A in the next wave, the first robot spawn gets locked off, as intended... however, gate A doesn't actually open, and the robots just spawn at gate B, which is closed, and they try to literally walk through the closed gate, making the wave unable to be beaten nor lost. (Similar to the bug at the release of the [[Two Cities Update]], except it now first happens when the gatebots capture a gate instead of when the wave starts.) | + | * If the gatebots manage to capture gate A and B, and the mercs beat the wave, the mercs have to be extra careful; If the gatebots capture gate A in the next wave, the first robot spawn gets locked off, as intended... however, gate A doesn't actually open, and the robots just spawn at gate B, which is closed, and they try to literally walk through the closed gate, making the wave unable to be beaten nor lost. (Similar to the bug at the release of the [[Two Cities Update]], except it now first happens when the gatebots capture a gate instead of when the wave starts.)--> |
== Trivia == | == Trivia == | ||
Line 51: | Line 51: | ||
{{Show achievement|Mann vs. Machievements|Software Downgrade}} | {{Show achievement|Mann vs. Machievements|Software Downgrade}} | ||
{{Show achievement|Mann vs. Machievements|Urban Strike}} | {{Show achievement|Mann vs. Machievements|Urban Strike}} | ||
+ | |||
+ | == Update history == | ||
+ | {{patch name|11|21|2013}} | ||
+ | * Added Mannhattan to the game | ||
+ | |||
+ | {{patch name|12|6|2013}} | ||
+ | * Rebalanced [[Empire Escalation (mission)|Empire Escalation]] | ||
+ | * Fixed credits not always being collected when they fall into the grinder | ||
+ | * Fixed a bug that allowed the gates to be captured out of order | ||
+ | * Fixed a lighting bug related to lower graphics settings that cause the map to be too dark | ||
{{Two Cities Update Nav}} | {{Two Cities Update Nav}} |
Revision as of 04:27, 7 December 2013
“You are so small! Is funny to me!” This article is a stub. As such, it is not complete. You can help Team Fortress Wiki by expanding it. |
“Let's go, let's go, let's go!” This article documents a recent addition. It may contain speculation, broken links or errors. You can help improve it by editing this page to include new information. |
Mannhattan | |
---|---|
Basic Information | |
Variants: | Blazehattan |
Developer(s): | Unknown |
Map Info | |
Environment: | Urban City |
Setting: | Daylight, Sunny |
Map Photos | |
Map Overview | |
“ | The first of our two cities, Mannhattan, takes our mercs all the way from the sun-blasted gravel pits of the Badlands to the urban sprawl of the East Coast, where they'll have to defend the manufacturing arm of Saxton Hale's boutique Mhankö line. Mannhattan's robot hordes can advance their own spawn points and introduce new bombs into the map for the first time, making for a unique new MvM experience.
— Two Cities Update page
|
” |
Mannhattan is a map, released in the Two Cities Update. It sees players in a metropolis area resembling Manhattan, defending the manufacturing arm of Mann Co's "Mhankö" line.
Unique to this map are its two gates, labelled Gate A and Gate B. Roughly half of the robots that spawn are "gatebots", identified by glowing yellow lights on their heads, which ignore the bomb and instead try to open the gates much like capturing control points. If a gate is captured, all bombs currently in play will be sent back to spawn, and all non-giant robots will be stunned for approximately twenty seconds. When this time expires, the robots will resume their assault and gain guaranteed critical hits for a short period of time. Note that unlike control points, the robots' capture progress cannot be blocked by the player alone, as they must destroy every robot in the capture zone to prevent it.
The capturing of a gate has three effects that will make the defenders' job more difficult: the robots' spawn will move up to the newly captured gate, captured gates cannot be closed or recaptured for the rest of the wave, and an additional bomb will be brought into play. This will force the defenders to split their forces accordingly, as players may have to defend against two or three bombs at once. In the event both gates are captured, the gatebots' lights will turn off, and they will join the rest of the horde in carrying the bombs.
Strategy
When updated with content, the Mannhattan Community Strategy page will contain some strategic points.
Trivia
- The map has a poster of King Kong with the words "Missing $50 Reward."
- The map's name is a play on Manhattan, a borough of New York City, known for its skyscrapers.
Gallery
- Mannhattan bot spawn1.jpg
The place where the robots spawn at the beginning.
Related achievements
Mannhattan has 5 map-specific achievements.
Chippin' In As a team, pit 10 guys in a single wave in Mannhattan. |
Get Off My Lawn Play an advanced mission without losing a single gate in Mannhattan. |
Now Legal To Eat Ooohh Ooh Ahh Ahhhh! ...in Mannhattan |
Software Downgrade As a team, kill 50 stunned radiowave robots in an advanced mission in Mannhattan. |
Urban Strike Kill 500 gate crashing robots in Mannhattan. |
Update history
- Added Mannhattan to the game
- Rebalanced Empire Escalation
- Fixed credits not always being collected when they fall into the grinder
- Fixed a bug that allowed the gates to be captured out of order
- Fixed a lighting bug related to lower graphics settings that cause the map to be too dark
|