Florian

@tryashtar This is a newly generated world. This happens in all worlds, just not necessarily as visible as here.

Yes, I used chunkbase. But it is not really relevant because I checked in-game. I have also just attached a new in-game screenshot with a map.

we don't have any responses from the developers regarding fixing this bug

we are all looking forward to receiving an update that will fix this bug!!

it lasts since the 1.16.200!! Some players have had their game refunded because of this lag!

our games are unplayable since this update, how much longer are you going to keep us waiting??

Here is my system, please Mojang update this version the shift makes my Minecraft unplayable 😞😞😞

my Minecraft is unplayable because of this lag...

?

Please how can I do half turn and return to 1.16.100 ??

On 20w27a, I got ~10 mspt on water creation and ~16 mspt on water removal.

I attached a screenshot where we can see the mspt graph.

The average mspt for a complete cycle is 11 mspt with a peak at 124 mspt.

I also attached a world save for 20w27a with a clock to facilitate testing.

Apparently of no use

Yes, the exact same error occurred with me, it's really annoying.

• MC-178145

I hope for both of us that the error will be fixed soon.

@violine1101 I just redid the test on my machine (the one used in the original post), and my timings are comparable to yours.

One thing to notice though, now that we have mspt chart, we can see that the maximum mspt is much higher than what we saw (more than 100 mspt), and the ~20mspt is an average over a handful of ticks.

Can confirm this too. Used a Efficiency 5 shovel on dirt.

Has it been fixed? This issue seems to be resolved https://bugs.mojang.com/browse/MC-123790 so why is this issue not marked so?

It is still in 1.13.1-pre2, but the performance keeps increasing. I just put the new times in the description.

Good job in tracking down the issue bit by bit: keep going 😉

As far as I can understand: yes.

MC-136107 was not out when I started to write this bug report though.

It is much better in 18w33a, but it is still much slower than in 1.12: I recorded a tick time of 24 mspt, which is 3 times slower than 1.12.

As a side note, the performance hit now looks symetric (same slow down when putting water than when removing water).
That was not the case in 1.12, so it might be good to sum up the results in a table:

So the water in 18w33a is still x3-x5 slower than in 1.12.

I fail to see the how it relates to MC-123263.
MC-123263 is about client performance (Frames Per Second) while this bug is about server performance (Ticks Per Second).

I can confirm something similar:

• Generated multiplayer survival map on 18w15a (using minecraft_server.jar)

• /location Stronghold would lead me to 8, ~, 8

• No stronghold there

• Updated to 18w16a

• /location Stronghold would lead me to 1000, ~, -1333

• No stronghold there

• ... restarted the game a few times ... (still on 18w16a)

• /location Stronghold would lead me to 8, ~, 8 again

• Still, no stronghold there

When I created a new singleplayer survival map using the exact same seed on 18w16a the `/location Stronghold command would lead to 1000, ~, -1333 again, and the stronghold would actually be there.

Is there any chance this can be fixed going forward from now?

Or do I have to generate a new map if I want to play the stronghold?

EDIT: My seed was -3747108452376540287