Make syncing a clock sensor with schedules easier

[DraconicSiege]

I've noticed something a little annoying that has to do with schedules and clock sensors. One cycle is 600 seconds long. The schedule has 24 segments. This results in each segment being 25 seconds long.Here is where it gets annoying. This means that each schedule segment is 4.1666666667% of a cycle long! The reason this is so troublesome is that the clock sensor is incremented by percentage, not seconds. Translating events on your schedule over to a clock sensor is thus not a simple matter and requires you to fine tune it when the event occurs, not just set it and forget. Well, at least if you are a perfectionist that is...

My suggestion is rather simple: change the schedule so there are 25 segments in a cycle, each one 24 seconds long. This results in each segment being exactly 4% of a cycle and gives you one more scheduling block to use. The night time would still be 3 segments, so it would last 72 seconds instead of 75. There is still plenty of time for dupes to regain stamina since they don't need to sleep to whole night anyway if they have cots or better. This would also mean 3 more seconds of sunshine for solar panels.

I just want this to be a simple quality of life change that makes things a little more neat and concise for those perfectionists out there. What do you guys think?

[Zarquan]

The 24 segments are to look like hours

I think it would be better to have the clock sensor operate in seconds rather than percents.

[DraconicSiege]

1 minute ago, Zarquan said:

The 24 segments are to look like hours

I think it would be better to have the clock sensor operate in seconds rather than percents.

Good point.

One other thing I forgot to say was that they should mark the segments on the clock sensor to help you line them up.