SigMod - User contributions [en-gb]

https://sigwiki.potato.tf/api.php?action=feedcontributions&feedformat=atom&user=Braindawg SigMod - User contributions [en-gb] 2026-06-05T13:25:22Z User contributions MediaWiki 1.40.0 https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7574 Main Page 2025-07-02T20:43:39Z

<p>Braindawg: /* Misc Resources */</p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> == Vanilla Tutorials ==<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons]</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Installing_on_Windows_with_WSL&diff=7571 Installing on Windows with WSL 2025-04-18T20:54:27Z

<p>Braindawg: /* Manual installation */</p> <hr /> <div>== Easy installation script ==<br /> Right click this link and select save link as:<br /> <br /> https://raw.githubusercontent.com/rafradek/sigsegv-mvm/master/windows_install_wsl.bat<br /> <br /> Run the downloaded bat file and follow the instructions printed in console<br /> <br /> == Manual installation ==<br /> Run the bat file and follow instructions printed in console<br /> <br /> Based on guides: https://docs.microsoft.com/en-us/windows/wsl/install-win10 https://wiki.teamfortress.com/wiki/Linux_dedicated_server<br /> <br /> Open PowerShell as administrator, then execute those commands<br /> dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart<br /> dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart<br /> <br /> Now restart your PC. After that, execute another PowerShell command<br /> wsl --set-default-version 2<br /> echo [wsl2] memory=2GB > $env:USERPROFILE/.wslconfig<br /> Open Microsoft Store and install Ubuntu. Launch Ubuntu from start menu. Fill in username and password info when asked. Install required packages by entering those commands into the window:<br /> sudo dpkg --add-architecture i386<br /> sudo apt-get update<br /> sudo apt-get install lib32z1 libncurses5:i386 libbz2-1.0:i386 lib32gcc-s1 lib32stdc++6 libtinfo5:i386 libcurl3-gnutls:i386 libsdl2-2.0-0:i386<br /> sudo ufw disable<br /> Those Ubuntu commands will install and update server in ~/hlserver/hlserver:<br /> mkdir ~/hlserver<br /> cd ./hlserver<br /> wget https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz<br /> tar zxf steamcmd_linux.tar.gz<br /> ./steamcmd.sh +login anonymous +force_install_dir ./hlserver +app_update 232250 +quit<br /> You can browse server files in windows explorer with this Ubuntu command:<br /> explorer.exe ~/hlserver/hlserver<br /> If you have an existing windows server installation you can copy server files here.<br /> <br /> Install a linux version of sourcemod and mm: source in this location<br /> <br /> Unpack all sigsegv archive contents into tf directory<br /> <br /> Create a server starting file with Ubuntu commands:<br /> echo "#!/bin/sh" > ~/startserver.sh<br /> echo "~/hlserver/hlserver/srcds_run +map bigrock +maxplayers 32 -enablefakeip" >> ~/startserver.sh<br /> chmod u+x ~/startserver.sh<br /> Run server with Ubuntu command:<br /> ~/startserver.sh<br /> Or, to run a server from windows CMD / PowerShell:<br /> wsl ~/startserver.sh<br /> You should check your linux server IP with a command executed in PowerShell. You can use this IP to connect to your server from this Windows PC. IP will change with every system reset:<br /> wsl hostname -I<br /> The section below tells how to connect to the server using your LAN or public IP if available<br /> <br /> <br /> You can make the server autostart by adding a scheduled task in Task Scheduler, on login condition, running wsl as a program with ~/startserver.sh as an argument.<br /> <br /> =Make the server accessible from the Internet without -enablefakeip=<br /> Download a program named [http://aluigi.altervista.org/mytoolz/sudppipe.zip sudppipe] (The browser may mark this file as unsafe so you might have to right click and select Save link As)<br /> <br /> Unpack the downloaded archive, then create tf2portpipe.bat file in the unpacked directory alongside sudppipe.exe. Replace port value with your own server port. The port should not be in use by any other program (TF2 client often binds to port 27015).<br /> @ECHO off<br /> <br /> SET port=27015<br /> <br /> FOR /F "tokens=* USEBACKQ" %%F IN (`wsl hostname -I`) DO (<br /> SET ip=%%F<br /> )<br /> %~dp0/sudppipe.exe -q -b 0.0.0.0 %ip% %port% %port%<br /> Run the bat file. If you wish to get rid of the console window, add a run on system startup scheduled task, with run whether user is logged on or not option, launching this script file as a program.<br /> [[Category:Tutorials]]</div>

