Late last night, and most of this morning we spent a lot of time trying to bulletproof our cloud save processes and make sure local clients and cloud save for player data had a single point of truth. We chose the cloud.
The cloud like that. We liked that. We did not consult the unity editor.
The editor did not like that.
The editor, revolted.
What happened what we pointed the local clients to use the cloud save as the default point of truth, and would write to the cloud. The cloud would verify and send back. Unfortunately race conditions ensued, and by the time the client sent data to the cloud, changes were being made at human speed, not being sent fast enough, and getting now stale data back causing the cloud save data to merge with or overwrite data.
This effected decks mostly. Entitlements in our investigations have seemed to be unaffected. So, if you WERE effected, you may experienced your saved decks being wiped.
And there is a HUGE reason as to why this happened.
Because we don't work in an "In Development" environment. We push EVERYTHING to our live production environment.
So, we rolled it back obviously and things seem to be better than before we rolled the changes back, and A LOT BETTER than after we rolled the changes back.
We also fixed some of the minor issues that this "shoot ourselves in the foot" moment exposed! There was a race condition with the account authorization and stale data causing you to open the app and it present you with the "Login / Register" screen but not let you login because you were already logged in according to saved tokens. The only fix was to close the game and reopen it. That sucked, and we finally figured out what it was, and in our internal tests, that has been fixed.
The CoNfLiCt ReSoLuTiOn also pushed us to find a few of the hang-up errors with deck saves, summoned card effects not triggering, and in our attempt to freeze the leaderboard it all went to hell.
A huge shout out to player "Username," (great...username... by the way) because they were our rival, and to test the Gravamen to make sure it was back in spec (we're going to grumble about our poor conflict resolution for at least a few days, and longer internally). Hopefully WE CRUSHED YOU WITH THE MIGHT OF OUR FULL ROSTER OF DEVELOPER TOOLS.
Honestly though, it looks like you spanked us more often than not. Looking at my stats alone, you'd think I suck at my own game. Which, I probably do, but ONWARD!
The gravamen should now trigger when you log back in, and there was an event that happened while you were away.
The Trophaeum should be properly locked, not displaying any of your rank points on the public face without opening the player profile. And your position should be set from season close to next season open.
If you come across any bugs, please join our discord to let us know and we'll get them fixed as soon as possible.
