| Author | Overtime at steel works, great capital |
|---|
| The shift overs at 8.30 but its already 8.33 and the shift isn't over. Some bug? |
Similar thread:
https://www.lordswm.com/forum_messages.php?tid=1917323 |
| It usually lags sometimes. I reckon that the enroll function has the lowest processing priority in the server or something. |
| In my personal experience, that "bug" only occurs when I enroll in Machining or Production factories and never at any of the Mining factories. |
| Question: does it happen when you have workaholic penalty? My multi is currently down to 0.1 wage and she spent a few minutes in overtime. |
It has nothing to do with workaholic penalty.
As far as I know, it is not known if this is a bug or by design. BrownBears answer covers as much as I know about it too. |
it seems to be a bug related to integers.
Shortly, when you start a shift after XX:X2'30" or XX:X7'30", server considers it as if it started at X5' or X0' that follows, but shows it as if it started 5 minutes earlier.
So, if a shift starts at 8:33, server will show its end at 8:30, but will really ends it at 8:35. |
| It is a design feature. Implemented to deter script users from trying to auto-enroll or auto-sell etc. By moving the shift end back 5 minutes, it upsets people trying to use scripts. |
I reckon that the enroll function has the lowest processing priority in the server or something.
+1
I think that's correct. The "worker payment" process checks all the mines every 5 minutes. Every once in a while, it lags, possibly because of a low priority or high server load. |
No, it is specifically a script breaker.
https://www.lordswm.com/forum_messages.php?tid=1892732 |
| closed by Queen_Amanda (2012-08-23 20:34:16) |
|---|