Braindawg https://sigwiki.potato.tf/index.php?title=CTFFlameManager&diff=7570 CTFFlameManager 2025-03-28T16:44:27Z

<p>Braindawg: </p> <hr /> <div>== Overview ==<br /> TBD<br /> <br /> '''Source location : [https://github.com/ValveSoftware/source-sdk-2013/blob/master/src/game/shared/tf/tf_flame.cpp /game/server/tf/tf_flame.cpp]'''<br /> <br /> '''Linked entity : [https://developer.valvesoftware.com/wiki/tf_flame_manager tf_flame_manager]'''<br /> <br /> ==[[Classes|Class Structure]]==<br /> *'''[[CBaseEntity]]'''<br /> **'''[[CTFPointManager]]'''<br /> ***'''CTFFlameManager'''<br /> <br /> == SendProps ==<br /> {| class="wikitable sortable mw-collapsible mw-collapsed" style="margin: 0 auto; width: 100%; padding: 0;"<br /> |+CTFFlameManager <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_hWeapon'''<br /> | style="width: 15%;" |Integer<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_hAttacker'''<br /> | style="width: 15%;" |Integer<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flSpreadDegree'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flRedirectedFlameSizeMult'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flFlameStartSizeMult'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flFlameEndSizeMult'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flFlameIgnorePlayerVelocity'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flFlameReflectionAdditionalLifeTime'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flFlameReflectionDamageReduction'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_iMaxFlameReflectionCount'''<br /> | style="width: 15%;" |Integer<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_nShouldReflect'''<br /> | style="width: 15%;" |Integer<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flFlameSpeed'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flFlameLifeTime'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flRandomLifeTimeOffset'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flFlameGravity'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flFlameDrag'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_flFlameUp'''<br /> | style="width: 15%;" |Float<br /> | style="width: 35%;" |<br /> |-<br /> | style="width: 50%;" |'''m_bIsFiring'''<br /> | style="width: 15%;" |Boolean<br /> | style="width: 35%;" |<br /> |}</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Useful_Code_Files&diff=7569 Useful Code Files 2025-03-28T16:39:11Z

<p>Braindawg: use official sdk links</p> <hr /> <div>* [https://github.com/ValveSoftware/source-sdk-2013/blob/master/src/public/const.h const.h]<br /> * [https://github.com/ValveSoftware/source-sdk-2013/blob/master/src/game/shared/tf/tf_shareddefs.h tf_shareddefs.h]<br /> * [https://github.com/ValveSoftware/source-sdk-2013/blob/master/src/game/shared/tf/tf_shareddefs.cpp tf_shareddefs.cpp]<br /> * [https://github.com/ValveSoftware/source-sdk-2013/blob/master/src/public/dt_common.h dt_common.h]<br /> <br /> SendProps (CNetwork*) are defined in entity header files (.h); DataMaps (DEFINE*) are defined in the entity code files (.cpp).<br /> <br /> (Some entities will have a copy of the same variable as both a SendProp and DataMap.)<br /> * [https://github.com/ValveSoftware/source-sdk-2013/blob/master/src/public/datamap.h datamap.h]<br /> * [https://github.com/ValveSoftware/source-sdk-2013/blob/master/src/public/networkvar.h networkvar.h]</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7565 Main Page 2025-03-09T19:24:28Z

<p>Braindawg: </p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> == Vanilla Tutorials ==<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/945446119842938880/Pop_File_Highlighter.xml Vanilla + Sigmod Syntax Highlighter for Notepad++ (slightly outdated)]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons]</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7564 Main Page 2025-03-09T19:24:21Z

<p>Braindawg: </p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> <br /> hkl;hjkl <br /> == Vanilla Tutorials ==<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/945446119842938880/Pop_File_Highlighter.xml Vanilla + Sigmod Syntax Highlighter for Notepad++ (slightly outdated)]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons]</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7563 Main Page 2025-03-09T19:24:04Z

