Reverse MvM Beginners Guide
Reverse MvM is a combination of custom popfile keyvalues that flips the teams and win conditions. Instead of defending against hordes of robots, players are spawned on the blue team and must fight their way to the hatch and deliver the bomb. Designing missions around this concept can be very complex and requires heavy usage of Point Templates. It is highly recommended that you have a basic understanding of hammer and map logic beforehand, as well as a deep understanding of our popfile mods.
An example popfile for Rottenburg can be found here. Red robot template files can be found here.
Maps
While the majority of existing mvm maps are suitable, longer and more complex maps are best for reverse. Bigrock, Mannhattan, and Rottenburg are examples of valve maps where it is relatively easy to stop players from getting to the hatch quickly, due to their layouts and/or overall length. Shorter and more open-ended maps such as Decoy, Mannworks, and Coaltown, are still completely valid options, however they will require ample counter-measures to avoid players bypassing every threat and camping at the hatch.
Gate Maps
Maps with gates are very useful for structuring your waves at the cost of simplicity. You can enable/disable bot spawns and connect your own custom logic to the outputs of the maps trigger_timer_door entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.
Engineer Teleporter Types
There are 2 separate types of engineer teleporters: regular teleporters, and engineer bot teleporters. Engineer bot teleporters act as a new spawn point, and will instantly teleport players to an exit on respawn with no entrance required. It is recommended to only use bot style teleporters in long maps that do not use gates, combining gates with this feature can cause balance problems as well as confusion for newer players.
As of 12/07/2021, The feature to place engineer-bot style teleporters is incredibly buggy. Only vanilla teleporters and teleporters built by actual engineer-bots are currently bug-free.
Placing Spawns
The best red spawn locations are not immediately noticeable and let bots navigate the map to hunt down players as efficiently as possible, regardless of the bomb path.
Spawning bots in easy to notice areas can break the illusion of RED having control over the map, and should be avoided unless done as a deliberate design choice. On the flipside, spawning bots miles away from the player or making them take needlessly long routes to join the fight is equally problematic and will ruin wave pacing. It’s important to strike a balance between these two extremes.
It is best to divide your map into distinct areas and place spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 areas that players need to progress through before deploying the bomb: The front, the church tower/bridge area, and the hatch. Spawn timings, bot types, and accompanying sub-waves, can then be adjusted depending on how long you want players to spend in each individual area of the map.
Friendly Robots
When adding friendly bots to your mission, you should balance them to be considerably weaker than the upcoming red robots. If your friendly bots are strong enough to beat the mission without player interference in a reasonable amount of time, players won't feel very engaged. A good system for picking good friendly robots is to pick the less dangerous variant of bots you are using in your waves. If a certain sub-wave uses crit rapid fire giant soldiers on red, send out normal giant soldiers on blu. This way, blu robots are at an inherent disadvantage and need players to assist them to progress.
It is recommended that VIP escorting objectives be very forgiving unless you specifically force the bot to only follow players. Do note that players are able to interact with bots in several ways. Heavies can heal them with lunchbox items, medics can uber them, soldiers can whip them, and bots will take nearby active teleporters. All of these features can be modified or disabled.
Lose Condition
In order to fail the wave when players lose, you will need to add your own game_round_win entity like so:
PointTemplates [$SIGSEGV]
{
LoseRelay
{
NoFixup 1
game_round_win //ignore this
{
"TeamNum" "2"
"targetname" "bots_win_red"
"switch_teams" "0"
"force_map_reset" "1"
"classname" "game_round_win"
}
logic_relay //trigger this
{
"targetname" "redwin_relay"
"OnTrigger" "bots_win_red,RoundWin,,0,-1"
}
}
}
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.
Preparing Your Map
Because many maps were not designed for this mode, it is recommended that you go through your map of choice and remove unwanted map entities, cover up holes in bot spawn with prop_dynamic, and generally prepare your map beforehand. For the bulk of custom logic, a logic_auto in combination with AddOutputs is recommended, as it will instantly trigger when a new wave loads. For example, if your mission gives the blue team infinite ammo, it wouldn't hurt to remove redundant ammo packs from the map like so
logic_auto
{
"origin" "0 0 0"
"targetname" "mainrelay"
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"
}
Many maps do not have gates or doors blocking the blue spawn area and will require you to add your own blockades. This can be as simple as placing a prop in front of the spawn and killing it when the wave starts, or as complex as creating a moving gate using func_tracktrain. For our example, we'll be using a func_forcefield, an invisible wall which can be disabled and enabled when wave start/end relays trigger using some basic AddOutputs
PointTemplates [$SIGSEGV]
{
corelogic
{
NoFixup 1
logic_auto
{
"targetname" "mainrelay"
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"
}
}
forcefield
{
NoFixup 1
func_forcefield
{
"targetname" "spawnbarrier"
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn
"angles" "0 90 0"
"rendermode" "10" //10 = don't render
"TeamNum" "2" //2 for red, 3 for blu
"mins" "-300 -300 -300"
"maxs" "300 300 300" //300x300 hu cube
}
}
}
* is a wildcard that can be used to reference multiple entities with the same prefix. It is only limited to suffixes (*_start_relay* would not work)
For more complex maps with a lot of entities, it may be beneficial to strip away certain decorative elements of the map to avoid hitting the edict limit while the wave is active (such as move_rope and keyframe_rope).
Upgrade Station
Upgrade stations will need to be placed in blue spawns. Do your best to strategically place these in areas that don't interfere with spawn points and cover up holes in the map if there are any. If your map has particularly cramped spawns, it might be wise to use a smaller model than the traditional one to signify an upgrade station, such as a resupply locker or a small weapons case. Do note the "mins" and "maxs" values for the func_upgradestation entity will need to be adjusted accordingly
station
{
NoFixup 1
func_upgradestation //upgrade station entity
{
"mins" "-105 -100 0"
"maxs" "105 100 242"
"solid" "0"
}
prop_dynamic //blu upgrade station model, can be found on potato servers
{
"targetname" "upgradestation"
"model" "models\props_mvm\mvm_upgrade_blu.mdl"
}
prop_dynamic //invisible collision prop
{
"targetname" "shopcollision"
"angles" "0 -90 0"
"model" "models/props_vehicles/train_flatcar_container.mdl"
"rendermode" "10" //invisible
"solid" "6" //solid collisions
}
}