The Insanity Continues - More Firefighter Troubles

[Orbit]

Well, I managed to put the fire out.  But now as soon as one fire truck leaves, another one comes and a fireman gets out and loiters for 5 hours, then gives the "everything 's okay" message, gets back in the truck and drives off, then another one comes and starts the cycle over again.  I've already gone through 10 cycles of trucks, and they keep coming.  I tried restarting the game, but that doesn't help.  Any help?

[Wolfee]

Umm, my aren't you lucky. Sorry I can't help much but have you tried using boolprop and forcing an error? I think that's what people do when freaky things happen in their games. 

[Orbit]

Boolprop and forcing an error?  Please enlighten me.  I have J.M.'s lot debugger which has a "force error" option......

[Wolfee]

 Wait that's it, sorry about that. I got it wrong. My brains a little tired tonight and I got things mixed up, opps . I believe J.M.s debugger is what you should use

[Lythdan]

Actually, the lot debugger forces an error on *everything*. To force an error on something specific, boolprop testingcheatsenabled true
--> shift click ---> force error.

[Orbit]

What should I force error and what option should I choose when force erroring it?

[DrBeast]

Wait, I'm missing episodes here. What exactly caught fire to begin with? Shift-click on that item, force error, reset. If that doesn't work, force error again, delete.

Edit: If that doesn't work either, use the lot debugger to force error on everything. Should grind your game to a halt for some time until the debugger is done forcing errors on everything, then it'll be business as usual. I think. I've never tried that function in my game.

[Orbit]

My sim started a cooking fire on a stove.  I have Carrigon's Bad Ass Fire Hack which caused the stove to burn until it was a pile of ashes.  When I use J.M.'s lot debugger, it forces an error on everything, but I presume that you have to enable testing cheats again, so I did, which gave me error messages about everything on the lot, but on some error messages, no matter which option you click, it stays on that error message.

[DrBeast]

My sim started a cooking fire on a stove.  I have Carrigon's Bad Ass Fire Hack which caused the stove to burn until it was a pile of ashes.  When I use J.M.'s lot debugger, it forces an error on everything, but I presume that you have to enable testing cheats again, so I did, which gave me error messages about everything on the lot, but on some error messages, no matter which option you click, it stays on that error message.

Take out that hack and see what happens. What do those error messages mention? What's the item that causes the error? Try Delete on those, you'll lose that item but retain your game. And leave that hack out for heaven's sake! Totally non-awesome, brrr!

[Venusy]

My sim started a cooking fire on a stove.  I have Carrigon's Bad Ass Fire Hack which caused the stove to burn until it was a pile of ashes.  When I use J.M.'s lot debugger, it forces an error on everything, but I presume that you have to enable testing cheats again, so I did, which gave me error messages about everything on the lot, but on some error messages, no matter which option you click, it stays on that error message.

Take out that hack and see what happens. What do those error messages mention? What's the item that causes the error? Try Delete on those, you'll lose that item but retain your game. And leave that hack out for heaven's sake! Totally non-awesome, brrr!

If I understood Orbit's post correctly, he ignored the "BIG RED BUTTON!" warning and hit Force Errors on the Lot Debugger in debug mode. Next time, use force errors on the lot debugger after making sure debug mode is OFF. But as DrBeast said, try yanking out the Bad Ass Fire hack and see if that's the culprint.

[DrBeast]

If I understood Orbit's post correctly, he ignored the "BIG RED BUTTON!" warning and hit Force Errors on the Lot Debugger in debug mode. Next time, use force errors on the lot debugger after making sure debug mode is OFF. But as DrBeast said, try yanking out the Bad Ass Fire hack and see if that's the culprint.

Hmm, yes, you're correct there. Been meaning to suggest that in both my replys but always forgot!