<p>Braindawg: </p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> == Vanilla Tutorials ==<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/945446119842938880/Pop_File_Highlighter.xml Vanilla + Sigmod Syntax Highlighter for Notepad++ (slightly outdated)]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons]</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7562 Main Page 2025-03-09T19:22:02Z

<p>Braindawg: </p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> <br /> sthsfghsgh <br /> == Vanilla Tutorials ==<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/945446119842938880/Pop_File_Highlighter.xml Vanilla + Sigmod Syntax Highlighter for Notepad++ (slightly outdated)]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons]</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7561 Main Page 2025-03-09T19:17:53Z

<p>Braindawg: </p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> == Vanilla Tutorials ==<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/945446119842938880/Pop_File_Highlighter.xml Vanilla + Sigmod Syntax Highlighter for Notepad++ (slightly outdated)]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons]</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7560 Main Page 2025-03-09T19:17:40Z

<p>Braindawg: </p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> == Vanilla Tutorials ==<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/945446119842938880/Pop_File_Highlighter.xml Vanilla + Sigmod Syntax Highlighter for Notepad++ (slightly outdated)]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons]<br /> <br /> fggadfgerag</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7559 Main Page 2025-03-09T19:16:52Z

<p>Braindawg: </p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> == Vanilla Tutorials ==<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/945446119842938880/Pop_File_Highlighter.xml Vanilla + Sigmod Syntax Highlighter for Notepad++ (slightly outdated)]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons] (War Paints do not work in vanilla)</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7558 Main Page 2025-03-09T19:16:39Z

<p>Braindawg: </p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> <br /> Test <br /> == Vanilla Tutorials ==<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/945446119842938880/Pop_File_Highlighter.xml Vanilla + Sigmod Syntax Highlighter for Notepad++ (slightly outdated)]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons] (War Paints do not work in vanilla)</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7557 Main Page 2025-03-09T19:05:38Z

<p>Braindawg: </p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> == Vanilla Tutorials ==<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/945446119842938880/Pop_File_Highlighter.xml Vanilla + Sigmod Syntax Highlighter for Notepad++ (slightly outdated)]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons] (War Paints do not work in vanilla)</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7556 Main Page 2025-03-09T19:05:27Z

<p>Braindawg: </p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> <br /> Test edit<br /> == Vanilla Tutorials ==<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/945446119842938880/Pop_File_Highlighter.xml Vanilla + Sigmod Syntax Highlighter for Notepad++ (slightly outdated)]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons] (War Paints do not work in vanilla)</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7555 Main Page 2025-03-09T19:01:42Z

<p>Braindawg: </p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> <br /> <br /> == Vanilla Tutorials ==<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/945446119842938880/Pop_File_Highlighter.xml Vanilla + Sigmod Syntax Highlighter for Notepad++ (slightly outdated)]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons] (War Paints do not work in vanilla)</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Main_Page&diff=7554 Main Page 2025-03-09T18:58:43Z

