Kristian Spangsege

Seeing the same thing here. No lag on client side. Server runs at very low tick rate. Eating takes a long time. Mobs move slowly and jittery. None of the usual suspects seem to be at play in this world (no redstone or other mechanical contraptions). The lag started to occur shortly after switching from 1.13-pre4 to 1.13-pre5.

Just tried to see whether upgrading from `18w21b` to `1.13-pre1` works, i.e., whether it no longer converts all book enchantments into "Protection". Unfortunately, Minecraft crashes whenever I try to open a `18w21b` world in `1.13-pre1`. I have tried two different worlds, one of them being a newly created one, where all I did was to put a couple of books in a chest. Not sure whether it is related to the books, or a general problem with upgrading to `1.13-pre1` from `18w21b`.

The problem has disappeared for me now. Apparently Mojang fixed the problem.

Judging from a comment in this forum thread, a possible workaround might be to use OneClient. Hopefullt it is not malware. Anybody have any experience with it?

According to this forum post, it also affects Windows 7.

As a temporary workaround you can use the test version of the new Launcher. That still seems to have an issue with modded versions though.

@unknown Unfortunately, this does not work on Linux Mint 18.1 (or Ubuntu 16.04) due to wrong version of libICU. Would be nice if we could compile the launcher ourselves.

./launcher: error while loading shared libraries: libicui18n.so.57: cannot open shared object file: No such file or directory

Question: If the problem is caused by an automatic launcher update, is there a way we can use the prior version of the launcher?

Same thing for me on Linux Mint 18.1 (Serena). Worked yesterday.

I'm wondering whether it is an Ubuntu package upgrade that caused it. Have you guys also updated Ubuntu packages since it last worked?

Confirmed for 1.8.4.

It seems to me that this has gotten a lot worse in version 1.8. It never occurred to me in 1.7.10, where I sailed a lot. It has now occurred trice for me i 1.8 over just a few days of play.

Also, as far as I can see, I am not doing anything differently than I used to, while in the boat.

The last time it happened, I entered the boat on shallow water (1 deep) and was killed almost instantaneously (within a second).

No soul sand or half slabs were involved in my cases.

Still not resolved in version 1.8 (the version released today). All issues mentioned above are still present.

All issues confirmed to still occur in 1.8-pre3

This collage hopefully helps to show exactly what I am talking about. Note that the bug occurs only in the preview versions of 1.8, and only to a repeater in an immediately adjacent series, and only when it is neither the first, nor the last repeater in that series. Note that this only addresses the synchronous aspects of this bug. By "synchronous" I mean that the timing of the "lock" signal is coupled strongly to the timing of the main input signal.

Yes, MC-54711 appears to coincide with my item 2 "Loosing 1-tick off". Also, it could be that my item 1 "Delayed lock" is just a different aspect of the same underlying bug, but maybe it is not.