Design Process


For me, the core of level design is crafting the player’s moment-to-moment emotions and affordances. What is the player feeling, and what is the player doing? Should the player feel afraid or delighted? What architectural design elements support those feelings? Can lighting, audio, or texture support that goal? What are the narrative beats, and how quickly should the players’ involvement ramp up?

The design process is also influenced by the stage of the game when I start working on a level. If it’s starting from scratch, I will focus on understanding and modeling the game space as well as establishing standards and performance goals on the target platforms.

If a large number of different platforms are involved, determining what steps may be possible to achieve good performance on the less powerful systems becomes important to maintain quality. This question may influence how levels are built.

From the team’s perspective, is there a design philosophy? Is the project using Rational Design or Player Experience of Needs Satisfaction (PENS)? These approaches can influence and, more importantly, guide the process .

As soon as some player actions are possible in-game, I will start testing out assumptions about the game space and estimating performance limitations. Some of the big questions to answer are how will content be loaded and drawn to fit the desired environment.

Sketches of different quality are created when needed to convey an idea. Sometimes it is gameplay specific, design specific, or functionally specific, like for a boss fight. I tend to work iteratively, moving from plan to elevation, to understand the problem in 3 dimensions. In some cases, I might start blocking things out in 3d as well in an application like SketchUp or Blender.

Sketching a gameplay scenario to discuss with the lead designer and environment artists.
A more detailed drawing can help fill in some gaps in terms of what game objects are needed.

Taking what I have learned from those early tests, I will start drawing out design ideas. This allows for fast iteration and early feedback. What moves forward from that process is grayed out and stand-in gameplay is established for systems that are not yet developed. This is usually when level design documents start to develop and can be shared for approval. At this stage, a full level can be built, iterated on, and approved for final artwork.

More detailed drawings can help describe a challenge or event for artists and programmers.
Quick floor plans can help get feedback early and takes little effort to revise.

I will usually be working with gameplay programmers and artists to develop any special features for the level. Level event scripting can begin and systems are added as they come online. Cinematics are simulated and any special animations can be planned. During this process, an ongoing review is encouraged, and feedback is incorporated as needed.

Once approved, the level is set for testing. I will generally set up a test document, which allows others to quickly move through the levels as needed to test different aspects and verify game walkthrough.

A level grayed out in Sketchup can quickly be moved into the editor for testing.