<p>Braindawg: Reverted edits by 172.68.174.11 (talk) to last revision by 141.101.109.162</p> <hr /> <div>Welcome to Potato's Custom MvM Wiki. Here you can find information about how to make your own MvM missions, resources for mission making, and information on our custom server mods. <br /> <br /> <br /> == Vanilla Tutorials ==<br /> * [https://www.youtube.com/watch?v=Z98ei5JLS_g&t=253s Basic Tutorial on how to make popfiles]<br /> *[https://drive.google.com/file/d/1N-DBsZiKiqjD4OSQH2bRLsYq1Sq4gHhA/view?usp=sharing Titanium Tank Mission Making Guide]<br /> * [https://steamcommunity.com/sharedfiles/filedetails/?id=1451627628 Canteen Crasher Mission Making Guide]<br /> * [https://drive.google.com/file/d/1rwcsiZJtKLcbfSBR3o-seQIxq_tTjzPJ/view?usp=sharing Madness vs Machines Expert Mission Making Guide]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=1911160067 Advanced Popfile Tricks]<br /> *[[Attribute information|Misc. documentation on certain attributes]]<br /> <br /> == [[:Category:Tutorials|Modded Tutorials]] ==<br /> <br /> * [[Create custom item decals]]<br /> *[https://steamcommunity.com/sharedfiles/filedetails/?id=2289315026 Introduction to Point Template Spawners]<br /> * [https://sigwiki.potato.tf/index.php/Design_PointTemplate_with_hammer_map_editor Designing your Point Templates in Hammer]<br /> * [[Reverse MvM Beginners Guide]]<br /> * [https://sigwiki.potato.tf/index.php/Installing_on_Windows_with_WSL Installing Sigmod on Windows with WSL]<br /> == [[:Category:Templates|Templates]] ==<br /> <br /> * [[Spider Tank]]<br /> * [[Modular Gatebots]]<br /> * [[Vaccinator Tank]]<br /> * [[Small Turret Tanks|Small Turret Tank]]<br /> *[[Rotating Shield]]<br /> *[[Timers]]<br /> == [[:Category:Popfile Additions|Custom popfile additions]] ==<br /> <br /> * [[WaveSchedule]]<br /> * [[Wave]]<br /> * [[WaveSpawn]]<br /> * [[TFBot]]<br /> == [[:Category:Misc Additions|Miscellaneous additions]] ==<br /> <br /> * [[Additions to existing entities]]<br /> *[[Entity Modules]]<br /> * [[Custom Entities]]<br /> * [[Sound Additions]]<br /> * [[List of custom attributes]]<br /> *[[List of modifications to vanilla attributes]]<br /> *[[Expressions]]<br /> *[[Lua|Lua Scripting]]<br /> == [[:Category:References|References]] ==<br /> <br /> * [https://github.com/rafradek/sigsegv-mvm/blob/master/scripts/mvm_bigrock_sigdemo.pop Demonstrative SigMod mission]<br /> * [[List of item definitions]]<br /> * [https://csrd.science/misc/econ-tf/items.html Complete list of item names] (internal and display)<br /> * [https://wiki.teamfortress.com/wiki/List_of_item_attributes List of vanilla item attributes]<br /> * [https://wiki.teamfortress.com/wiki/Cheats#addcond List of AddCond values]<br /> * [https://gist.github.com/sigsegv-mvm/9ce39744fde2aa4c6156 Documentation of all vanilla popfile keyvalues]<br /> * [[Unusual effect IDs]]<br /> * [https://github.com/sigsegv-mvm/population Population files used by Valve missions]<br /> * [[Entity Properties]]<br /> <br /> == Misc Resources ==<br /> <br /> * [https://testing.potato.tf/icons.html Wavebar Icon Repository] <br /> * [https://marketplace.visualstudio.com/items?itemName=PotatoMvM.popfile-language-support Vanilla Popfile Syntax Highligher for VSCode]<br /> * [https://www.dropbox.com/s/1w6v8udq74x2gy3/popfile.tmLanguage.json?dl=0 Sigmod Syntax Highlighter for VSCode]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/945446119842938880/Pop_File_Highlighter.xml Vanilla + Sigmod Syntax Highlighter for Notepad++ (slightly outdated)]<br /> * [https://cdn.discordapp.com/attachments/480416823695638578/933769904778264686/bettericons.zip Fixed valve icons] <br /> * [https://github.com/Mince64/Popfile-Modifier/tree/main Wavebar Generator]<br /> * [https://github.com/NPsim/P3/releases/tag/2.1.0 Standalone Popfile Parser]<br /> * [https://docs.google.com/document/d/e/2PACX-1vR4mcdvfPIib0sfEtzhv_l6lz42ox6xmFr4jxVYceSxL8na9fkrxVkTFz5qVbl1qV3A4VzY-t7CJ-f8/pub War Paint IDs for Decorated weapons] (War Paints do not work in vanilla)</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=231 Reverse MvM Beginners Guide 2021-12-09T03:51:48Z

<p>Braindawg: /* 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>

Braindawg https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=230 Reverse MvM Beginners Guide 2021-12-08T16:50:15Z

<p>Braindawg: /* Maps */</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, 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>

Braindawg https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=229 Reverse MvM Beginners Guide 2021-12-08T16:41:41Z

<p>Braindawg: </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 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>

Braindawg https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=184 Reverse MvM Beginners Guide 2021-10-28T06:45:19Z

