Marlo

Play as Sprout, a clay person controlled by a plant. Mold your moveset in this bullet-hell roguelike to defeat the clay enemies and finish the run.

Role: Team Lead, Systems Designer, Programmer
Time: July 2026-Present
Team size: 6

Engine: Godot 4

Demo coming soon to itch

Features I Created

Enemies

I created the entire enemy system. There is a wide range of enemies, from nondescript blobs to ladybugs to ants covered in mold. They each have custom behaviors, attacks, mana levels, and ranges, that have been turned into dials and dropdowns the level designers can edit.

Skill Editor

I helped make the skill editor, which helps every developer make skills for both the player and enemies. I specifically worked on the text box and list portions, the viewports, animations, and meshes. This has seriously cut down on programming time and allows us to create skills with 0 code.

Shop and Pickup

I created a system that allows players to pick up skills for free, pick them up for a price, as well as passive abilities and custom overrides for certain shops. I also programmed all of the UI systems for the skills, mana, skill info, currency, and wave progress.

Set and Animations

I made a component that can easily be attached to any node in the game that animates a mesh to appear from the ground and disappear into the ground. I also created a system that swaps out what we call a “stage” every once in a while to keep variety.

Development Videos

Here is a look into some prototypes and proof of concept.

Development

If you’re curious about the project, want to learn more details, or want to see how I think just take a look at some of these things I handle.

  • Team Lead Experience
  • State Machine
  • Skill Systems
  • Documentation
  • Skills Data Table

I am team lead for this project, which means that I organize our meetings, conduct our agendas, make sure everyone is on track, and also make sure the developers are happy. I organize playtesting, keep track of portfolio content, run the Discord server, and remind everyone of timelines. I make sure our team gets things done, but am also a passionate programmer.

Most of the issues that I handle involve coordinating meetings, making sure everyone has enough time to complete their tasks, and that everyone is doing what they are supposed to do. We have weekly meetings where I go over the agenda, and the day before a sprint is due I have everyone discuss if they are going to finish their sprints or not, and why. If they are struggling, we will work on a compromise, because we are also busy students and homework can get hard.

image

I was in charge of the enemies for this game, and the task was to keep the enemies varied and interesting without having to write more code. I had to draft a fairly complicated state machine before programming the state machine and I used a digital whiteboard to keep track of the states. Enemies will not have all of these states, but I wanted the enemy code to be able to handle most combinations of the states, which is why many states loop to a state that loops back to itself.

image

I also helped with drafting ideas for skills, as well as figuring out synergies, attack moves, and defensive moves. Here is a snapshot of some of the skills and passive abilities that have the same category we have drafted for the game.

I implement systems like the skill icons, UI feedback like mana usage and currency usage, and work on the design of the game. We want the game to be extremely varied, but also balanced, so we have all of the potential skills in categories with a key that indicates how much clay a skill costs and cooldown it has.

We have been writing documentation, mostly for the other developers, so that they can use our tools. I have specifically configured the enemies, for example, to have editable behavior without having to write any code. We include the type, name of the variable, as well as the description and any examples if necessary. We also write descriptions for variables within the game so when you hover over a variable it will describe how to use it just like how Godot does it.

image

In order to keep track of what skills and abilities we have as well as any description, cost, clay cost, and cooldown. This is important to see all of the stats in one place, so we can easily balance the game and check on what the other programmers are doing. Here’s a small screenshot of some of our data:

image