How Godforge Builds Its Combat System

When you dive into Godforge and witness a hero unleash a game-changing ultimate or a perfectly timed [Confuse] effect flips the battle, it’s easy to miss the hundreds of hours of collaboration, iteration, and raw passion behind the scenes. That’s exactly what this latest Fateless podcast episode reveals, as Simon is joined by developers Marcelo and Alejandro to pull back the curtain on the game’s combat development—and it’s an eye-opener.
Let’s break it down.

This week’s podcast welcomes two new voices to the Godforge dev discussion: Marcelo, a senior developer with a decade of experience across PC, mobile, VR/AR, and now, the mythical battlegrounds of Godforge—and Alejandro, an intern currently wrapping up his game dev studies in Belgium.

Marcelo’s journey includes building serious games for sign language training and working on high-fidelity roguelikes like Dawn of Fire. Alejandro, on the other hand, brings fresh eyes and a hunger to learn, balancing his studies while contributing directly to combat systems and hero design in the game.

Despite being from different backgrounds and time zones (Canada and Spain), both developers rave about the flexibility and supportive communication at Fateless, a fully remote studio where the passion for RPGs binds the team together.

Combat in Godforge isn’t just a system—it’s a living, evolving beast. As Simon, Brad, and the devs explain, the team draws from their love of MMOs and classic turn-based RPGs to build a battle system that’s rich with options and strategic depth.

One standout mechanic is the Ultimate system, which balances initiative and speed. Players can opt for ultra-fast builds to gain more turns or build around frequent ultimate usage. Both playstyles are viable—and balancing them is no easy feat.

According to Brad, this will be a cornerstone of Godforge’s strategy layer. Getting that balance right is a constant tug-of-war in the design process, especially when the ultimate meter directly influences tempo and power spikes in battle.

The development process isn’t just about making flashy abilities—it’s about building a modular, scalable combat engine. Alejandro walks us through his journey implementing individual status effects, which can take half a day to a full day depending on complexity.

And not all effects are created equal.

There are:

• Simple stat changes like boosting [Defense] or reducing [Attack]
• Damage over Time (DoT) or [Heal over Time] mechanics that require timers and conditional triggers
• And then there are complex disruptors like [Confuse], where a hero might suddenly turn on their own team.

Implementing [Confuse] wasn’t just about functionality. It challenged the team to think about visual clarity, camera movement, and animation—especially with Godforge’s more zoomed-out battle view. Marcelo explains that sometimes devs have to “cheat the camera” or simplify movement to make effects feel natural without breaking immersion.

It’s a constant dance between dev and design, trying to decide what’s technically possible and visually satisfying. Every new effect, from [Charm] to ally-assist attacks, adds another layer of challenge and complexity.

Right now, Godforge has over 50 combat effects implemented—and that number’s only going to grow. With 200+ heroes planned at launch, plus weapons with unique passives and boss mechanics that change across phases, the scope is massive.

The dev team has to think modularly, building generic systems that can apply effects flexibly, like a universal buff/debuff structure that just swaps variables instead of duplicating logic 100 times over.

And yes, that even includes tools to check how many polygons are hiding inside tiny tree models on campaign maps, helping optimize performance for mobile without sacrificing quality.

Building a game of this scale isn’t always glamorous. Progress can feel slow, especially early on. As Simon says, “What looked cool six months ago now looks trash,” a testament to how rapidly the game’s visuals and systems have evolved.

But for Marcelo and Alejandro, the reward is in the moment something *clicks*.

“When you implement an ability and it finally works in-game, that feeling is unmatched,” Alejandro shares. “Seeing it all come together during testing, watching heroes execute your code… that’s the real payoff.”

Marcelo echoes that sentiment, explaining how hitting small development milestones keeps morale high. Even printing a debug line that proves something works is a little victory on the road to building a polished game.

The podcast wraps up with a fun question: If you could bring any myth or legend into Godforge, who would you choose?

Alejandro’s pick? Kratos-inspired brutality. He’d love to see a character wielding a throw-and-recall axe, packed with satisfying animations and high-impact abilities.

Marcelo, on the other hand, leans into mythic monsters, with the Kraken topping his wishlist for boss fights. Picture tentacles crashing through the battlefield and massive-scale VFX—now that’s a challenge worth building.

And as for dream projects, Marcelo hopes to one day create something that rivals his all-time favorite: The Witcher 3. Maybe, just maybe, a Godforge RPG spinoff could be in the cards?

This podcast was more than just a peek into Fateless’ workflow—it was a celebration of what makes Godforge special. A passionate team, bold game mechanics, and a never-ending pursuit of polish. Whether you’re here for the mythology, the tactical gameplay, or just to see a tiny studio build something epic, this episode hits home.