Fix: disable time updates when not needed

[reosfire]

When time rate is zero we do not need to send TimeUpdatePackets to users.

[emortaldev]

What about when you do setTimeRate(0) and setTimeRate(1)? TimeUpdate will stay as null

[mworzala]

This should not alter the time update. Avoiding sending the time packet should be handled when sending it during tick, here:

Minestom/src/main/java/net/minestom/server/instance/Instance.java

Line 666 in 4fea03f

PacketUtils.sendGroupedPacket(getPlayers(), createTimePacket());

I was under the impression the client would predict the time rate so you had to continuously send the time packet, but apparently that is not the case (anymore?).

[reosfire]

This should not alter the time update. Avoiding sending the time packet should be handled when sending it during tick, here:

Minestom/src/main/java/net/minestom/server/instance/Instance.java

Line 666 in 4fea03f

PacketUtils.sendGroupedPacket(getPlayers(), createTimePacket());

I was under the impression the client would predict the time rate so you had to continuously send the time packet, but apparently that is not the case (anymore?).

You right client some how uses this information. But it is not clear how exactly. If continuous packets sending is disabled, everything what I can imagine works properly. Probably this changes must wait for clarification of how client is affected by them

[DeidaraMC]

You right client some how uses this information. But it is not clear how exactly. If continuous packets sending is disabled, everything what I can imagine works properly. Probably this changes must wait for clarification of how client is affected by them

The client uses the world age for shaders