Programmable Sleep Clock v3.31

<< < (54/59) > >>

J. M. Pescado:
There's no manual bedtime. The bedtime is calculated based on the recharge rate of your bed combined with the desired wake time. The clock automatically makes the calculations to determine when that is, which changes based on your sim's energy status.

jsalemi:
I know this hasn't been updated since mid-June, so maybe it's the latest Seasons patch causing it, but the bed nazi suddenly seems much more agressive.  It's kicking out parents who autonomously go into the kid's bedroom to tuck them in, or neat sims autonomously going into another bedroom to make the beds.  It wouldn't be bad if it didn't send them all the way to the curb, but I've been surprised many times to see a sim heading for the door that currently wasn't under my control, only to find a 'No bed for you!' icon in their queue.  I've had to turn off the bed nazi in pretty much every lot with kids or a particularly neat sim.

BattyCoda:
I have seen this behavior as well. This was a parent heading up to "Tuck in".

Gwill:
Quote from: J. M. Pescado on 2007 July 08, 20:06:08

The Sleep Clock does not wake up sims, so not sure what's going on there. Are they fully recharged? Perhaps it's the coffin code which is wonky, and Servos were not meant to use coffins.

Quote from: J. M. Pescado on 2005 July 26, 17:45:53

Sim will not awaken even if
   his energy bar is full/you queue stuff until the appointed time, unless
   his energy bar is full 6 hours in advance of the time (as standard).


Could it be as simple as the fact that servos are "assign only" and thus do not have a wake hour, and therefore is awakened?  Possibly in combination with power/energy confusion?  I refuse to leave mysteries unsolved!

Oh, and I've also noticed parents suddenly getting kicked out when trying to tuck in a child.  I'm pretty sure it didn't use to do that; I think it changed when I installed the latest seasons patch.

witch:
Now a while ago, people were saying Bed Nazi wasn't working properly, I certainly found it wasn't. Maybe JM updated it and the patch has now fixed something and we're getting a double whammy?

Navigation

[0] Message Index

[#] Next page

[*] Previous page