A 24-student capstone studio's shipped game — a tower full of enemies and levels I helped design and build, and a Git repo I ran end to end.
"Tails of the Tower" was built by "Too Many Cooks," a 24-student practical capstone studio, across a single semester. The studio started with 24 people pitching ideas in an "atomized" ideation process and narrowed down to one concept everyone would build together. I was one of nine programmers on the resulting team.
Add a fuller breakdown here of the game's core loop, what the player actually does floor to floor, and what made the tower concept worth building.
Notes from across the semester. Newest entries first — duplicate one of these blocks to add your own.
Write the ship-day entry here: what the final build actually includes, what got cut in the last two weeks, and how it felt watching nine programmers' worth of commits turn into one playable build.
Write about the enemy design process here: how encounters were laid out on paper and chalkboard first, how that translated into GDScript behavior, and what changed once enemies were actually placed in levels and playtested.
Write about the Git workflow you set up here: branch strategy, the Discord webhook for commit activity, and what reviewing every commit that went into the build actually looked like week to week.
Write about the studio's atomized ideation process here: how 24 students pitched concepts and narrowed down to "Tails of the Tower," and what made this concept the one that survived.