Making your own mvm waves

[Simulacron]

I want to create my own mvm waves, however all tutorials that I find use websides like http://mvm.tf/
I heard they create a big mess, so I don't want to use them. My problem is that I don't really know what to do know, I looked a t the mvm_example.pop but it isn't explaining everything. And where can I find the robot_standart.pop and robot_giant.pop, so I know which special robots are available?

 

[SnickerPuffs]

I'd just use mvm.tf . It's actually not that hard, and I've never heard of it creating a "big mess", as you put it.

 

[FortyTwo]

https://github.com/whayay/def_tf2_hud/tree/master/scripts/population
This link contains all of the official MVM waves including robot_standard.pop, robot_giant.pop and robot_gatebot.pop
I think the mvm_example.pop had explained the basics very well (the // means that it just a annotation).
How I've learned to make MVM missions is that I've take a look at some of the official waves to see how they are done. It was not hard to learn since that the words are really simple to understand.

 

[UKCS-Alias]

the robot standard and giant files (there also is a gatebot one for mannhattan, but thats not recommended for beginners). both are in the gcf files. You might be unable to directly open them and might need something like gcfscape. If im right they are directly next to the example popfile in the popfile list, maybe a folder up (the same folder as where all missions are placed).

Since i already wanted to make such guide but never bothered to im made a quick one that at least should get you going into understanding what a popfile does:
http://tf2maps.net/threads/a-short-guide-to-explain-popfiles-requires-example-pop.28298/

I'd just use mvm.tf . It's actually not that hard, and I've never heard of it creating a "big mess", as you put it.

Its because you cant read the popfile contents. mvm.tf is known to add alot of attributes and templates that arent used or are already defined earlier. This part is a mess in reading and worse when debugging. Your popfile wouldnt update properly once valve updates theirs. in some cases breaking the mission. Good luck finding the bug when mvm.tf cant even read your popfile anymore as it broke with it once they update it, or maybe it generates broken files. Its unreliable.
Most popfile makers will instantly close and delete your popfile once noticing its from mvm.tf. They wont even bother fixing your mess.

If you want to make a good mission, knowing what you do is a must. And understanding the popfile itself is a key part. mvm.tf isnt even failproof against deadlocks, doesnt let you learn anything about what certain attributes do.

mvm.tf is the same as trying to create a map in hammer using sketchup and porting that file directly. It can be used for a quick mockup, but it NEVER should be the final file for the mission or even the first alpha ment for playing.