Development

To read Part 1 of our Level Design development post, click here.

Keeping Things Fresh While Creating a Monster

Kyle On Mechanics

One of the obstacles for designing levels in BattleBlock Theater was creating mechanics–which are interactive level sequences–to keep the game new and exciting. We always wanted there to be something new in the next level; something always keeping the player on their toes and saying, “Oh, wow! That was cool!” To do this, we would set a broad goal for the Campaign or level (e.g. “We want Campaign 4 to be boulder-centric“) and work around our ideas and layouts. This initial focused mindset would force us to use block types that we might have been underusing or create sequences with block combinations we would not have tried before.

 

Creating new mechanics didn’t always happen organically while designing campaign levels though. Every level in the game didn’t go straight from brain to scrain… err, screen. Sometimes the idea would come to us while we were just playing through our already created levels; sometimes we would come up with something while messing around in the level editor. This created a fairly non-linear approach to our design process because we would come up with something really cool and then have to go back through the campaign, teach the mechanic, and expand upon it.

 

 

Personally, I love creating new mechanics. Nothing brought me more joy in BattleBlock Theater than creating something that hadn’t been done before. From a superficial perspective, BattleBlock Theater only has a couple handfuls of block types to choose from, but, if you think about it, there are a little less than 38^1200 block combinations available in the game. I said think about it. Mind=Blown. ==^o.o^===k

 

 

However, not all of our ideas came off the cuff. There were periods where I would lack inspiration and bang my head into my computer desk as if an idea might fall out (note to reader: it doesn’t work). Luckily, I devised some techniques to help through this process that can translate into any form of game/level design. Here they are (Keep them secret. Keep them safe):

 

1. Critical Analysis: This is what I call the process of going through everything we have—the existing sequences/combinations of blocks we already used—and figuring out what we have available. This was important to ensure a lack of redundancy. If I noticed there were no mechanics in the game that didn’t require you to use the wings with boulders, I’d take note and use that as inspiration to create a mechanic that did use that block combination. This process often had an overlap with my other techniques.

 

2. Building from a Base: This is where I would take an existing sequence or mechanic and I would expand upon it. This could be changing the focused mechanic to another block type (e.g. changing a saw on ice to a saw on gum blocks), turning the section into a CoOp sequence, or simplifying the existing mechanic to place earlier in the campaign. This led to a lot of playthroughs of the game to ensure we didn’t miss anything; the design process wasn’t always from the bottom up.

 

3. Getting Uncomfortable: When the previous two techniques weren’t enough or additional inspiration was needed, I would put myself into awkward scenarios to force myself to create something new. Often, this was sitting uncomfortably close to Ryan or standing on my head while trying to design. Most of the time, those didn’t work, so I would force myself to design in parameters that were extreme in verticality, opposite of our current norm, or a unique take on an existing process. This led to some very unique and fun level design which was critical to our design process.

 

This is just a fraction of my design process and each of us designers has our own techniques. With that said, I hope this gives you some insight on the design process of BattleBlock Theater and the brains that went into it. Some loser below me will now write some things. 😉

Hello! My name is Ryan Horn, and I’m a level designer.

 

Just like writer’s block or painter’s block (I think that’s a thing. If not, it should be), a level design block is plenty frustrating. Sometimes you don’t have any inspiration and nothing seems appealing; other times you have so much inspiration that it morphs into a mushy pile of tepid, indistinct ideas… which is even less appealing. Through many long and occasionally frustrating days in beautiful San Diego, I figured out a few techniques to help me take levels from their initial desolate desolation to the shiny and exciting completed levels that you find in BattleBlock Theater.

 

Before we really get started though, I have a little preface to throw in your face: In it’s end state, no level exists in a vacuum. When Billy is playing that level you poured your heart and soul into, it will always be sandwiched by other levels. Because of this, it’s very important to consider progression between levels when creating your creation.

 

Lay the Bones

