[FIXED] [CD] Game created cat only household
Product: The Sims 4
Platform:PC
Which language are you playing the game in? English
How often does the bug occur? Rarely (0% - 9%)
What is your current game version number? n/a
What expansions, game packs, and stuff packs do you have installed? All released content installed.
Steps: How can we find the bug ourselves? Not sure what to say here. I just noticed the problem yesterday. It does appear to be the only pet only household created by the game in the different worlds in this save. Since it isn't supposed to happen, I have no idea how it occurred, or how the issue could be duplicated.
What happens when the bug occurs? Penthouse shown as occupied but only a cat shows. It has caused weirdness, though. At different times when I kept checking to see if there was an owner, it has shown different housed sims in San Myshuno pictured with the cat. It's like the game knows it shouldn't be there alone but can't solve the problem. I've seen the sim that lives next door to the Jang family shown with it, as well as Rasoya and tonight it even showed a ghost that moved into San Myshuno but lives elsewhere.
What do you expect to see? No pet only household since it isn't supposed to be allowed by the game.
Have you installed any customization with the game, e.g. Custom Content or Mods? Never used.
Did this issue appear after a specific patch or change you made to your system? Neutral/Not Sure
I haven't attempted to rectify the problem yet because I'm not sure of the best way to handle, i.e. evict or attempt a merge. The name for the household is Holliday but no such household appears in household manager when accessed from top icon. I got the pic I've attached by clicking on the household button with the lot selected.
Well, since the cat comes with 20,000 simoleans, I guess I should select a family to merge it with, lol.
- @crinrict since you're trying to clean up the list by checking status on old issues, thought I'd say that I haven't had this occur in my game since January 2018. It didn't seem to be a prevalent problem at the time either.
Think we can safely assume this issue was fixed and you can close this thread.