Skip to content

Technical test · Aug 2025

A Witch's Tale

2D action RPG built in one week as a Unity technical test, architecture first.

Playable
A Witch's Tale title screen: a pixel-art snowy forest with a frosted willow, the game's logo, and Play Demo and Quit buttons.

TL;DR

  • Designed, built and documented a complete 2D action RPG in one week, about 48 hours of work.
  • Event-driven architecture: UI, audio, gameplay and saving communicate through events, with no direct dependencies.
  • Data-driven content with ScriptableObjects, MVP input, a drag-and-drop inventory, save/load and FMOD audio.

Overview

A Witch's Tale is a 2D side-scrolling action RPG that I built from scratch in one week, about 48 hours of work, as the technical test for a Unity Game Developer position. The brief was to design, program and document a complete, scalable game architecture, so the code and the documents matter as much as the game.

Alongside the code, I used Aseprite heavily to produce and modify the game's assets.

Architecture highlights

  • Item-based skill system: the core loop. Abilities like Double Jump and Dash come from the items you equip.
  • Decoupled systems: UI, audio, gameplay and saving communicate through events, with no direct dependencies between them.
  • Data-driven design: items, loot and dialogue live in ScriptableObjects, so designers can add content without touching code.
  • MVP input: player controls follow the Model-View-Presenter pattern.
  • Inventory and equipment UI: a complete interactive UI with a "ghost icon" drag-and-drop system.
  • Save and load: the full inventory and equipment state persists between sessions.
  • Event-driven FMOD audio: a decoupled sound system with dedicated bridges for player, UI and world sounds.

Documentation

The test asked for documentation, so I wrote a game design document in Figma, kept the project plan on a Notion board, and produced a technical design and performance assessment plus a full system flow diagram. All of them are linked below.

What I learned

The week improved my architecture design: every system had to stay decoupled and documented under a hard deadline. If I built it again, I'd give the inventory and item system a sturdier, more robust architecture.

Shipping the build

The project was designed, programmed and tested in Unity 6000.0.35f1. A build-only animation bug persisted, so I re-imported the project and made the final executable with Unity 6000.0.50f1 to get a stable build, and documented why in the repository.

Media

Trailer

Screenshots and art

  • Equipment and inventory, with drag-and-drop between them.
  • The full system flow, from input to save file.

1 / 2

Equipment and inventory screens side by side: head, ring, body, weapon and boots slots next to a grid holding a potion and a gem.
Equipment and inventory, with drag-and-drop between them.

Like this?

Let's talk

Open to conversations about developer and production roles, and collaborations. I'm in Recife, Brazil (UTC−3).