Hello, this is Finalblow.
First and foremost, we sincerely apologize for having to share more disappointing news with everyone who has been waiting so patiently for the game.
Our recently submitted build was rejected during review, and additional time will be required for another review.
There were two main issues identified during this review process.
1. Controller-Related Review Requirement
Steam informed us that all features of the game must be fully operable with a controller.
However, this was not a previously communicated review requirement that we overlooked or knowingly failed to address.
Our build has already undergone review several times, but no controller-related issue was mentioned during any of the previous reviews.
As a result, we believed that the current implementation would not cause any issues during the release review.
Had this requirement been communicated during one of the previous rejections, we would have had sufficient time to address it in advance.
However, we were only informed of it during this latest review, leaving us in a position where we must implement additional changes immediately before release.
Because it would have been difficult for us to anticipate this issue based on the previous review results and guidance, we were also considerably taken aback by this reason for rejection.
Nevertheless, we will confirm the necessary requirements, make the required changes as quickly as possible, and resubmit the build for review.
> After checking, we found that this is not mandatory. Therefore, it was not a reason for the build’s rejection. We apologize for the incorrect information.
2. Early Access Configuration Issue
The new build included a message explaining that the game is currently in Early Access, along with the newly added reporting feature.
However, this message was also cited as a reason for rejection because our Steam store page was not configured for an Early Access release.
When we first created the store page approximately a year and a half ago, we understood that we had selected Early Access and submitted answers to the relevant questions. Since all of our announcements have consistently stated that the game would be released in Early Access, this review was the first time we became aware that the store page was currently configured for a full release.
At this time, we are unable to determine exactly how or when the configuration changed. However, we clearly bear responsibility for failing to thoroughly verify the final store page settings before release.
We sincerely apologize for the problems caused by our insufficient checks.
We have contacted Steam regarding both the Early Access configuration and the release date change. Our Early Access release procedure and future review schedule will need to be adjusted depending on Steam’s response and how they decide to handle these requests.
Estimated Release Schedule
Estimated release date: July 31, 2026, at 6:00 PM KST
We considered setting an earlier date. However, despite submitting the build with more than ten business days of leeway before the original release date, repeated review delays and rejections meant that we only received the latest review result today.
We determined that setting another overly tight schedule could result in yet another release date change. To avoid causing the same confusion again, we have reluctantly chosen a date that allows sufficient time for the process.
However, this schedule may change depending on how Steam handles our requests regarding the Early Access configuration and release date. We therefore ask for your understanding that we cannot confirm the July 31 release date with certainty at this time.
We will provide an update as quickly as possible as soon as we receive a response or if there are any changes to the schedule.
Once again, we sincerely apologize to everyone who has been disappointed or inconvenienced by this situation.
We understand that those who were waiting for the game and expecting it to launch on July 13 may feel frustrated and have lost confidence as the release of a game that should already have been available continues to be delayed.
We believe that we bear significant responsibility for failing to complete the final checks and release preparations properly.
We also fully understand that these problems cannot be dismissed simply because we are a small development team.
We will conduct our checks much more thoroughly to ensure that the same problems do not occur again.
We once again offer our deepest apologies to everyone who has been waiting.
Sincerely,
Finalblow