Re:Blade · published
Hello, this is the developer.
First, my sincere apologies.
Yesterday's Awakening / Enlightenment rework update build had a serious issue where the Awakening menu wasn't functioning properly. A hotfix has just been applied to restore normal behavior.
If you have Re:Blade installed, the update downloads automatically — just restart the game.
In yesterday's build, the "Awaken" button inside the Awakening menu wasn't responding to clicks. This is the most critical fix in this hotfix.
Some of the old Hidden Awakenings that should no longer appear after the rework were still present. These have been cleaned up.
The achievement previously required collecting "every Awakening effect," but because the Awakening ID system has changed, the achievement would have needed constant updates to keep up. It's now changed to "collect every Awakening effect in the Awakening Compendium."
Yesterday's Awakening / Enlightenment rework update included a migration step for existing players:
- Register currently owned Awakening effects into the newly added Awakening Compendium
- Reset all currently owned Awakening effects and refund points based on current Awakening Level
Due to an ordering error in this process, the Awakening effect pool itself ended up being emptied. As a result, even when pressing the Awaken button, there were no Awakening effects available to roll.
This hotfix resolves the issue by restructuring the process so that the Awakening effect pool is registered first.
During internal developer testing, the systems were built up sequentially, so the ordering-conflict case that surfaced during real-world migration wasn't caught in advance. I'm genuinely sorry for not catching this before it reached you.
In particular, my deepest apologies to everyone who booted up the game after yesterday's update only to find the Awakening menu not working as expected.
I'll be more thorough going forward. If issues do surface, I'll keep responding with hotfixes as quickly as I can.
Genuine thanks to every player who reported the bug quickly and shared detailed context — that's what made it possible to find the root cause and ship a hotfix this fast.
If you notice anything else off, please leave a comment / post in the Discussions / drop a message in Discord — anywhere works. I'm reading everything.
See you in the Raid.
— STAGE Games