Fateless Podcast Recap: The Divinity Exploit That Broke the Game
This week’s Fateless Podcast dives deep into one of the most critical—and least visible—parts of game development: quality assurance. Brad, joined by QA testers Juho, Isabela, and Garret, break down how thousands of player reports shaped Godforge during Alpha and how QA is evolving for Early Access.
From the start, the Godforge community proved to be a powerhouse. Over 2,000 bug reports poured in during Alpha, revealing interactions no internal team could catch alone. As Juho jokes, “No amount of QA can match the combined strength of 10,000 nerds.” That player-driven discovery continues to guide the dev team today.
To handle the volume, the studio shifted from Discord tickets to a more advanced service desk, allowing the QA team to sort duplicates, rank severity, and prioritize fixes. Some bugs—like the infamous Immortal Hercules endlessly reviving—required immediate emergency patches, while purely visual glitches (hello, Pink Tristan) could wait their turn.
Looking ahead, the testers say Early Access will feel significantly smoother than Alpha. Improved optimization, reduced crashes, restored summoning systems, better-balanced battles, and more diverse environments headline the upgrade list. And yes—memory leaks and long-session slowdowns have been a major point of focus.
The QA team also emphasizes that their job isn’t just finding bugs—it’s speaking up. Whether it’s an ability that doesn’t feel fun or a system that disrupts gameplay, QA acts as the “final barrier” before features make it into players’ hands.
As Early Access approaches, players can again expect to take part in shaping the game. The best place to stay involved? The Godforge Discord, where testing updates, bug reporting tools, and community discussions will all live.
