<aside> 🛠 This section is about the issues tackled by the development team for this week, and that the changes which won't be included in the next release right away.
</aside>
Several players have reported issues with the game not progressing further on the first loading screen displaying Verifying transaction..., and the team hastily launched an investigation.
Internally, at that stage the game client doesn't just validate the transaction, it does something much more complex. one of them is to receive the information of the currently logged-in avatar from the blockchain node and deserialize it. here we found one major problem. Deserialization failed because some information on the avatars of the users who reported the problem was missing. Fortunately, the cause of the problem was quickly discovered. In v100070 there was a patch to adjust the daily rewards, which was caused by incorrect application of code to migrate old user information to new user information. The reason this didn't happen to all users is that users who migrated their state at least once before receiving their daily rewards are not affected by the migration code.
We fixed a bug in the migration code in daily reward action and applied an additional hotfix so that if one avatar state is broken it will ignore it and load the other avatar state, which is coming in v100075. In addition, the avatar state that has failed migration will be recovered by creating an additional recovery action in v100076.
It was often seen that the NCG was negative, or the NCG balance after the transaction was displayed incorrectly. Also, there were many times when the AP seemed to remain, but in fact, the AP was no longer there. These issues will be fixed as much as possible in v100075.
The reason for this problem was that before the actual state was changed, the client tried to show it as if the action was already filled, or the NCG balance was calculated and displayed in advance.(a.k.a. local layer) For fast gameplay and usability, we wanted to show the client as immediate changes as possible even before transaction processing, but this didn't work as well as we expected. 😞
So we stripped down these implementations and force them to show only the correct results for each state. We thought it was better to show the result a little later than to show the wrong value.
Users will be able to pour multiple APs into one battle and receive rewards and experience points at once. However, this feature is not entirely for stabilization. Users will be able to use the sweep feature only on stages cleared with 3 stars. It is an approach that adds convenience functions to the cleared stage.
UI design work is in progress. We plan to start development with a kickoff meeting for the development of this feature.