Dragorn421

Converting to 1.12.2 then to 1.13 fails too: the 1.13-pre2 client crashes with the same error as in the "first_attempt"-prefixed files.

And, still as a side note, the launcher crashed the two times I exited the game.

(thanks for suggesting though!)

This may affect 1.13-pre1 (os: Windows 10 x64, java: 1.8.0_25 x64)

I "converted" a 1.12 world over to 1.13, ran /locate Igloo and got the same issue as described here: server froze, I eventually got kicked out.

Going back in the same world (worlds menu showed it was a 1.13 world), I could not reproduce the bug: there still was a freeze but eventually i got told there was no igloo nearby. Further runs of the command (still targeting igloos) caused no freezing

As a side note, the world conversion took about 20 seconds, though the world is a small creative test one with few chunks generated. And i'm not playing on a toaster!

The block animation may be considered okay, but this should be considered as a bug since it causes non-pausing of client-side velocity on singleplayer worlds. Unsure if I should create a new ticket.

How to reproduce (1.12 pre6):
1) In singleplayer (didn't test multiplayer, i guess it's not affected), jump and while in the air hit escape (or open a command block, or a written book, same deal)
2) See the game rendering continue to animate blocks, and applying any velocity or gravity, but since the game is "paused" it puts you back at your previous location almost instantly, which causes some "shaking".

Same in other languages (it's actually weird that the narrator automatically uses the system language instead of the game language or some other setting, maybe I just didn't find it). Not sure if it actually is a bug though.

Confirmed for 1.12

Actually the boat movements seems to get softened, and that makes it visually bounce on the air when it hits the slime block server-side and it goes up again before it hits the ground client-side.

MC-111271 describes it better, and the gif in this issue is still relevant for 1.12.

EDIT: on a side note, slime blocks pushed by pistons sometimes fail to launch a boat in the air and only push it a few blocks. Is that a different issue?

I don't see how this could get fixed, and the player can anyway use some mod to use xray. It's a pain for servers alright, but for adventure maps or solo I think the players are only ruining their own experience when using xray.

Only "fix" I know is what several plugins do on servers: hide all the blocks (do not send them at all to the client) which are not supposed to be seen. I don't think Mojang wants to do that, even if it was disabled by default.

Confirmed for 1.10.2

Definitely confirmed for 1.9. I got similar issues to previous ones multiple times.

Confirmed in 1.9 release, I found a sheep stuck in a cobblestone wall.
It was one of the red sheeps that was stuck in the wall i'm looking at in this screenshot http://puu.sh/ns0NT/975ba2cd06.png (i'm facing negative x y and z). It happened on a 1.9 vanilla server which "java -version" is:
java version "1.7.0_95"
OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)

I don't know if this happens because of chunk unloading and loading or just if the world stays loaded quite some time.

I updated my server's version to 1.9 from 1.8.9. Immediately after I log on two zombies are attacking me: they came from the hundred zombies that were still in my xp farm collection thing when I stopped the server to update it, so they escaped their cell somehow. I still have a save of the 1.8.9 world if you need it (500mo though), but this seems quite random and not easy to reproduce.
Here is what their 'cell' looks like: http://puu.sh/nq6wD/325b690631.png
They stand on a slab and there is a 1.5 blocks gap (no baby zombies can reach this point).
Sadly I don't feel like this is fixed, or it's a different issue. I didn't notice anything weird in logs (3 entities, not zombies, seemed to have duplicated UUIDs).

Another Confirmed for 16w04a

This is a weird behavior because you can make the boat go forward, then leave it, and come one month (in game or not) later and the boat will take its momentum back. Even in Minecraft things aren't supposed to freeze like that, excepted chunk unloading. I consider it a bug since it didn't behave like this in previous versions, and wasn't mentioned in update notes.

Confirmed in 16w02a.
Water renders flickering, and is inside the boat.

This happens in Minecraft 1.8.8, should I open a new issue, as this one is really old and closed?