Reverse MvM Beginners Guide

2021-07-22T14:53:33Z

Orinuse: missed one

Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule custom 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 [https://sigwiki.potatomvm.tf/index.php/Design_PointTemplate_with_hammer_map_editor Point Templates]. It is highly recommended that you have a basic understanding of hammer and map logic beforehand.

An example popfile for Rottenburg can be found [https://www.dropbox.com/s/iu84axj1r0vhg0y/mvm rottenburg reverse core logic.pop?dl=1rial mission here]

==Getting Started==
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 [https://developer.valvesoftware.com/wiki/Prop_dynamic prop_dynamic], and generally prepare your map beforehand. For the bulk of custom logic, a [https://developer.valvesoftware.com/wiki/Logic_auto logic_auto] in combination with [https://developer.valvesoftware.com/wiki/AddOutput 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 <syntaxhighlight lang="cpp">
logic_auto
{
"origin" "0 0 0"
"targetname" "mainrelay"
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"
}
</syntaxhighlight>

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 [https://developer.valvesoftware.com/wiki/Func_tracktrain func_tracktrain]. For our example, we'll be using a [https://developer.valvesoftware.com/wiki/Func_forcefield func_forcefield], an invisible wall which can be disabled and enabled when wave start/end relays trigger using some basic AddOutputs
<syntaxhighlight lang="cpp">
PointTemplates [$SIGSEGV]
{
corelogic
{
NoFixup 1
logic_auto
{
"origin" "0 0 0"
"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
{
"disablereceiveshadows" "0"
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn
"angles" "0 90 0"
"renderamt" "255"
"rendercolor" "255 255 255"
"renderfx" "0"
"rendermode" "10"
"TeamNum" "2"
"targetname" "spawnbarrier"
"mins" "-300 -300 -300"
"maxs" "300 300 300"
"StartDisabled" "0"
}
}
}
</syntaxhighlight>
''* is a [https://developer.valvesoftware.com/wiki/Wildcard wildcard] that can be used to reference multiple entities with the same prefix. It is only limited to prefixes (*_start_relay* would not work)''

''For more complex maps with a lot of entities, it may be beneficial to strip away unnecessary decorative elements of the map to avoid hitting the edict limit. move_rope and keyframe_rope for example can be safely removed if necessary.''

==Lose Condition==
In order to fail the wave when players lose, you will need to add your own game_round_win entity like so:

<syntaxhighlight lang="cpp">
PointTemplates [$SIGSEGV]
{
LoseRelay
{
NoFixup 1
game_round_win //ignore this
{
"origin" "0 0 0"
"TeamNum" "2"
"targetname" "bots_win_red"
"switch_teams" "0"
"force_map_reset" "1"
"classname" "game_round_win"
}
logic_relay //trigger this
{
"origin" "0 0 0"
"targetname" "redwin_relay"
"OnTrigger" "bots_win_red,RoundWin,,0,-1"
}
}
}
</syntaxhighlight>

It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.

Reverse MvM Beginners Guide

2021-07-22T14:51:25Z

Orinuse: /* Getting Started */ Attempt to remove "Pages with syntax highlighting errors" category

Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule custom 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 [https://sigwiki.potatomvm.tf/index.php/Design_PointTemplate_with_hammer_map_editor Point Templates]. It is highly recommended that you have a basic understanding of hammer and map logic beforehand.

An example popfile for Rottenburg can be found [https://www.dropbox.com/s/iu84axj1r0vhg0y/mvm rottenburg reverse core logic.pop?dl=1rial mission here]

==Getting Started==
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 [https://developer.valvesoftware.com/wiki/Prop_dynamic prop_dynamic], and generally prepare your map beforehand. For the bulk of custom logic, a [https://developer.valvesoftware.com/wiki/Logic_auto logic_auto] in combination with [https://developer.valvesoftware.com/wiki/AddOutput 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 <syntaxhighlight lang="cpp">
logic_auto
{
"origin" "0 0 0"
"targetname" "mainrelay"
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"
}
</syntaxhighlight>

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 [https://developer.valvesoftware.com/wiki/Func_tracktrain func_tracktrain]. For our example, we'll be using a [https://developer.valvesoftware.com/wiki/Func_forcefield func_forcefield], an invisible wall which can be disabled and enabled when wave start/end relays trigger using some basic AddOutputs
<syntaxhighlight lang="cpp">
PointTemplates [$SIGSEGV]
{
corelogic
{
NoFixup 1
logic_auto
{
"origin" "0 0 0"
"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
{
"disablereceiveshadows" "0"
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn
"angles" "0 90 0"
"renderamt" "255"
"rendercolor" "255 255 255"
"renderfx" "0"
"rendermode" "10"
"TeamNum" "2"
"targetname" "spawnbarrier"
"mins" "-300 -300 -300"
"maxs" "300 300 300"
"StartDisabled" "0"
}
}
}
</syntaxhighlight>
''* is a [https://developer.valvesoftware.com/wiki/Wildcard wildcard] that can be used to reference multiple entities with the same prefix. It is only limited to prefixes (*_start_relay* would not work)''

''For more complex maps with a lot of entities, it may be beneficial to strip away unnecessary decorative elements of the map to avoid hitting the edict limit. move_rope and keyframe_rope for example can be safely removed if necessary.''

==Lose Condition==
In order to fail the wave when players lose, you will need to add your own game_round_win entity like so:

<syntaxhighlight>
PointTemplates [$SIGSEGV]
{
LoseRelay
{
NoFixup 1
game_round_win //ignore this
{
"origin" "0 0 0"
"TeamNum" "2"
"targetname" "bots_win_red"
"switch_teams" "0"
"force_map_reset" "1"
"classname" "game_round_win"
}
logic_relay //trigger this
{
"origin" "0 0 0"
"targetname" "redwin_relay"
"OnTrigger" "bots_win_red,RoundWin,,0,-1"
}
}
}
</syntaxhighlight>

It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.

SigMod - User contributions [en-gb]

Reverse MvM Beginners Guide

Reverse MvM Beginners Guide