MalbaCato

this is not suited for the bugtracker, but as I assume this ticket is going to attract many of these questions, answer is go to https://adoptopenjdk.net and follow some simple installation prompts, make sure to download java version 16.

WEB-1839 that got resolved as a duplicate of this had one detail that is missing from fabian's report - it claimed "Host your own server" should be unticked in the Windows 10 column.

While IIRC the the possibility to self host does indeed exist on Win10, I'm not going to install the OS just to test that, and will just point out the bit of information lost by that duplicate closure.

Confirmed for 18w33a

Can we rename the issue to be more descriptive please?
I'm sure that counting something that was implemented more than 4 years ago as new is on the more confusing side of things.

Was able to reproduce in the current version
I updated affected versions, please reopen.

(Also of course that was done on the latest OS)

Currently can't reproduce, but it may need further testing. This big is somewhat random and sometimes it just doesn't occur. I also updated the OS since then so it also may have some affect, and might still be present for others.
TL;DR "cannot reproduce" not "fixed"

Can we change the name to exclude the unhelpful 1.5 in there? Thanks!

Please change MC125252 to MC-125252 so that they actually link to the issues.

So is there another ticket already?

Here -> https://www.youtube.com/watch?v=DcUHJfAnrcI
(The bug in the description of that video was resolved as a duplicate to this one, but it wasn't reopened)

Still in 1.12.1

@unknown About "Fix Version/s", it is updated only when the version (in which the bug is fixed) is finished and ready to release as a public snapshot.
The only way for us to know ahead of time is the "Assignee" field. That is the way I understand the info in the top.

@unknown - Every bug is a bug and it should be fixed, (unless @unknown says its a won't fix), it doesn't matter how important or hard it is to fix.The more game-breaking ones are of course prioritised (like MC-111645), but for most issues the votes count is the way to sort them.

About the resolution of the bug itself - it's a little more complicated then that, go watch @unknown's video if you haven't.

sorry for the unnecessary bug updates, the syntaxes never work the first time

Click this image if the other one doesn't load.

@unknown No, the Spawn Protection area is a sphere centred at the world-spawn, but it doesn't matter, because the bug still exists in vanilla.

Ok, got you!
Just let us know what will happen with the client bug, not now - when you will decide.

First, can someone update the description and affected versions to 1.11?
Second, SunCat, you should test bugs in the latest version, (I believe that what being a helper means).
Also, the bug I described has nothing to do with https://bugs.mojang.com/browse/MC-87661, which is a server side bug, (though it can be opened as a separated one if needed and hasn't already, then we can mark https://bugs.mojang.com/browse/MC-107494 as fixed and related).

In 1.11, from the server perspective (tested with /entitydata @e[type=vex] {} ):

/summon vex

- with a sword.

/summon vex ~ ~ ~ {HandItems:[0:{},1:{}]}

- without a sword.

/entitydata @e[type=vex] {HandItems:[0:{},1:{}]}

- empties the hands.

/replaceitem entity @e[type=vex] slot.weapon.mainhand air

- empties the hand.

/give @p minecraft:spawn_egg 1 0 {EntityTag:{id:"minecraft:vex",HandItems:[0:{},1:{}]}}

- when used, spawns a vex without a sword.

However, from the client side, the egg spawns a vex with a sword.
Quitting the world and reentering - fixes the graphic glitch.

Cannot reproduce.

They can be, if the bottle isn't thrown directly at them, they won't teleport.
Endermen only teleport if a projectile is flying directly into them, that's what the code checks.