Development History

Overview

Guncaster's journey from concept to release wasn't a straight line. Over more than a year, the game went through three major reimaginations, survived multiple team shifts, and was guided at every turn by community feedback. This is the chronology of how a silly “wizard with a gun” concept evolved into a free-to-play boomer-shooter that resonated with 88% of players, and why the team that built it chose to pursue different paths afterward.
Below you'll find the iterations that reshaped Guncaster's vision, the features we cut along the way and why, the story of Grimoire Studios from founding to dissolution, and the lessons learned from shipping a game under real constraints.

Contributed Breakdowns

Guncaster Homepage
Level Design
Movement System
Audio System
AI Programming
Backend

DEVELOPMENT HISTORY

Studio History
Gameplay Showcase
Project Pipeline

Guncaster

A Boomer shooter fps where you fight enemies to regain the art of guncasting and your tower, featuring:

  • Fun and fluid movement system that lets players bounce off walls, dash around, and traverse their surroundings

  • Beautifully textured and stylized environment pieces to draw the whole game together

  • Hand made level modules that randomly generate to make each run unique

  • Diverse spell system with different spellcasting abilities, beware, your enemies can use it too

  • Dangerous enemy roster with engaging combat encounters for each zone

  • Scalable stats that let you become increasingly overpowered

  • An exhilarating multi-phase final boss encounter

  • Roguelite progression that carries stats between runs

  • Funny enemy voices and absurd ragdolls

  • Stunning music for both exploration and battle

  • Dynamic audio that reacts while you fight

  • A whooping 88% positive rating on Steam


But Guncaster wasn’t always like this

Timeline

Guncaster began as a 4-person team project in early 2024. The original concept followed a whimsical roguelite premise: a wizard armed with a gun exploring dungeons to reclaim his lost tower. The player would upgrade their abilities in a quirky mini-mall turned home base before venturing out into the dungeon. After a couple months of exploration and prototyping, the team decided to continue development and refine the vision.

Iteration 1

Guncaster’s humble beginnings

Following a brief break, the team regrouped with a clearer focus and began building a stronger foundation. It started with a fresh ideas and a blank canvas. The team evaluated progression and story and set off on production. This phase saw the introduction of entirely new systems, including a modular level snapping tool, a custom spellcasting framework, and fluid movement. Although progress was steady and productive, user feedback revealed that key gameplay elements still needed improvement. We took their feedback seriously, reshaping core systems based on what we learned.

Iteration 2

Guncaster testing out new ideas

After a leadership shift and serious evaluation of our external feedback, the team entered a final stretch dedicated to refinement. Broken systems were rebuilt, rough mechanics were polished, and the game’s tone shifted to better align with player expectations. While the end product evolved far from the original concept, the result was a tighter, more engaging experience that resonated more strongly with its intended audience.

Iteration 3

Guncaster blossoming into a game

A history

Guncaster went through three major iterations during development, evolving drastically from concept to release. These changes were guided primarily by our community and their continued feedback throughout the process. They told us what worked, what didn't, and what they hoped for and we listened.

  • Iteration 1

    Iteration 1 started as most game projects do, with an idea. Four of us set out to build it: myself, Kay Blake, Brian Tromba, and Xander Hacking. We envisioned a whimsical roguelite dungeon shooter centered on a wizard wielding a gun and devised a story to support it. The story was straightforward and focused on a wizard who gets evicted from his tower by goblins, grabs his gun, and ventures out from a temporary home base in a quirky mini-mall to reclaim his tower.
    Our team split into 4 roles, I would handle level design, Kay would work on art, Brian would create the AI, and Xander would focus on the character. We built rudimentary systems during this phase, but several core ideas persisted including randomized level generation, fast-paced movement, enemy variety, and a spellcasting mechanic.
    Once we had a playable prototype, we pitched it and received encouraging feedback, enough to convince us there was an audience for this concept. However, life called for all of us, and we took a collective break before gearing for the real work.

  • Iteration 2

    Starting Iteration 2, the team regrouped with a fresh codebase and a shifted roster. The new lineup was: myself as designer, Kay Blake as artist, Lauren Sterling as programmer, Brian Tromba as AI programmer, and Xander Hacking as leadership and character controller programmer. Building from scratch meant reconsidering everything. The “wizard in a mini-mall” premise no longer fit our vision. We explored new directions such as fighting to recover stolen memories instead of a tower, deciding whether the primary weapon would be spells or the gun, or how to introduce level variety. For example, our early concept featured a world map centered around a colossal skeleton warrior where players would traverse his remains and enter dungeons around different appendages. While the narrative took a backseat to systems work, this visual grounded us for the time being.
    Formalizing our commitment, we founded Grimoire Studios as our publishing LLC. I personally built the hub world and testing dungeon while the team tackled core systems such as spell casting, random generation, and movement. The AI work lagged behind, and community feedback on both the AI units and movement felt weak. I shifted focus to help stabilize these systems, taking on programming duties alongside design.
    Shortly after, Brian had to step back from the project entirely. I took over as Lead AI programmer, and while trying to match my new AI to the movements state machine structure I discovered something. Examining the movement system's “Hierarchical” Finite State Machine, I found it was fundamentally broken. Around the same time, Xander encountered personal difficulties that forced him to step down from the project. He handed over programming responsibilities to me and leadership to Kay.
    This meant I was now juggling level design, AI programming, and ongoing movement system work and was heavily stretched. However, this period coincided with community playtesting becoming more active, and their feedback was invaluable in guiding our next phase. After navigating these shifts and consolidating the codebase, the team took a month-long break to regroup.

  • Iteration 3

    Iteration 3 was our refinement phase, driven almost entirely by community feedback. With me split across multiple systems, I organized my work into focused sprints: first the character controller until the community felt satisfied with its responsiveness, then level design variety (adding Sky Islands, Scholar's Tower, Dungeon, and Sewers), then an intensive AI rebuild where I fixed the entire system and built unique enemy types for each zone. Between playtests and value tweaking, combat finally felt right.
    It was also in iteration 3 that gameplay saw a major shift. Originally the story followed our wizard as he traveled dungeons from his mini-mall, trying to reclaim his tower. It then changed to him exploring dungeons across the land covered in the remains of the a giant. In this last change we meshed ideas and cut scope creep focusing on what we could plausibly achieve. Instead you would fight through waves in dungeons you explored, working your way through the different zones to make it to your tower. Only then could you face your nemesis spell sniper and reclaim your tower. While it didn’t feature a overly complex story, it was just the right of story involvement for our game to feel alive.
    The final stretch was polish. I rebuilt most levels, retuned character values, optimized the AI across all zones, and refined the overall experience. This stretch involved heavy crunch time, but by the end, the game had come together. When it came time to publish, we made a decision. Rather than ship at the originally planned $5 price point, we decided to release for free on Steam. Despite our best efforts, the team agreed the product wasn’t at a level we would describe as marketable as a paid product. The community response was positive and the game landed at 88% positive across reviews. The community's positive reception vindicated our decision to release for free and our focus on quality over monetization paid off.