confirming in 1.20.60.26
no. same error "Target position is not a container" changing the loot table wont fix that. reproed in 1.20.30
affects 1.20.30 betas and 1.20.10 release
this was moved here from the public jira, whoever moved it here needs to move it back since it doesn't belong here
came looking for the same thing, also reproducing when playing sound from animations and playsound, completely ignoring the sound_definitions
The fix for this, added in 1.17.20.22 has broken the light_block functionality as we can no longer interact with mobs that are behind the light blocks or buttons in adventure mode.
This occurs in Marketplace content as well. This causes problems with game logic and player control. Happens more often in multiplayer than single player, but can occur in single player too. Seems to happen when there is a player isn't in perfect sync with the local server.
Can confirm this also occurs on Win10
If anyone comes across this, the actual bug that should be reported is that animation controller commands do not currently work in the beta. It is not a bug with the map but a bug with the game that is causing the above behavior.
still occuring 1.16.200
[media]This bug has affected loads of people, there is a solution: Go into Settings, Storage, World Templates. Delete the Infinity Skyblock template there and then download it fresh again from the store. Sometimes there are issues with the download.
That said, it's still a bug that this happens, so the report should stay. I've had dozens of people emssage me with the same issue.
confirmed, horizontal movement basically halted in bedrock vs java where you get to slide for ages
Confirmed on win10 too and a world I started in 1.11.0.3
Still happening, 1.1.4
yo yo yo, doesn't work in 1.8 confirmedamundo. Tried to use it on a sign and no dice.
I cannot as I don't have one I can release to the public. However I have made a private bug report which has it attached.
Please re-open this still happens in 14w34a and 14w34b
Please re-open this still happens in 14w34a and 14w34b
Still an issue even in 1.8 snapshots
Also confirmed for 14w07a
this is still an issue