How to reproduce the bug:
Go to a new world and type "/tick freeze".
Build a copper golem.
Do "/data get entity (uuid from the golem) next_weather_age".
Real result:
The copper golem takes far too long to advance to the next weather state. Example: next_weather_age = 519863L, gametime = 692. 519863 minus 692 equals the remaining time to wait until the next stage (in ticks). However, this is far too long and makes no sense.
Expected result:
The copper golem must not set the next timestamp for next_weather_age so far into the future.
Hi!
Thank you for your report!
We're actually already tracking this issue at MC-300362, so I will resolve and link this ticket as a Duplicate.
I suggest also to browse through the main issue for potential fixes.
If you would like to add a vote and any extra information to the main ticket it would be appreciated. Thanks!
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki