As it turns out, Reaper's Rewards is ACCOUNT-BOUND! EAxis finally learned how to FOMO event but the Happy At Home fiasco continues.
Comment overhauled! - 10/1/2024
Let's talk accountDataDB.package as I understand it:
For Happy At Home, accountDataDB.package is the new home of your reward entitlements. However, the entitlements aren't automatically generated or permanently added. No, that would be too easy. Instead, accountDataDB.package detects the HAH entitlement code in your UserSetting.INI file and adds it to itself.
IF AND ONLY IF your UserSetting.INI file contains the string of entitlement code that unlocks the Happy At Home rewards, THEN AND ONLY THEN will it be added to accountDataDB.package the next time the game is launched, removing the need to backup the UserSetting.INI file, but creating the need to backup the accountDataDB.package.
If you already lost your HAH rewards because you lost your UserSetting.INI file any time during the three months this nonsense has been ongoing and no one pointed you in the direction of the INI modification, accountDataDB.package will not magically give you back your rewards.
All they did was remove the dependency from the DEVICE-BOUND UserSetting.INI and toss it onto the DEVICE-BOUND accountDataDB.package.
⚡ 10/1/2024 - BUT WAIT! THERE'S MORE! accountDataDB.package not only pulls entitlement data from UserSetting.INI, but it also immediately removes that entitlement data from the INI, so if you lose your accountDataDB after your entitlement data is moved but manage to retain your INI, you're absolutely, positively, screwed! Thank you EAxis!
Unless consoles protect this file automatically, which I assume they don't, console simmers will still lose their HAH rewards if their consoles go wonky.
Here's how I tested this:
I lost my HAH rewards. I created FOMO Unlock mods partially because I couldn't be bothered to modify the INI every time I deleted it for troubleshooting. So, I...
Removed my unlock and added the code that unlocks the HAH rewards to the INI.
Launched the game and verified the HAH rewards were available.
Exited the game and deleted my INI file, then launched the game and verified that yes, the HAH rewards were still there because the entitlement data was now in accountDataDB.package.
Exited the game again, removed accountDataDB.package, launched, and as expected, the HAH rewards were gone again.
Repeated these steps a few more times to verify.
Why this round about nonsense with accountDataDB.package and HAH if it doesn't actually solve the problem?
Are they intending to do more impermanent FOMO events?
Is it really so hard for EAxis to just unlock the HAH rewards for everyone instead of playing this game with us?
This is why I'm confused about the new EAxis statement that they're finally aware of the situation and doing something about it. They know this problem exists, they knew this problems exists. So why did they invest time into this nonsense with accountDataDB.package and Happy At Home when they could have just unlocked it in Update 9/18/2024?
You caused this problem. You can easily fix it, but you refuse to. Why?