<p>Braindawg: /* Pacing and Structure */</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.<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 /> ==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 /> == 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 maps that have more complex paths to the hatch are best suited for reverse. Bigrock, Mannhattan, and Rottenburg are examples of valve maps where it is relatively easy to stop players from blast jumping directly to hatch, 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 the map and camping at the hatch, usually by blocking the hatch until the last subwave is ended and/or adding very strong defenses. <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 further towards the hatch that are spread far apart, 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 /> __FORCETOC__</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=183 Reverse MvM Beginners Guide 2021-10-28T06:43:38Z

<p>Braindawg: /* Pacing and Structure */</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.<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 /> ==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 /> == Pacing and Structure ==<br /> [[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg. Players would take the top path in this example]]<br /> While the majority of existing mvm maps are suitable, longer maps that have more complex paths to the hatch are best suited for reverse. Bigrock, Mannhattan, and Rottenburg are examples of valve maps where it is relatively easy to stop players from blast jumping directly to hatch, 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 the map and camping at the hatch, usually by blocking the hatch until the last subwave is ended and/or adding very strong defenses. <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 further towards the hatch that are spread far apart, 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 /> __FORCETOC__</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=182 Reverse MvM Beginners Guide 2021-10-28T06:42:23Z

<p>Braindawg: /* Pacing and Structure */</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.<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 /> ==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 /> == Pacing and Structure ==<br /> [[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg. Players would take the top path in this example]]<br /> While the majority of existing mvm maps are suitable, longer maps that have more complex paths to the hatch are best suited for reverse. Bigrock, Mannhattan, and Rottenburg are examples of valve maps where it is relatively easy to stop players from blast jumping directly to hatch, 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 the map and camping at the hatch, usually by blocking the hatch until the last subwave is ended and/or adding very strong defenses. <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 further towards the hatch that are spread far apart, 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. 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 /> __FORCETOC__</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=181 Reverse MvM Beginners Guide 2021-10-28T06:40:22Z

<p>Braindawg: /* Pacing and Structure */</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.<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 /> ==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 /> == Pacing and Structure ==<br /> [[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg. Players would take the top path in this example]]<br /> While the majority of existing mvm maps are suitable, longer maps that have more complex paths to the hatch are best suited for reverse. Bigrock, Mannhattan, and Rottenburg are examples of valve maps where it is relatively easy to stop players from blast jumping directly to hatch, 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 the map and camping at the hatch, usually by blocking the hatch until the last subwave is ended and/or adding very strong defenses. <br /> <br /> Once you've identified a map you feel is best for your mission, the best way to achieve good pacing is to have bot spawns that move progressively further towards the hatch that are spread far apart, 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. 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 /> __FORCETOC__</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=180 Reverse MvM Beginners Guide 2021-10-28T06:39:48Z

<p>Braindawg: /* Pacing and Structure */</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.<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 /> ==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 /> == Pacing and Structure ==<br /> [[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg. Players would take the top path in this example]]<br /> While the majority of existing mvm maps are suitable, longer maps that have more complex paths to the hatch are best suited for reverse. Bigrock, Mannhattan, and Rottenburg are examples of valve maps where it is relatively easy to stop players from blast jumping directly to hatch, 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 the map and camping at the hatch, usually by blocking the hatch until the last subwave is ended and/or adding very strong defenses. <br /> <br /> Once you've identified a map you feel is best for your mission, the best way to achieve good pacing is to have bot spawns that move progressively further towards the hatch that are spread far apart, 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 is balanced and timed 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. 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 /> __FORCETOC__</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=179 Reverse MvM Beginners Guide 2021-10-28T06:35:03Z

