Is there any guide for mvm map making?
- Thread starter BenCo
- Start date
Three Million
L4: Comfortable Member
- Jul 2, 2015
- 197
- 75
http://tf2maps.net/threads/guide-lets-talk-about-mann-vs-machine.20439/
A bit of an oldie, but it's a good analysis of layout and some of the specialty entities, though not really the creation basics. For that, I'm sure you need at least this.
A bit of an oldie, but it's a good analysis of layout and some of the specialty entities, though not really the creation basics. For that, I'm sure you need at least this.
Last edited:
That guide however, even with some outdated info still has the best start since it doesnt realy talk about the entity technical part, but about the design of the map itself. And this is still where most people see issues with. Understanding logic on why a map is shaped a certain way is vital for mvm.
Not only that, but the spine theory is still valid in ALL valve maps. Even though recent maps have a less visible one.
For mannhattan: the containers show a clear spine of the map which is why the teleporters are often placed there, the spine has the best access to all sections on the map.
For rottenburg: rather than a single spine its made out of many smaller ones. The front shows the baricade section which is a spine to guide bots around it. the tank destroys this spine. the first next one is just outside that tunnel, and the remaining spines are based on the path the bots take. If they take the lower one the bridge can be used as a spine, if they take the higher path, the spine is placed slightly back on the side. And then when they reach the hatch they have to make a 180 degree turn, its not a spine, but does effectively the same.
A spine does 1 key feature that players use in their defence. it provides cover and makes bots cluster. You can make nearly every block a spine by just taking care of navigation paths.
Also, mapping technical its best to grab a decompile (i would recommend bigrock because it contains engineers aswel, and it still has the simplest shape for an mvm map - a large single spine), and the vmf of mvm_example for entity work to set up a map in its basics.
Learn it the hard way in notepad++. To make it better readable set the syntax highlighting to C++.
Not only that, but the spine theory is still valid in ALL valve maps. Even though recent maps have a less visible one.
For mannhattan: the containers show a clear spine of the map which is why the teleporters are often placed there, the spine has the best access to all sections on the map.
For rottenburg: rather than a single spine its made out of many smaller ones. The front shows the baricade section which is a spine to guide bots around it. the tank destroys this spine. the first next one is just outside that tunnel, and the remaining spines are based on the path the bots take. If they take the lower one the bridge can be used as a spine, if they take the higher path, the spine is placed slightly back on the side. And then when they reach the hatch they have to make a 180 degree turn, its not a spine, but does effectively the same.
A spine does 1 key feature that players use in their defence. it provides cover and makes bots cluster. You can make nearly every block a spine by just taking care of navigation paths.
Also, mapping technical its best to grab a decompile (i would recommend bigrock because it contains engineers aswel, and it still has the simplest shape for an mvm map - a large single spine), and the vmf of mvm_example for entity work to set up a map in its basics.
It recommends mvm.tf, that automaticly makes it horrible. mvm.tf makes a popfile a huge mess. And its also well known to make them even that corrupt to crash the server.
Learn it the hard way in notepad++. To make it better readable set the syntax highlighting to C++.
Last edited:
Finally found that layout guide! Thanks