The Plum Gate Posted December 20, 2020 Share Posted December 20, 2020 We have this cycle timer for automation. It's kind of a trick getting things set to work in such that they correlate with the block schedule the duplicants use during their work shifts ( - the existing block scheduling mechanic is great ). It would be nice to have an automation timer or block scheduler that shared the block format behavior with the duplicant's shift scheduler. This would have the same type of paintable interface used for dupe scheduling incorporating the red / green color motif, paintable to control signal output on a per schedule block basis rather than by percentages of cycle. This would allow multiple on and off time blocks for a single timer (port) as well. ( though, not multiple schedules or output terminals per timer. ) Multiple schedules per single timer building sounds like a ribbon cable attached automation building. So, this is an additional building suggestion for the 4 bit wire. I just need this night light on when my night owl scared of the dark dupe is actually sleeping so, a correlation with the dupe schedule blocks and automation timers would be great. I managed a work around in the meantime with the existing timer. Link to comment Share on other sites More sharing options...
Sith515 Posted December 21, 2020 Share Posted December 21, 2020 Probably the easiest and most optimal way is to just put all nyctophobic dupes in one area and plug a lamp on a motion sensor (it still detects dupes just existing in that spot), simply because they won't always come at exactly bedtime and leave at exactly worktime (you can watch francis video on that) Alternatively, weight plates, but it's the same exact solution really (both just directly plug on the lamp with nothing fancy) Link to comment Share on other sites More sharing options...
The Plum Gate Posted December 21, 2020 Author Share Posted December 21, 2020 These are good solutions, and I can manage with the existing timer in this particular instance. Such a block scheduler would kind of unify timely automation processes with schedules. This type of scheduling gives a bit more agency to automation timers in general as the resultant machine behaviour could be treated more like a duplicant's work schedule. I can imagine a better interplay here, that is to say. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.
Please be aware that the content of this thread may be outdated and no longer applicable.