Build / Buy Changes Do Not Save & Revert Upon Reloading a Game.
Product: The Sims 4
Platform:PC
Which language are you playing the game in? English
How often does the bug occur? Every time (100%)
What is your current game version number? 1.89.214.1030
What expansions, game packs, and stuff packs do you have installed? Cottage Living, Snowy Escape, Eco Lifestyle, Discover University, Island Living, Get Famous, Seasons, Cats & Dogs, City Living, Get Together. Get To Work Realm of Magic, Strangerville, Jungle Adventure, Parenthood, Vampires, Dine Out, Spa Day, Outdoor Retreat Tiny Living, Moschino, My First Pet, Laundry Day, Fitness, Vintage Glamour, Backyard, Cool Kitchen, Perfect Patio
Steps: How can we find the bug ourselves? Not sure unless it was happening to your save file as well.
What happens when the bug occurs? New items bought in Build / Buy mode will disappear upon reloading a save file.
What do you expect to see? Items I bought previously to still be present.
Have you installed any customization with the game, e.g. Custom Content or Mods? Not now. I've removed them.
Did this issue appear after a specific patch or change you made to your system? Neutral/Not Sure
I'm having an issue where anything I buy in Build / Buy mode does not show up when I next load the save.
I can save the game normally, and household funds will be saved from the last time too. But any new items I bought will vanish, and the lot will have reverted to how it was before I made any changes.
Passage of time is still saved; sims age up, gain skills, get promoted, etc.
I have disabled mods, cleared my cache, repaired my game, & completely reinstalled the Sims 4, but the issue is still occurring.
I also tested on a new save file, and I am still experiencing the issue there.
Not sure what to do from here, any advice would be greatly appreciated!
I fixed the issue.
I made a copy of my Sims 4 Documents Folder, then deleted the original folder.
When I started the sims again it made a new Sims 4 folder in my documents.
I moved my saves & mods back in after that, and the issue isn't happening anymore. Not sure what the specific issue was, but glad it's fixed.