Mann Vs Machine

This is a draft page. It is a work in progress open to editing by anyone.
Remember to check for any notes left by the tagger at this article's talk page.

Mann Vs Machine is a cooperative game mode for  Team Fortress 2 involving players protecting a vital asset or location from waves of robotic clones of the mercenaries or other kinds of robots!

Note: If you wish to learn more about the mechanics and features, check out the Wiki page

Community Knowledge & Hosting Potato.tf; a long standing Mann Vs Machine community site that provides a Discord server for networking and communication with other creators, hosts testing servers, etc. SigMod Wiki; community made documentation and findings for mission making, and documentation for custom extensions Robot Icon Repository; custom robot icon repository that you can download from Map Entities info_player_teamspawns; spawn positions for the players (RED team), and robots (BLU team) func_upgradestation; when entered shows the Upgrade menu Logical Entities; hologram visibility, navigation influence, bomb hatch logic, etc. Flag Based Goal System: func_capturezone entity acting as the bomb hatch the players must defend item_teamflag entity acting as bombs the robots can carry and deploy on the bomb hatch func_flagdetectionzone; any bots carrying a bomb that interact with this trigger will inform players about this with announcements and alarms tf_logic_mann_vs_machine; this entity marks the map as being for the Mann vs. Machine game mode game_round_win; in this case specifically used to indicate when the robots successfully blow up the hatch tf_gamerules; handles team roles, and generic game mode logic team_round_timer; most likely to ensure the game mode references the timer and set to infinite time Confirm:Do we require "team_round_timer" and/or "tf_gamerules" to run Mann Vs Machine maps properly? Navigation Mesh Related Entities tf_point_nav_interface; this entity (usually named "nav_refresh") allows mappers or mission writers to influence the navigation mesh, specifically recalculating it during runtime Func_nav_avoid Func_nav_blocker func_nav_prerequisite Func_nav_prefer Robot Related Entities point_populator_interface; this entity (usually named "pop_interface") allows mappers or mission writers to influence robot spawning, EventChangeAttributes, and setting the default EventChangeAttributes trigger_bot_tag; any bots that interact with this trigger can be given tags, or have tags be removed from them filter_tf_bot_has_tag path_tracks; for Tank spawning and navigation Bug:If there are no path_tracks present in the map, the game will crash func_tfbot_hint; Sniper hints Engineer Hints: bot_hint_engineer_nests bot_hint_sentrygun bot_hint_teleporter_exit

Robots Population Files; these text files contain information relating to waves, spawns, templates, etc. TFBot Technicalities Class Based Robot Variants Scout-Bots Soldier-Bots Pyro-Bots Demo-Bots Heavy-Bots Engi-Bots Medic-Bots Sniper-Bots Spy-Bots Specialized Sentry Busters Tanks Submodes Valve's Submodes "Ironman" Mode Gateway Mode Community Submodes One Mann Army Mode Region Control Mode Development Content Embedding See also Category:Mann Vs Machine