Mann vs. Machine
| “ | Gray Mann has built an unstoppable automaton army with a single purpose: to destroy all things Mann Co. Luckily for you, the majority of this robot legion is equipped with basic weaponry that could never level an entire building. Unluckily, they also have access to giant bombs, which they’d drag through hell if it meant dropping one in a Mann Co. bombhole. And it’s up to you to stop them.
— Mann vs. Machine publicity blurb
|
” |
Mann vs. Machine is a co-op game mode released in the update of the same name. In Mann vs. Machine, a team up to six players attempts to prevent a horde of AI-controlled robots from carrying a bomb to their base. Players can purchase upgrades for their weapons using in-game currency, called credits. All purchased upgrades will last for the duration of the game. If a player leaves during the game for any reason, providing they reconnect, their upgrades will be retained.
The only achievements obtainable in Mann vs. Machine are the Mann vs. Machievements.
Mann vs. Machine uses a separate set of "Best Moments" thus keeps track of separate performance report.
The game mode currently has four difficulties: Normal, Intermediate, Advanced, and Expert.
Contents
Videos
| Trailer | Instructional Film |
|---|---|
Mechanics
The team is attacked by a horde of AI-controlled robots, and must try to prevent the robots from successfully delivering a bomb to the players' base (as in Payload). Each robot destroyed provides the players with credits (when one player collects a money pile, it is divided equally amongst the players). Between waves of robots, the players have the chance to upgrade their weapons at an Upgrade Station inside the base using this money. They may also upgrade abilities for their current class. The upgraded abilities are kept, even while switching to a different class, but the purchased abilities are only available for the class that they were purchased for.
Robots
Most of the robot horde is made up of plain robotic versions of eight of the nine playable classes (there are no robot Engineers), with their respective basic weapons equipped. However, there are also a number of special robots with unique abilities.
The bomb-carrying robot receives buffs, which increase over time. A HUD graphic displays the amount of time until the next buff. Buffs are activated by the bomb carrier via taunting, setting off an accompanying audio cue. These buffs are divided into three stages, which stack together:
| Stages | Upgrades |
|---|---|
 |
Defensive buff, shared with all nearby robots |
 |
Health regeneration |
 |
Full crits all the time |
Abilities and Upgrades
Players may use their accumulated credits at an Upgrade Station to fill Canteen with a buff—such as personal ÜberCharge, a five-second critical hit boost, or ammunition refill—or an ability such as rapid building upgrades for Engineers or the ability to teleport back to the spawn point. All of these Canteens each provide up to three uses and must be filled with the same buff.
Players may also purchase personal abilities for themselves or for upgraded weapons.
 Scout
|
|
|---|---|
 Soldier
|
|
 Pyro
|
|
 Demoman
|
|
 Heavy
|
|
 Engineer
|
|
 Medic
|
|
 Sniper
|
|
 Spy
|
Gameplay
For the sake of identification, all human players will be dressed in RED and will be identified as team DEFENDERS while all robots will have BLU colors in their visual effects and in the kill feed.
The players will load into a selected mission which contains a number of waves, each containing a set number (Though support troops will spawn infinitely based off a timer in each wave) of predetermined enemies for the human team to attempt to defend against.
Before each wave begins, Defenders will be given a graphic indication of the impending onslaught, including information on what wave they are on, the total number of waves, and the number and type of enemies the wave will contain. Primary targets will have numbers underneath them and will be classified by class or (in the case of special robots) their specialty. Red groups indicate tanks as well as giant robots. Support targets will be noted as such and will tend to be focused on attacking the players rather than carrying the bomb (though some like Scout supports will try to carry the bomb at times). Snipers and Spies are always assigned support roles.
When at least three players enter a Mann vs. Machine server, the option to begin play is enabled. During the setup phase before the robots arrive, Engineers are able to instantly place buildings, fully upgraded to level 3, at no metal cost, and Medics can instantly fill their ÜberCharge meters and rapidly max out ally overheals. Once one player declares he is ready, a 150-second countdown clock will begin. As more players acknowledge they are ready, the clock time will be reduced in 30-second intervals (to 120, 90, 60, and 30 seconds, respectively, depending on the number of players present). Players joining the server during the countdown will not increase the time. If all players acknowledge that they are ready, the round is committed and the clock is reduced to ten seconds. Regardless of how it is done, once the countdown ends, the robots will begin their approach to the field.
Robots cannot attack or be damaged until they jump down into the players' field. A strength gauge will appear to note the remaining forces of the wave. Only primary targets count towards this progress. As they are destroyed, the gauge will empty. Once it is completely empty, the wave is defeated. During the wave, support icons may appear to indicate a specific threat.
- Sniper - Snipers are entering the field. They enter like regular robots but will be focused on attacking players from afar. Snipers will always display visible lasers from their rifles when scoped, making them easier to spot. Beware of their Special counterparts, the Bowmen. They don't produce visible lasers.
- Spy - Spy robots are on the field. Unlike the other robots, these used their cloaks to infiltrate the field and will enter from the player's side of the field (which means they'll be coming from behind you most of the time), already disguised as a human. They will act as your average Spy would: sapping Engineer buildings and attempting backstabs.
- Sentry Buster - Sentry Busters will fixate on a Sentry Gun on the field and try to get close to it. If it reaches the Sentry or runs out of health, it will stop and then explode powerfully after two seconds, destroying all buildings and players within the explosion's radius. Note the Sentry Buster will target the closest Sentry Gun to the ramp, regardless of how much damage it has received.
- Tank - Heavily-armored tanks will enter the field from specific entry points. They won't attack but will move implacably towards the bomb hatch until they are destroyed or reach their destination. They can however crush any unfortunate player that gets stuck between them and a static object like a wall or fence. Tanks do not need to carry or retrieve the main bomb as each one contains its own bomb.
After each successful wave, the defenders will be evaluated based on how aggressively money was collected (with a credit rating ranging from F to A+). If all the piles of money are collected (the A+ grade), the team will earn a $100 bonus. Once a mission is completed, the defenders will be given a final evaluation, and the server will load the next Mann vs. Machine map after an interval of 20 seconds.
Abandoning Matches
 | “Oh dear, I've made quite a mess.” This page has been marked for general cleanup. Reason given: This may need a bit of tweaking Please see Team Fortress Wiki style guide for information on how to improve this article. |
