https://sigwiki.potato.tf/api.php?action=feedcontributions&feedformat=atom&user=192.168.1.218SigMod - User contributions [en-gb]2026-06-11T13:22:08ZUser contributionsMediaWiki 1.40.0https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=1497Reverse MvM Beginners Guide2022-02-18T05:56:23Z<p>192.168.1.218: /* Placing Spawns */</p>
<hr />
<div>Reverse MvM is a combination of [https://sigwiki.potato.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>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.</s>''<br />
<br />
<sup>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.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
The best red spawns aren’t obvious and let bots quickly navigate the map to hunt down players as efficiently as possible, regardless of the bomb path. <br />
<br />
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<br />
<br />
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 distinct areas that players need to progress through before deploying the bomb: The front, the church tower/bridge area, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map. <br />
<br />
== Friendly Robots ==<br />
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. <br />
<br />
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. <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"targetname" "spawnbarrier"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"rendermode" "10" //invisible<br />
"solid" "6" //solid collisions<br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=1496Reverse MvM Beginners Guide2022-02-18T04:50:06Z<p>192.168.1.218: /* Placing Spawns */</p>
<hr />
<div>Reverse MvM is a combination of [https://sigwiki.potato.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>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.</s>''<br />
<br />
<sup>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.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas and placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to progress through before deploying the bomb: The front, the church tower/bridge area, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player in order to ensure they don't make too much progress too quickly, then waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this and place your spawns behind cover along the main bot path, letting bots navigate their way to the player themselves. This serves multiple purposes: <br />
<br />
* New sub-waves can be seamlessly blended into old ones easily, rather than abruptly ending and having new bots appear out of thin air. <br />
* It allows red bots to spread around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. <br />
* It better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
* If bots stray too far from players, they will not cause the wave to hang if <code>WaitForAllSpawned</code> is used instead of <code>WaitForAllDead</code> <br />
* Due to the semi-random behavior of bots when navigating the map, different playthroughs will have minor pacing changes that can improve replay value <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. <br />
<br />
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. <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=1495Reverse MvM Beginners Guide2022-02-18T02:35:01Z<p>192.168.1.218: /* Placing Spawns */</p>
<hr />
<div>Reverse MvM is a combination of [https://sigwiki.potato.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>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.</s>''<br />
<br />
<sup>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.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player in order to ensure players don't make too much progress too quickly, then waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this and place your spawns behind cover along the main bot path, letting bots navigate their way to the player themselves. This serves multiple purposes: <br />
<br />
* New sub-waves can be seamlessly blended into old ones easily, rather than abruptly ending and having new bots appear out of thin air. <br />
* It allows red bots to spread around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. <br />
* It better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
* If bots stray too far from players, they will not cause the wave to hang if <code>WaitForAllSpawned</code> is used instead of <code>WaitForAllDead</code> <br />
* Letting bots swarm the map and not forcing fights onto players improves replay value and is less formulaic <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CPasstimeGun&diff=1494CPasstimeGun2022-02-17T03:26:41Z<p>192.168.1.218: </p>
<hr />
<div>== Overview ==<br />
...<br />
<br />
'''Source location : /game/shared/tf/tf_weapon_passtime_gun.h'''<br />
<br />
'''Linked entity : [https://developer.valvesoftware.com/wiki/tf_weapon_passtime_gun tf_weapon_passtime_gun]'''<br />
<br />
==[[Classes|Class Structure]]==<br />
*'''[[CBaseEntity]]'''<br />
**'''[[CBaseAnimating]]'''<br />
***'''[[CEconEntity]]'''<br />
****'''[[CBaseCombatWeapon]]'''<br />
*****'''[[CTFWeaponBase]]'''<br />
******'''CPasstimeGun'''<br />
<br />
== SendProps ==<br />
{| class="wikitable sortable mw-collapsible mw-collapsed" style="margin: 0 auto; width: 100%; padding: 0;"<br />
|+CPasstimeGun <br />
! style="width: 50%; background-color: #303030; color: white" |Name <br />
! style="width: 15%; background-color: #303030; color: white" |Type<br />
! style="width: 35%; background-color: #303030; color: white" |Description<br />
|-<br />
| style="width: 50%;" |'''m_eThrowState'''<br />
| style="width: 15%;" |Integer<br />
| style="width: 35%;" |<br />
|-<br />
| style="width: 50%;" |'''m_fChargeBeginTime'''<br />
| style="width: 15%;" |Float<br />
| style="width: 35%;" |<br />
|}</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=1359Reverse MvM Beginners Guide2022-02-14T19:53:40Z<p>192.168.1.218: /* Friendly Robots */</p>
<hr />
<div>Reverse MvM is a combination of [https://sigwiki.potato.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>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.</s>''<br />
<br />
<sup>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.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=1358Reverse MvM Beginners Guide2022-02-14T19:53:06Z<p>192.168.1.218: /* Friendly Robots */</p>
<hr />
<div>Reverse MvM is a combination of [https://sigwiki.potato.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>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.</s>''<br />
<br />
<sup>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.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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 any lose conditions built around VIP escorting objectives be very forgiving <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=1357Reverse MvM Beginners Guide2022-02-14T19:51:10Z<p>192.168.1.218: /* Engineer Teleporter Types */</p>
<hr />
<div>Reverse MvM is a combination of [https://sigwiki.potato.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>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.</s>''<br />
<br />
<sup>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.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives be very forgiving <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=WaveSchedule&diff=1356WaveSchedule2022-02-14T19:49:42Z<p>192.168.1.218: /* Reverse MvM */</p>
<hr />
<div>==Precache==<br />
<syntaxhighlight><br />
PrecacheSound "weapons/rocket_directhit_shoot_crit.wav" [$SIGSEGV] //If your mission contains custom sounds that are used by pointtemplate entities or sound overrides, you must include those sounds with precachesound<br />
PrecacheScriptSound "Weapon_RPG.Single" [$SIGSEGV] //Sound script version of precache sound<br />
PrecacheModel "models/props_soho/bookstand002.mdl" [$SIGSEGV] //Precaches model. This might be required in some circumstances, such as "custom projectile model" attribute, or prop with custom model<br />
PrecacheSentenceFile "scripts/sentences.txt" [$SIGSEGV] //Precache sentence file<br />
PrecacheDecal "decals/tscorch" [$SIGSEGV] //Precache decal file<br />
PrecacheGeneric "" [$SIGSEGV] //Precache generic file<br />
PrecacheParticle "env_fire_large_smoke" [$SIGSEGV] //Precache particle<br />
</syntaxhighlight>Precaching helps to ensure that the content used in the mission will be loaded propely and downloaded to the clients<br />
<br />
== Halloween ==<br />
ForceHoliday 2 [$SIGSEGV] //Enforces Halloween mode, but does not enable wave 666 and zombie bots<br />
NoThrillerTaunt 1 [$SIGSEGV] // No thriller taunt in halloween (default: 0)<br />
NoCritPumpkin 1 [$SIGSEGV] // No crit pumpkin on player death drop in halloween (default: 0)<br />
NoHolidayPickups 1 [$SIGSEGV] // If set, pickups will remain with default models (default: 0)<br />
ZombiesNoWave666 1 [$SIGSEGV] // If set to 1, the game will not display wave 666 when EventPopFile is set (default: 0)<br />
<br />
BotsDropSpells 1 [$SIGSEGV] //If set, bots will drop spells<br />
GiantsDropRareSpells 1 [$SIGSEGV] //If set, giants will drop rare spells rather than common<br />
SpellDropRateCommon 0.5 [$SIGSEGV] //Drop chance for common spell books, from 0 to 1<br />
SpellDropRateGiant 0.5 [$SIGSEGV] //Drop chance for rare spell books, from 0 to 1<br />
SpellDropForBotsInTeam Blue [$SIGSEGV] // When set, drop spells only if bots are from Red/Blue team<br />
SpellBookNormalRoll [$SIGSEGV] // Override spell roll. The value specifies how many spell charges to give. You can duplicate spells to increase their roll chance<br />
{<br />
"Healing Aura" 3<br />
"Fireball" 3<br />
"Ball O' Bats" 2<br />
"Healing Aura" 3<br />
"Pumpkin MIRV" 1 <br />
"Superjump" 4<br />
"Invisibility" 2<br />
"Teleport" 4<br />
"Tesla Bolt" 3<br />
"Minify" 1<br />
"Meteor Shower" 5<br />
"Summon Monoculus" 1<br />
"Summon Skeletons" 4<br />
}<br />
SpellBookRareRoll [$SIGSEGV] // Override spell roll. The value specifies how many spell charges to give. You can duplicate spells to increase their roll chance<br />
{<br />
"Healing Aura" 3<br />
"Fireball" 3<br />
"Ball O' Bats" 2<br />
"Healing Aura" 3<br />
"Pumpkin MIRV" 1 <br />
"Superjump" 4<br />
"Invisibility" 2<br />
"Teleport" 4<br />
"Tesla Bolt" 3<br />
"Minify" 1<br />
"Meteor Shower" 5<br />
"Summon Monoculus" 1<br />
"Summon Skeletons" 4<br />
}<br />
==Reverse MvM==<br />
ReverseWinConditions 1 [$SIGSEGV] //Player team wins if bots deliver the bomb.<br />
SetCreditTeam 3 [$SIGSEGV] //Sets which team can pickup money. Set to 3 to allow blu team to collect money instead<br />
BluHumanFlagCapture 1 [$SIGSEGV] //Can blu humans capture the flag<br />
BluHumanFlagPickup 1 [$SIGSEGV] //Can blu humans pickup flags<br />
BluHumanInfiniteAmmo 0 [$SIGSEGV] //Enable infinite ammo for blu humans (default: 1)<br />
BluHumanInfiniteCloak 1 [$SIGSEGV] //Enable infinite cloak for blu humans (default: 1)<br />
AllowJoinTeamBlueMax 4 [$SIGSEGV] //How many players can join the blue team<br />
AllowJoinTeamBlue 1 [$SIGSEGV] //If it is possible to join team blue<br />
HumansMustJoinTeam blue [$SIGSEGV] //Set to blue to force players join the blu team<br />
BluPlayersAreRobots 1 [$SIGSEGV] //If set, blu players use robot models<br />
BotTeleportUberDuration 2 [$SIGSEGV] // How long should uber last for robots exiting engineer bot teleporter (default: 5)<br />
BluHumanTeleportOnSpawn 1 [$SIGSEGV] // Should players get teleported to engineer bot teleport on spawn (default: 0)<br />
BluHumanBotTeleporter 1 [$SIGSEGV] // Should player teleporters teleport players and bots on spawn (default: 0)<br />
[[Category:Popfile Additions]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=1355Reverse MvM Beginners Guide2022-02-14T16:22:38Z<p>192.168.1.218: /* Upgrade Station */</p>
<hr />
<div>Reverse MvM is a combination of [https://sigwiki.potato.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>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.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives be very forgiving <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=1354Reverse MvM Beginners Guide2022-02-14T16:18:46Z<p>192.168.1.218: /* Engineer Teleporter Types */</p>
<hr />
<div>Reverse MvM is a combination of [https://sigwiki.potato.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>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.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives be very forgiving <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well. 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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=1353Reverse MvM Beginners Guide2022-02-14T16:16:48Z<p>192.168.1.218: </p>
<hr />
<div>Reverse MvM is a combination of [https://sigwiki.potato.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style teleporters is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives be very forgiving <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well. 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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CTFBaseProjectile&diff=1299CTFBaseProjectile2022-02-14T00:29:40Z<p>192.168.1.218: </p>
<hr />
<div>== Overview ==<br />
...<br />
<br />
'''Source location : ...'''<br />
<br />
'''Linked entity : ...'''<br />
<br />
==[[Classes|Class Structure]]==<br />
*'''[[CBaseEntity]]'''<br />
**'''[[CBaseAnimating]]'''<br />
***'''[[CBaseAnimatingOverlay]]'''<br />
****'''[[CBaseFlex]]'''<br />
*****'''[[CBaseCombatCharacter]]'''<br />
******'''[[CBasePlayer]]'''<br />
*******'''CTFPlayer'''<br />
<br />
== SendProps ==<br />
{| class="wikitable sortable mw-collapsible mw-collapsed" style="margin: 0 auto; width: 100%; padding: 0;"<br />
|+CTFBaseProjectile <br />
! style="width: 50%; background-color: #303030; color: white" |Name <br />
! style="width: 15%; background-color: #303030; color: white" |Type<br />
! style="width: 35%; background-color: #303030; color: white" |Description<br />
|-<br />
| style="width: 50%;" |'''m_vInitialVelocity'''<br />
| style="width: 15%;" |Vector<br />
| style="width: 35%;" |<br />
|-<br />
| style="width: 50%;" |'''m_hLauncher'''<br />
| style="width: 15%;" |Integer<br />
| style="width: 35%;" |<br />
|}<br />
<br />
== Entity DataMaps ==<br />
{| class="wikitable sortable mw-collapsible mw-collapsed" style="margin: 0 auto; width: 100%; padding: 0;<br />
|+CTFBaseProjectile <br />
! style="width: 50%; background-color: #303030; color: white" |Name <br />
! style="width: 15%; background-color: #303030; color: white" |Type<br />
! style="width: 35%; background-color: #303030; color: white" |Description<br />
|-<br />
| style="width: 50%;" |'''CTFBaseProjectileFlyThink'''<br />
| style="width: 15%;" |<br />
| style="width: 35%;" |<br />
|}</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CTFBaseProjectile&diff=1298CTFBaseProjectile2022-02-14T00:28:20Z<p>192.168.1.218: </p>
<hr />
<div>== Overview ==<br />
...<br />
<br />
'''Source location : ...'''<br />
<br />
'''Linked entity : ...'''<br />
<br />
==[[Classes|Class Structure]]==<br />
*'''[[CBaseEntity]]'''<br />
**'''[[CBaseAnimating]]'''<br />
***'''[[CBaseAnimatingOverlay]]'''<br />
****'''[[CBaseFlex]]'''<br />
*****'''[[CBaseCombatCharacter]]'''<br />
******'''[[CBasePlayer]]'''<br />
*******'''CTFPlayer'''<br />
<br />
== SendProps ==<br />
{| class="wikitable sortable mw-collapsible mw-collapsed" style="margin: 0 auto; width: 100%; padding: 0;"<br />
|+CTFBaseProjectile <br />
! style="width: 50%; background-color: #303030; color: white" |Name <br />
! style="width: 15%; background-color: #303030; color: white" |Type<br />
! style="width: 35%; background-color: #303030; color: white" |Description<br />
|-<br />
| style="width: 50%;" |'''m_vInitialVelocity'''<br />
| style="width: 15%;" |Vector<br />
| style="width: 35%;" |<br />
|-<br />
| style="width: 50%;" |'''m_hLauncher'''<br />
| style="width: 15%;" |Integer<br />
| style="width: 35%;" |<br />
|}<br />
<br />
== Entity DataMaps ==<br />
{| class="wikitable sortable mw-collapsible mw-collapsed" style="margin: 0 auto; width: 100%; padding: 0;<br />
|+CTFWeaponBaseMelee <br />
! style="width: 50%; background-color: #303030; color: white" |Name <br />
! style="width: 15%; background-color: #303030; color: white" |Type<br />
! style="width: 35%; background-color: #303030; color: white" |Description<br />
|-<br />
| style="width: 50%;" |'''CTFBaseProjectileFlyThink'''<br />
| style="width: 15%;" |<br />
| style="width: 35%;" |<br />
|}</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CBaseProjectile&diff=1275CBaseProjectile2022-02-13T23:18:23Z<p>192.168.1.218: </p>
<hr />
<div>== Overview ==<br />
...<br />
<br />
'''Source location : ...'''<br />
<br />
'''Linked entity : ...'''<br />
<br />
==[[Classes|Class Structure]]==<br />
*'''[[CBaseEntity]]'''<br />
**'''[[CBaseAnimating]]'''<br />
***'''[[CBaseAnimatingOverlay]]'''<br />
****'''[[CBaseFlex]]'''<br />
*****'''[[CBaseCombatCharacter]]'''<br />
******'''[[CBasePlayer]]'''<br />
*******'''CTFPlayer'''<br />
<br />
== SendProps ==<br />
{| class="wikitable sortable mw-collapsible mw-collapsed" style="margin: 0 auto; width: 100%; padding: 0;"<br />
|+CBaseProjectile <br />
! style="width: 50%; background-color: #303030; color: white" |Name <br />
! style="width: 15%; background-color: #303030; color: white" |Type<br />
! style="width: 35%; background-color: #303030; color: white" |Description<br />
|-<br />
| style="width: 50%;" |'''m_hOriginalLauncher'''<br />
| style="width: 15%;" |Integer<br />
| style="width: 35%;" |<br />
|}</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CTFTauntProp&diff=724CTFTauntProp2022-02-02T22:24:45Z<p>192.168.1.218: </p>
<hr />
<div>== Overview ==<br />
...<br />
<br />
'''Source location : ...'''<br />
<br />
'''Linked entity : ...'''<br />
<br />
==[[SendProps|Class Structure]]==<br />
*'''[[CBaseEntity]]'''<br />
**'''[[CBaseAnimating]]'''<br />
***'''[[CBaseAnimatingOverlay]]'''<br />
****'''[[CBaseFlex]]'''<br />
*****'''[[CBaseCombatCharacter]]'''<br />
******'''[[CBasePlayer]]'''<br />
*******'''CTFPlayer'''<br />
<br />
== SendProps ==<br />
{| class="wikitable sortable" style="margin: 0 auto; width: 100%; padding: 0;"<br />
|+CTFTauntProp <br />
! style="width: 50%; background-color: #303030; color: white" |Name <br />
! style="width: 15%; background-color: #303030; color: white" |Type<br />
! style="width: 35%; background-color: #303030; color: white" |Description<br />
|-<br />
| style="width: 50%;" |'''m_nFlagCaptures'''<br />
| style="width: 15%;" |Integer<br />
| style="width: 35%;" |<br />
|-<br />
| style="width: 50%;" |'''m_iRole'''<br />
| style="width: 15%;" |Integer<br />
| style="width: 35%;" |<br />
|-<br />
| style="width: 50%;" |'''team_object_array_element'''<br />
| style="width: 15%;" |Integer<br />
| style="width: 35%;" |<br />
|-<br />
| style="width: 50%;" |'''"team_object_array"'''<br />
| style="width: 15%;" |Array<br />
| style="width: 35%;" |<br />
|-<br />
| style="width: 50%;" |'''m_hLeader'''<br />
| style="width: 15%;" |Integer<br />
| style="width: 35%;" |<br />
|}</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CAI_BaseNPC&diff=666CAI BaseNPC2022-01-31T00:43:57Z<p>192.168.1.218: </p>
<hr />
<div>== Overview ==<br />
...<br />
<br />
'''Source Location: /game/server/ai_basenpc.h'''<br />
<br />
==[[SendProps|Class Structure]]==<br />
*'''[[CBaseEntity]]'''<br />
**'''[[CBaseAnimating]]'''<br />
***'''[[CBaseAnimatingOverlay]]'''<br />
****'''[[CBaseFlex]]'''<br />
*****'''[[CBaseCombatCharacter]]'''<br />
******'''CAI_BaseNPC'''<br />
<br />
== SendProps ==<br />
{| class="wikitable sortable" style="margin: 0 auto; width: 100%; padding: 0;"<br />
|+CAI_BaseNPC<br />
! style="width: 50%; background-color: #303030; color: white" |Name <br />
! style="width: 15%; background-color: #303030; color: white" |Type<br />
! style="width: 35%; background-color: #303030; color: white" |Description<br />
|-<br />
|'''m_lifeState'''<br />
|Integer<br />
|<br />
|-<br />
|'''m_bPerformAvoidance'''<br />
|Boolean<br />
|<br />
|-<br />
|'''m_bIsMoving'''<br />
|Boolean<br />
|<br />
|-<br />
|'''m_bFadeCorpse'''<br />
|Boolean<br />
|<br />
|-<br />
|'''m_iDeathPose'''<br />
|Integer<br />
|<br />
|-<br />
|'''m_iDeathFrame'''<br />
|Integer<br />
|<br />
|-<br />
|'''m_bSpeedModActive'''<br />
|Boolean<br />
|<br />
|-<br />
|'''m_iSpeedModRadius'''<br />
|Integer<br />
|<br />
|-<br />
|'''m_iSpeedModSpeed'''<br />
|Integer<br />
|<br />
|-<br />
|'''m_bImportanRagdoll'''<br />
|Boolean<br />
|<br />
|-<br />
|'''m_flTimePingEffect'''<br />
|Float<br />
|<br />
|}</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CAI_BaseNPC&diff=665CAI BaseNPC2022-01-31T00:42:51Z<p>192.168.1.218: </p>
<hr />
<div>== Overview ==<br />
Contains functionality common between NPCs and players.<br />
<br />
'''Source Location: /game/server/basecombatcharacter.h'''<br />
<br />
==[[SendProps|Class Structure]]==<br />
*'''[[CBaseEntity]]'''<br />
**'''[[CBaseAnimating]]'''<br />
***'''[[CBaseAnimatingOverlay]]'''<br />
****'''[[CBaseFlex]]'''<br />
*****'''CBaseCombatCharacter'''<br />
<br />
== SendProps ==<br />
{| class="wikitable sortable" style="margin: 0 auto; width: 100%; padding: 0;"<br />
|+CAI_BaseNPC<br />
! style="width: 50%; background-color: #303030; color: white" |Name <br />
! style="width: 15%; background-color: #303030; color: white" |Type<br />
! style="width: 35%; background-color: #303030; color: white" |Description<br />
|-<br />
|'''m_lifeState'''<br />
|Integer<br />
|<br />
|-<br />
|'''m_bPerformAvoidance'''<br />
|Boolean<br />
|<br />
|-<br />
|'''m_bIsMoving'''<br />
|Boolean<br />
|<br />
|-<br />
|'''m_bFadeCorpse'''<br />
|Boolean<br />
|<br />
|-<br />
|'''m_iDeathPose'''<br />
|Integer<br />
|<br />
|-<br />
|'''m_iDeathFrame'''<br />
|Integer<br />
|<br />
|-<br />
|'''m_bSpeedModActive'''<br />
|Boolean<br />
|<br />
|-<br />
|'''m_iSpeedModRadius'''<br />
|Integer<br />
|<br />
|-<br />
|'''m_iSpeedModSpeed'''<br />
|Integer<br />
|<br />
|-<br />
|'''m_bImportanRagdoll'''<br />
|Boolean<br />
|<br />
|-<br />
|'''m_flTimePingEffect'''<br />
|Float<br />
|<br />
|}</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CBaseAnimating&diff=628CBaseAnimating2022-01-30T04:59:23Z<p>192.168.1.218: </p>
<hr />
<div>== Overview ==<br />
All entities with models inherit from this class, even if they don't have any animations. <br />
<br />
'''Source Location : /game/server/baseanimating.h'''<br />
<br />
== Parent Structure ==<br />
<br />
* '''CBaseEntity'''<br />
** '''CBaseAnimating'''<br />
<br />
== SendProps ==<br />
'''CBaseAnimating'''<br />
<br />
'''m_nForceBone''' (CBaseAnimating)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecForce''' (CBaseAnimating)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSkin''' (CBaseAnimating)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nBody''' (CBaseAnimating)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nHitboxSet''' (CBaseAnimating)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flModelScale''' (CBaseAnimating)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flPoseParameter''' (CBaseAnimating)<br />
<br />
000 (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''001''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''002''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''003''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''004''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''005''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''006''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''007''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''008''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''009''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''010''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''011''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''012''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''013''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''014''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''015''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''016''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''017''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''018''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''019''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''020''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''021''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''022''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''023''' (m_flPoseParameter)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSequence''' (CBaseAnimating)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flPlaybackRate''' (CBaseAnimating)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flEncodedController''' (CBaseAnimating)<br />
<br />
000 (m_flEncodedController)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''001''' (m_flEncodedController)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''002''' (m_flEncodedController)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''003''' (m_flEncodedController)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bClientSideAnimation''' (CBaseAnimating)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bClientSideFrameReset''' (CBaseAnimating)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nNewSequenceParity''' (CBaseAnimating)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nResetEventsParity''' (CBaseAnimating)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nMuzzleFlashParity''' (CBaseAnimating)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hLightingOrigin''' (CBaseAnimating)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hLightingOriginRelative''' (CBaseAnimating)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''serveranimdata''' (CBaseAnimating)<br />
<br />
m_flCycle (serveranimdata)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_fadeMinDist''' (CBaseAnimating)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_fadeMaxDist''' (CBaseAnimating)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flFadeScale''' (CBaseAnimating)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CBaseEntity&diff=264CBaseEntity2022-01-30T01:39:27Z<p>192.168.1.218: </p>
<hr />
<div>== Overview ==<br />
The class from which all entity types derive from. The only exceptions to this are [https://wiki.alliedmods.net/TempEnts_(SourceMod_SDKTools) TempEnts], which are temporary entities that are too simple to warrant the overhead of inheriting from CBaseEntity.<br />
<br />
'''Source Location : /game/server/baseentity.h'''<br />
<br />
== SendProps ==<br />
<br />
===== '''CBaseEntity''' =====<br />
'''AnimTimeMustBeFirst''' (CBaseEntity)<br />
<br />
m_flAnimTime (AnimTimeMustBeFirst)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flSimulationTime''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
'''m_vecOrigin''' (CBaseEntity)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
The local origin of the entity, which is it's position relative to the entity's parent. If the entity has no parent, the relative position from the global origin (0, 0, 0) is used.<br />
<br />
'''m_ubInterpolationFrame''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nModelIndex''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_Collision''' (CBaseEntity)<br />
<br />
m_vecMinsPreScaled (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMaxsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMins''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMaxs''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSolidType''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_usSolidFlags''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSurroundType''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_triggerBloat''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bUniformTriggerBloat''' (m_Collision)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMinsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMaxsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMins''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMaxs''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nRenderFX''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nRenderMode''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
https://developer.valvesoftware.com/wiki/Render_Modes<br />
<br />
'''m_fEffects''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_clrRender''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iTeamNum''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_CollisionGroup''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flElasticity''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flShadowCastDistance''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hOwnerEntity''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hEffectEntity''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''moveparent''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iParentAttachment''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''movetype''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''movecollide''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_angRotation''' (CBaseEntity)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iTextureFrameIndex''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''predictable_id''' (CBaseEntity)<br />
<br />
m_PredictableID (predictable_id)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bIsPlayerSimulated''' (predictable_id)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bSimulatedEveryTick''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bAnimatedEveryTick''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bAlternateSorting''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nModelIndexOverrides''' (CBaseEntity)<br />
<br />
'''000''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''001''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''002''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''003''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CBaseEntity&diff=263CBaseEntity2022-01-30T01:38:11Z<p>192.168.1.218: Undo revision 262 by 192.168.1.218 (talk)</p>
<hr />
<div>== Overview ==<br />
The class from which all entity types derive from. The only exceptions to this are [https://wiki.alliedmods.net/TempEnts_(SourceMod_SDKTools) TempEnts], which are temporary entities that are too simple to warrant the overhead of inheriting from CBaseEntity.<br />
<br />
'''Source Location : /game/server/baseentity.h'''<br />
<br />
== SendProps ==<br />
<br />
===== '''CBaseEntity''' =====<br />
'''AnimTimeMustBeFirst''' (CBaseEntity)<br />
<br />
'''m_flAnimTime''' (AnimTimeMustBeFirst)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flSimulationTime''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecOrigin''' (CBaseEntity)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
The local origin of the entity, which is it's position relative to the entity's parent. If the entity has no parent, the relative position from the global origin (0, 0, 0) is used.<br />
<br />
'''m_ubInterpolationFrame''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nModelIndex''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_Collision''' (CBaseEntity)<br />
<br />
m_vecMinsPreScaled (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMaxsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMins''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMaxs''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSolidType''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_usSolidFlags''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSurroundType''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_triggerBloat''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bUniformTriggerBloat''' (m_Collision)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMinsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMaxsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMins''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMaxs''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nRenderFX''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nRenderMode''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
https://developer.valvesoftware.com/wiki/Render_Modes<br />
<br />
'''m_fEffects''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_clrRender''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iTeamNum''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_CollisionGroup''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flElasticity''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flShadowCastDistance''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hOwnerEntity''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hEffectEntity''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''moveparent''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iParentAttachment''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''movetype''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''movecollide''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_angRotation''' (CBaseEntity)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iTextureFrameIndex''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''predictable_id''' (CBaseEntity)<br />
<br />
m_PredictableID (predictable_id)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bIsPlayerSimulated''' (predictable_id)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bSimulatedEveryTick''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bAnimatedEveryTick''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bAlternateSorting''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nModelIndexOverrides''' (CBaseEntity)<br />
<br />
'''000''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''001''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''002''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''003''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CBaseEntity&diff=262CBaseEntity2022-01-30T01:37:34Z<p>192.168.1.218: /* CBaseEntity */</p>
<hr />
<div>== Overview ==<br />
The class from which all entity types derive from. The only exceptions to this are [https://wiki.alliedmods.net/TempEnts_(SourceMod_SDKTools) TempEnts], which are temporary entities that are too simple to warrant the overhead of inheriting from CBaseEntity.<br />
<br />
'''Source Location : /game/server/baseentity.h'''<br />
<br />
== SendProps ==<br />
<br />
===== '''CBaseEntity''' =====<br />
'''AnimTimeMustBeFirst''' (CBaseEntity)<br />
<br />
'''m_flAnimTime''' (AnimTimeMustBeFirst)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flSimulationTime''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecOrigin''' (CBaseEntity)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
The local origin of the entity, which is it's position relative to the entity's parent. If the entity has no parent, the relative position from the global origin (0, 0, 0) is used.<br />
<br />
'''m_ubInterpolationFrame''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nModelIndex''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_Collision''' (CBaseEntity)<br />
<br />
m_vecMinsPreScaled (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMaxsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMins''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMaxs''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSolidType''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_usSolidFlags''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSurroundType''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_triggerBloat''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bUniformTriggerBloat''' (m_Collision)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMinsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMaxsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMins''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMaxs''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nRenderFX''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nRenderMode''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
https://developer.valvesoftware.com/wiki/Render_Modes<br />
<br />
'''m_fEffects''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_clrRender''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iTeamNum''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_CollisionGroup''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flElasticity''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flShadowCastDistance''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hOwnerEntity''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hEffectEntity''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''moveparent''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iParentAttachment''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''movetype''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''movecollide''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_angRotation''' (CBaseEntity)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iTextureFrameIndex''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''predictable_id''' (CBaseEntity)<br />
<br />
m_PredictableID (predictable_id)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bIsPlayerSimulated''' (predictable_id)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bSimulatedEveryTick''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bAnimatedEveryTick''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bAlternateSorting''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nModelIndexOverrides''' (CBaseEntity)<br />
<br />
'''000''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''001''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''002''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''003''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CBaseEntity&diff=261CBaseEntity2022-01-30T01:25:31Z<p>192.168.1.218: </p>
<hr />
<div>== Overview ==<br />
The class from which all entity types derive from. The only exceptions to this are [https://wiki.alliedmods.net/TempEnts_(SourceMod_SDKTools) TempEnts], which are temporary entities that are too simple to warrant the overhead of inheriting from CBaseEntity.<br />
<br />
'''Source Location : /game/server/baseentity.h'''<br />
<br />
== SendProps ==<br />
<br />
===== '''CBaseEntity''' =====<br />
'''AnimTimeMustBeFirst''' (CBaseEntity)<br />
<br />
'''m_flAnimTime''' (AnimTimeMustBeFirst)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flSimulationTime''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecOrigin''' (CBaseEntity)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
The local origin of the entity, which is it's position relative to the entity's parent. If the entity has no parent, the relative position from the global origin (0, 0, 0) is used.<br />
<br />
'''m_ubInterpolationFrame''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nModelIndex''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_Collision''' (CBaseEntity)<br />
<br />
m_vecMinsPreScaled (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMaxsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMins''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMaxs''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSolidType''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_usSolidFlags''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSurroundType''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_triggerBloat''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bUniformTriggerBloat''' (m_Collision)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMinsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMaxsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMins''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMaxs''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nRenderFX''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nRenderMode''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
https://developer.valvesoftware.com/wiki/Render_Modes<br />
<br />
'''m_fEffects''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_clrRender''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iTeamNum''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_CollisionGroup''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flElasticity''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flShadowCastDistance''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hOwnerEntity''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hEffectEntity''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''moveparent''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iParentAttachment''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''movetype''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''movecollide''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_angRotation''' (CBaseEntity)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iTextureFrameIndex''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''predictable_id''' (CBaseEntity)<br />
<br />
m_PredictableID (predictable_id)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bIsPlayerSimulated''' (predictable_id)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bSimulatedEveryTick''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bAnimatedEveryTick''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bAlternateSorting''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nModelIndexOverrides''' (CBaseEntity)<br />
<br />
'''000''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''001''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''002''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''003''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CBaseEntity&diff=260CBaseEntity2022-01-30T01:00:05Z<p>192.168.1.218: </p>
<hr />
<div>== Overview ==<br />
The class from which all entity types derive from. The only exceptions to this are [https://wiki.alliedmods.net/TempEnts_(SourceMod_SDKTools) TempEnts], which are temporary entities that are too simple to warrant the overhead of inheriting from CBaseEntity.<br />
<br />
'''Source Location : /game/server/baseentity.h'''<br />
<br />
== SendProps ==<br />
<br />
===== '''CBaseEntity''' =====<br />
'''AnimTimeMustBeFirst''' (CBaseEntity)<br />
<br />
'''m_flAnimTime''' (AnimTimeMustBeFirst)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 255 (8 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flSimulationTime''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 255 (8 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecOrigin''' (CBaseEntity)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_ubInterpolationFrame''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 3 (2 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nModelIndex''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: -4096 - 4095 (13 bits signed)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_Collision''' (CBaseEntity)<br />
<br />
m_vecMinsPreScaled (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMaxsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMins''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMaxs''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSolidType''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 7 (3 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_usSolidFlags''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 1023 (10 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSurroundType''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 7 (3 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_triggerBloat''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 255 (8 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bUniformTriggerBloat''' (m_Collision)<br />
<br />
Type: boolean<br />
<br />
Range: 0 - 1 (1 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMinsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMaxsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMins''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMaxs''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nRenderFX''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 255 (8 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nRenderMode''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 255 (8 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_fEffects''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 1023 (10 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_clrRender''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 4294967295 (32 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iTeamNum''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: -32 - 31 (6 bits signed)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_CollisionGroup''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 31 (5 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flElasticity''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flShadowCastDistance''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hOwnerEntity''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 2097151 (21 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hEffectEntity''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 2097151 (21 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''moveparent''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 2097151 (21 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iParentAttachment''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 63 (6 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''movetype''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 15 (4 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''movecollide''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 7 (3 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_angRotation''' (CBaseEntity)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iTextureFrameIndex''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 255 (8 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''predictable_id''' (CBaseEntity)<br />
<br />
m_PredictableID (predictable_id)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 2147483647 (31 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bIsPlayerSimulated''' (predictable_id)<br />
<br />
Type: boolean<br />
<br />
Range: 0 - 1 (1 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bSimulatedEveryTick''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Range: 0 - 1 (1 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bAnimatedEveryTick''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Range: 0 - 1 (1 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bAlternateSorting''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Range: 0 - 1 (1 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nModelIndexOverrides''' (CBaseEntity)<br />
<br />
'''000''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Range: -4096 - 4095 (13 bits signed)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''001''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Range: -4096 - 4095 (13 bits signed)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''002''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Range: -4096 - 4095 (13 bits signed)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''003''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Range: -4096 - 4095 (13 bits signed)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Classes&diff=259Classes2022-01-30T00:54:53Z<p>192.168.1.218: </p>
<hr />
<div>== Class Parent Hierarchy ==<br />
<br />
* '''[[CBaseEntity]]'''<br />
** '''CBaseAnimating''' <small><sub>(CBaseEntity)</sub></small><br />
*** '''CBaseAnimatingOverlay''' <sub><small>(CBaseAnimating)</small></sub><br />
**** '''CEconEntity''' <sub><small>(CBaseAnimatingOverlay)</small></sub><br />
***** '''CBaseAttributableItem''' <sub><small>(CEconEntity)</small></sub><br />
***** '''CBaseCombatWeapon''' <sub><small>(CEconEntity)</small></sub><br />
****** '''CTFWeaponBase''' <sub><small>(CBaseCombatWeapon)</small></sub><br />
******* '''CPasstimeGun''' <sub><small>(CTFWeaponBase)</small></sub><br />
******* '''CTFWeaponBaseMelee''' <sub><small>(CTFWeaponBase)</small></sub><br />
******** '''CTFBat''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
********* '''CTFBat_Fish''' <sub><small>(CTFBat)</small></sub><br />
********* '''CTFBat_Wood''' <sub><small>(CTFBat)</small></sub><br />
********** '''CTFBat_Giftwrap''' <sub><small>(CTFBat_Wood)</small></sub><br />
******** '''CTFBonesaw''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
******** '''CTFBreakableMelee''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
********* '''CTFBottle''' <sub><small>(CTFBreakableMelee)</small></sub><br />
********* '''CTFBreakableSign''' <sub><small>(CTFBreakableMelee)</small></sub><br />
*********'''CTFStickBomb''' <sub><small>(CTFBreakableMelee)</small></sub><br />
******** '''CTFBuffItem''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
*********'''CTFParachute''' <sub><small>(CTFBuffItem)</small></sub><br />
**********'''CTFParachute_Primary''' <sub><small>(CTFParachute)</small></sub><br />
**********'''CTFParachute_Secondary''' <sub><small>(CTFParachute)</small></sub><br />
******** '''CTFClub''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
******** '''CTFFireAxe''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
********'''CTFFists''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
********'''CTFKatana''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
********'''CTFKnife''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
********'''CTFWrench''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
*********'''CTFRobotArm''' <sub><small>(CTFWrench)</small></sub><br />
********'''CTFRocketPack''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
********'''CTFShovel''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
********'''CTFSlap''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
********'''CTFSword''' <sub><small>(CTFWeaponBaseMelee)</small></sub><br />
******* '''CTFWeaponBaseGun''' <sub><small>(CTFWeaponBase)</small></sub><br />
******** '''CTFGrenadeLauncher''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
********* '''CTFCannon''' <sub><small>(CTFGrenadeLauncher)</small></sub><br />
******** '''CTFSMG''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
********* '''CTFChargedSMG''' <sub><small>(CTFSMG)</small></sub><br />
******** '''CTFJar''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
********* '''CTFCleaver''' <sub><small>(CTFJar)</small></sub><br />
*********'''CTFJarGas''' <sub><small>(CTFJar)</small></sub><br />
*********'''CTFJarMilk''' <sub><small>(CTFJar)</small></sub><br />
*********'''CTFThrowable''' <sub><small>(CTFJar)</small></sub><br />
**********'''CTFSpellBook''' <sub><small>(CTFThrowable)</small></sub><br />
******** '''CTFPipebombLauncher''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
********* '''CTFCompoundBow''' <sub><small>(CTFPipebombLauncher)</small></sub><br />
******** '''CTFRocketLauncher''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
********* '''CTFCrossbow''' <sub><small>(CTFRocketLauncher)</small></sub><br />
********* '''CTFRaygun''' <sub><small>(CTFRocketLauncher)</small></sub><br />
********** '''CTFDRGPomson''' <sub><small>(CTFRaygun''')'''</small></sub><br />
*********'''CTFGrapplingHook''' <sub><small>(CTFRocketLauncher)</small></sub><br />
*********'''CTFParticleCannon''' <sub><small>(CTFRocketLauncher)</small></sub><br />
*********'''CTFRocketLauncher_AirStrike''' <sub><small>(CTFRocketLauncher)</small></sub><br />
*********'''CTFRocketLauncher_DirectHit''' <sub><small>(CTFRocketLauncher)</small></sub><br />
*********'''CTFRocketLauncher_Mortar''' <sub><small>(CTFRocketLauncher)</small></sub><br />
********'''CTFFlameThrower''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
*********'''CTFWeaponFlameBall''' <sub><small>(CTFFlameThrower)</small></sub><br />
********'''CTFFlareGun''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
*********'''CTFFlareGun_Revenge''' <sub><small>(CTFFlareGun)</small></sub><br />
********'''CTFLaserPointer''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
********'''CTFMechanicalArm''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
********'''CTFMinigun''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
********'''CTFShotgun''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
*********'''CTFScatterGun''' <sub><small>(CTFShotgun)</small></sub><br />
**********'''CTFPEPBrawlerBlaster''' <sub><small>(CTFScatterGun)</small></sub><br />
**********'''CTFSodaPopper''' <sub><small>(CTFScatterGun)</small></sub><br />
*********'''CTFShotgun_HWG''' <sub><small>(CTFShotgun)</small></sub><br />
*********'''CTFShotgun_Pyro''' <sub><small>(CTFShotgun)</small></sub><br />
*********'''CTFShotgun_Revenge''' <sub><small>(CTFShotgun)</small></sub><br />
*********'''CTFShotgun_Soldier''' <sub><small>(CTFShotgun)</small></sub><br />
*********'''CTFShotgunBuildingRescue''' <sub><small>(CTFShotgun)</small></sub><br />
********'''CTFPistol''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
*********'''CTFPistol_Scout''' <sub><small>(CTFPistol)</small></sub><br />
**********'''CTFPistol_ScoutPrimary''' <sub><small>(CTFPistol_Scout)</small></sub><br />
**********'''CTFPIstol_ScoutSecondary''' <sub><small>(CTFPistol_Scout)</small></sub><br />
********'''CTFRevolver''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
********'''CTFSniperRifle''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
*********'''CTFSniperRifleClassic''' <sub><small>(CTFSniperRifle)</small></sub><br />
*********'''CTFSniperRifleDecap''' <sub><small>(CTFSniperRifle)</small></sub><br />
********'''CTFSyringeGun''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
********'''CWeaponMedigun''' <sub><small>(CTFWeaponBaseGun)</small></sub><br />
*******'''CTFLunchBox''' <sub><small>(CTFWeaponBase)</small></sub><br />
********'''CTFLunchBox_Drink''' <sub><small>(CTFLunchBox)</small></sub><br />
*******'''CTFWeaponBuilder''' <sub><small>(CTFWeaponBase)</small></sub><br />
********'''CTFWeaponSapper''' <sub><small>(CTFWeaponBuilder)</small></sub><br />
*******'''CTFWeaponInvis''' <sub><small>(CTFWeaponBase)</small></sub><br />
*******'''CTFWeaponPDA''' <sub><small>(CTFWeaponBase)</small></sub><br />
********'''CTFWeaponPDA_Engineer_Build <sub><small>(</small></sub>'''<sub><small>CTFWeaponPDA)</small></sub><br />
********'''CTFWeaponPDA_Engineer_Destroy''' <sub><small>(CTFWeaponPDA)</small></sub><br />
********'''CTFWeaponPDA_Spy''' <sub><small>(CTFWeaponPDA)</small></sub><br />
*******'''CWeaponIFMBase''' <sub><small>(CTFWeaponBase)</small></sub><br />
********'''CWeaponIFMBaseCamera''' <sub><small>(CTFWeaponIFMBase)</small></sub><br />
*********'''CWeaponIFMSteadyCam''' <sub><small>(CTFWeaponIFMBaseCamera)</small></sub><br />
***** '''CEconWearable''' <sub><small>(CEconEntity)</small></sub><br />
******'''CTFWearable''' <sub><small>(CEconWearable)</small></sub><br />
*******'''CTFPowerupBottle''' <sub><small>(CTFWearable)</small></sub><br />
*******'''CTFWearableCampaignItem''' <sub><small>(CTFWearable)</small></sub><br />
*******'''CTFWearableDemoShield''' <sub><small>(CTFWearable)</small></sub><br />
*******'''CTFWeaponPDAExpansion_Dispenser''' <sub><small>(CTFWearable)</small></sub><br />
*******'''CTFWeaponPDAExpansion_Teleporter''' <sub><small>(CTFWearable)</small></sub><br />
*******'''CTFWearableLevelableItem''' <sub><small>(CTFWearable)</small></sub><br />
*******'''CTFWearableRazorback''' <sub><small>(CTFWearable)</small></sub><br />
*******'''CTFWearableRobotArm''' <sub><small>(CTFWearable)</small></sub><br />
*******'''CTFWearableVM''' <sub><small>(CTFWearable)</small></sub><br />
******'''CTFWearableItem''' <sub><small>(CEconWearable)</small></sub><br />
****'''CTFRagdoll''' <small><sub>(CBaseAnimatingOverlay)</sub></small><br />
*** '''CBaseFlex''' <sub><small>(CBaseAnimating)</small></sub><br />
**** '''CBaseCombatCharacter''' <sub><small>(CBaseFlex)</small></sub><br />
***** '''CAI_BaseNPC''' <sub><small>(CBaseCombatCharacter)</small></sub><br />
***** '''CBaseObject''' <sub><small>(CBaseCombatCharacter)</small></sub><br />
****** '''CBaseObjectUpgrade''' <sub><small>(CBaseObject)</small></sub><br />
******* '''CObjectSapper''' <sub><small>(CBaseObjectUpgrade)</small></sub><br />
****** '''CObjectDispenser''' <sub><small>(CBaseObject)</small></sub><br />
******* '''CObjectCartDispenser''' <sub><small>(CObjectDispenser)</small></sub><br />
******* '''CPlayerDestructionDispenser''' <sub><small>(CObjectDispenser)</small></sub><br />
******* '''CRobotDispenser''' <sub><small>(CObjectDispenser)</small></sub><br />
****** '''CObjectSentrygun''' <sub><small>(CBaseObject)</small></sub><br />
****** '''CObjectTeleporter''' <sub><small>(CBaseObject)</small></sub><br />
***** '''CBasePlayer''' <sub><small>(CBaseCombatCharacter)</small></sub><br />
******'''CTFPlayer''' <sub><small>(CBasePlayer)</small></sub><br />
*****'''CTFTauntProp''' <sub><small>(CBaseCombatCharacter)</small></sub><br />
***** '''NextBotCombatCharacter''' <sub><small>(CBaseCombatCharacter)</small></sub><br />
****** '''CEyeballBoss''' <sub><small>(NextBotCombatCharacter)</small></sub><br />
****** '''CHeadlessHatman''' <sub><small>(NextBotCombatCharacter)</small></sub><br />
****** '''CMerasmus''' <sub><small>(NextBotCombatCharacter)</small></sub><br />
****** '''CTFBaseBoss''' <sub><small>(NextBotCombatCharacter)</small></sub><br />
*******'''CTFTankBoss''' <sub><small>(CTFBaseBoss)</small></sub><br />
******'''CTFRobotDestruction_Robot''' <sub><small>(NextBotCombatCharacter)</small></sub><br />
******'''CZombie''' <sub><small>(NextBotCombatCharacter)</small></sub><br />
*** '''CBaseProjectile''' <sub><small>(CBaseAnimating)</small></sub><br />
**** '''CBaseGrenade''' <sub><small>(CBaseProjectile)</small></sub><br />
***** '''CTFWeaponBaseGrenadeProj''' <sub><small>(CBaseGrenade)</small></sub><br />
****** '''CTFGrenadePipebombProjectile''' <sub><small>(CTFWeaponBaseGrenadeProj)</small></sub><br />
******* '''CTFStunball''' <sub><small>(CTFGrenadePipebombProjectile)</small></sub><br />
******** '''CTFBall_Ornament <sub><small>(CTFStunball)</small></sub>'''<br />
*******'''CTFProjectile_Jar''' <sub><small>(CTFGrenadePipebombProjectile)</small></sub><br />
********'''CTFProjectile_Cleaver''' <sub><small>(CTFProjectile_Jar)</small></sub><br />
********'''CTFProjectile_JarGas''' <sub><small>(CTFProjectile_Jar)</small></sub><br />
********'''CTFProjectile_JarMilk''' <sub><small>(CTFProjectile_Jar)</small></sub><br />
********'''CTFProjectile_SpellBats''' <sub><small>(CTFProjectile_Jar)</small></sub><br />
*********'''CTFProjectile_SpellKartBats''' <sub><small>(CTFProjectile_SpellBats)</small></sub><br />
*********'''CTFProjectile_SpellMeteorShower''' <sub><small>(CTFProjectile_SpellBats)</small></sub><br />
*********'''CTFProjectile_SpellMirv''' <sub><small>(CTFProjectile_SpellBats)</small></sub><br />
*********'''CTFProjectile_SpellPumpkin''' <sub><small>(CTFProjectile_SpellBats)</small></sub><br />
*********'''CTFProjectile_SpellSpawnBoss''' <sub><small>(CTFProjectile_SpellBats)</small></sub><br />
*********'''CTFProjectile_SpellSpawnHorde''' <sub><small>(CTFProjectile_SpellBats)</small></sub><br />
*********'''CTFProjectile_SpellSpawnZombie''' <sub><small>(CTFProjectile_SpellBats)</small></sub><br />
*********'''CTFProjectile_SpellTransposeTeleport''' <sub><small>(CTFProjectile_SpellBats)</small></sub><br />
********'''CTFProjectile_Throwable''' <sub><small>(CTFProjectile_Jar)</small></sub><br />
*********'''CTFProjectile_ThrowableBreadMonster''' <sub><small>(CTFProjectile_Throwable)</small></sub><br />
*********'''CTFProjectile_ThrowableBrick''' <sub><small>(CTFProjectile_Throwable)</small></sub><br />
*********'''CTFProjectile_ThrowableRepel''' <sub><small>(CTFProjectile_Throwable)</small></sub><br />
**** '''CTFBaseProjectile''' <sub><small>(CBaseProjectile)</small></sub><br />
***** '''CTFBaseRocket''' <sub><small>(CTFBaseProjectile)</small></sub><br />
******'''CTFFlameRocket''' <sub><small>(CTFBaseRocket)</small></sub><br />
******'''CTFProjectile_Arrow''' <sub><small>(CTFBaseRocket)</small></sub><br />
*******'''CTFProjectile_GrapplingHook''' <sub><small>(CTFProjectile_Arrow)</small></sub><br />
*******'''CTFProjectile_HealingBolt''' <sub><small>(CTFProjectile_Arrow)</small></sub><br />
******'''CTFProjectile_Rocket''' <sub><small>(CTFBaseRocket)</small></sub><br />
*******'''CTFProjectile_BallOfFire''' <sub><small>(CTFProjectile_Rocket)</small></sub><br />
*******'''CTFProjectile_MechanicalArmOrb''' <sub><small>(CTFProjectile_Rocket)</small></sub><br />
*******'''CTFProjectile_SentryRocket''' <sub><small>(CTFProjectile_Rocket)</small></sub><br />
*******'''CTFProjectile_SpellFireball''' <sub><small>(CTFProjectile_Rocket)</small></sub><br />
********'''CTFProjectile_SpellLightningOrb''' <sub><small>(CTFProjectile_SpellFireball)</small></sub><br />
********'''CTFProjectile_SpellKartOrb''' <sub><small>(CTFProjectile_SpellFireball)</small></sub><br />
******'''CTFProjectile_EnergyBall''' <sub><small>(CTFBaseRocket)</small></sub><br />
******'''CTFProjectile_Flare''' <sub><small>(CTFBaseRocket)</small></sub><br />
*****'''CTFProjectile_EnergyRing''' <sub><small>(CTFBaseProjectile)</small></sub><br />
****'''CTFWeaponBaseMerasmusGrenade''' <sub><small>(CBaseProjectile)</small></sub><br />
*** '''CHalloweenPickup''' <sub><small>(CBaseAnimating)</small></sub><br />
**** '''CBonusDuckPickup''' <sub><small>(CCHalloweenPickup)</small></sub><br />
**** '''CHalloweenGiftPickup''' <sub><small>(CCHalloweenPickup)</small></sub><br />
*** '''CCurrencyPack''' <sub><small>(CBaseAnimating)</small></sub><br />
**** '''CBonusPack''' <sub><small>(CCurrencyPack)</small></sub><br />
*** '''CBreakableProp''' <sub><small>(CBaseAnimating)</small></sub><br />
**** '''CDynamicProp''' <sub><small>(CBreakableProp)</small></sub><br />
***** '''CBasePropDoor''' <sub><small>(CDynamicProp)</small></sub><br />
***** '''CTFItem''' <sub><small>(CDynamicProp)</small></sub><br />
****** '''CCaptureFlag''' <sub><small>(CTFItem)</small></sub><br />
**** '''CPhysicsProp''' <sub><small>(CBreakableProp)</small></sub><br />
***** '''CPhysicsPropMultiplayer''' <sub><small>(CPhysicsProp)</small></sub><br />
*** '''CEnvParticleScript''' <sub><small>(CBaseAnimating)</small></sub><br />
*** '''CTeleportVortex''' <sub><small>(CBaseAnimating)</small></sub><br />
**** '''CHightower_TeleportVortex''' <sub><small>(CTeleportVortex)</small></sub><br />
*** '''CTFAmmoPack''' <sub><small>(CBaseAnimating)</small></sub><br />
*** '''CTFDroppedWeapon''' <sub><small>(CBaseAnimating)</small></sub><br />
***'''CTFGenericBomb''' <sub><small>(CBaseAnimating)</small></sub><br />
*** '''CMerasmusDancer''' <sub><small>(CBaseAnimating)</small></sub><br />
*** '''CPasstimeBall''' <sub><small>(CBaseAnimating)</small></sub><br />
*** '''CPhysMagnet''' <sub><small>(CBaseAnimating)</small></sub><br />
*** '''CPointCommentaryNode''' <sub><small>(CBaseAnimating)</small></sub><br />
*** '''CPropVehicleDriveable''' <sub><small>(CBaseAnimating)</small></sub><br />
*** '''CRagdollProp <sub><small>(CBaseAnimating)</small></sub>'''<br />
**** '''CRagdollPropAttached''' <sub><small>(CRagdollProp)</small></sub><br />
***'''CMedigunShield''' <sub><small>(CBaseAnimating)</small></sub><br />
***'''CPumpkinBomb''' <sub><small>(CBaseAnimating)</small></sub><br />
***'''CTFReviveMarker''' <sub><small>(CBaseAnimating)</small></sub><br />
***'''CWaterBullet''' <sub><small>(CBaseAnimating)</small></sub><br />
***'''CBaseViewModel''' <sub><small>(CBaseAnimating)</small></sub><br />
****'''CTFViewModel''' <sub><small>(CBaseViewModel)</small></sub><br />
***'''CFish''' <sub><small>(CBaseAnimating)</small></sub><br />
** '''CBaseDoor''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CBaseParticleEntity''' <sub><small>(CBaseEntity)</small></sub><br />
*** '''CEntityParticleTrail''' <sub><small>(CBaseParticleEntity)</small></sub><br />
*** '''CFireTrail''' <sub><small>(CBaseParticleEntity)</small></sub><br />
*** '''CSmokeStack''' <sub><small>(CBaseParticleEntity)</small></sub><br />
*** '''CSteamJet''' <sub><small>(CBaseParticleEntity)</small></sub><br />
***'''DustTrail''' <sub><small>(CBaseParticleEntity)</small></sub><br />
***'''MovieExplosion''' <sub><small>(CBaseParticleEntity)</small></sub><br />
***'''ParticleSmokeGrenade''' <sub><small>(CBaseParticleEntity)</small></sub><br />
***'''RocketTrail''' <sub><small>(CBaseParticleEntity)</small></sub><br />
***'''SmokeTrail''' <sub><small>(CBaseParticleEntity)</small></sub><br />
***'''SporeExplosion''' <sub><small>(CBaseParticleEntity)</small></sub><br />
***'''SporeTrail''' <sub><small>(CBaseParticleEntity)</small></sub><br />
***'''CParticleFire'''<br />
**'''CBaseTeamObjectiveResource''' <sub><small>(CBaseEntity)</small></sub><br />
***'''CTFObjectiveResource''' <sub><small>(CBaseTeamObjectiveResource)</small></sub><br />
**'''CBeam''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CBoneFollower''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CBreakableSurface''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CCaptureFlagReturnIcon''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CCaptureZone''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CDynamicLight''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CEmbers''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CEntityDissolve''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CEntityFlame''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CEnvProjectedTexture''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CEnvQuadraticBeam''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CEnvScreenEffect''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CEnvScreenOverlay''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CEnvTonemapController''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CFireSmoke''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CFunc_LOD''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CFuncAreaPortalWindow''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CFuncConveyor''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CFuncForceField''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CFuncLadder <sub><small>(CBaseEntity)</small></sub>'''<br />
** '''CFuncMonitor <sub><small>(CBaseEntity)</small></sub>'''<br />
** '''CFuncPasstimeGoal''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CFuncReflectiveGlass''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CFuncRespawnRoom''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CFuncRespawnRoomVisualizer''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CFuncRotating''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CFuncSmokeVolume''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CFuncTrackTrain''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CHalloweenSoulPack <sub><small>(CBaseEntity)</small></sub>'''<br />
** '''CHandleTest''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CInfoLadderDismount''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CInfoLightingRelative''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CMannVsMachineStats''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CMaterialModifyControl''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CParticlePerformanceMonitor''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CPhysBox''' <sub><small>(CBaseEntity)</small></sub><br />
*** '''CPhysBoxMultiplayer''' <sub><small>(CPhysBox)</small></sub><br />
** '''CPlasma''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CPointCamera''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CPoseController''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CPrecipitation''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CSlideshowDisplay''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CSniperDot''' <sub><small>(CBaseEntity)</small></sub><br />
*** '''CLaserDot''' <sub><small>(CSniperDot)</small></sub><br />
** '''CSprite''' <sub><small>(CBaseEntity)</small></sub><br />
*** '''CSpriteOriented''' <sub><small>(CSprite)</small></sub><br />
*** '''CSpriteTrail''' <sub><small>(CSprite)</small></sub><br />
** '''CSpotlightEnd''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CTeamTrainWatcher''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CTesla <sub><small>(CBaseEntity)</small></sub>'''<br />
** '''CTest_ProxyToggle_Networkable''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CTFBotHintEngineerNest''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CTFPointManager''' <sub><small>(CBaseEntity)</small></sub><br />
***'''CTFFlameManager''' <sub><small>(CTFPointManager)</small></sub><br />
***'''CTFGasManager''' <sub><small>(CTFPointManager)</small></sub><br />
**'''CTFGlow <sub><small>(CBaseEntity)</small></sub>'''<br />
**'''CTFHellZap''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CTFPasstimeLogic''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CVGuiScreen''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CVoteController''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CWorld''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CBonusRoundLogic''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CColorCorrection''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CEnvDetailController''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CEnvWind''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CFogController''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CFunc_Dust''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CFuncOccluder''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CGameRulesProxy''' <sub><small>(CBaseEntity)</small></sub><br />
*** '''CTeamplayRoundBasedRulesProxy''' <sub><small>(CGameRulesProxy)</small></sub><br />
****'''CTFGameRulesProxy''' <sub><small>(CTeamplayRoundBasedRulesProxy)</small></sub><br />
**'''CLightGlow''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CMonsterResource''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CParticleSystem''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CPlayerResource''' <sub><small>(CBaseEntity)</small></sub><br />
***'''CTFPlayerResource''' <sub><small>(CPlayerResource)</small></sub><br />
**'''CRagdollManager''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CRopeKeyFrame''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CShadowControl <sub><small>(CBaseEntity)</small></sub>'''<br />
**'''CSun''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CTeam''' <sub><small>(CBaseEntity)</small></sub><br />
***'''CTFTeam''' <sub><small>(CTeam)</small></sub><br />
**'''CTeamRoundTimer''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CTFMiniGame''' <sub><small>(CBaseEntity)</small></sub><br />
***'''CTFHalloweenMinigame''' <sub><small>(CTFMiniGame)</small></sub><br />
****'''CTFHalloweenMinigame_FallingPlatforms''' <sub><small>(CTFHalloweenMinigame)</small></sub><br />
**'''CTFMinigameLogic''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CTFRobotDestructionLogic''' <sub><small>(CBaseEntity)</small></sub><br />
***'''CTFPlayerDestructionLogic''' <sub><small>(CTFRobotDestructionLogic)</small></sub><br />
**'''CTFRobotDestruction_RobotGroup''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CTFRobotDestruction_RobotSpawn''' <sub><small>(CBaseEntity)</small></sub><br />
**'''CWaterLODControl''' <sub><small>(CBaseEntity)</small></sub><br />
* '''CBaseTempEntity'''<br />
** '''CTEParticleSystem''' <sub><small>(CBaseTempEntity)</small></sub><br />
*** '''CTEBloodStream''' <sub><small>(CTEParticleSystem)</small></sub><br />
*** '''CTEDust''' <sub><small>(CTEParticleSystem)</small></sub><br />
*** '''CTEExplosion''' <sub><small>(CTEParticleSystem)</small></sub><br />
*** '''CTEGaussExplosion''' <sub><small>(CTEParticleSystem)</small></sub><br />
*** '''CTELargeFunnel''' <sub><small>(CTEParticleSystem)</small></sub><br />
*** '''CTEShowLine''' <sub><small>(CTEParticleSystem)</small></sub><br />
*** '''CTESparks''' <sub><small>(CTEParticleSystem)</small></sub><br />
** '''CTEBreakModel''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEBSPDecal''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEBubbles''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEBubbleTrail''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEClientProjectile''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEDecal''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEDynamicLight''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEEffectDispatch''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEFizz''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEFootprintDecal''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEGlowSprite''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEImpact''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEKillPlayerAttachments''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEMuzzleFlash''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEPhysicsProp''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEPlayerDecal''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEProjectedDecal''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEShatterSurface''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTESmoke''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTESprite''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTESpriteSpray''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTETFBlood''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTETFExplosion''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTETFParticleEffect''' <sub><small>(CBaseTempEntity)</small></sub><br />
** '''CTEWorldDecal''' <sub><small>(CBaseTempEntity)</small></sub><br />
**'''CTEBaseBeam''' <sub><small>(CBaseTempEntity)</small></sub><br />
*** '''CTEBeamEntPoint''' <sub><small>(CTEBaseBeam)</small></sub><br />
*** '''CTEBeamEnts''' <sub><small>(CTEBaseBeam)</small></sub><br />
*** '''CTEBeamFollow''' <sub><small>(CTEBaseBeam)</small></sub><br />
*** '''CTEBeamLaser''' <sub><small>(CTEBaseBeam)</small></sub> <br />
*** '''CTEBeamPoints''' <sub><small>(CTEBaseBeam)</small></sub><br />
*** '''CTEBeamRIng''' <sub><small>(CTEBaseBeam)</small></sub><br />
*** '''CTEBeamRingPoint''' <sub><small>(CTEBaseBeam)</small></sub><br />
**'''CTEBeamSpline''' <sub><small>(CBaseTempEntity)</small></sub><br />
**'''CTEMetalSparks''' <sub><small>(CBaseTempEntity)</small></sub><br />
*** '''CTEArmorRicochet''' <sub><small>(CTEMetalSparks)</small></sub><br />
**'''CTEBloodSprite''' <sub><small>(CBaseTempEntity)</small></sub><br />
**'''CTEEnergySplash''' <sub><small>(CBaseTempEntity)</small></sub><br />
**'''CTEFireBullets''' <sub><small>(CBaseTempEntity)</small></sub><br />
**'''CTEPlayerAnimEvent''' <sub><small>(CBaseTempEntity)</small></sub><br />
*'''CColorCorrectionVolume''' <small><sub>(CBaseTrigger)</sub></small><br />
* '''CInfoOverlayAccessor''' <small><sub>(CPointEntity)</sub></small><br />
* '''CSceneEntity <small><sub>(CPointEntity)</sub></small>'''<br />
* '''CTestTraceline <small><sub>(CPointEntity)</sub></small>'''</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=CBaseEntity&diff=258CBaseEntity2022-01-30T00:51:22Z<p>192.168.1.218: </p>
<hr />
<div>== Overview ==<br />
The class from which all entity types derive from. The only exceptions to this are [https://wiki.alliedmods.net/TempEnts_(SourceMod_SDKTools) TempEnts], which are temporary entities that are too simple to warrant the overhead of inheriting from CBaseEntity.<br />
<br />
'''Source Location : /game/server/baseentity.h'''<br />
<br />
== SendProps ==<br />
<br />
===== '''CBaseEntity''' =====<br />
'''AnimTimeMustBeFirst''' (CBaseEntity)<br />
<br />
'''m_flAnimTime''' (AnimTimeMustBeFirst)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 255 (8 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flSimulationTime''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 255 (8 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecOrigin''' (CBaseEntity)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_ubInterpolationFrame''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 3 (2 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nModelIndex''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: -4096 - 4095 (13 bits signed)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_Collision''' (CBaseEntity)<br />
<br />
m_vecMinsPreScaled (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMaxsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMins''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecMaxs''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSolidType''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 7 (3 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_usSolidFlags''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 1023 (10 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nSurroundType''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 7 (3 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_triggerBloat''' (m_Collision)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 255 (8 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bUniformTriggerBloat''' (m_Collision)<br />
<br />
Type: boolean<br />
<br />
Range: 0 - 1 (1 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMinsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMaxsPreScaled''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMins''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_vecSpecifiedSurroundingMaxs''' (m_Collision)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nRenderFX''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 255 (8 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nRenderMode''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 255 (8 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_fEffects''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 1023 (10 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_clrRender''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 4294967295 (32 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iTeamNum''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: -32 - 31 (6 bits signed)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_CollisionGroup''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 31 (5 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flElasticity''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_flShadowCastDistance''' (CBaseEntity)<br />
<br />
Type: float<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hOwnerEntity''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 2097151 (21 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_hEffectEntity''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 2097151 (21 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''moveparent''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 2097151 (21 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iParentAttachment''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 63 (6 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''movetype''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 15 (4 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''movecollide''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 7 (3 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_angRotation''' (CBaseEntity)<br />
<br />
Type: vector<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_iTextureFrameIndex''' (CBaseEntity)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 255 (8 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''predictable_id''' (CBaseEntity)<br />
<br />
m_PredictableID (predictable_id)<br />
<br />
Type: integer<br />
<br />
Range: 0 - 2147483647 (31 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bIsPlayerSimulated''' (predictable_id)<br />
<br />
Type: boolean<br />
<br />
Range: 0 - 1 (1 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bSimulatedEveryTick''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Range: 0 - 1 (1 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bAnimatedEveryTick''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Range: 0 - 1 (1 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_bAlternateSorting''' (CBaseEntity)<br />
<br />
Type: boolean<br />
<br />
Range: 0 - 1 (1 bits unsigned)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''m_nModelIndexOverrides''' (CBaseEntity)<br />
<br />
000 (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Range: -4096 - 4095 (13 bits signed)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''001''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Range: -4096 - 4095 (13 bits signed)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''002''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Range: -4096 - 4095 (13 bits signed)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?<br />
<br />
'''003''' (m_nModelIndexOverrides)<br />
<br />
Type: integer<br />
<br />
Range: -4096 - 4095 (13 bits signed)<br />
<br />
Description:<br />
<br />
------------<br />
<br />
..?</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Classes&diff=250Classes2022-01-29T19:44:42Z<p>192.168.1.218: Created page with "== Class Parent Hierarchy == * '''CBaseEntity''' ** '''CBaseAnimating''' <small><sub>(CBaseEntity)</sub></small> *** '''CBaseAnimatingOverlay''' <sub><small>(CBaseAnimating)<..."</p>
<hr />
<div>== Class Parent Hierarchy ==<br />
<br />
* '''CBaseEntity'''<br />
** '''CBaseAnimating''' <small><sub>(CBaseEntity)</sub></small><br />
*** '''CBaseAnimatingOverlay''' <sub><small>(CBaseAnimating)</small></sub><br />
**** '''CEconEntity''' <sub><small>(CBaseAnimatingOverlay)</small></sub><br />
***** '''CBaseAttributableItem''' <sub><small>(CEconEntity)</small></sub><br />
***** '''CBaseCombatWeapon''' <sub><small>(CEconEntity)</small></sub><br />
****** CTFWeaponBase<br />
******* CPasstimeGun<br />
******* CTFWeaponBaseMelee<br />
******** CTFBat<br />
********* CTFBat_Fish<br />
********* CTFBat_Wood<br />
********** CTFBat_Giftwrap<br />
******** CTFBonesaw<br />
******** CTFBreakableMelee<br />
********* CTFBottle<br />
********* CTFBreakableSign<br />
******** CTFBreakableMelee<br />
******** CTFBuffItem<br />
******** CTFClub<br />
******** CTFFireAxe<br />
******* CTFWeaponBaseGun<br />
******** CTFGrenadeLauncher<br />
********* CTFCannon<br />
******** CTFSMG<br />
********* CTFChargedSMG<br />
******** CTFWeaponJar<br />
********* CTFCleaver<br />
******** CTFPipebombLauncher<br />
********* CTFCompoundBow<br />
******** CTFRocketLauncher<br />
********* CTFCrossbow<br />
********* CTFRaygun<br />
********** CTFDRGPomson<br />
***** CEconWearable<br />
*** '''CBaseFlex''' <sub><small>(CBaseAnimating)</small></sub><br />
**** '''CBaseCombatCharacter''' <sub><small>(CBaseFlex)</small></sub><br />
***** '''CAI_BaseNPC''' <sub><small>(CBaseCombatCharacter)</small></sub><br />
***** '''CBaseObject''' <sub><small>(CBaseCombatCharacter)</small></sub><br />
****** '''CBaseObjectUpgrade''' <sub><small>(CBaseObject)</small></sub><br />
******* CObjectSapper<br />
****** CObjectDispenser<br />
******* CObjectCartDispenser<br />
******* CPlayerDestructionDispenser<br />
******* CRobotDispenser<br />
****** CObjectSentrygun<br />
****** CObjectTeleporter<br />
***** '''CBasePlayer''' <sub><small>(CBaseCombatCharacter)</small></sub><br />
***** NextBotCombatCharacter<br />
****** CEyeballBoss<br />
****** CHeadlessHatman<br />
****** CMerasmus<br />
****** CTFBaseBoss<br />
*** '''CBaseProjectile''' <sub><small>(CBaseAnimating)</small></sub><br />
**** '''CBaseGrenade''' <sub><small>(CBaseProjectile)</small></sub><br />
***** CTFWeaponBaseGrenadeProj<br />
****** CTFGrenadePipebombProjectile<br />
******* CTFStunball<br />
******** CTFBall_Ornament<br />
**** CTFBaseProjectile<br />
***** CTFBaseRocket<br />
*** '''CHalloweenPickup''' <sub><small>(CBaseAnimating)</small></sub><br />
**** '''CBonusDuckPickup''' <sub><small>(CCHalloweenPickup)</small></sub><br />
**** CHalloweenGiftPickup<br />
*** CCurrencyPack<br />
**** CBonusPack<br />
*** '''CBreakableProp''' <sub><small>(CBaseAnimating)</small></sub><br />
**** '''CDynamicProp''' <sub><small>(CBreakableProp)</small></sub><br />
***** '''CBasePropDoor''' <sub><small>(CDynamicProp)</small></sub><br />
***** CTFItem<br />
****** CCaptureFlag<br />
**** CPhysicsProp<br />
***** CPhysicsPropMultiplayer<br />
*** CEnvParticleScript<br />
*** CTeleportVortex<br />
**** CHightower_TeleportVortex<br />
*** CTFAmmoPack<br />
*** CTFDroppedWeapon<br />
*** CMerasmusDancer<br />
*** CPasstimeBall<br />
*** CPhysMagnet<br />
*** CPointCommentaryNode<br />
*** CPropVehicleDriveable<br />
*** CRagdollProp<br />
**** CRagdollPropAttached<br />
** '''CBaseDoor''' <sub><small>(CBaseEntity)</small></sub><br />
** '''CBaseParticleEntity''' <sub><small>(CBaseEntity)</small></sub><br />
*** CEntityParticleTrail<br />
*** CFireTrail<br />
*** CSmokeStack<br />
*** CSteamJet<br />
** '''CBoneFollower''' <sub><small>(CBaseEntity)</small></sub><br />
** CBreakableSurface<br />
** CCaptureFlagReturnIcon<br />
** CCaptureZone<br />
** CDynamicLight<br />
** CEmbers<br />
** CEntityDissolve<br />
** CEntityFlame<br />
** CEnvProjectedTexture<br />
** CEnvQuadraticBeam<br />
** CEnvScreenEffect<br />
** CEnvScreenOverlay<br />
** CEnvTonemapController<br />
** CFireSmoke<br />
** CFunc_LOD<br />
** CFuncAreaPortalWindow<br />
** CFuncConveyor<br />
** CFuncForceField<br />
** CFuncLadder<br />
** CFuncMonitor<br />
** CFuncPasstimeGoal<br />
** CFuncReflectiveGlass<br />
** CFuncRespawnRoom<br />
** CFuncRespawnRoomVisualizer<br />
** CFuncRotating<br />
** CFuncSmokeVolume<br />
** CFuncTrackTrain<br />
** CHalloweenSoulPack<br />
** CHandleTest<br />
** CInfoLadderDismount<br />
** CInfoLightingRelative<br />
** CMannVsMachineStats<br />
** CMaterialModifyControl<br />
** CParticlePerformanceMonitor<br />
** CPhysBox<br />
*** CPhysBoxMultiplayer<br />
** CPlasma<br />
** CPointCamera<br />
** CPoseController<br />
** CPrecipitation<br />
** CSlideshowDisplay<br />
** CSniperDot<br />
*** CLaserDot<br />
** CSprite<br />
*** CSpriteOriented<br />
*** CSpriteTrail<br />
** CSpotlightEnd<br />
** CTeamTrainWatcher<br />
** CTesla<br />
** CTest_ProxyToggle_Networkable<br />
** CTFBotHintEngineerNest<br />
* '''CBaseTeamObjectiveResource'''<br />
* '''CBaseTempEntity'''<br />
** CTEParticleSystem<br />
*** CTEBloodStream<br />
*** CTEDust<br />
*** CTEExplosion<br />
*** CTEGaussExplosion<br />
*** CTELargeFunnel<br />
*** CTEShowLine<br />
*** CTESparks<br />
** CTEBreakModel<br />
** CTEBSPDecal<br />
** CTEBubbles<br />
** CTEBubbleTrail<br />
** CTEClientProjectile<br />
** CTEDecal<br />
** CTEDynamicLight<br />
** CTEEffectDispatch<br />
** CTEFizz<br />
** CTEFootprintDecal<br />
** CTEGlowSprite<br />
** CTEImpact<br />
** CTEKillPlayerAttachments<br />
** CTEMuzzleFlash<br />
** CTEPhysicsProp<br />
** CTEPlayerDecal<br />
** CTEProjectedDecal<br />
** CTEShatterSurface<br />
** CTESmoke<br />
** CTESprite<br />
** CTESpriteSpray<br />
** CTETFBlood<br />
** CTETFExplosion<br />
** CTETFParticleEffect<br />
** CTEWorldDecal<br />
* '''CBeam'''<br />
* CBaseViewModel<br />
* CBonusRoundLogic<br />
* CColorCorrection<br />
* CColorCorrectionVolume<br />
* CEnvDetailController<br />
* CEnvWind<br />
* CFIsh<br />
* CFogController<br />
* CFunc_Dust<br />
* CFuncOccluder<br />
* CGameRulesProxy<br />
** CTeamplayRoundBasedRulesProxy<br />
* CInfoOverlayAccessor<br />
* CLightGlow<br />
* CMonsterResource<br />
* CParticleFire<br />
* CParticleSystem<br />
* CPlayerResource<br />
* CRagdollManager<br />
* CRopeKeyFrame<br />
* CSceneEntity<br />
* CShadowControl<br />
* CSun<br />
* CTeam<br />
* CTeamRoundTimer<br />
* CTEBaseBeam<br />
** CTEBeamEntPoint<br />
** CTEBeamEnts<br />
** CTEBeamFollow<br />
** CTEBeamLaser<br />
** CTEBeamPoints<br />
** CTEBeamRIng<br />
** CTEBeamRingPoint<br />
* CTEMetalSparks<br />
** CTEArmorRicochet<br />
* CTEBeamSpline<br />
* CTEBloodSprite<br />
* CTEEnergySplash<br />
* CTEFireBullets<br />
* CTEMetalSparks<br />
* CTEPlayerAnimEvent<br />
* CTestTraceline</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=240Reverse MvM Beginners Guide2022-01-27T03:09:54Z<p>192.168.1.218: </p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potato.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style teleporters is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives be very forgiving <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well. 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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=239Reverse MvM Beginners Guide2022-01-23T20:21:51Z<p>192.168.1.218: /* Friendly Robots */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style teleporters is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives be very forgiving <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well. 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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=236Reverse MvM Beginners Guide2021-12-17T01:55:21Z<p>192.168.1.218: /* Placing Spawns */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style teleporters is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. <br />
<br />
Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives either be very forgiving, or take advantage of custom behavior changing keyvalues such as InterruptAction to give players more control over the VIP. It is highly recommended not to allow VIP bots to pick up the bomb, but still have them use default bomb-hunting behavior. This way, if a player picks up the bomb and there are < 4 blu robots nearby*, they will be protected and escorted by the VIP. <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well. 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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=235Reverse MvM Beginners Guide2021-12-17T01:53:51Z<p>192.168.1.218: /* Placing Spawns */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style teleporters is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
For new reverse mission makers, it is not recommended to go overboard on making the bots themselves very interesting and outlandish. While traditional community mvm is largely about creating new and interesting bots in your waves, the main hurdle of making a fun reverse mission is good red spawn locations and pacing. More time should be spent optimizing red spawns and map flow rather than creating new bot types. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. <br />
<br />
Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives either be very forgiving, or take advantage of custom behavior changing keyvalues such as InterruptAction to give players more control over the VIP. It is highly recommended not to allow VIP bots to pick up the bomb, but still have them use default bomb-hunting behavior. This way, if a player picks up the bomb and there are < 4 blu robots nearby*, they will be protected and escorted by the VIP. <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well. 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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=234Reverse MvM Beginners Guide2021-12-17T01:53:23Z<p>192.168.1.218: /* Placing Spawns */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 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 [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
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. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style teleporters is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable. Each spawn must be carefully chosen to cover as much ground as possible. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to complete before deploying the bomb: The front, the church tower, and the hatch. Spawns and accompanying sub-waves can then be adjusted depending on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
For new reverse mission makers, it is not recommended to go overboard on making the bots themselves very interesting and outlandish. While traditional community mvm is largely about creating new and interesting bots in your waves, the main hurdle of making a fun reverse mission is good red spawn locations and pacing. More time should be spent optimizing red spawns and map flow rather than creating new bot types. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. <br />
<br />
Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives either be very forgiving, or take advantage of custom behavior changing keyvalues such as InterruptAction to give players more control over the VIP. It is highly recommended not to allow VIP bots to pick up the bomb, but still have them use default bomb-hunting behavior. This way, if a player picks up the bomb and there are < 4 blu robots nearby*, they will be protected and escorted by the VIP. <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well. 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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=228Reverse MvM Beginners Guide2021-12-08T03:59:46Z<p>192.168.1.218: /* Upgrade Station */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. <br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]. Red robot template files can be found [https://www.dropbox.com/s/c9lri6egkhp5o8o/redbots.zip?dl=1 here].<br />
<br />
== Maps ==<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style teleporters is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable, and each spawn must be carefully and thoughtfully chosen to cover as much ground as possible before it becomes simply too far from the player to be useful. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower/bridge, and the hatch. Spawns can be placed and accompanying sub-waves can be timed based on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
For new reverse mission makers, it is not recommended to go overboard on making the bots themselves very interesting and outlandish. While traditional community mvm is largely about creating new and interesting bots in your waves, the main hurdle of making a fun reverse mission is good red spawn locations and pacing. More time should be spent optimizing red spawns and map flow rather than creating new bot types. Reverse as a concept carries itself, and many of the existing reverse missions that are suitable for an event make ample use of valve bot templates converted to red team. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. <br />
<br />
Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives either be very forgiving, or take advantage of custom behavior changing keyvalues such as InterruptAction to give players more control over the VIP. It is highly recommended not to allow VIP bots to pick up the bomb, but still have them use default bomb-hunting behavior. This way, if a player picks up the bomb and there are < 4 blu robots nearby*, they will be protected and escorted by the VIP. <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<br />
<br />
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<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=227Reverse MvM Beginners Guide2021-12-08T03:35:10Z<p>192.168.1.218: /* Friendly Robots */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]<br />
<br />
== Maps ==<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style teleporters is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable, and each spawn must be carefully and thoughtfully chosen to cover as much ground as possible before it becomes simply too far from the player to be useful. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower/bridge, and the hatch. Spawns can be placed and accompanying sub-waves can be timed based on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. <br />
<br />
Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives either be very forgiving, or take advantage of custom behavior changing keyvalues such as InterruptAction to give players more control over the VIP. It is highly recommended not to allow VIP bots to pick up the bomb, but still have them use default bomb-hunting behavior. This way, if a player picks up the bomb and there are < 4 blu robots nearby*, they will be protected and escorted by the VIP. <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=226Reverse MvM Beginners Guide2021-12-08T03:34:44Z<p>192.168.1.218: /* Friendly Robots */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]<br />
<br />
== Maps ==<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style teleporters is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable, and each spawn must be carefully and thoughtfully chosen to cover as much ground as possible before it becomes simply too far from the player to be useful. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower/bridge, and the hatch. Spawns can be placed and accompanying sub-waves can be timed based on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. <br />
<br />
Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives either be very forgiving, or take advantage of custom behavior changing keyvalues such as InterruptAction to give players more control over the VIP. It is highly recommended not to allow VIP bots to pick up the bomb, but still have them use default bomb-hunting behavior. This way, if a player picks up the bomb and there are < 4 blu robots nearby*, they will be escorted by the VIP. <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=225Reverse MvM Beginners Guide2021-12-08T03:33:09Z<p>192.168.1.218: /* Friendly Robots */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]<br />
<br />
== Maps ==<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style teleporters is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable, and each spawn must be carefully and thoughtfully chosen to cover as much ground as possible before it becomes simply too far from the player to be useful. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower/bridge, and the hatch. Spawns can be placed and accompanying sub-waves can be timed based on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. <br />
<br />
Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives either be very forgiving, or take advantage of custom behavior changing keyvalues such as InterruptAction to give players more control over their actions. It is highly recommended not to allow VIP bots to pick up the bomb, but still have them use default bomb-hunting behavior. This way, if a player picks up the bomb and there are < 4 blu robots nearby*, they will be escorted by the VIP. <br />
<br />
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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=224Reverse MvM Beginners Guide2021-12-08T03:29:08Z<p>192.168.1.218: </p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]<br />
<br />
== Maps ==<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style teleporters is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable, and each spawn must be carefully and thoughtfully chosen to cover as much ground as possible before it becomes simply too far from the player to be useful. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower/bridge, and the hatch. Spawns can be placed and accompanying sub-waves can be timed based on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress too quickly, then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into old ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. <br />
Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives either be very forgiving, or take advantage of custom behavior changing keyvalues such as InterruptAction to give players more control over their actions. It is highly recommended not to allow VIP bots to pick up the bomb, but still have them use default bomb-hunting behavior. This way, if a player picks up the bomb and there are < 4 blu robots nearby*, they will be escorted by the VIPDo 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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
==Preparing Your Map==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=223Reverse MvM Beginners Guide2021-12-08T03:25:09Z<p>192.168.1.218: /* Engineer Teleporter Types */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods]. An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]<br />
<br />
== Maps and Structure ==<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== <s>Engineer Teleporter Types</s> ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style teleporters is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
==Getting Started==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''<sup>* 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 suffixes (*_start_relay* would not work)</sup>'' <br />
<br />
''<sup>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 (such as move_rope and keyframe_rope).</sup>''<br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable, and each spawn must be carefully and thoughtfully chosen to cover as much ground as possible before it becomes simply too far from the player to be useful. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower/bridge, and the hatch. Spawns can be placed and accompanying sub-waves can be timed based on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress before the next section or miss the wave. Then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into older ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
== Friendly Robots ==<br />
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 bots using valve templates 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. <br />
Due to the complexity of balancing overpowered and underpowered blu robots for your wave, it is recommended that any lose conditions built around VIP escorting objectives either be very forgiving, or take advantage of custom behavior changing keyvalues such as InterruptAction to give players more control over their actions. It is highly recommended not to allow VIP bots to pick up the bomb, but still have them use default bomb-hunting behavior. This way, if a player picks up the bomb and there are < 4 blu robots nearby*, they will be escorted by the VIPDo 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. <br />
<br />
<sup>*Max escort limit can be adjusted with FlagEscortCountOffset, or by giving the bot Action EscortFlag</sup> <br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=222Reverse MvM Beginners Guide2021-12-08T03:07:24Z<p>192.168.1.218: /* Placing Spawns */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods].<br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]<br />
<br />
== Maps and Structure ==<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== Engineer Teleporter Types ===<br />
''<s>There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.</s>''<br />
<br />
<sup>As of 12/07/2021, The feature to place engineer-bot style mobile spawns is horribly broken. Only vanilla teleporters and teleporters built by actual engineer-bots are currently functional.</sup><br />
<br />
=== Friendly Robots ===<br />
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 bots using valve templates 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. <br />
<br />
<br />
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.<br />
<br />
==Getting Started==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''* 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 suffixes (*_start_relay* would not work)'' <br />
<br />
''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 (such as move_rope and keyframe_rope).''<br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable, and each spawn must be carefully and thoughtfully chosen to cover as much ground as possible before it becomes simply too far from the player to be useful. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front, the church tower/bridge, and the hatch. Spawns can be placed and accompanying sub-waves can be timed based on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress before the next section or miss the wave. Then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, using WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into older ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
<br />
<br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=221Reverse MvM Beginners Guide2021-12-08T03:01:41Z<p>192.168.1.218: /* Placing Spawns */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods].<br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]<br />
<br />
== Maps and Structure ==<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== Engineer Teleporter Types ===<br />
There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.<br />
<br />
=== Friendly Robots ===<br />
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 bots using valve templates 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. <br />
<br />
<br />
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.<br />
<br />
==Getting Started==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''* 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 suffixes (*_start_relay* would not work)'' <br />
<br />
''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 (such as move_rope and keyframe_rope).''<br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Bot spawn timing and placement is the most important ingredient for making your mission enjoyable, and each spawn must be carefully and thoughtfully chosen to cover as much ground as possible before it becomes simply too far from the player to be useful. <br />
<br />
It is best to divide your map into distinct areas that players need to conquer before progressing to the next stage, placing spawns accordingly for where those sections of the map are. Rottenburg, for example, could be cut into 3 distinct areas that players need to beat before deploying the bomb: The front/tunnel area, the church tower/bridge area, and the hatch. Spawns can be placed and accompanying sub-waves can be timed based on how long you want players to spend in each individual area of the map.<br />
<br />
A common mistake new reverse mission makers will make is placing spawns very close to the player, sometimes in plain view, in order to ensure players don't make too much progress before the next section or miss the wave. Then, waiting for all bots to be dead in the previous sub-wave before spawning the next. It is best to avoid this practice and, instead, place your spawns far behind cover along the main bot path, and use WaitForAllSpawned over WaitForAllDead. This serves multiple purposes: When bots are spawned further back and need to make their way to players, new sub-waves are seamlessly blended into older ones, rather than abruptly ending and having new bots appear out of thin air. It also allows red bots to spread more thinly around the map, catching rushers and taking flank routes without needing to be explicitly told to do so. It also better highlights the direction players need to go if they get lost, as they can simply follow the trail of red bots to the next location in the map. <br />
<br />
<br />
<br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=220Reverse MvM Beginners Guide2021-12-06T03:47:58Z<p>192.168.1.218: /* Placing Spawns */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods].<br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]<br />
<br />
== Maps and Structure ==<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== Engineer Teleporter Types ===<br />
There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.<br />
<br />
=== Friendly Robots ===<br />
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 bots using valve templates 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. <br />
<br />
<br />
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.<br />
<br />
==Getting Started==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''* 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 suffixes (*_start_relay* would not work)'' <br />
<br />
''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 (such as move_rope and keyframe_rope).''<br />
<br />
== Placing Spawns ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
Once you've identified a map you feel is best for your mission, the next step is to create bot spawns that move progressively closer to the hatch, combined with sub-waves that give players adequate time to move forward and engage in the next sub-wave after it.<br />
<br />
<br />
<br />
<br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=219Reverse MvM Beginners Guide2021-12-06T03:39:35Z<p>192.168.1.218: /* Pacing and Structure */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods].<br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]<br />
<br />
== Maps and Structure ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== Engineer Teleporter Types ===<br />
There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.<br />
<br />
=== Friendly Robots ===<br />
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 bots using valve templates 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. <br />
<br />
<br />
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.<br />
<br />
==Getting Started==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''* 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 suffixes (*_start_relay* would not work)'' <br />
<br />
''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 (such as move_rope and keyframe_rope).''<br />
<br />
== Placing Spawns ==<br />
Once you've identified a map you feel is best for your mission, the next step is to create bot spawns that move progressively closer to the hatch, combined with sub-waves that give players adequate time to move forward and engage in the next sub-wave after it. If each sub-wave and spawn location is balanced correctly, players will not spend the majority of their time in one part of the map. If spawns are too fast and too close together, the mission will be a slog and players will struggle to progress. If new sub-waves are too slow to begin and spawns are spread too far apart, the threat will be too spread out and players can simply ignore the next sub-wave, head straight to the hatch, and let everything come to them. Do your best to strike a balance between these two extremes.<br />
<br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=210Reverse MvM Beginners Guide2021-12-01T07:07:23Z<p>192.168.1.218: </p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods].<br />
<br />
An example popfile for Rottenburg can be found [https://testing.potato.tf/tf/scripts/population/mvm_rottenburg_reverse_core_logic.pop here]<br />
<br />
== Pacing and Structure ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
<br />
Once you've identified a map you feel is best for your mission, the next step is to create bot spawns that move progressively closer to the hatch, combined with sub-waves that give players adequate time to move forward and engage in the next sub-wave after it. If each sub-wave and spawn location is balanced correctly, players will not spend the majority of their time in one part of the map. If spawns are too fast and too close together, the mission will be a slog and players will struggle to progress. If new sub-waves are too slow to begin and spawns are spread too far apart, the threat will be too spread out and players can simply ignore the next sub-wave, head straight to the hatch, and let everything come to them. Do your best to strike a balance between these two extremes.<br />
<br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== Engineer Teleporter Types ===<br />
There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.<br />
<br />
=== Friendly Robots ===<br />
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 bots using valve templates 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. <br />
<br />
<br />
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.<br />
<br />
==Getting Started==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''* 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 suffixes (*_start_relay* would not work)'' <br />
<br />
''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 (such as move_rope and keyframe_rope).''<br />
<br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=User:Orin/Sandbox/Entity_Additions&diff=206User:Orin/Sandbox/Entity Additions2021-11-21T21:06:16Z<p>192.168.1.218: draft</p>
<hr />
<div>'''WIP. Feel free to edit, but don't paste anything from here into the main page without my consent. If you have anything that needs to go there, edit it there.'''<br />
<br />
__NOEDITSECTION__<br />
<br />
<div style="float:right;clear:all;padding:0 1em;">__TOC__</div><br />
All entity-oriented feature additions: Inputs, Outputs, Targetting, etc. are all documented here within their own heaps of lists.<br />
<br />
To traverse this page, use the ''Table of Contents'' at the right side, or use the CTRL+F shortcut for your Browser.<br />
== I/O Expansions ==<br />
=== Targetname Prefixes ===<br />
When targetting entities, adding prefixes of the format <code>@name1@</code> will instead target an entity relative to the given entity, usually by relationships.<br />
{| class="wikitable" style="table-layout: fixed;"<br />
! Prefix<br />
! Description<br />
|-<br />
| <code>@p@<targetname></code><br />
| Targets the parent of an entity. Example: <code>@p@!activator</code>.<br />
|-<br />
| <code>@c@<targetname></code><br />
| Targets the child of an entity. Example: <code>@c@!activator</code>.<br />
|-<br />
| <code>@bb<''vector'' mins> <''vector'' maxs>@<targetname></code><br />
| Target ''all'' entiities within a [https://developer.valvesoftware.com/w/images/6/63/BoundingBoxMinsMaxs.png bounding box] relative to the given entity. Example: <code>@bb-100 -100 -100 100 100 100@prop_dynamic</code>.<br />
|}<br />
<br />
=== point_viewcontrol ([https://developer.valvesoftware.com/wiki/Point_viewcontrol VDC]) ===<br />
==== <u>Inputs</u> ====<br />
{| class="wikitable" style="table-layout: fixed;"<br />
! Input<br />
! Description<br />
|-<br />
| <code>$EnableAll</code><br />
| Enable the camera for all players on the map.<br>&nbsp;❗ '''Warning:''' Spawnflag #512 may not do anything. (<code>Start At Player, Interruptable by Player</code>)<br />
|-<br />
| <code>$EnableAll</code><br />
| Disable the camera for all players on the map.<br />
|-<br />
| <code>$SetTarget <entity></code><br />
| Set current target as the entity. (Describe this better)<br />
|}<br />
<br />
=== tank_boss ([https://developer.valvesoftware.com/wiki/Tank_boss VDC]) ===<br />
==== <u>Outputs</u> ====<br />
{| class="wikitable" style="table-layout: fixed;"<br />
! Output<br />
! Description<br />
|-<br />
| <code>$OnStartDeploy</code><br />
| Fired when the tank is deploying the bomb<br />
|}<br />
<br />
== Entity Expansions ==<br />
<br />
=== [https://developer.valvesoftware.com/wiki/Point_viewcontrol obj_sentrygun] (Sentry Gun) ===<br />
==== <u>Spawnflags</u> ====<br />
* '''[64]''' - Spawn as mini-sentry<br />
<br />
=== [https://developer.valvesoftware.com/wiki/Tf_point_weapon_mimic tf_point_weapon_mimic] (Weapon Mimic) ===<br />
; <u>General</u><br />
1. Added projectile type 4 - Bullet.<br />
:- <code>SpeedMax</code> keyvalue determines max distance (infinite if not specified).<br />
:- <code>SplashRadius</code> determines knockback force.<br />
2. Shot projectiles are now team-assignable with <code>teamnum</code> keyvalue (2 for RED, 3 for BLU).<br />
:- Previously they're always of BLU team.<br />
3. If a player owner is set with <code>$SetOwner</code> or <code>$InheritOwner</code>, fired projectiles are assigned the same owner.<br><br />
4. Stickybombs are automatically removed if the mimic is killed.<br />
==== Spawnflags ====<br />
* '''[1]''' - Shot projectile callback; fires the <code>OnUser4</code> output whenever a projectile is shot, with <code>!activator</code> as the projectile.<br />
* '''[2]''' - Allow the keyvalues "''FireSound''" and "''ParticleEffect''" to have functionality.<br />
<br />
=== Tank (tank_boss) ===<br />
* When a tank with <code>PointTemplate</code>(s) starts deploying, "OnUser4" output is fired.<br />
<br />
=== Medic shield (entity_medigun_shield) ===<br />
==== Spawnflags ====<br />
* '''[1]''' - Never expire, and don't block LOS<br />
* '''[2]''' - Spawn as LV2 Shield<br />
<br />
=== logic_case ===<br />
==== Text formatter ====<br />
With the use of the added inputs, logic_case can be transformed into a text formatter, replacing % in the format string into format parameters.<br />
<br />
Example point template usage:<syntaxhighlight lang="php"><br />
Formatter<br />
{<br />
OnSpawnOutput<br />
{<br />
Target "formattest"<br />
Action "$Format"<br />
Delay 1<br />
}<br />
logic_case<br />
{<br />
"targetname" "formattest"<br />
"case16" "You have % out of % coins left. % %% done" // Formatter string<br />
"case01" "6" //First argument<br />
"case02" "12" //Second argument<br />
"case03" "50" //Third argument<br />
"ondefault" "player,$DisplayTextCenter,,0,-1"<br />
}<br />
}<br />
</syntaxhighlight>This would display "You have 6 out of 12 coins left. 50 % done" to all players<br />
<br />
==== Menus ====<br />
You can use $DisplayMenu input to display a menu for the player, up to 15 entries<syntaxhighlight lang="php"><br />
Menu<br />
{<br />
OnSpawnOutput<br />
{<br />
Target "menutest"<br />
Action "$DisplayMenu"<br />
Delay 1<br />
Param "player"<br />
}<br />
logic_case<br />
{<br />
"targetname" "menutest"<br />
"case16" "Menu title|30|Cancel" // Title, menu duration (0 for infinite), display optional cancel button<br />
"case01" "option1" //First argument<br />
"case02" "!disabled option" //Second argument, disabled<br />
"case03" "suicide" //Third argument<br />
"oncase03" "!activator,sethealth,0,0,-1" // Selected 3rd option<br />
"ondefault" "player,$DisplayTextCenter,he,0,-1" // No option selected<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
==== Inputs ====<br />
<br />
* $FormatString <string><br />
** Sets formatting string, then fires OnDefault output, with formatted string as parameter<br />
* $FormatStringNoFire <string><br />
** Sets formatting string<br />
* $FormatInput1 <string><br />
** Sets formatting input argument 1, then fires OnDefault output, with formatted string as parameter<br />
* $FormatInput2-15 <string><br />
** Sets formatting input argument 2-15, then fires OnDefault output, with formatted string as parameter<br />
* $FormatInputNoFire1 <string><br />
** Sets formatting input argument 1<br />
* $Format<br />
** Fires OnDefault output, with formatted string as parameter<br />
* $TestSigsegv<br />
** Fires OnUser1 output. Can be used to test if sigsegv extension is active<br />
* $ToInt <any><br />
** Fires OnDefault output, converts parameter value from string/float to integer<br />
* $ToFloat <any><br />
** Fires OnDefault output, converts value from string/int to real number<br />
* $CallerToActivator <any><br />
** Fires OnDefault output, but the !caller entity is converted to !activator<br />
* $GetKeyValueFromActivator <string><br />
** Fires OnDefault output, the key value from the !activator entity is the parameter<br />
* $GetConVar <string><br />
** Fires OnDefault output, the convar (console variable) number value is the parameter<br />
* $GetConVarString <string><br />
** Fires OnDefault output, the convar (console variable) string value is the parameter<br />
*$DisplayMenu <entity><br />
**Display menu at player<br />
*$HideMenu <entity><br />
**Hide menu at player<br />
<br />
== tf_gamerules ==<br />
<br />
=== Inputs ===<br />
<br />
* $StopVO <string><br />
** Stops sound that was started with PlayVO input<br />
<br />
* $StopVORed <string><br />
** Stops sound that was started with PlayVORed input<br />
<br />
* $StopVOBlue <string><br />
** Stops sound that was started with PlayVOBlue input<br />
*$SetBossHealthPercentage <float><br />
**Set Halloween boss bar percentage to a value between 0 and 1. 0 hides the health bar, any other value makes the bar appear<br />
*$SetBossState <int><br />
**If set to 1, makes the health bar green, like if Merasmus is hiding. If set to 0, the bar goes back to normal<br />
*$AddCurrencyGlobal <int><br />
**Add currency to all players<br />
<br />
== player ==<br />
<br />
=== Inputs ===<br />
<br />
* $AllowClassAnimations <0|1><br />
** Allow class animations instead of using refpose when UseCustomModel input is fired to change player model<br />
* $SwitchClass <string><br />
** Switch player class. The parameter can be either a class name (heavyweapons for example), or class index<br />
*$SwitchClassInPlace <string><br />
**Switch player class in current position. The parameter can be either a class name (heavyweapons for example), or class index<br />
* $ForceRespawn<br />
** The player instantly respawns<br />
* $ForceRespawnDead<br />
** The player instantly respawns, but only if they are dead<br />
* $DisplayTextCenter <string><br />
** Display text in the middle of the screen<br />
* $DisplayTextChat <string><br />
** Display text to the player's chat<br />
* $Suicide<br />
** Kill the player<br />
* $ChangeAttributes <string><br />
** If the player is a bot, this can be used to change active EventChangeAttributes<br />
* $RollCommonSpell<br />
** Roll common spell<br />
* $SetSpell <string><br />
** Set player current spell to one of the following:<br />
*** Fireball<br />
*** Ball O' Bats<br />
*** Healing Aura<br />
*** Pumpkin MIRV<br />
*** Superjump<br />
*** Invisibility<br />
*** Teleport<br />
*** Tesla Bolt<br />
*** Minify<br />
*** Meteor Shower<br />
*** Summon Monoculus<br />
*** Summon Skeletons<br />
* $AddSpell <string><br />
** Adds spell to the number of spells. If the spell is different than the current one, it replaces the spell. The parameter is the same as in $SetSpell<br />
* $AddCond <int> [int]<br />
** Add condition to player. If a second argument is present, the condition will only run for a specified duration<br />
* $RemoveCond <int><br />
** Remove condition from player<br />
* $AddPlayerAttribute <string><br />
** Add attribute to player, the parameter should be passed in this way: attribute|value. Example: "move speed bonus|1.2"<br />
* $RemovePlayerAttribute <string><br />
** Remove attribute from player. Example: "move speed bonus"<br />
* $AddItemAttribute <string><br />
** Add attribute to item in slot, the parameter should be passed in this way: attribute|value|slot. Example "damage bonus|2|0" adds 100% damage bonus to primary weapon<br />
* $RemoveItemAttribute <string><br />
** Remove attribute from item in slot, the parameter should be passed in this way: attribute|slot. Example "damage bonus|0" removes damage bonus from primary weapon<br />
* $PlaySoundToSelf <string><br />
** Play sound to the player<br />
*$IgnitePlayerDuration <float><br />
**Ignite the player for a specified duration in seconds<br />
*$WeaponSwitchSlot <int><br />
**Forcibly switches to weapon in slot<br />
*$WeaponStripSlot <int><br />
**Removes weapon from a slot (-1 = current slot)<br />
*$GiveItem <string><br />
**Gives an item to the player<br />
*$AddCurrency <int><br />
**Add currency to the player<br />
*$RemoveCurrency <int><br />
**Remove currency from the player<br />
*$SetCurrency <int><br />
**Set currency to specified value<br />
*$CurrencyOutputX <string><br />
**Fires input if player currency is above specified value (the X in input name), the attribute should be passed in this way: target,input,parameter.<br />
*$CurrencyInvertOutputX<string><br />
**Fires input if player currency is below specified value(the X in input name), the attribute should be passed in this way: target,input,parameter<br />
*$DropItem <int><br />
**Drop item in slot (-1 = current slot)<br />
*$RemoveItem <string><br />
**Remove item with a name<br />
*$Regenerate<br />
**Regenerate the player, as if touching resupply cabinet<br />
*$RefillAmmo<br />
**Restore player ammo<br />
<br />
== trigger_hurt ==<br />
If entity owner is set with $SetOwner or $InheritOwner, the owner will become the damage inflictor<br />
<br />
== Filter entities ==<br />
The server will no longer crash if the activator entity got removed the time TestActivator is called<br />
<br />
=== Inputs ===<br />
<br />
* $TestEntity <entity><br />
** Test any entity, rather than only the !activator<br />
<br />
== Trigger entities ==<br />
The server will no longer crash if the caller entity got removed the time StartTouch or EndTouch is called<br />
<br />
=== Inputs ===<br />
<br />
* $StartTouchEntity <entity><br />
** StartTouch any entity, rather than only the !caller<br />
* $EndTouchEntity <entity><br />
** EndTouch any entity, rather than only the !caller<br />
<br />
== game_ui ==<br />
The server will no longer crash if the player using the entity disconnected from the server<br />
<br />
== $filter_keyvalue ==<br />
Custom filter that lets you filter entities matching the key value. Shares inputs with [https://developer.valvesoftware.com/wiki/Filter_base filter_base] entity<br />
<br />
=== Keyvalues ===<br />
<br />
* $name <string><br />
** Name of the key to compare, example: health<br />
* $value <any><br />
** Value to compare against<br />
* $compare <string><br />
** The condition for passing the filter (default: equal). Should only be set for numeric values<br />
** Possible values:<br />
*** equal<br />
*** less than<br />
*** greater than<br />
*** less than or equal<br />
*** greater than or equal<br />
<br />
== $filter_variable ==<br />
Custom filter that lets you filter entities matching the custom entity variable (declared by firing $SetVar$variablename input of the entity). Shares inputs with [https://developer.valvesoftware.com/wiki/Filter_base filter_base] entity<br />
<br />
=== Keyvalues ===<br />
<br />
* $name <string><br />
** Name of the variable to compare, example: myvar<br />
* $value <any><br />
** Value to compare against<br />
* $compare <string><br />
** The condition for passing the filter (default: equal). Should only be set for numeric values<br />
** Possible values:<br />
*** equal<br />
*** less than<br />
*** greater than<br />
*** less than or equal<br />
*** greater than or equal<br />
<br />
== $filter_datamap ==<br />
Custom filter that lets you filter entities matching the [https://raw.githubusercontent.com/powerlord/tf2-data/master/datamaps.txt datamap] prop. Shares inputs with [https://developer.valvesoftware.com/wiki/Filter_base filter_base] entity<br />
<br />
=== Keyvalues ===<br />
<br />
* $name <string><br />
** Name of the variable to compare, example: m_iHealth<br />
* $value <any><br />
** Value to compare against<br />
* $compare <string><br />
** The condition for passing the filter (default: equal). Should only be set for numeric values<br />
** Possible values:<br />
*** equal<br />
*** less than<br />
*** greater than<br />
*** less than or equal<br />
*** greater than or equal<br />
<br />
== $filter_prop ==<br />
Custom filter that lets you filter entities matching the [https://raw.githubusercontent.com/powerlord/tf2-data/master/netprops.txt send prop]. Shares inputs with [https://developer.valvesoftware.com/wiki/Filter_base filter_base] entity<br />
<br />
=== Keyvalues ===<br />
<br />
* $name <string><br />
** Name of the variable to compare, example: m_nCurrency<br />
* $value <any><br />
** Value to compare against<br />
* $compare <string><br />
** The condition for passing the filter (default: equal). Should only be set for numeric values<br />
** Possible values:<br />
*** equal<br />
*** less than<br />
*** greater than<br />
*** less than or equal<br />
*** greater than or equal<br />
<br />
== All entities ==<br />
<br />
=== Inputs ===<br />
<br />
* $FireUserAsActivator1-4 <string><br />
** Acts like FireUser1-4, but the entity becomes the !activator, and the parameter is passed in OnUser1-4 output<br />
*$FireUser5-8 <string><br />
** Fires custom $onuser5-8 output<br />
* $TakeDamage <int><br />
** Take specified amount of damage<br />
* $TakeDamageFromActivator <int><br />
** Take specified amount of damage, the !activator is the damage inflictor<br />
* $SetModel <string><br />
** Set custom model<br />
* $SetModelOverride <string><br />
** Set custom model, only changes the appearence<br />
* $SetModelSpecial <string><br />
** Set custom model, in a special way, it does less additional changes to the entity<br />
* $SetOwner <entity><br />
** Set entity owner<br />
* $InheritOwner <entity><br />
** Set entity owner to the passed entity owner<br />
* $InheritParent <entity><br />
** Set entity parent to the passed entity parent<br />
* $GetKeyValue <string><br />
** Fire OnUser1 output, with key value as a parameter<br />
* $MoveType <int>,<int><br />
** Set move type<br />
* $PlaySound <string><br />
** Play sound from this entity<br />
* $StopSound <string><br />
** Stop playing sound from this entity<br />
* $SetLocalOrigin <vector><br />
** Set origin relative to parent<br />
* $SetLocalAngles <vector><br />
** Set angles relative to parent<br />
* $SetLocalVelocity <vector><br />
** Set velocity relative to parent<br />
* $TeleportToEntity <entity><br />
** Teleport to specified entity<br />
* $MoveRelative <vector><br />
** Move relative to parent (world)<br />
* $RotateRelative <vector><br />
** Rotate relative to parent (world)<br />
*$SetKey$(keyvalue name) <string><br />
**Set keyvalue to specified value<br />
*$GetKey$(keyvalue name) <string><br />
**parameter format: entity|input|default value<br />
**example: !activator|$DisplayTextCenter|def<br />
**Trigger the input of an entity, with keyvalue as a paramer (default value if not found)<br />
*$SetVar$(variable name) <string><br />
**Set custom entity variable<br />
*$GetVar$(variable name) <string><br />
**parameter format: entity|input|default value<br />
**example: !activator|$DisplayTextCenter|def<br />
**Trigger the input of an entity, with variable as a paramer (default value if not found)<br />
*$SetData$([https://raw.githubusercontent.com/powerlord/tf2-data/master/datamaps.txt datamap] prop name) <string><br />
**Set datamap property to specified value<br />
*$GetData$([https://raw.githubusercontent.com/powerlord/tf2-data/master/datamaps.txt datamap] prop name) <string><br />
**parameter format: entity|input|default value<br />
**example: !activator|$DisplayTextCenter|def<br />
**Trigger the input of an entity, with datamap prop as a paramer (default value if not found)<br />
*$SetProp$([https://raw.githubusercontent.com/powerlord/tf2-data/master/netprops.txt send prop] name) <string><br />
**Set send property to specified value<br />
*$GetProp$([https://raw.githubusercontent.com/powerlord/tf2-data/master/netprops.txt send prop] name) <string><br />
**parameter format: entity|input|default value<br />
**example: !activator|$DisplayTextCenter|def<br />
**Trigger the input of an entity, with send prop as a paramer (default value if not found)<br />
<br />
=== Outputs ===<br />
<br />
* $OnUser5-8 <string><br />
** Called when $FireUser5-8 input is used<br />
* $OnKilled<br />
** Fired when the entity is killed. The calling entity no longer exist and cannot be accessed</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Modular_Gatebots&diff=202Modular Gatebots2021-11-12T06:50:59Z<p>192.168.1.218: Fixed page having no category (added Templates); Fixed the "syntax highlighting" error category appearing</p>
<hr />
<div>Gatebot templates that can be used alongside other templates<br />
<br />
== Templates ==<br />
<br />
* GatebotScout<br />
* GatebotPyro<br />
* GatebotSoldier<br />
* GatebotHeavy<br />
* GatebotDemoman<br />
* GatebotEngineer<br />
* GatebotMedic<br />
* GatebotSniper<br />
* GatebotSpy<br />
<br />
== Example ==<br />
[[File:Modulargatebot.png|thumb|Gatebot template used alongside demoknight template]]<br />
<syntaxhighlight lang="php"><br />
#base robot_giant.pop<br />
#base robot_standard.pop<br />
#base robot_gatebot_modular.pop<br />
WaveSchedule<br />
{<br />
Wave<br />
{<br />
WaveSpawn<br />
{<br />
Name "wave01a"<br />
Where spawnbot<br />
TotalCount 1<br />
WaitBeforeStarting 0<br />
<br />
TFBot<br />
{<br />
Template T_TFBot_Demoman_Knight<br />
AddTemplate GatebotDemoman [$SIGSEGV]<br />
}<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
== Download ==<br />
Popfile: https://testing.potatomvm.tf/tf/scripts/population/robot_gatebot_modular.pop<br />
<br />
[[Category:Templates]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=List_of_custom_attributes&diff=201List of custom attributes2021-11-12T06:48:28Z<p>192.168.1.218: Fixed category not pointing to "Misc Additions". (category pointed to References)</p>
<hr />
<div>{| class="wikitable sortable"<br />
!Attribute Name<br />
!Description<br />
!Example Value<br />
|-<br />
| parachute disabled<br />
|if set to 1, the user cannot deploy parachutes<br />
| 1<br />
|-<br />
|fires milk bolt<br />
|Secondary attack: crossbow fires milk bolt. Regenerates every x seconds<br />
|1<br />
|-<br />
|force distribute currency on death<br />
| The bot with the attribute distributes its currency on death, like with sniper kills<br />
|1<br />
|-<br />
|melee cleave attack<br />
|Melee weapon attacks all enemies in range<br />
|1<br />
|-<br />
| extra damage on hit penalty<br />
|Special mode for revolver: each hit reduces damage, up to x times. Likely does not work<br />
|1<br />
|-<br />
|extra damage on hit<br />
|<br />
|1<br />
|-<br />
|mod teleporter speed boost<br />
|Grants the players speed buff for 4 seconds after leaving teleporter<br />
|1<br />
|-<br />
|set turn to ice<br />
| Turns the victim ragdoll to ice<br />
|1<br />
|-<br />
| can breathe under water<br />
|Can player breathe underwater<br />
|1<br />
|-<br />
| cannot swim<br />
|If set to 1 player cannon swim <br />
|1<br />
|-<br />
|swimming mastery<br />
|If set to 1 player can swim at full class speed<br />
|1<br />
|-<br />
|ability doubletap teleport<br />
|If set to 1 player move his teleporter with double tapped movement keys. Does not work<br />
|1<br />
|-<br />
|mod ignore resists absorbs<br />
| A worse version of damage piercing since it only ignores battalion backup 35% reduction. Does not work?<br />
|1<br />
|-<br />
|scoreboard minigame<br />
|Players with this attribute are granted more points for kills but lose points after death<br />
|1<br />
|-<br />
|wet immunity<br />
|Is the player immune to wet statuses like jarate or mad milk<br />
|1<br />
|-<br />
|ability master sniper<br />
|Huntsman: reduces shoot time 40%/70%, same functionality as faster reload rate but limited to 2 points<br />
Sniper rifle: reduces zoom time 40%/70% (like reload rate does). increases charge rate 50%/200%, but actually 100% due to the cap<br />
|2<br />
|-<br />
|last shot crits<br />
|Last revolver shot in the clip is critical<br />
|1<br />
|-<br />
|keep disguise on attack<br />
|Keep disguise after attacking. Revolver only<br />
|1<br />
|-<br />
|add give health to teammate on hit<br />
| On hit ally: heal your teammate for x health, draining your own health<br />
|75 <br />
|-<br />
|mod minigun can holster while spinning<br />
|Can switch to other weapons while spinning minigun<br />
|1<br />
|-<br />
|sapper deploy time<br />
|Probably does nothing, otherwise it adds time required for the sapper to activate<br />
|1<br />
|-<br />
|kill combo fire rate boost<br />
|On kill: gives x% fire rate bonus, stacks up to 3 times. Killing different class clears the combo<br />
|0.1<br />
|-<br />
|mult dispenser rate<br />
|Healh and ammo dispenser rate<br />
| 2<br />
|-<br />
| mvm sentry ammo<br />
|Sentry max ammo multiplier<br />
|2<br />
|-<br />
| build small sentries<br />
|Sentry is 20% smaller. 33% less health, 25% less metal required to upgrade <br />
|1<br />
|-<br />
|mult teleporter recharge rate<br />
|Teleporter recharge duration multiplier <br />
|1<br />
|-<br />
| disguise as dispenser on crouch<br />
|As spy, disguise as dispenser when crouching<br />
|1<br />
|-<br />
|ubercharge transfer<br />
|On hit, as a medic, with "ubercharge ammo" syringegun: transfer x% of the used uber to the enemy medic<br />
|34<br />
|-<br />
|ubercharge ammo<br />
| Uses ubercharge as ammo. 100 for full uber use. Syringegun (not crossbow) only <br />
|10<br />
|-<br />
|teleport instead of die<br />
| On death: x% chance of being immediately revived at spawn with 1 health<br />
|0.5<br />
|-<br />
|mod projectile heat seek power<br />
| Flare and rocket homing seek power in degrees per second <br />
|360<br />
|-<br />
| mod projectile heat aim error<br />
|Rocket max error in aim in degrees <br />
|90<br />
|-<br />
|mult dmg vs same class<br />
|Damage vs same class multipler<br />
|2<br />
|-<br />
|uber on damage taken<br />
|On take damage: x% chance of gaining invicibility for 3 seconds<br />
| 1<br />
|-<br />
|mult dmgtaken from melee<br />
|Damage taken from melee multipier <br />
| 0.3<br />
|-<br />
| mult crit when health is below percent<br />
|Player is crit boosted when below x% health.<br />
|0.5<br />
|-<br />
|penetration damage penalty<br />
|Penetrated players receive only x% damage. Bullets only. Can be damage bonus despite the name <br />
| 0.5<br />
|-<br />
| firing forward pull<br />
|Player is pushed x units and speed boosted when firing flamethrower. Limited by ground move speed<br />
|1000<br />
|-<br />
|mod soldier buff range<br />
| x% soldier buff range bonus <br />
|1.7<br />
|-<br />
|mult rocketjump deploy time<br />
|Deploy speed bonus when rocket jumping<br />
|0.4<br />
|-<br />
|mul nonrocketjump attackrate<br />
|Fire rate multiplier when not rocket jumping<br />
|0.5<br />
|-<br />
|aoe heal chance<br />
|On hit: refire time * (x/60) % chance for aoe heal for 1s (24 hp healed total). use 60 for 100% chance on 1s refire time weapon, 600 for 0.1s<br />
|80<br />
|-<br />
| crits on damage<br />
| On hit: refire time * (x/60) % chance for crit boost for 3s. use 60 for 100% chance on 1s refire time weapon, 600 for 0.1s<br />
|80 <br />
|-<br />
|stun on damage<br />
|On hit: refire time * (x/60) % chance for stun for 3s. use 60 for 100% chance on 1s refire time weapon, 600 for 0.1s<br />
| 80<br />
|-<br />
|aoe blast on damage<br />
| On hit: refire time * (x/60) % chance for 100 hu blast that stuns players for 2 seconds and applies bleed. use 60 for 100% chance on 1s refire time weapon, 600 for 0.1s <br />
|80<br />
|-<br />
| mult dmg with reduced health<br />
| Grants up to x% damage bonus based on current health. Only for melee weapons<br />
|2<br />
|-<br />
|mult airblast primary refire time<br />
|Multiplier of how fast can pyro use primary fire again after airblasting <br />
| 4<br />
|-<br />
|mod flamethrower spinup time<br />
|Spin up time for flamethrowers in seconds<br />
|2.4<br />
|-<br />
| mult airblast cone scale<br />
|Player pushback cone scale. Might not work after JI<br />
|1.8<br />
|-<br />
|airblast functionality flags<br />
|Combination of flamethrower flags, used to limit airblast functionality. You have to add those numbers to enable specific functions (by default all are enabled):<br />
1 - If airblast should push players<br />
<br />
2 - If airblast can put out afterburn<br />
<br />
4 - If airblast can reflect projectiles<br />
<br />
8 - If airblast can stun players<br />
<br />
16 - If airblast disrupts player aim<br />
|9<br />
|-<br />
|reverse airblast<br />
|airblast pushes players towards the pyro. Does not work? <br />
|1<br />
|-<br />
|airblast dashes<br />
|airblast pushes the pyro himself rather than others<br />
|1<br />
|-<br />
|mult sniper charge per sec with enemy under crosshair<br />
|Sniper rifle charge rate when looking at the enemy. Still subject to the 200% charge rate limit<br />
|2<br />
|-<br />
|sniper beep with enemy under crosshair<br />
|Beeps when the sniper is looking at the enemy while charging, if set to 1 <br />
|1<br />
|-<br />
|disable buildings on hit<br />
|On building hit: Disable for x seconds<br />
|4<br />
|-<br />
| regenerate stickbomb<br />
|Regenerates caber on use<br />
| 1<br />
|-<br />
|mult smack time<br />
|Melee smack time multiplier (0.2s default)<br />
|4<br />
|-<br />
|medic machinery beam<br />
|If set to 1, enables healing buildings as medic. increases building healing rate by 10% for each point<br />
|1<br />
|-<br />
|arrow mastery<br />
|Shoots additional 2 arrows per level<br />
| 1<br />
|-<br />
|custom item model<br />
|Custom item model name<br />
|<br />
|-<br />
|custom weapon fire sound<br />
| Custom weapon fire sound. Does not work for the weapon owner<br />
|<br />
|-<br />
|explosive bullets<br />
| Bullets explode in x radius on hit (147 is rocket launcher radius)<br />
|100<br />
|-<br />
|mult projectile scale<br />
| Projectile model scale multipier<br />
|2<br />
|-<br />
| mult projectile count<br />
|Fire multiple projectiles at once<br />
|4<br />
|-<br />
| projectile trail particle<br />
|Projectile trail particle name<br />
|<br />
|-<br />
|explosion particle<br />
|Explosion particle name<br />
|<br />
|-<br />
|radius sleeper<br />
|Restores sydney sleeper explosion on headshot<br />
|1<br />
|-<br />
|cannot be sapped<br />
|Bot with this attribute cannot be affected by the sapper<br />
|1<br />
|-<br />
|item color rgb<br />
|Item tint color<br />
|223424<br />
|-<br />
| is invisible<br />
|Is item invisible <br />
| 1<br />
|-<br />
| cannot taunt<br />
|Cannot taunt<br />
|1<br />
|-<br />
|projectile acceleration<br />
|Rocket acceleration in hu/s^2 <br />
|500<br />
|-<br />
|is miniboss<br />
|The player is miniboss<br />
|1<br />
|-<br />
|model scale<br />
| Player model scale<br />
|1<br />
|-<br />
|cannot upgrade<br />
|Player upgrade possibility<br />
|1<br />
|-<br />
|min respawn time<br />
|Minimal respawn time in seconds <br />
|4<br />
|-<br />
|always crit<br />
|Weapon always crits <br />
|1<br />
|-<br />
|mult firerocket rate<br />
|Sentry rocket fire rate<br />
| 1<br />
|-<br />
|building max level<br />
|Building max level limit <br />
|1<br />
|-<br />
|sentry rapid fire<br />
|Allows for faster sentry fire rate, up to 66 shots per second<br />
| 1<br />
|-<br />
|dont count damage towards crit rate<br />
| Dealing damage with weapon does not increase crit rate<br />
|1<br />
|-<br />
|reduced damage rampup<br />
|Set damage rampup to 20%<br />
|1<br />
|-<br />
|no reduced damage rampup<br />
|Set damage rampup to 50%<br />
|1<br />
|-<br />
|force damage falloff<br />
|Force damage rampup and falloff<br />
|1<br />
|-<br />
| no damage falloff<br />
|No damage rampup and falloff<br />
|1<br />
|-<br />
|can headshot<br />
|Weapon can headshot. Hitscan only <br />
|1<br />
|-<br />
|building color rgb<br />
|Building tint color<br />
|23424<br />
|-<br />
|building scale<br />
|Building scale. Values above 1.17 make it difficult for players to build on uneven ground<br />
|1.54 <br />
|-<br />
|mult stun resistance<br />
|Stun slow multiplier. 0 to be fully stun slow immune <br />
| 0<br />
|-<br />
|allow friendly fire<br />
| Allow to deal friendly fire damage<br />
|1<br />
|-<br />
|receive friendly fire<br />
| Receive friendly fire from teammates<br />
|1<br />
|-<br />
|cannot headshot<br />
|Weapon Cannot headshot<br />
|1<br />
|-<br />
|mult crit dmg<br />
|Crit damage multiplier<br />
|1.54<br />
|-<br />
| cannot be headshot<br />
|Cannot be headshot. Hitscan only<br />
|1<br />
|-<br />
|attachment name<br />
| Use this model attachment instead of bonemerging. If the name is empty, it will follow player origin instead.<br />
Common attachments for robot models: head, eye_1, flag. Some bot models also have eye_2, partyhat. Demo &amp; soldier additionally contain foot_L and foot_R<br />
<br />
Common attachments for player models: head, eyes, flag, partyhat, bread_face, bread_head, effect_hand_L, effect_hand_R, bread_hand_r, bread_hand_l, bread_butt, bread_heel_l, foot_L, foot_R<br />
|head<br />
|-<br />
|attachment offset<br />
| Item offset from the attachment origin <br />
|4 2 44<br />
|-<br />
|attachment angles<br />
|Rotation for attached items<br />
|25 25 0<br />
|-<br />
| attachment scale<br />
|Model scale for attached items<br />
|1.5<br />
|-<br />
|mod projectile heat aim time<br />
|For how long should the projectile home in<br />
|1.75<br />
|-<br />
|projectile gravity<br />
|Projectile gravity in hu/s^2<br />
|600 <br />
|-<br />
|projectile acceleration time<br />
|For how long should the projectile accelerate<br />
|2.55<br />
|-<br />
| grenade explode on impact<br />
|Grenades explode on impact<br />
| 1<br />
|-<br />
|<br />
projectile lifetime<br />
|Projectile lifetime in seconds <br />
| 52<br />
|-<br />
|not solid to players<br />
| The player is not solid to other players<br />
|1<br />
|-<br />
|is suicide counter<br />
|If set, the player takes this amount of damage per second, ignores uber, does not apply damage force<br />
|1<br />
|-<br />
|always allow taunt<br />
|Always allow the player to taunt, even midair <br />
|1<br />
|-<br />
|mult reflect velocity<br />
| Reflected projectile speed multiplier<br />
| 1<br />
|-<br />
|custom kill icon<br />
|Use custom kill icon. Icons are defined in scripts/mod_textures.txt in tf_misc_dir.vpk<br />
|armageddon<br />
|-<br />
|mod projectile heat follow crosshair<br />
|Homing projectiles follow crosshair<br />
|1<br />
|-<br />
| cannot be upgraded<br />
|Weapon cannot be upgraded<br />
|1<br />
|-<br />
|projectile no deflect<br />
|Projectile cannot be deflected<br />
| 1<br />
|-<br />
| projectile acceleration start time<br />
|Time before projectile starts accelerating <br />
|1<br />
|-<br />
| player gravity ballon head<br />
|Player gravity multiplier when ballon head condition (TF_COND_BALLOON_HEAD). 0 is for regular gravity<br />
|12<br />
|-<br />
| mult dmg vs giants<br />
|Damage multiplier vs giants<br />
|2.5<br />
|-<br />
| mult dmg vs tanks<br />
| Damage multiplier vs tanks<br />
|2.5<br />
|-<br />
| mult dmg vs npc<br />
|Damage multiplier vs npc including tanks excluding player bots <br />
| 2.5<br />
|-<br />
| custom hit sound<br />
|Custom sound played when a player victim is hit with the weapon<br />
|fdfdf<br />
|-<br />
| custom impact sound<br />
|Custom sound played when a rocket / projectile / bullet hits something<br />
|fdfdf<br />
|-<br />
|custom weapon reload sound<br />
|Custom weapon reload sound<br />
|fdfdf <br />
|-<br />
|no explosion particles<br />
| No explosion particles and sounds<br />
|1<br />
|-<br />
| override projectile type extra<br />
|Special version of override projectile type that adds more projectile types:<br />
"mechanicalarmorb" - Short circuit orb<br />
|mechanicalarmorb<br />
|-<br />
|dmg current health<br />
|Deal additional damage based on fraction of target current health<br />
|0.34<br />
|-<br />
|dmg max health<br />
| Deal additional damage based on fraction of target max health<br />
|0.34<br />
|-<br />
|dmg missing health<br />
|Deal additional damage based on fraction of target missing health<br />
|0.34<br />
|-<br />
|cannot be teleported<br />
|Player cannot be teleported<br />
|1<br />
|-<br />
| mult medigun range<br />
|Medigun range multiplier <br />
|1.5<br />
|-<br />
|projectile penetration limit<br />
|Penetration limit for projectiles<br />
|3<br />
|-<br />
|max aoe targets<br />
|Max targets affected by explosives and flamethrowers<br />
|4<br />
|-<br />
|add cond on hit<br />
| Add condtion to the target on hit<br />
| 56<br />
|-<br />
|add cond on hit duration<br />
|Add condtion on hit duration<br />
|4<br />
|-<br />
|remove cond on hit<br />
|Remove condtion from target on hit<br />
|57<br />
|-<br />
|add damage type<br />
|Add damage type to the attack<br />
|1<br />
|-<br />
|remove damage type<br />
|Remove damage type from the attack <br />
| 1<br />
|-<br />
|special damage type<br />
| Sets a special damage type to a range from 1-3<br />
|1<br />
|-<br />
|dmg taken mult from special damage type 1<br />
| Damage taken multiplier from weapons with special damage type 1<br />
|4<br />
|-<br />
|dmg taken mult from special damage type 2<br />
|Damage taken multiplier from weapons with special damage type 2<br />
|4<br />
|-<br />
|dmg taken mult from special damage type 3<br />
|Damage taken multiplier from weapons with special damage type 3<br />
|4<br />
|-<br />
|mult effect duration<br />
|Effect duration multiplier on drinks, jars<br />
|3<br />
|-<br />
|effect cond override<br />
|Effect condtion override on drinks, jars, ubers and many other effects<br />
| 24<br />
|-<br />
|self add cond on hit<br />
| Add condition to self on hit target<br />
|54<br />
|-<br />
|self add cond on hit duration<br />
|Add condition to self on hit target duration<br />
| 3<br />
|-<br />
|add cond on kill<br />
| Add condition on kill<br />
|57<br />
|-<br />
|add cond on kill<br />
| Add condition on kill duration<br />
| 10<br />
|-<br />
|special item description<br />
|Item description <br />
|item description<br />
|-<br />
| mult flag carrier move speed<br />
|Flag carrier move speed multipier<br />
|0.66<br />
|-<br />
|overheal from heal on kill<br />
|On kill healing can overheal <br />
|1<br />
|-<br />
|fire input on hit<br />
|Fire input on hit targets. The player is the activator. The format is &lt;target&gt;^&lt;input&gt;^&lt;param&gt;. If omitted, default param is damage received<br />
| !self^SetHealth^0<br />
|-<br />
|fire input on hit name restrict<br />
|Restrict input on hit to specified targetname or classname. Wildcards are allowed<br />
|player<br />
|-<br />
| grenade bounce speed<br />
|Grenades bounce off walls, retaining x% of speed after each bounce<br />
| 0.8<br />
|-<br />
|grenade bounce damage<br />
| Grenades explode on direct hits even if the grenade already touched a wall, dealing x% additional damage<br />
|0.3<br />
|-<br />
|projectile gravity native<br />
| Gravity for arrows and flares. 0 is default gravity. For grenades and stickybombs, any value will disable gravity <br />
|0.4<br />
|-<br />
|grenade no drag<br />
|No drag for grenades and stickybombs<br />
|1<br />
|-<br />
|stickybomb stick to enemies<br />
|Stickybombs stick to enemies <br />
|1<br />
|-<br />
| stickybomb no stick<br />
|Stickybombs do not stick to ground<br />
|1<br />
|-<br />
|collect currency on kill<br />
| Bots killed by the weapon drop red money<br />
| 1<br />
|-<br />
|stomp player damage<br />
|Damage applied to enemies when touching them<br />
|100<br />
|-<br />
|reflect keep team<br />
|Projectiles reflected by this weapon keep their original team<br />
|1<br />
|-<br />
|custom wind up sound<br />
|Custom minigun wind up sound. Does not override default sound<br />
|sound.wav<br />
|-<br />
|custom wind down sound<br />
|Custom minigun wind down sound. Does not override default sound<br />
|sound.wav<br />
|-<br />
|reflect magnet<br />
|If set to 1, reflected projectiles aim towards the pyro<br />
|1<br />
|-<br />
|stay after regenerate<br />
|Stay after hitting resupply cabinet or upgrading, if the weapon in the inventory in the slot is different<br />
|1<br />
|-<br />
|custom minigun spin sound<br />
|Custom minigun spin sound. The sound will not loop unless its made to loop<br />
|sound.wav<br />
|-<br />
|stomp player time<br />
|Time between each stomp damage and push. By default, it happens every tick<br />
|0.1<br />
|-<br />
|arrow hit kill time<br />
|If set to any value other than 0, sets custom arrow kill time after hitting something<br />
|0.3<br />
|-<br />
|custom projectile size<br />
|Custom projectile hitbox size<br />
|30<br />
|-<br />
|mod sentry cost<br />
|Sentry cost multiplier<br />
|1.25<br />
|-<br />
|mod dispenser cost<br />
|Dispenser cost multiplier<br />
|1.25<br />
|-<br />
|penetrate teammates<br />
|Bullets and projectiles penetrate teammates<br />
|1<br />
|-<br />
|add cond when active<br />
|Add condition when weapon is active. To provide a second condition, multiply it by 256. To provide a third condition, multiply it by 65536<br />
|11<br />
|-<br />
|mult step height<br />
|Step height multiplier (x * 18hu)<br />
|10<br />
|-<br />
|ignore player clip<br />
|Ignore player clip brushes<br />
|1<br />
|-<br />
|allow bunny hop<br />
|Allow bunny hopping. 1 - auto bhop. 2 - manual bhop<br />
|1<br />
|-<br />
|fire input on kill<br />
|Fire input on killed targets. The player is the activator. The format is <target>^<input>^<param>. If omitted, default param is damage received. !projectile is the projectile entity<br />
|!self^SetHealth^0<br />
|-<br />
|fire input on kill name restrict<br />
|Restrict input on hit to specified targetname. Wildcards are allowed<br />
|player<br />
|-<br />
|fire full clip at once<br />
|Fire entire clip at once<br />
|1<br />
|-<br />
|reload full clip at once<br />
|Reload full clip at once<br />
|1<br />
|}<br />
[[Category:Misc Additions]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=200Reverse MvM Beginners Guide2021-11-11T05:52:41Z<p>192.168.1.218: /* Engineer Teleporter Types */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods].<br />
<br />
An example popfile for Rottenburg can be found [https://www.dropbox.com/s/iu84axj1r0vhg0y/mvm&#x20;rottenburg&#x20;reverse&#x20;core&#x20;logic.pop?dl=1rial&#x20;mission here]<br />
<br />
== Pacing and Structure ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
<br />
Once you've identified a map you feel is best for your mission, the next step is to create bot spawns that move progressively closer to the hatch, combined with sub-waves that give players adequate time to move forward and engage in the next sub-wave after it. If each sub-wave and spawn location is balanced correctly, players will not spend the majority of their time in one part of the map. If spawns are too fast and too close together, the mission will be a slog and players will struggle to progress. If new sub-waves are too slow to begin and spawns are spread too far apart, the threat will be too spread out and players can simply ignore the next sub-wave, head straight to the hatch, and let everything come to them. Do your best to strike a balance between these two extremes.<br />
<br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== Engineer Teleporter Types ===<br />
There are 2 separate types of engineer teleporters: regular teleporter behavior, and engineer bot teleporter behavior. 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.<br />
<br />
=== Friendly Robots ===<br />
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 bots using valve templates 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. <br />
<br />
<br />
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.<br />
<br />
==Getting Started==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''* 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 suffixes (*_start_relay* would not work)'' <br />
<br />
''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 (such as move_rope and keyframe_rope).''<br />
<br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=199Reverse MvM Beginners Guide2021-11-11T05:32:18Z<p>192.168.1.218: /* Pacing and Structure */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods].<br />
<br />
An example popfile for Rottenburg can be found [https://www.dropbox.com/s/iu84axj1r0vhg0y/mvm&#x20;rottenburg&#x20;reverse&#x20;core&#x20;logic.pop?dl=1rial&#x20;mission here]<br />
<br />
== Pacing and Structure ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
<br />
Once you've identified a map you feel is best for your mission, the next step is to create bot spawns that move progressively closer to the hatch, combined with sub-waves that give players adequate time to move forward and engage in the next sub-wave after it. If each sub-wave and spawn location is balanced correctly, players will not spend the majority of their time in one part of the map. If spawns are too fast and too close together, the mission will be a slog and players will struggle to progress. If new sub-waves are too slow to begin and spawns are spread too far apart, the threat will be too spread out and players can simply ignore the next sub-wave, head straight to the hatch, and let everything come to them. Do your best to strike a balance between these two extremes.<br />
<br />
=== Gate Maps ===<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
=== Engineer Teleporter Types ===<br />
There are 2 separate types of engineer teleporters: The standard teleporter behavior, And engineer bot teleporter behavior. Engineer bot teleporters act as a new spawn point, and will instantly teleport all players to an exit. 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.<br />
<br />
==Getting Started==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''* 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 suffixes (*_start_relay* would not work)'' <br />
<br />
''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 (such as move_rope and keyframe_rope).''<br />
<br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=198Reverse MvM Beginners Guide2021-11-10T16:24:47Z<p>192.168.1.218: /* Lose Condition */</p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods].<br />
<br />
An example popfile for Rottenburg can be found [https://www.dropbox.com/s/iu84axj1r0vhg0y/mvm&#x20;rottenburg&#x20;reverse&#x20;core&#x20;logic.pop?dl=1rial&#x20;mission here]<br />
<br />
== Pacing and Structure ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
<br />
Once you've identified a map you feel is best for your mission, the next step is to create bot spawns that move progressively closer to the hatch, combined with sub-waves that give players adequate time to move forward and engage in the next sub-wave after it. If each sub-wave and spawn location is balanced correctly, players will not spend the majority of their time in one part of the map. If spawns are too fast and too close together, the mission will be a slog and players will struggle to progress. If new sub-waves are too slow to begin and spawns are spread too far apart, the threat will be too spread out and players can simply ignore the next sub-wave, head straight to the hatch, and let everything come to them. Do your best to strike a balance between these two extremes.<br />
<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
==Getting Started==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''* 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 suffixes (*_start_relay* would not work)'' <br />
<br />
''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 (such as move_rope and keyframe_rope).''<br />
<br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own [https://developer.valvesoftware.com/wiki/Game_round_win game_round_win] entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
== Upgrade Station ==<br />
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, use them to cover up holes in the map as well.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=197Reverse MvM Beginners Guide2021-11-10T16:09:53Z<p>192.168.1.218: </p>
<hr />
<div>Reverse MvM refers to a combination of [https://sigwiki.potatomvm.tf/index.php/WaveSchedule 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 [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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop popfile mods].<br />
<br />
An example popfile for Rottenburg can be found [https://www.dropbox.com/s/iu84axj1r0vhg0y/mvm&#x20;rottenburg&#x20;reverse&#x20;core&#x20;logic.pop?dl=1rial&#x20;mission here]<br />
<br />
== Pacing and Structure ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access and periodically opening them. <br />
<br />
Once you've identified a map you feel is best for your mission, the next step is to create bot spawns that move progressively closer to the hatch, combined with sub-waves that give players adequate time to move forward and engage in the next sub-wave after it. If each sub-wave and spawn location is balanced correctly, players will not spend the majority of their time in one part of the map. If spawns are too fast and too close together, the mission will be a slog and players will struggle to progress. If new sub-waves are too slow to begin and spawns are spread too far apart, the threat will be too spread out and players can simply ignore the next sub-wave, head straight to the hatch, and let everything come to them. Do your best to strike a balance between these two extremes.<br />
<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
==Getting Started==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''* 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 suffixes (*_start_relay* would not work)'' <br />
<br />
''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 (such as move_rope and keyframe_rope).''<br />
<br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own game_round_win entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
== Upgrade Station ==<br />
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 use them to cover up holes in the map.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=196Reverse MvM Beginners Guide2021-11-08T02:27:09Z<p>192.168.1.218: </p>
<hr />
<div>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, as well as a deep understanding of our [https://testing.potatomvm.tf/mvm_bigrock_sigdemo.pop custom popfile keyvalues].<br />
<br />
An example popfile for Rottenburg can be found [https://www.dropbox.com/s/iu84axj1r0vhg0y/mvm&#x20;rottenburg&#x20;reverse&#x20;core&#x20;logic.pop?dl=1rial&#x20;mission here]<br />
<br />
== Pacing and Structure ==<br />
[[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg.]]<br />
While the majority of existing mvm maps are suitable, longer and more complex maps are best suited 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, usually by blocking the hatch until the last subwave is ended, or blocking off large regions of the map from access. <br />
<br />
Once you've identified a map you feel is best for your mission, the next step is to create bot spawns that move progressively closer to the hatch, combined with sub-waves that give players adequate time to move forward and engage in the next sub-wave after it. If each sub-wave and spawn location is balanced correctly, players will not spend the majority of their time in one part of the map. If spawns are too fast and too close together, the mission will be a slog and players will struggle to progress. If new sub-waves are too slow to begin and spawns are spread too far apart, the threat will be too spread out and players can simply ignore the next sub-wave, head straight to the hatch, and let everything come to them. Do your best to strike a balance between these two extremes.<br />
<br />
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 [https://developer.valvesoftware.com/wiki/Trigger_timer_door trigger_timer_door] entity using AddOutput, giving you the option to add rewards or enable new mission mechanics when capturing a gate.<br />
<br />
==Getting Started==<br />
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"><br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
}<br />
</syntaxhighlight> <br />
<br />
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<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
corelogic<br />
{<br />
NoFixup 1<br />
logic_auto <br />
{<br />
"origin" "0 0 0" <br />
"targetname" "mainrelay"<br />
"OnMapSpawn" "item_ammopack*,Kill,,0,-1"<br />
<br />
"OnMapSpawn" "wave_start_relay*,AddOutput,OnTrigger spawnbarrier:Disable:0:-1,0,-1"<br />
"OnMapSpawn" "wave_finished_relay*,AddOutput,OnTrigger spawnbarrier:Enable:0:-1,0,-1"<br />
}<br />
}<br />
forcefield<br />
{ <br />
NoFixup 1<br />
func_forcefield<br />
{<br />
"disablereceiveshadows" "0"<br />
"origin" "2724.365479 -2303.941650 -143.139458" //rottenburg spawn<br />
"angles" "0 90 0"<br />
"renderamt" "255"<br />
"rendercolor" "255 255 255"<br />
"renderfx" "0"<br />
"rendermode" "10" //10 = don't render<br />
"TeamNum" "2" //2 for red, 3 for blu<br />
"targetname" "spawnbarrier"<br />
"mins" "-300 -300 -300"<br />
"maxs" "300 300 300" //300x300 hu cube<br />
"StartDisabled" "0"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
''* 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 suffixes (*_start_relay* would not work)'' <br />
<br />
''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.''<br />
<br />
==Lose Condition==<br />
In order to fail the wave when players lose, you will need to add your own game_round_win entity like so:<br />
<br />
<syntaxhighlight lang="cpp"><br />
PointTemplates [$SIGSEGV]<br />
{<br />
LoseRelay <br />
{<br />
NoFixup 1<br />
game_round_win //ignore this<br />
{<br />
"origin" "0 0 0"<br />
"TeamNum" "2"<br />
"targetname" "bots_win_red"<br />
"switch_teams" "0"<br />
"force_map_reset" "1"<br />
"classname" "game_round_win"<br />
}<br />
logic_relay //trigger this<br />
{<br />
"origin" "0 0 0"<br />
"targetname" "redwin_relay"<br />
"OnTrigger" "bots_win_red,RoundWin,,0,-1"<br />
} <br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
It's up to you to decide how you want players to lose. Timers, VIP Escort, and Tanks are popular ways to do so.<br />
<br />
== Upgrade Station ==<br />
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 use them to cover up holes in the map.<syntaxhighlight lang="c++"><br />
<br />
station<br />
{<br />
NoFixup 1<br />
func_upgradestation //upgrade station entity<br />
{<br />
"mins" "-105 -100 0" <br />
"maxs" "105 100 242"<br />
"solid" "0"<br />
}<br />
prop_dynamic //blu upgrade station model, can be found on potato servers<br />
{<br />
"targetname" "upgradestation"<br />
"angles" "0 0 0"<br />
"DisableBoneFollowers" "0"<br />
"disablereceiveshadows" "0"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"model" "models\props_mvm\mvm_upgrade_blu.mdl"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "255"<br />
"renderfx" "0"<br />
"rendermode" "0"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"solid" "0"<br />
"spawnflags" "0"<br />
"origin" "0 0 0"<br />
}<br />
prop_dynamic //invisible collision prop <br />
{<br />
<br />
"targetname" "shopcollision"<br />
"angles" "0 -90 0"<br />
"DisableBoneFollowers" "1"<br />
"disablereceiveshadows" "1"<br />
"model" "models/props_vehicles/train_flatcar_container.mdl"<br />
"disableshadows" "1"<br />
"ExplodeDamage" "0"<br />
"ExplodeRadius" "0"<br />
"fademaxdist" "0"<br />
"fademindist" "-1"<br />
"fadescale" "1"<br />
"MaxAnimTime" "10"<br />
"maxdxlevel" "0"<br />
"MinAnimTime" "5"<br />
"mindxlevel" "0"<br />
"modelscale" "1"<br />
"PerformanceMode" "0"<br />
"pressuredelay" "0"<br />
"RandomAnimation" "0"<br />
"renderamt" "0"<br />
"renderfx" "0"<br />
"rendermode" "10"<br />
"SetBodyGroup" "0"<br />
"skin" "0"<br />
"CollisionGroup" "5"<br />
"solid" "6"<br />
"spawnflags" "0"<br />
"StartDisabled" "0"<br />
"origin" "0 0 0" <br />
} <br />
}<br />
</syntaxhighlight><br />
<br />
__FORCETOC__<br />
[[Category: Tutorials]]</div>192.168.1.218