Hello!
I have created test custom dimension, but “has_fixed_time: true” parameter does nothing: when you request daytime via “/time query daytime” command, you get daytime still ticking. So it goes 1000, 1001, 1002… 20 times at second.
That causes problems with some technical moments on my map. Also shaders interpret this as real time and when time gets to night time – there are no shades at all.
Attachments
Comments 4
I know this 🙂, Though. But, for example, on paper every dimension is independent. Well, it is not so important, because we’re talking about vanilla version. But then – what is this parameter needed for? It looks like it does nothing.
Thechnical time is still ticking, visual settings are independent and controlled via environment attributes. Timelines are also still ticking. In my opinion there are two possible time instances: tech + visual. What else?
I don’t understand what this parameter does…
“However, the remainder of behaviors formerly affected by fixed_time being present will now instead use the has_fixed_time boolean”
What are remainder of behaviors? If it’s not visuals (environment attributes) then it’s technical time with influences spawn. bees and so on. But if time and timelines are still ticking, then the only thing that remsins is tech gameplsy time…
Hi!
Thank you for your report!
After consideration, the issue is being closed as Invalid.
You have posted a feedback. This site is for bug reports only.
For feedback, please visit https://feedback.minecraft.net
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
The passing of time is global, not per-dimension