It’s easier and more efficient for me to start big and work progressively smaller, so I’ll usually begin with brainstorming thumbnails of the player’s route through the level. Calling them thumbnails makes them sound far more developed than they actually are; they’re squiggles in a box, but they help form the skeleton of the level.

 

Once I pick a squiggle box I’ll bring it into the editor by roughly outlining the squiggle, then play with the shapes and spaces that start to emerge. I’ve found that beginning things this way helps me create a more interesting and varied level faster than if I were to pick a corner and start adding things from there. It also helps the level be more efficient in how space is used, and less wasted space from efficient design means more awesomeness can be fit into one level.

All this is done with the position of the level in the Chapter loosely in mind, as well as any Chapter-specific design goals. For example, Chapter 7 needed to have more level spanning puzzles, and Chapter 4 needed more boulders. For most of the Chapters this comes into play more when you get into the specific sequences, but it’s always a good thing to keep in mind.

 

Muscle the Skeleton

Once I have the skeleton of the level laid out, I move on to adding some muscle to it, i.e. actually adding gameplay sequences. I do this mostly off the cuff, and I’ll let myself be loosely guided by the spaces and shapes that emerged post-squiggle import. These spaces and shapes help structure and focus future sequences; staring at a blank space does not a good level make (Yoda – duh). It also helps tremendously to see how the entire level is structured. Seeing these larger relationships allows me to more easily create sections that interact in interesting ways, while at the same time ensuring that space is used efficiently.

 

When creating more finalized gameplay sequences, Chapter positioning begins to come into play a lot more. I need to consider desired mechanics, difficulty, and any player lessons that need to be implemented or emphasized. These are mostly guided by where this awkward fleshy creation will go in the Chapter, as well as any other design goals already in place (level-spanning puzzles, etc). These considerations are also limited by the fact that the level is still a prototype; sections and levels will inevitably get moved around in the next stage to ensure the Chapter flows well. Difficulty is also something that will get finalized in the next step, but I at least have an idea of the desired difficulty and try to incorporate that when making a section.

 

Even with all the above flimflam floating around in my head, the primary design direction for specific sequences is determined by my own style, which boils down simply to creating player movement. Vertical, horizontal, teleporting, catapulted movement; it doesn’t matter so long as the player is moving. All that movement can get tiring though, so I also like to throw in some simpler puzzles to break things up. This foundational style is something that influences most of my levels, even with a larger design goal in place.

 

Flesh the Muscle

Contrary to what you might think, the final stage of polishing and tweaking often takes the longest to complete. You might think it’s safe to assume that you tie a pretty bow on the level and call it done, but you would be wrong.
This final stage requires numerous steps, the first (and most important) of which is positioning within the Chapter. This is primarily determined by difficulty relative to the other prototypes. Sometimes there’s a level that fits perfectly in a certain position except for one sequence, in which case we switch the sequence with one from another level. Other times a sequence is so great we want to expand on it, requiring changes to following sections and levels. During this step there are many small tweaks and changes aimed at achieving the desired sense of difficulty and progression through the level as well as the Chapter as a whole.

The second and most time consuming, but critical, step is playtesting both the level and the Chapter as a whole (because Billy doesn’t play a single level). This allows me to see where people might have problems that might have been overlooked and adjust things accordingly. I cannot overstate how important this step is. Playtesting your levels repeatedly with multiple people and making adjustments from what you learn is what will make your final levels feel smooth, clean and complete.

Now, I’m not suggesting you invite strangers into your house to playtest your levels like we did. That would be creepy and weird for both parties. Friends and family are good for feedback, and don’t be afraid to upload early versions online and get Forum feedback.

 

That about sums up my creation process and how I, mostly, avoid a level design block. I hope all my talking will help keep your creations fresh and exciting. The bottom line to keep in mind: have fun and playtest. If you have fun playing something, someone else probably will too. If you then playtest the heck out of it and make changes, many more people will enjoy your stuff. The End!