Haven’s Toll: Doomslay

Haven’s Toll: Doomslay is 2.5D narrative dress-up game where players take on the role of Jackie, a girl whose sister mysteriously disappeared after joining a local clothing-obsessed doomsday cult. Use your fashion sense to infiltrate the cult, get to know its members, and slowly unravel the mystery behind your sister’s disappearance.

Haven’s Toll: Doomslay was a 4-month collaboration between myself and three other team members. I took on the role of lead engineer, as well as producer. Most of the logic behind the game was written by me, particularly regarding the dress-up mechanics and how they impacted the dialogue system.

You can play the game on itch.io, here!

What I Did:

Creative Director

  • Oversaw all in-engine development, incorporating plugins to handle UI and dialogue systems, and maintaining project code base.

  • Determined development priorities and distributed tasks between myself and our other engineer accordingly, providing them with a skeleton to work off of where necessary.

  • Established asset pipelines with team from project start, allowing for seamless incorporation of new content from writers and artists as development progressed.

  • Tracked development tasks week-to-week and ensured adherence to development timeline, pushing for content cuts or refactors when necessary.

Our meeting notes template, which I've used on every long-term team project since 2022.

Our meeting notes template, which I've used on every long-term team project since 2022.

A spreadsheet tracking the clothes available in our game, their status (in-build or not), and how the different NPCs react to each piece.

A spreadsheet tracking the clothes available in our game, their status (in-build or not), and how the different NPCs react to each piece.

An early test scene to determine NPC interactivity and dialogue system functionality.

An early test scene to determine NPC interactivity and dialogue system functionality.

A script snippet highlighting the clothes system. Our clothing were both UI elements as well as modular pieces of our character model, so this code adjusted the appearance of the clothing programmatically.

A script snippet highlighting the clothes system. Our clothing were both UI elements as well as modular pieces of our character model, so this code adjusted the appearance of the clothing programmatically.

A snippet from our dialogue system using Pixel Crushers Dialogue System. Branches were made accessible according to clothing preferences.

A snippet from our dialogue system using Pixel Crushers Dialogue System. Branches were made accessible according to clothing preferences.

A character responds negatively to the player's outfit choices.

A character responds negatively to the player's outfit choices.

A character responds neutrally to the player's outfit choices.

A character responds neutrally to the player's outfit choices.

A character responds positively to the player's outfit choices.

A character responds positively to the player's outfit choices.

Our quick and dirty progress tracking spreadsheet for our end of project push.

Our quick and dirty progress tracking spreadsheet for our end of project push.

A gameplay still in the closet, which grows more populated as the player buys more clothing in game.

A gameplay still in the closet, which grows more populated as the player buys more clothing in game.

A gameplay still during investigation.

A gameplay still during investigation.

A gameplay transition.

A gameplay transition.