📢Developer Note – 1st CBT Q&A

Hello, this is the King’s Raid Team.

First of all, we would like to sincerely thank everyone who shared their feedback and opinions following the recent Closed Beta Test (CBT).

We have carefully reviewed all feedback raised through the community, videos, and other channels, and we fully recognize that many concerns and questions were expressed—particularly regarding our operational approach, system changes, and overall content structure.

In this developer note, we would like to address the key issues most frequently mentioned during the CBT period, explaining why the test was conducted in its current form and what direction we are currently considering, presented in a Q&A format.

💡 Q1. The scale of the CBT felt too small, and communication with the team seemed insufficient. A. To be completely honest, after taking over King’s Raid, we felt a strong sense of urgency that we might already be behind schedule. As a result, we rushed the preparation of this CBT, which led to several shortcomings on our part.

We sincerely apologize for these shortcomings, and we will continue to improve them moving forward. We kindly ask for your understanding as we work through these issues.

We also acknowledge that we did not sufficiently share information regarding development progress, changes, and design intentions, which understandably led to the impression of poor communication.

Our biggest regret during this CBT was the lack of adequate dialogue with our players. As we move toward the official launch, we will make a stronger effort to actively share development updates through developer notes and official announcements, and to communicate more openly with our community.

💡 Q2. The stamina restriction made it feel like gameplay was being blocked. Why was it set up this way? A. The stamina system was introduced to create an efficient daily progression loop while preventing excessive gaps in growth between heavy users and more casual players.

However, due to the relatively limited scope of this CBT, only about half of the originally planned additional purchasable stamina amount was made available. As a result, the stamina restriction may have felt more restrictive than intended.

As we move toward official service, we plan to gradually increase the maximum amount of stamina available per day. We greatly appreciate your continued feedback regarding this system.

💡 Q3. Characters cannot be purchased directly from the shop, and there are too few characters available early on. A. The character acquisition structure was designed with new players in mind, aiming to reduce confusion and the risk of early progression mistakes that can occur when too many characters are introduced at once.

However, because this CBT focused more on system testing than on fully conveying design intentions, the limited exposure to heroes likely caused frustration.

Going forward, we plan to adjust the hero acquisition flow based on actual data, allowing players greater freedom to develop characters according to their own preferences.

💡 Q4. Auto-battle feels less comfortable than before, and the game seems to strongly favor manual control. The balance also feels very different. A. The combat system was adjusted to allow player choices and direct input to enhance the overall combat experience.

That said, during this CBT, the number of available heroes was limited, and many of the selected heroes emphasized manual control. This likely resulted in a stronger impression of manual-focused gameplay.

Heroes that better support smooth auto-play are currently in development, and balance adjustments will continue even after the CBT. We will reflect your feedback and continue improving the system so players can once again experience the familiar sense of combat enjoyment.

💡 Q5. There wasn’t enough content in the CBT, so there wasn’t much to test. A. This CBT was designed to focus on validating key system changes—specifically the Hero’s Inn system and combat balance—rather than introducing new stages or multiplayer content.

Our priority was to gather feedback on core system changes rather than the quantity of content, which may have made the test feel limited in scope.

In future tests, we plan to provide a wider range of content, expanding both the testing scope and overall gameplay experience.

This CBT marked the first step before full service, and rather than delivering a fully polished experience, it was conducted to validate direction and structure.

We take full responsibility for areas where explanations were insufficient and where the gameplay experience felt inconvenient. Testing and development will continue, and we will refine systems and balance step by step based on the valuable feedback you have shared.

We also commit to sharing development progress and changes more proactively moving forward.

Once again, thank you to everyone who provided feedback. We will continue striving to deliver a better King’s Raid experience.

Thank you.