Sponsored By

Level Design Lesson 7: Combat Congestion and Traffic

Today's lesson covers the importance of having multiple paths and being able to distribute players amongst the paths to keep an enjoyable and controllable experience for your audience.

Raymond Benefield, Blogger

September 7, 2010

3 Min Read

[This was originally posted on my personal blog www.reachingperfection.com]

[Forge Lessons is a level design series that I have written for the halo forge (the simplistic in-game level editor) communities. While it is tailored towards Halo multiplayer map design I feel that it covers general level design very well. I would love everyone's opinions on how these lessons can translate into other games and genres like the Call of Duty series, the Unreal Series, RTS games, platformer games, etc.]

Have you ever taken the time to wonder why most maps are designed to have multiple paths? Most people just blindly build their maps to have multiple paths because it has become a simple standard base rule that everyone follows. I feel that it is important to completely understand why standard practices exist in the industry. Take the time to imagine a Halo map with only one path between two flag points. Everyone just ends up clashing over and over again in the center right? This is a phenomenon that I like to call Combat Congestion.

What’s wrong with it?

So what’s wrong with everyone running into each other and just shooting to try to kill someone? Nothing if that is what you want. It creates simplistic gameplay because it removes the skill of out-smarting your opponent based on path selection and cutting him off. Not only that, but there is no order to 8 people running at each other at once. It is hard for players to choose their target so it ends up being chance that you only get shot by one person or the whole other team at once. Dying to 4 people at once happens a lot faster than just 1 or 2 guys. You end up having no time at all to plan out your attack and if you don’t have any time at all to use skill or strategy then what fun is that?

The concept of Traffic

The basic concept of traffic is an observance of how players are spread out on your map. If you have too many players traversing one area then maybe you should spread them out a little more. The more players that go through an area the higher chance of combat congestion happening. And as discussed, this is something that we need to avoid as it is no fun to the player.

Avoiding the chaos

So having one path can cause combat congestion, that’s pretty simple to understand. Well having multiple paths around the map isn’t magically going to solve this problem. You have to use a variety of Path Manipulation techniques in order to get your players to spread out and to reduce the chance of combat congestion happening on your map. A ton of tricks exist for what I call controlling traffic, and you’ve already learned some of them. Incentives can be used to force players to take paths that players normally wouldn’t. Deterrents can be used to discourage players from taking commonly traversed paths. But Incentives and Deterrents can’t just exist on the map. They end up having no effects on a player if player is unaware of them being on the map. Remember that talk on Knowledge is Power? You have to use techniques like Eye Catching, Area Introduction, Color Contrast, and Screen Real Estate. But in order to understand those techniques and fully apply them you have to be able to think in Perspectives and observe Perspective Variance. So again why do all of these things? Because combat congestion is one of those things that will cause a bad First Impression for your map, and we already learned how bad that can be. It is one of those things that are just frustrating to experience because nobody enjoys just running in and dying. They enjoy using their skills. This was your first combination lesson where I tie everything that you’ve learned so far and everything that you will learn together to help you grasp the bigger picture. Hope you enjoyed it.

Read more about:

Blogs
Daily news, dev blogs, and stories from Game Developer straight to your inbox

You May Also Like