Maarten ‘Marnamai’ Frooninckx recently released the first chapter of his Half-Life 2 mod DownFall on Steam. It’s been some time since we’ve last seen such critically acclaimed single-player add-on for one of the most beloved series in gaming. In this article, Maarten and I will discuss the mod’s conception and take a look at its ongoing development.
Hello Maarten. Before we get started, could you please tell us a little bit about yourself?
I’m Maarten Frooninckx, better known as “Marnamai” on the internet. I have a background in art and I’m veteran Half-Life 2 mapper. I started out back in 2005, after having discovered that I could make my own Half-Life 2 maps with the Source SDK. Most of my initial work consists out of small test maps that I made for fun. I have been part of a few modding teams, but none of those projects ever reached completion. Is easy to become over-ambitious and underestimate the workload. That’s why a lot of mods fail. So in 2009 I decided to go solo, work on a smaller scope for DownFall and learn what I needed to get it done along the way.
Watch out! We've got a sniper over here.
Wait a minute! You started DownFall in 2009? That’s one hell of a development cycle. Why did it take so long?
Yeah, it took me 8 years to release the first part on Steam. The original goal was to provide a fun expansion for Half-Life 2 which used the Episode 2 setting and learn as much as I could. Later this idea evolved into making DownFall a playable portfolio piece that I could hopefully use to land a job as a Level Designer. The entire project was a huge learning experience for me. The more I learned, the more critical I became. That’s why I’ve completely scrapped the entire project several times over. Actually, what you get to play now is the third version. Of course I haven’t worked on DownFall the entire time. I decided to take a 3D Modeling course so that I could make my own props. I also worked on various other side projects. It wasn’t until the end of 2015, when I started the latest iteration, that I made a serious effort to actually finish the project.
DownFall is based on Episode 2, so it wouldn’t work without using Source 2013. Were you ever tempted to switch to a another version of Source?
I’m a sucker for the way Episode 2 utilizes the post-apocalyptic setting. I love all the old industrial buildings and big outside areas. I especially like the mines and caves. Plus, the gameplay is just spot on. It has a lot of appeal to me so no, I was never tempted. The main problem with using different versions of the Source engine is that you never know if everything keeps working and sorting that out would not only be a monumental task, but also require dedicated coders. Black Mesa’s customized Source engine would be the closest match, but the code they used isn’t publicly available, so I wouldn’t be able to implement the required changes I have planned for the gameplay in chapter 2. I’d also like to implement volumetric lighting which should result in some extra eye candy.
Wait for it!
Speaking of using older technology. You’ve managed to get big open maps and beautiful vistas out of Source. What difficulties did you face?
Using the Source engine has a lot of benefits. There’s a vast library of assets available you can use and BSP is awesome for blocking out something fast and iterate on it. Plus, it has a big user base you can fall back to for questions or help. I know Source has been widely criticized for lacking proper documentation, but most of that has been taken care of by the community. You do face quite a few limitations, so over the years I’ve become real familiar with all the hacks to get things to work. Things like splitting levels if they are too big, how to optimize large outdoor levels, dealing with lightmap problems, hitting entity limits and how to handle leaks.
I really enjoyed the combat encounters in DownFall. You provided enough options and a lot of those felt refreshing to me. How did you go about setting these up?
My levels usually begin with an idea for a setting, location or gameplay encounter. I start doing research by collecting reference material and sketching out layouts or structures. During this process most of the ideas materialize. I’m very fond of creating encounters unique to a setting or environment. You could argue that the setting is only a layer of paint applied to the gameplay, but I prefer to blend setting and gameplay together. I strongly believe that it leads to more unique encounters that really complement each other. When I am in the early phases of a level, I make small prototype maps for gameplay scenario’s or scripted events. It allows me to test the viability and iterate fast. Once I am happy with those, I implement them into the block out (greybox) and test them as often as possible. During these tests, problem areas surface and I start the iterative process of adjusting the block out and gameplay setups to get them just right.
Planning is where it's at.
Another thing that I noticed is that the pacing is really on point. Care to elaborate on that?
I try to space out encounters to give the player some downtime in between combat. I fill that downtime with exploration, puzzles or story exposition. It is very important to have a good difficulty curve to keep things interesting. You start out slow, introduce the enemies and weapons that gradually increase the difficulty over time. You rely on gating to make sure the player knows the mechanics before being allowed to continue. It’s important to be fair but also challenge the player at the same time to provide a sense of progression. Some people have a natural flair for achieving good pacing, but in my case it came from years of playing games. You learn what works by observing, experimenting, testing and listening to feedback.
By now it’s obvious that you’ve learned a lot while making DownFall. Any do’s or don’ts you wish to share with our readers?
- Show, don’t tell. A picture is worth a thousand words. Never have a player press a button without showing what it did. Players need the game to give them feedback on their actions.
- Start testing early and test often. There’s nothing worse than finding a serious problem when you are late in development. Also, listen to feedback because you’ll discover solutions for problems and learn how to improve upon the existing designs.
- Avoid over thinking solutions, the simplest solutions are often the best ones.
- Have a group of trusted designers who you can share ideas with. Bring in other people to test your work for a fresh perspective. It can be hard to hear negative feedback about your work, but do not to get too defensive and try to figure out a way to extract useful data to help you improve.
- Develop a personal discipline to work on your levels every day, not just when you feel like it and don’t be too ambitious. Aim for something you can actually achieve and take it from there.
Eat lead Combine!
Thank you for sharing that. I’m also wondering why you opted for a Steam release? Having a bigger audience is a given, but were there any other reasons?
Yeah, it has a huge install base and that means you can reach a bigger pool of potential players. Far more than any traditional modding site could reach. Of course, you still rely on those websites and social media to raise awareness and generate interest. But using Steam also allows you to use beta branches for playtesting and send out updates without having to worry if everybody is using the same version of the mod. Plus, you have the Steam community features which bring you much closer to your audience.
Congratulations on the successful release. Before we finish this interview, I have to know, did you really do everything yourself?
Pretty much, yeah. All of the level design, additional models, animations, textures, Steam Greenlight campaign and the Steam release build are done by me. DownFall mostly uses default assets as I prefer to focus on the level design and only create assets when their role is pivotal in the design. I did bring in a Foley Artist, who’s is also a Composer, to make some new sounds and ambient tracks. For the next chapters I’m working together with two programmers, we have some new gameplay features planned and some bugged entities require fixing.
I’m very satisfied with the reception by the community. During the Greenlight campaign DownFall reached the third rank and was Greenlit in just over 12 days with a Yes/No ratio of 76%. The accumulated reviews resulted in a ‘very positive’ rating on the Steam Store with a 97% approval rating.
A little teaser of things to come.
That’s an amazing job. Thank you for sharing this with us. I enjoyed DownFall, especially the funny touch on the end and I can’t wait to play more. To our readers, be sure to check out DownFall on Steam and leave a review.