- Mar 5, 2024
- 66
- 33
Well as v8.31 was released to the public yesterday, without an anouncement of the date beforehand. I will just post this now - and thus give everyone the opportunity to use this feature (eventhough I do not really think, that anyone, who did not figure that one out for himself/herself does deserve to use this feature without possible negative sideeffects of occassionally losing a day by going to bed too late).
The variable $daycount is set to 1 at the time the midnight calculations do happen. Meaning, if the midnight calculations happen at midnight, then one has to go to bed at 6:48 am at the latest to not miss a day. If the midnight calculations happen at 0:06 am, then one has to go to bed at 6:52 am at the latest (in this case the displayed clock does also match the "internal" $daycount variable between 0:06 am until one goes to bed or until the variable $daycount is again 240 or higher). And if the midnight calculations happen at 0:12 am then on can go to bed at 7:00 am or earlier (to not lose a day).
Now there are ways to make sure that the midnight calculations do happen late. Ie. by starting a round of carousing in Dockgrave tavern at - lets say - 11:54 pm, which would then let the midnight calculations happen at 2:54 am, as a round of carousing takes 3 hours. By starting a pool party at precisely 11:54 pm, the midnight calculations can only happen at 1:54 am (or later).
Happy feature using.
BTW: This could easily be fixed, if (in the case the $daycount variable is set to 1) the value of _savecount-241 would be added to $daycount (if _savecount-241 is positive) - as _savecount is set to $daycount before $daycount is set to 1.
The variable $daycount is set to 1 at the time the midnight calculations do happen. Meaning, if the midnight calculations happen at midnight, then one has to go to bed at 6:48 am at the latest to not miss a day. If the midnight calculations happen at 0:06 am, then one has to go to bed at 6:52 am at the latest (in this case the displayed clock does also match the "internal" $daycount variable between 0:06 am until one goes to bed or until the variable $daycount is again 240 or higher). And if the midnight calculations happen at 0:12 am then on can go to bed at 7:00 am or earlier (to not lose a day).
Now there are ways to make sure that the midnight calculations do happen late. Ie. by starting a round of carousing in Dockgrave tavern at - lets say - 11:54 pm, which would then let the midnight calculations happen at 2:54 am, as a round of carousing takes 3 hours. By starting a pool party at precisely 11:54 pm, the midnight calculations can only happen at 1:54 am (or later).
Happy feature using.
BTW: This could easily be fixed, if (in the case the $daycount variable is set to 1) the value of _savecount-241 would be added to $daycount (if _savecount-241 is positive) - as _savecount is set to $daycount before $daycount is set to 1.