<p>Braindawg: /* Pacing and Structure */</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.<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 /> ==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 /> == Pacing and Structure ==<br /> [[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg. Players would take the top path in this example]]<br /> While the majority of existing mvm maps are suitable for reverse missions, longer maps that have more complex paths to the hatch which cannot be immediately bypassed by blast jumping are best suited for reverse. Bigrock, Mannhattan, and Rottenburg are examples of valve maps where it is relatively easy to stop players from jumping directly to hatch, 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 the map and camping at the hatch, usually by blocking the hatch until the last subwave is ended and/or adding very strong defenses. <br /> <br /> <br /> <br /> Once you've identified a map you feel is best for your mission, the best way to achieve good pacing is to have bot spawns that move progressively further towards the hatch at a steady rate, combined with sub-waves that give players adequate time to move forward and engage in the next sub-wave after it. Think of each sub-wave and custom spawn location you create as a new challenge that players need to complete before moving to the next location. If each sub-wave is balanced and timed 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, camp at the hatch with the bomb, and let everything come to them. Do your best to strike a balance between these two extremes.<br /> <br /> <br /> Maps with gates are very useful for structuring your waves. 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 as well, adding rewards or enabling new mission mechanics when capturing the gate.<br /> <br /> __FORCETOC__</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=178 Reverse MvM Beginners Guide 2021-10-28T06:34:44Z

<p>Braindawg: /* Pacing and Structure */</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.<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 /> ==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 /> == Pacing and Structure ==<br /> [[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg. Players would take the top path in this example]]<br /> The map you select and pacing of your waves are the most integral part of making an enjoyable reverse mission. <br /> <br /> <br /> While the majority of existing mvm maps are suitable for reverse missions, longer maps that have more complex paths to the hatch which cannot be immediately bypassed by blast jumping are best suited for reverse. Bigrock, Mannhattan, and Rottenburg are examples of valve maps where it is relatively easy to stop players from jumping directly to hatch, 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 the map and camping at the hatch, usually by blocking the hatch until the last subwave is ended and/or adding very strong defenses. <br /> <br /> <br /> Once you've identified a map you feel is best for your mission, the best way to achieve good pacing is to have bot spawns that move progressively further towards the hatch at a steady rate, combined with sub-waves that give players adequate time to move forward and engage in the next sub-wave after it. Think of each sub-wave and custom spawn location you create as a new challenge that players need to complete before moving to the next location. If each sub-wave is balanced and timed 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, camp at the hatch with the bomb, and let everything come to them. Do your best to strike a balance between these two extremes.<br /> <br /> <br /> Maps with gates are very useful for structuring your waves. 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 as well, adding rewards or enabling new mission mechanics when capturing the gate.<br /> <br /> __FORCETOC__</div>

Braindawg https://sigwiki.potato.tf/index.php?title=Reverse_MvM_Beginners_Guide&diff=177 Reverse MvM Beginners Guide 2021-10-28T06:33:15Z

<p>Braindawg: /* Pacing and Structure */</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.<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 /> ==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 /> == Pacing and Structure ==<br /> [[File:Rotten.png|thumb|Custom spawn and sub-wave layout example for Rottenburg. Players would take the top path in this example]]<br /> The pacing of your waves is the most integral part of making an enjoyable reverse mission. Specifically: map selection, spawn locations, spawn timing, and sub-wave duration. <br /> <br /> <br /> While the majority of existing mvm maps are suitable for reverse missions, longer maps that have more complex paths to the hatch which cannot be immediately bypassed by blast jumping are best suited for reverse. Bigrock, Mannhattan, and Rottenburg are examples of valve maps where it is relatively easy to stop players from jumping directly to hatch, 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 the map and camping at the hatch, usually by blocking the hatch until the last subwave is ended and/or adding very strong defenses. <br /> <br /> <br /> Once you've identified a map you feel is best for your mission, the best way to achieve good pacing is to have bot spawns that move progressively further towards the hatch at a steady rate, combined with sub-waves that give players adequate time to move forward and engage in the next sub-wave after it. Think of each sub-wave and custom spawn location you create as a new challenge that players need to complete before moving to the next location. If each sub-wave is balanced and timed 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, camp at the hatch with the bomb, and let everything come to them. Do your best to strike a balance between these two extremes.<br /> <br /> <br /> Maps with gates are very useful for structuring your waves. 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 as well, adding rewards or enabling new mission mechanics when capturing the gate.<br /> <br /> __FORCETOC__</div>

Braindawg https://sigwiki.potato.tf/index.php?title=File:Rotten.png&diff=176 File:Rotten.png 2021-10-28T05:37:26Z

<p>Braindawg: </p> <hr /> <div>custom spawn and sub-wave layout example for rottenburg, players take the top path on Wave 1 in this example</div>

Braindawg