Jump to content

Recommended Posts

Posted

A friend of mine opened up a server a few weeks ago and all has been great until a few days ago. Time flies by rapidly whenever he tries to play. A whole day will pass for him in about a minute, and he can’t pick up anything either.  Does anyone know what to do to fix this?

Thank you!

  • 4 months later...
Posted (edited)

When reporting a bug, please always give some information, like game version you play on and mods you use, general hardware info (especially CPU), if it happens on a server how many players do experience the same issue, if possible the affected player's latency...

Without information everything anyone can do is guess what could cause such a problem, which makes finding the actual problem take longer and with that finding a fix for it even more so.

Edited by Hal13
  • 1 year later...
Posted (edited)

I am experiencing this as well. I was able to reproduce it past a computer reboot, thinking it was due to not having rebooted my computer in a few days.

  • CPU: Intel Core i7 860 2.8 GHz
  • OS: Windows 10 22H2
  • Game version: 1.18.8
  • Active mods:
    • Animal Cages 2.0.6
    • Kiln Spreading 1.0.0
    • MumbleLink 1.3.1
    • Pet AI 1.5.5
    • Tree Tapping 1.0.0
    • Vintage Titan 0.2.1
    • Creative Mode 1.18.8
    • Essentials 1.18.8
    • Survival Mode 1.18.8
    • Wolf taming 1.5.4

EDIT: Resetting /time speed and /time hoursperday to  60 and 24 respectively fixed the issue.

2023-08-26 14_23_09-Clipboard.png

Edited by toshirotaii
  • Like 1
  • 7 months later...
Posted

Just started happening to me, too! I checked the base time and it says: Base Time speed 60 set, 1 day = 8.2 real minutes.

Last night 1 day = 40 realm minutes!  Now the torches are burning like the end of the world and the sun is streaking across the sky! I'm betting the game will be unplayable in this mode... I'll never make enough progress to survive winter! The time defaults were set to normal on world creation except 1 month = 30 days.

Posted

@Maethius This generally happens when you somehow manage to leave a bed "improperly". Don't ask me how, I don't know :P But that way the time acceleration from the bed doesn't get cancelled.

The solution is to enter the bed again and get out of it normally.

  • Like 3
  • Thanks 3
  • 1 month later...
  • 8 months later...
Posted (edited)

Still happening - had a run (1.20) suddenly start going fast, slept twice, changed the /time speed setting, and all is fine. Thanks for the advice, ppl.

Edited by Aspendosia
  • 1 month later...
  • 2 months later...
Posted

The next time someone runs into this problem, does a search, and winds up here, they can check out this video that I made.  I do a deep dive into the save file and examine which data in there actually changes (and how to change it back) when this glitch rears its hyperactive head.

  

  • 1 month later...
Posted
On 5/23/2025 at 4:28 PM, Zippy Wonderdust said:

The next time someone runs into this problem, does a search, and winds up here, they can check out this video that I made.  I do a deep dive into the save file and examine which data in there actually changes (and how to change it back) when this glitch rears its hyperactive head.

  

To answer the question you had at the end of the video, the data is encoded in the Protobuf format. The game saves TimeSpeedModifiers in a key value store where the key is a string and the value is a float.


Looking at [E2 01 - 0F [0A 08 - "sleeping" - 15 - 00 A0 A5 44]]


[E2 01] is 226 Varint encoded. Taking 226, which is 11100-010 in binary, 11100 is 28, which is the tag for TimeSpeedModifiers and 010 is 2, which is the ID for a length prefixed type. As you figured out, [0F] is 16 Varint encoded, which is the length of the encoded key value pair.


The key value pair is encoded the same way. [0A] is 10, which is 1-010, 1 is the tag for Key 010 means its length is prefixed. You then have the length 08 followed by "sleeping". Next you have 15, which is 10-101, 2 is the tag for Value and 101 is 5, which is the ID for a fixed 32-bit value. The remaining 4 bytes are the float.

  • 4 weeks later...
Posted

Still happening in 1.20.12. I have no useful information for repo conditions, but /time speed and /time stop commands had no effect, despite both printing standard response to log and the actual speed variable seemed to be updating fine, as I was able to read it back with /time speed. Exiting the world and loading in again had no effect. Closing the game and opening it again had no effect. Going to bed resolved the issue just like for other people here. That's all I got.

  • Like 1
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.