The creeper in the example is not ridden by the player
Reproduced in 23w07a
Instead of relogging I walked 32 blocks away from the standing tamed leashed wolf and teleported 1000 blocks towards positive x and then teleported 1000 blocks towards negative x after a few seconds of waiting
I think this should be reopened as referring to a technical restriction doesn't make sense here, removing technical limitations is part of the day to day work of the minecraft developers.
Minecraft live showed that hidden passageways with movable bookshelves are intended, the footage showing the old bookshelves is the workaround for now. The fact that the new bookshelves are not movable in the first snapshot shows that the developers did not allocate time to fix it yet, it does not mean that immovable bookshelves are "working as intended". Minecraft Live clearly showed that the bookshelves are planned to be movable.
This ticket is also not a duplicate of the ticket regarding all block entities, which is a completely different design decision.
Fixed in 22w14a
Place a mob inside a boat, so that the head of the mob is inside two blocks. Set the blocks at the head to shulker boxes using /setblock. Observe the behavior when opening the different boxes
Still not fixed. One of my cats just died after they teleported to me after a friend went to the base to get some materials. I hope this bug will be fixed before 1.18 comes out.
Due to the latest terrain blending features, the issue is visually harder to see (unless cutting through a player base). Looking at the log and then checking those chunks for cut off trees and cut off caves reliably shows that this bug is not fixed.
cave_air is only relevant to world generation and should never be saved. Currently there are other bugs in the game (such as this one and https://bugs.mojang.com/browse/MC-232359) which make it possible to detect a difference between the air types.
Confirmed in 20w48a. Also affects the new pointed dripstone blocks.
Yes it is still a problem in 1.16.4. There is no known way to observe the issue ingame, besides slightly increased CPU time. You can reproduce this by loading an empty world and then adding water to chunks. The chunk sections will then be randomticked for no good reason, it might show up in the profiler. The issue I am reporting here is not about the lag, but about the defect that makes the randomtickable fluid counter be essentially useless. When lavalogged blocks are added it will immediately become observable by loading a chunk with lots of water and then removing the water. The lava from the lavalogged blocks would then no longer spread fire.
Steps to reproduce:
use a mostly empty world
/tp @s 72 10 -93
/setblock 72 0 -93 grass_block
/fill 72 1 -93 72 10 -93 bamboo
/summon minecraft:arrow 72.2 12.00 -92.8
Then the arrow will be stuck mid air like this and not despawn, it can also not be picked up. This also confirms the theory that this is about the invalid data in the shape cache.
[media]/summon minecraft:arrow 72.2 12.00 -92.8
Manually shot some arrows: this one is not despawning
[media]Confirmed in 1.16.2 pre 1
This is probably caused by bamboo having a shapeCache in the code even though the collision is location dependent (random offset).
There might be more blocks that have this problem. When fixing this bug that has to be considered. Also this bug manifests so rarely only, because in lots of cases the shape chache isn't used, even though it could.
This mistake also affects lava blocks (has shape cache even though it has a entity dependent hitbox).
The problem is that the composter is resetting itself when its inventory is told that it is changed, but it doesn't actually check that someone took the bonemeal out of the inventory.
This also affects mobs being pushed by pistons while inside berry bushes. They do not take damage in 1.25.1-rc1 while they do take damage in 1.21.4.
[media]