top of page

Dungeon of the Wraith King

Development

Role: Level Designer | Game Designer

Genre: 2D Side-Scrolling Action Game

Engine: Unity

Team Size: 1

Development Time: 14 weeks

Gameplay Overview

A combat-focused 2D side-scroller that flips the traditional dungeon-crawler perspective. Instead of playing as a hero exploring a dungeon, players take on the role of a skeleton tasked with defending its master's tomb from invading knights.


Players fight their way through a vertically structured dungeon, navigating platforms, environmental hazards, and increasingly challenging enemy encounters before reaching the surface for a climactic boss battle. The level design focuses on combat-driven spaces, enemy variety, vertical traversal, and progressively escalating challenges.

Level Design & Blockout Process

DotWK Level Design & Blockout Process.png

I began designing the level by first sketching the layout on paper with pencil. This allowed me to quickly experiment with the overall flow of the dungeon without being constrained by the tools or implementation. I focused on how the player would move through each area, where verticality and platforms could be introduced, and how individual rooms could transition into one another.

​

Because the game is designed around the perspective of playing as a dungeon creature rather than the traditional hero entering a dungeon, I wanted the level to feel like the player was fighting their way through a dungeon that was being invaded. The layout was therefore designed around a series of combat-focused areas, platforms, hazards, and traversal sections that gradually lead the player toward the surface and the final confrontation.

Final Level Layout Sketch

Once I was satisfied with the initial layout, I transferred the design into Unity and created a playable blockout. At this stage, my priority was not visual polish, but establishing the level's structure and testing whether the layout actually supported the intended gameplay. I recreated the major elements from the paper design, including:

 

  • Platforms and vertical traversal routes

  • Individual rooms and combat areas

  • Enemy placement and encounter setups

  • Collectable locations

  • Environmental hazards such as spikes

  • Transitions between different sections of the dungeon

  • The overall path leading toward the final boss encounter

 

Using simple placeholder geometry allowed me to quickly test the level from the player's perspective. I came up with a color coded system to make it easier to identify any issues with the level layout that can be easily seen visually, for example if there's too much red on the map, that could mean too many enemies or hazards in one area.

Final Level Layout in Unity.jpg

Final Level Layout in Unity

Adding UI Elements.jpg

Adding UI Elements

Final Blockout.jpg

Final Blockout

After establishing the level layout and gameplay flow, I began translating the blockout into a playable space in Unity. I first added the necessary UI elements and labeled the different gameplay components to clearly identify how the player would interact with the space.

​

I then introduced color to the blockout to better understand the player's perspective and how the different elements of the environment would read during gameplay. This helped me evaluate the visual hierarchy of the space while continuing to make adjustments to the placement of platforms, enemies, hazards, and collectables.

Blockout Playtesting

​

Once the initial blockout was playable, I tested the level from the player's perspective to evaluate the overall flow and identify problems that were difficult to recognize from the layout alone. I focused on movement between areas, platform spacing, enemy encounters, combat pacing, and whether the player was being guided naturally through the level.

​

This stage allowed me to catch issues early and make changes to the layout before moving further into development. Rather than treating the original paper design as fixed, I used the playable blockout as a way to continuously test and refine the level.

Iteration & Refinement

As development continued, I used successive playable versions of the level to evaluate how the design was holding up in a more complete game environment. The beta version gave me an opportunity to test the level with more of its intended gameplay, visuals, enemies, and mechanics in place.

Beta Version

​

By this stage, the core layout, platforming, enemy encounters, and traps had been refined through blockout testing. The beta version was a near-final representation of the level 1, with level 2 having major changes.

The original boss battle didn't work out as original planned, and so I changed the character completely to better fit the story and overall gameplay.

Full Playthrough Video

GDD Document

bottom of page