EngineHub
Locking time breaks redstone
using the /time -l command will lock the time to specified value but will also break all redstone circuits in that world.
This is unavoidable when locking the time fully. Many of the minecraft physics operations and redstone changes occur every tick. Time lock prevents ticks from occuring, causing problems with physics and stopping redstone.
On Sun, Jul 31, 2011 at 7:09 PM, d00ba < [email protected]>wrote:
using the /time -l command will lock the time to specified value but will also break all redstone circuits in that world.
Reply to this email directly or view it on GitHub: https://github.com/sk89q/commandbook/issues/23
duplicate of something (can't check now, go look through the closed issues it's probably there)
zml2008: True, though surely theres ways around this.
For example: Instead of locking the time completely, it would lock it to a specific hour so time still moves normally. Locking the time to 3pm would set the time to 3pm and allow time to continue as normal until it reaches 4pm it would then loop back to 3pm and so on.
There are plugins not made by sk. Look at some. There are a few that do what you want.
Sent from my iPhone
On Aug 3, 2011, at 11:21 AM, d00ba [email protected] wrote:
zml2008: True, though surely theres ways around this.
For example: Instead of locking the time completely, it would lock it to a specific hour so time still moves normally. Locking the time to 3pm would set the time to 3pm and allow time to continue as normal until it reaches 4pm it would then loop back to 3pm and so on.
Reply to this email directly or view it on GitHub: https://github.com/sk89q/commandbook/issues/23#issuecomment-1720348
