west of east

Project Info

My role: Level Designer and Game Designer

Team size: 7 persons

Project duration: 7 weeks

Tools: Unity

Project type: School Project

my contribution

Level design

  • Designed the level

  • Conducted playtesting

  • Iterating

  • Assembling all the components from the other team members and putting them in the level.

Gameplay design

  • Designed the abilities of the characters together with the other designers

  • Conducted focused playtesting on different variables like player speed, damage, etc


West of East is a tactical stealth game like Desperados. It was created during my third game project at Futuregames. We had a ten minute time limit on how long the game should take to complete.

In West of East you control the two characters Irene and Curt, who are dead set on taking revenge on the Stallion Bandits. The two characters each have a different set of complementary abilities that the player has to use in order to succeed.

Game loop


Level design process



Sketching overall layout and encounter design.


Combine different layouts and encounters into complete areas.


Creating the rough 3d layout for each of the areas in the game.


Reworking areas according to feedback from playtest, implement 3d assets, test collision and navigation. Repeat this step until satisfied.

Level design goals


Creating multiple ways to solve encounters


Designing areas that encourage the player to use the different characters abilities in synergy with each other


Creating a tutorial that teaches the mechanics in a natural way for the player

Choice is the flavour of life

A big part of this game genre is the players tactics and ability to plan. I wanted to provide the player with opportunities to solve the different encounters in their own personal way with their own tactics.

Teamwork makes the dreamwork

One of the primary mechanics of the game is being able to seamlessly switch between the two characters. Therefore I designed the levels so that the two characters had to help each other out in order to survive. One of the characters has abilities focused on killing enemies while the other is more focused on distraction and crowd control. I designed encounters that required the player to use abilities from both characters in order to progress.

Character B has to distract the green enemy in order for character A to slip past and kill both the enemies.

Like riding a bike

One of my personal goals for this project was to provide a strong tutorial for the player. I decided upon a linear design that forced the player to complete encounters in a specific order, this to easier introduce the mechanics. I wanted to teach the player some basic tactics for them to feel confident enough to come up with their own further on.

Showing tutorials.PNG


I wanted my design process to be based on player feedback, therefore I conducted playtesting often and early on. I also needed to adapt my level to the ten minute time limit so I had to optimize the level layout. Here is a showcase of the major iterations made to the level:


First iteration

This is the first iteration of the main level. The general consensus of the playtesters was that it had too much filler in it, the core mechanics didn’t get enough time in the spotlight.

One of the biggest complaints from testers was that this specific area felt vague and unclear. They didn't know where to go or how to navigate. In this scenario the player has to move to the location to the left of the house and distract the guard below. My problem was that players kept running down the ramp, making the game much harder for themselves. To more clearly communicate my intended solution I removed the house, made the spot where I wanted them to stand pop out more. I also worked with the narrative designer to make the dialogue reflect this, pointing the player to the correct location. This worked well and playtesters cleared the area much more easily.

What i learned

It is hard to design levels from a top down perspective when you want to get the player to go to a specific location. I couldn’t rely on the same tricks I normally would  when designing a FPS level for instance. This was much more of a group effort with level design, narrative design and art all working together.


I learned that designing encounters that suit your own difficulty level makes them too hard for the general player. Especially when you take into consideration that the player is presented with so much information in each encounter, information that me as a designer already have internalized and won’t notice. Without the amount of playtesting and iteration I did in the project the game would be too hard and confusing to complete.