If a player leaves a match, they will incur a penalty if all of the following circumstances are met:
- They leave a game while playing a Mann Up game on an official server; and
- They have not played through a single wave to completion or failure; and
- There are 5 or more players currently connected to the server (including the player)
Otherwise, it is safe to leave the game without a penalty. If they meet all of the circumstances repeatedly, they will receive a penalty wherein they are placed in a low-priority pool and will have much longer to wait for matchmaking.
When a player presses the disconnect button, they will receive a message telling them whether it is safe to leave, they are abandoning and will get a penalty or they are abandoning without getting a penalty. However, if the player leaves by other means (such as via the console or steam invite), they will not receive a message and may get a penalty without being notified.
If a player loses their connection to a game, their spot will be reserved and they will have 3 minutes to rejoin. If they do not return within the 3 minutes, they will be counted as having left the server intentionally. After a crashing or a loss of Internet connection, a player can restart Team Fortress 2 and then shall receive a prompt for them to reclaim their spot. This prompt will also tell them what (if any) penalties you will incur by declining. If the player fails to rejoin within three minutes AND fills out the criteria above, they will count as having abandoned the match.
Players that are kicked for being idle are counted as having quit intentionally and will incur a penalty. Players that are votekicked from the server are not considered to have left intentionally and will not be considered as abandoning a game.
Strategy
Maps
Mann vs. Machine maps carry the mvm_ prefix
| Name | Picture | File name |
|---|---|---|
| Coal Town | 
|
mvm_coaltown
|
| Decoy | 
|
mvm_decoy
|
| Mannworks | 
|
mvm_mannworks
|
Unused content
- RED versions of all of the robots can be found in the game files.
- An Engineer robot was originally going to be in the game according to the secret files in the source filmmaker.
Bugs
- Sometimes a menu such as team, class, or upgrade choice will freeze on screen, forcing the player to refresh the HUD. (This can be accomplished by typing hud_reloadscheme in the console or pressing TAB.)
- When killed by a dead bot, such as from afterburn, or when removing a destroyed Spy bot's Sapper, the kill feed may show that the bot has moved to spectator mode. This is due to the internal routine that reassigns bot players for the next attack.
- Sometimes after the wave is complete, the Administrator will continue to issue warnings about the bomb's progress. This does not impede progress in any way.
- Bots will occasionally become stuck when jumping down into the map from their spawn. On rarer occasions this will cause the bot to Immediately die upon touching the ground.
- Giant bots have been known to die upon falling from a decent height, regardless of health remaining.
- Bots that are destroyed while speaking and players who are killed while using Mann vs. Machine-related responses will continue speaking after their destruction/death. Tank Robots that are destroyed as they stop to deploy the bomb will continue to play the buzz and ding sound sequence.
- It is possible for the Administrator to announce the team has failed the mission when they haven't, by destroying the bomb carrier as it is about to disappear into the bomb hole. The bomb hatch will be destroyed, but the game considers the bomb undeployed. In this case, the real bomb will never make it to the hatch as it will continue to kill anything that steps in to it.
- Currently, there is an exploit, allowing Demomen with Chargin' Targe and fully upgraded resistance to fire and explosions to receive no damage from afterburn/explosions at all.
- Hitting the F4 key will still toggle ready-up even if the ready-up command was set to another key.
- A rare bug that crashes the game can occur when a Pyro airblasts a giant bot.
- Sometimes, when the map is finished, the loot screen shows up empty. This situation becomes recurrent for the player affected.
- Robot Snipers' blue lasers often glitch, being visible through solid objects and walls, even after the Sniper has been killed.
Related achievements
Update history
- Added Mann vs. Machine.
- Fixed a client crash related to Mann vs. Machine stats.
- Fixed a crash related to server plug-ins spawning a Tank before the game is ready.
- Updated the dedicated server to exit when attempting to start a Mann vs. Machine map with less than 32 maxplayers.
- Fixed
mp_timelimitcausing Mann vs. Machine mode to not reset properly when the defenders lose. - Fixed the Mann vs. Machine wave loss/victory dialog buttons not being clickable sometimes.
- Fixed the Mann vs. Machine victory dialog getting stuck on the screen.
- Fixed the Mann vs. Machine wave summary dialog showing up at the beginning of the first wave.
- Fixed the disconnect reason not being localized properly for Mann vs. Machine mode.
- Fixed player glow colors not based on player health in some community mods outside of Mann vs. Machine mode.
- Removed console spew related to missing movement warnings.
- Updated the matchmaking ConVar
tf_mm_strict.
- Fixed matchmaking sending players to out-of-date servers.
- Fixed the server browser showing an incorrect player count in MvM games.
- Fixed MvM intro video not playing on some Macs.
- Fixed the sound precache string table being nearly full in non-MvM games.
- This was causing the "error writing string table baseline" and "failed reading message net_SetConVar" errors.
- Added a new command
"player_ready_toggle"for players to ready-up.- Can be bound to any key in the Keyboard tab of the Options dialog.
- Fixed a few MvM sounds not being precached properly.
- Added Taskbar Window Flash and Drum Roll sound on successful match making for Windows users.
- Sound will play even if the game is minimized.
- Added difficulty text "Normal" and "Advanced" to the MvM scoreboard when playing official Valve missions.
- Fixed UI Bugs related to the MvM splash screens (Wave Loss and Victory).
- Server browser will now show MvM mission name in the "map" column. (E.g. "mvm_mannworks_advanced").
- Fixed a crash when spawning the tank in non-MvM games. Added SetHealth, SetMaxHealth, AddHealth, and RemoveHealth inputs to the tank entity
- Fixed an issue in the Server Browser where replay bots would add to the player count.
- Fixed a bug that would sometimes cause the bomb to get positioned incorrectly when dropped.
- Added safeguards to prevent bots from getting stuck in certain cases.
- Fixed Steel Gauntlet robots failing to destroy mini-Sentry Guns on slopes.
- Fixed the party leader’s mission completions showing in the game lobby instead of your own.
- Matchmaking search criteria supports selecting multiple missions.
- Matchmaking will prevent late joining into the a server near the end of the last wave.
- Added the tour number to the information on the scoreboard.
- Fixed a false positive for the achievement "Clockwork Carnage".
- Added a new command "
bot_hurt".- Parameters
-name [bot name],-team [red/blue/all],-damage [amount].
- Parameters
- Fixed a bug where players could only buy 1 upgrade at a time from the Upgrade Station.
- Fixed a bug where the Victory dialog would sometimes show during incorrect times.
- Added two tours of duty, each with new unique loot:
- Operation Oil Spill, with 6 intermediate skill missions.
- Operation Gear Grinder, with 3 expert skill missions.
- If a player connects to a MvM game through matchmaking and loses their connection, their spot will be held for a brief duration and they will be given a chance to reconnect.
- After victory on a Mann Up server, the players will be put into a lobby together.
- Improved matchmaking searching status screen.
- Balance changes:
- Explosive Headshots
- Damage is now 150 regardless of upgrade level.
- Damage is done in one tick instead of the previous six.
- Added a slowing effect based on upgrade level (50%-80% slow, 2-4 second duration).
- Radius still scales with upgrade level (unchanged).
- Marked For Death duration reduced to 7 seconds from 15 seconds when the target is a giant robot.
- Reduced the "effect bar recharge rate increased" upgrade from 20% increments with an 80% cap to 15% increments with a 60% cap.
- Explosive Headshots
- Added a penalty system to deter players from repeatedly abandoning Mann Up games
- Corrected the respawn time for the Mannslaughter mission
- Updated MissionCycle behavior. Servers will always cycle to a mission listed in the MissionCycle file.
External links
| ||||||||||||||||||||||||||||||||||||||
