Reinforcement of development and management teams and response to the issue

We recognize that the trust of our users has been undermined by our handling of various problems during the Early Access period of Eternal Crypt – Wizardry BC – and by our decision to exclude some users from the third ranking event.
We have reviewed comments and feedback on this issue from our users and discussed it internally. We sincerely announce our future initiatives and response to this issue.

1. Reinforcement of development team and review development process
We are working to improve and strengthen our development team, including additional resources, for the upcoming Early Access phase and the official release so that the game can be played again without any glitches.

UpdatedDevelopment Team:
– Additional engineering resources
Bug fixes
Functional improvements
Usability improvement

– Additional Level-design resources
Optimize game balance without having to stay for long periods of time
Balance adjustments for long-term operation
Automate and streamline level design checks as the game expands

– Improved quality control system and additional resources
Review verification perspectives and expand verification items
Automate and streamline verification items in accordance with the expansion of items to be verified
Re-testing of all numerical functions

– Improved user support
Improve response speed and quality
Improved collaboration between support and development teams

2. Improve operations team and processes
– We will keep updating the status of development to regain the trust of our users.
– When a problem such as a bug occurs, we will immediately report the situation in an open space.
– Depending on the situation, we will implement a decision-making process that takes user votes into account (details to be announced at a later date).

3. Policy on bugs and incidents
– If a user exploits a bug to the detriment of other users, that user will be dealt with severely.
– The bug bounty system will be set up (details to be announced at a later date).

4. Regarding our handling of various problems during the Early Access period
– The 3rd Ranking Event
We have confirmed that there was a ranking change due to the use of a glitch. We are very sorry for this situation that occurred.
The problem identified in this case is that when an adventurer slot levels up another slot without waiting for the level increase to take effect, the level increase decision is not processed correctly, allowing the adventurer to level up beyond the original limit set for the slot, and DPS can also be increased to a value beyond the limit.
In response to this issue, we have reviewed the logs of all users and confirmed that there were several users who were deemed to have arbitrarily and repeatedly used the glitch to update the deepest floor of their reach, and we have taken steps to exclude these users from the ranking.
In reviewing the logs, we had two producers as well as several people, including engineers, who looked at multiple logs from different angles, including the occurrence of problems, and reviewed the logs.
Since there may be cases of unintentional glitches, we have not taken any action to exclude users from the rankings if, after reviewing the logs, we determine that it is not arbitrary.
The following is our response to those who were excluded from the 3rd ranking.
Excluded from the 3rd ranking
No reward for the 3rd ranking
Earned BC tokens, Adventurer NFTs, and game items will be available for them as usual going forward. They can play our game after Early Access Phase 2.
However, we would like to point out that we may suspend their account in the future if we find repeated use of the glitches intentionally.

– The 1st Ranking Event and the 2nd Ranking Event
In response to the detection of the above glitch, we also conducted another verification of the logs for the first and second rankings as well.
As a result, it was found that there were users who were using the same glitch.
As for the 1st and 2nd rankings, we will recalculate the rankings excluding the affected users, and those users whose ranking rewards changed as a result of the recalculation will receive the difference as compensation.
We will announce the schedule and timing for the awarding of the rewards as soon as possible.

– Differences in response to bugs detected to date
First of all, we are very sorry for the many bugs that have occurred since Early Access that have affected your gaming experience.
One of the major differences between our response this time and the previous one was the MP recovery bug. Since it is impossible to avoid this problem and there are cases of unintentional use, we informed everyone of the existence of the problem and made a special exception to not exclude people from the rankings even if they used the bug.
Additionally, due to an issue with the Skillboard Reset function, there was an inconsistency in Skillboard effect activation values between Skillboard Reset and Re-Login, resulting in an unintended shift in DPS up or down. To minimize the occurrence of inconsistent values, we have temporarily disabled the skillboard reset feature.
We responded to each bug in the best way we could, based on the details of each event and the scope of its impact. However, we believe that the disparity in our response to each issue has created a sense of mistrust among users.
We also feel that we could have done better in our response to each bug.
Based on these considerations, we are pleased to present Policy on bugs and incidents.

– Regarding actions that exploit the bug to the detriment of other users
Again, it is our policy to take strict action against any actions that take advantage of the glitch to the detriment of other users, after sufficient review of logs, etc. We will make every effort to minimize glitches and maintain a normal playing environment for all users.
In addition, we will consider implementing a bug bounty system, which has been suggested as an improvement plan to encourage users to actively report bugs. We will be discussing the details of this system while listening to the community, so please wait for the announcement.

We will continue to work to regain our users’ trust by taking the above actions and regularly updating the community on the status of these actions.

We really appreciate your continued support of this project.