This issue also seems to make you unable to /give player heads of players that are not currently in the world/server
Sounds like a big TPS lag spike, is there anything at that point that might cause it when it loads?
Wrong section, this is a bedrock issue
I think i just had a stroke reading that. If it's telling you that you are already logged in and you restarted your pc that can mean you are logged in at an another location
Idk what am i doing wrong, but every time i search it comes up with totally unrelated stuff, so i report. But every single time a couple hours after i post it someone always finds a duplicate
AFAIK random tickspeed doesnt affect copper weathering, nor does rain. It takes about 60-80 ingame days to change state once
Soo, what is supposed to be the problem here? Of couse the river is a river biome, what did you think?
No, this isnt the place to ask this and you sohuld email them. And you made a mistake by posting your email adress here
Confirmed for 1.16.3
This has been reported a lot of times already, if it really bothers you, vanillatweaks has a resource pack that fixes them
Sadly, i wasnt't able to recreate it in vanilla. It might be a plugin bug, but if it works in vanilla, it would require so precise timing that it would be very impractical to use
That's what the picture shows. The part generated in 1.14.4 has ores and trees, and the part generated in 1.16.2 is just blank stone with the occasional village. On the topic of villages, if i generate a superflat world with a biome that doesn't have villages it will generate plains villages, but i see that has already been reported. Preset:
minecraft:bedrock,60*minecraft:stone;minecraft:taiga;village,mineshaft,stronghold,decoration,lake,lava_lake
Some windows pcs have a function button that activates the function keys. So instead of pressing F3 + N you press Fn + F3 + N
I forgot: Villages with the old style well do this too
Are you sure it isn't caused by the resource pack?
This is not a bug. You force quit minecraft so the world didn't save properly.
Data corruption is not a bug and it should not be reported here
They are not supposed to waterlog yet. Maybe they will in a later snapshot
Can confirm in 1.20.1