Godforge Beta Q&A Breakdown

If you enjoy conversation about the practical reality of game development. That is exactly what this Godforge Q&A delivers. Instead of just hyping up the next test phase, Simon and Juho dig into the systems behind the scenes, from backend architecture and QA processes to mobile optimisation, beta rewards, hero variety, and long-term design goals.

I believe this is the kind of update players love to see. Why? Because it does not just tell us that Godforge is moving forward. It shows how the team is thinking, what problems they have already tackled, and where their priorities sit as the game moves toward beta and beyond. For anyone following Godforge closely, this Q&A gives a much clearer picture of what the upcoming experience is trying to achieve.

One of the biggest points covered in the discussion was the team’s move to a new backend system through MetaPlay. It is a major upgrade that should have a direct impact on how Godforge feels to play.

Previously, the game relied on a system that could struggle when too many server requests hit at once. In a hero collector like Godforge, that becomes a serious issue very quickly. Summoning heroes, upgrading gear, completing quests, moving equipment around, and handling large batches of actions all create constant server calls. When too much of that happens at once, performance suffers.

The new setup is designed to solve exactly that problem. Rather than relying on repeated back and forth calls in the same way, MetaPlay runs game logic in sync with the client. In simple terms, it gives the team a much more stable and responsive framework for handling all those heavy interactions. That should be especially important for actions like mass gear selling, upgrading, and account progression, where players expect speed and consistency.

The team also explained that they are entering beta with server scale that should comfortably exceed expected demand. If additional scaling is needed, they can increase capacity relatively quickly.

Another key takeaway from this Q&A is just how much emphasis Fateless is placing on testing. Juho’s role has evolved significantly, moving from community management work into a central QA position, especially around backend migration and systems testing.

Godforge is reaching the stage where strong ideas and stylish visuals are no longer enough on their own. Systems need to work consistently, heroes need to behave as intended and bugs need to be caught, ranked, and resolved in a structured way. From the sounds of it, that process is already well underway.

The team mentioned that a huge number of bugs are being raised daily, with triage happening constantly to sort critical issues from minor ones. Some problems are as small as incorrect text or unclear tooltips. Others are much bigger and affect actual gameplay or system performance. That is normal in development, especially when features become more complete and testing gets deeper.

What stands out here is the mindset. Fateless are not pretending bugs will disappear. They are talking openly about process, prioritisation, and iteration. That is exactly what you want to hear before a beta. A polished experience is never about having zero issues. It is about identifying the important ones fast and acting on them effectively.

If you have been wondering how serious Fateless is about mobile, this Q&A makes the answer pretty clear. Mobile optimisation is one of the team’s biggest priorities, and it has already had dedicated support from Unity specialists focused specifically on improving performance.

Godforge is trying to hit a quality bar that looks impressive on both PC and mobile. That balance is never easy. A game with detailed heroes, flashy animations, VFX, and large-scale battle systems naturally puts pressure on lower-end devices.

According to the team, the improvement since earlier testing has already been dramatic. Juho described using a very low-end test device that went from barely running the game at all to reaching much more playable performance. This is exactly what players want to hear, especially if they are hoping to play Godforge on older phones.

There are still challenges to solve, particularly around devices running hot and broader support for lower-spec hardware, but the direction is positive. Fateless also hinted at an interesting long-term possibility: a more heavily upscaled PC version with even better visuals. Since mobile constraints limit polygon counts and other graphical choices, a stronger PC-focused build could eventually let the team push hero detail much further.

For now, though, the big message is simple. Godforge is being built with cross-platform play in mind, and mobile is not being treated like an afterthought.

One of the most useful clarifications in this Q&A is that the beta is not trying to be a full version of Godforge. It is a focused test.

That matters because some features players might expect, like PvP or tower content, are being held back. But the reason is not because the team is worried those systems will break under load. It is because Fateless wants the dev team focused on polishing the core of the game first. That means campaign, summoning, general progression, gear systems, heroes, and the foundational gameplay loop are getting priority.

Rushing every feature into beta just to say it is there would probably create a weaker experience overall. By narrowing scope, the team can gather more useful feedback on the systems that matter most right now.

The beta will still include plenty to explore. Players can expect a large hero pool, several dungeon types, campaign content, some story scenes, and a variety of progression systems to test. There will also be goals, rewards, and incentives to engage. Importantly, the team confirmed that beta progression will not carry over, but players will still be able to earn rewards that can later be redeemed in the main game.

That gives the beta a clear identity. It is there to stress test systems, gather feedback, and help refine the live experience.

One of the most exciting parts of the Q&A is the confirmation that beta will not hold back on the hero roster. Fateless expects players to have access to over 200 heroes, which is a huge statement for a game at this stage.

Why does that matter so much? A small launch pool usually leads to immediate meta rigidity. Players identify the best teams fast, content starts feeling solved too early, and experimentation fades. A deeper roster creates more room for discovery, niche counters, creative team building, and different solutions to the same encounter.

Simon was very clear on this point. The team wanted enough heroes in the game so that bosses could have meaningful answers, players could build in different directions, and content would not instantly collapse into one dominant strategy (see Void Hunters recent Alpha where its all about Bohdan). Juho reinforced that, noting how boring it can feel when a game launches with such a limited roster that the best lineup is solved almost instantly.

That philosophy is encouraging. It lines up well with previous Godforge discussions around faction depth, kit identity, and making heroes feel like they have a real place in the game.

Thor fans may need to be patient, though. He is not expected to be part of beta or early access, with Fateless positioning him more as a future live-service style release hero.

The Q&A also touched on how much of the story players will see during beta. Fateless is taking a measured approach here, allowing players to experience part of the campaign and some cutscenes while still holding back a lot of story content for later. That seems like the right balance. Players get a real feel for presentation and narrative flow, while the full arc stays protected.

On top of that, the team is clearly thinking carefully about rewards. Beta players will have goals to work toward, login-style benefits, and some form of earnable rewards that matter beyond the test itself. At the same time, Fateless does not want players becoming so attached to a temporary beta account that resetting for early access feels terrible. That is one of the big reasons the team prefers shorter, focused testing windows rather than leaving beta live indefinitely.

Feedback will also play a huge role. The team plans to use surveys, reporting portals, and Discord to collect player impressions and bug reports. That is especially important for evolving systems like Faith, the renamed and reworked version of Divinity, where the team wants players to help judge whether the changes actually feel better in practice.

This Q&A is one of the clearest signs yet that Godforge is entering a more mature phase of development. The conversation is no longer just about cool hero concepts or broad vision. It is about infrastructure, stability, optimisation, hero depth, and player experience.

There is still work to do. Fateless say that openly. But the direction looks strong, and the reasoning behind their decisions feels grounded. The backend changes sound meaningful, mobile optimisation is getting real attention, QA is ramping up hard, and the roster depth could give Godforge one of its biggest long-term strengths.

If you are following the game closely, this update should leave you feeling optimistic. There is a lot to unpack, and even more to test once players get their hands on the next build.