So far the only thing I could find is with the fillbiome command.
Steps to reproduce:
Create a new world with a datapack that has a tick.mcfunction with the following command: execute as @a at @s run fillbiome ~-10 ~-10 ~-10 ~10 ~10 ~10 minecraft:deep_dark
Teleport to a random completely unloaded location e.g. /tp 10000 100 10000
Observe the game’s log output to see a bunch of warnings [19:01:09] [Render thread/WARN] (Minecraft) Ignoring chunk since it's not present: 624, 624 [19:01:09] [Render thread/WARN] (Minecraft) Ignoring chunk since it's not present: 625, 624 [19:01:09] [Render thread/WARN] (Minecraft) Ignoring chunk since it's not present: 624, 625
The fillbiome command sends a ClientboundChunksBiomesPacket , so when that command starts executing in a chunk that is not ready to be sent to the client, the client receives packets for a chunk that doesn’t exist yet from its POV.
Now this isn’t really a big problem cause when the chunk’s data does get sent to the client, the biome data will still eventually be correct. So barely a “gameplay issue” but it’s all I could really find in a fully vanilla environment.
So far the only thing I could find is with the fillbiome command.
Steps to reproduce:
Create a new world with a datapack that has a
tick.mcfunction
with the following command:execute as @a at @s run fillbiome ~-10 ~-10 ~-10 ~10 ~10 ~10 minecraft:deep_dark
Teleport to a random completely unloaded location
e.g.
/tp 10000 100 10000
Observe the game’s log output to see a bunch of warnings
[19:01:09] [Render thread/WARN] (Minecraft) Ignoring chunk since it's not present: 624, 624
[19:01:09] [Render thread/WARN] (Minecraft) Ignoring chunk since it's not present: 625, 624
[19:01:09] [Render thread/WARN] (Minecraft) Ignoring chunk since it's not present: 624, 625
The fillbiome command sends a
ClientboundChunksBiomesPacket
, so when that command starts executing in a chunk that is not ready to be sent to the client, the client receives packets for a chunk that doesn’t exist yet from its POV.Now this isn’t really a big problem cause when the chunk’s data does get sent to the client, the biome data will still eventually be correct. So barely a “gameplay issue” but it’s all I could really find in a fully vanilla environment.