SLScoolUser

This issue also applies to basalt (see MC-171553 for an example).

I tried this with both regular fire and blue fire, in all three dimensions, and in a world where I had never been exposed to Netherite. Fire does not burn items.

Duplicate of MC-88967 ?

When mobs are trying to swim while they are directly against another block, they gain a lot more vertical momentum than they otherwise would. Are the creepers in those screenshots being pressed up against any blocks?

From what I can tell, the black/normal lighting is based on eye level (the red square on the hitbox), which is also true for the player taking damage (but not silverfish, it seems). I'm guessing that it was based on something else in the past.

Can confirm, with these two notes:

• Damage dealing, even the 3/4 damage reduction to not-head body parts, is still dependent on the dragon itself. The green hitboxes are purely visual in this matter (but they still are in the same layout as they would be if they were correct).

• The green hitboxes, the actual dragon, and the origin (0,0,0) seem to always form a straight line, with the dragon itself in the center. The dragon seems to be 50-60% of the way from the origin to the hitboxes.

I just tried this in a superflat world. About 80% of the animals disappeared behind the experience orb while the other 20% did not. I tried this without mob spawning turned on, so from what I just saw, it doesn't matter if you're "looking through an experience orb at a mob that existed in the world before it" instead of "one after it."

The bug for the entity form was fixed, but the item form might still have the bug.

Is this also true of other 2D sprites, such as eggs and ender pearls?

Where on the website are you seeing this?

I'm not going to try to figure out how I never noticed it, especially with how often I check the bug tracker in general. Thanks for pointing it out, though.

Could you include the seed (/seed) and coordinates (F3, or Fn+F3)?

Based on the video, I believe you mixed up sticks with fences.

After some further experimentation, I found that the items are not getting deleted because they are ghost items (for some reason–which is why this bug report exists). /data get entity @p Inventory shows that the item is not saved in your inventory, reloading the world causes it to disappear, grabbing the item in survival mode causes it to disappear, etc.

Seems to duplicate MC-157494.

"Without using external editors, the only possible prefixes are formatting codes for team colors, and the only possible suffix is the reset code (so characters after a team member's name aren't formatted)."
This line was added to the wiki's Scoreboard article on January 31, 2013. Take it as you will.

If "Ctrl+Cmd+Q" does work for you, then the bug is solved (invalid).

After testing this out, I found that there are two possible outcomes that can occur. If you place a block using your second hand and then destroy the block using your main hand, either the second hand animation will be cut short (and instantly go back to the default position) or the main hand animation will not play. The first instance seems to occur when the breaking happens more than 0.2 seconds after the block placing. The second instance seems to occur when the breaking happens less than 0.2 seconds after the block placing. (0.2 seconds is an estimated time)

I can confirm this also works in 1.14.4.

Based on the video you linked and my own experimentation, here's a procedure to replicate the bug:

1. Fill the hotbar as much as desired (can be left empty, but filling it with as many as 9 items makes step 2 quicker).

2. Pick-block anything from the world that is not already in your toolbar. Continue doing this until there is at least 10 different items in your inventory (i.e. a full hotbar, and at least 1 item not in your hotbar).

3. Load any toolbar.

4. Open to the "Survival Inventory" tab.

5. Shift-click the "Destroy Item" button.

And, like you said, any blocks which had been pick-blocked will not be deleted.

Some various, potentially helpful notes:

• Loading a toolbar before doing the pick-blocking is not necessary, but it definitely makes the bug reproduction process faster.

• For step 3, you can use any toolbar.

• You can repeat steps 1, 2, and 3 as many times as you want, in any order (so long as the minimal requirements for the bug are met).

Quoting the wiki:
"On Macs, you must use the command button instead, but since this quits the game, you must do Ctrl+Cmd+Q."

That should solve the problem.