I did something extremely stupid on my game, and I am stumped as to how to fix it.

I feel victim to the Open for Business bug whereby my Sim got stuck shooing people away when she tried to close down for the day and drive her own car home, and, not thinking clearly, I decided to delete her to force a respawn, which has worked for me in the past when a Sim has gotten stuck. However... she was the only one on the lot. (Not thinking at all!) So, now that entire family is stuck in limbo, as I cannot go to their house to summon her, and I cannot make someone go to the business lot in question, as it is listed as "closed". I can summon the "missing" Sim if I use the Batman Box on other lots, and I can invite her and her spouse over to other Sims' houses via the phone and interact with her normally. She also shows up fine in SimPE, and she isn't listed as unplayable. Just to make sure, I also removed all of my custom content and that did not make any difference.

Is there any way I can either force someone to go to that lot so I can summon the missing Sim back, or is there a way I can make her reappear, or any other idea? I'd really hate to scrap that family entirely, but if that's what I must do, then at least I learned to patch my game, right?

Last edited by Xihao : 20th May 2010 at 02:47 AM. Reason: Problem solved

If you run SimPE and open your neighborhood, then select Family Information (FAMI) in the left pane and your family in the right pane, and look at the Plugin View in the bottom pane, is the "Now on Lot" field equal to either your family lot instance or your business lot instance (ie, the instance number of the Lot Description (LTXT))? If it's the business lot instance, could you try changing it to your family lot instance? Be sure to backup first, since I'm not sure that this will work.

That completely fixed it! Thank you so much!!

Excellent. This is a problem that I've seen reported by a lot of people, but I've never seen a good solution before. While doing something else in SimPE, I noticed this field and immediately thought about this problem. But, since I've never experienced the bug myself, I wasn't able to test the solution.

Last edited by Mootilda : 20th May 2010 at 03:16 PM. Reason: Fix typo