rorybd
Assigned
Reported
MCPE-226874
Boat buttons cannot be moved when customizing controls with the "D-Pad & tap to interact" control mode
Unconfirmed
MC-231283
Sneak Detection Inconsistency Between Scoreboards and Predicates
Community Consensus
MC-217607
Resetting of attack speed when switching items is based on an item's type as opposed to its attack speed
Community Consensus
MC-216870
Items dropped upon player death are not tagged with the Thrower NBT
Confirmed
Comments
Can confirm in 2.29.11-1.12.3. The launcher reports that "Skin images must be 64x64 or 64x32 pixel PNG files" even when the file matches those dimensions and file type.
This should be flagged for review. Jeb has previously gone on record to note that this is a bug — perhaps indicating that it should instead be marked as "Won't Fix."
However, the way in which the trident flickers in the player's first person view is potentially triggering for those with epilepsy, which may be a good reason to switch to the usual behaviour for when tridents lose their targets — that is, to drop as an item.
Isn't this working as intended? While thrown, the trident is not inside of the player's inventory — and thus isn't affected by keepInventory.
Isn't this working as intended? Tridents pop into items when they lose track of their owners.
In Java Edition, tridents get dropped as items (or simply disappear if initially thrown in Creative mode) when the thrower enters spectator mode. Bedrock should probably share this behaviour.
This should be flagged for review. It would be trivial to fix and is a quite glaring error.
This should be flagged for review. There is no logical reason why this texture shouldn't be more in line with, say, the furnace top texture, and to mark it as "Works as Intended" (not even "Won't Fix") feels like an abuse of that resolution type.
This is obviously a bug and should be flagged for review. There is no logical reason why these items would use inconsistent palettes; it is evidently just a texturing error, and to mark it as "Works as Intended" (not even "Won't Fix") feels like a blatant abuse of that resolution type.
Can confirm in 1.20.4
Can confirm in 1.20.3
Can confirm in 1.20.2
Can confirm in 1.20 pre-release 6
Can confirm in 1.20 pre-release 6. Happened upon a nether fortress in a soul sand valley and it has an overwhelming amount of blazes and wither skeletons especially.
Why is this marked as invalid? Why would it be "natural" that the skin doesn't refresh upon rejoining a singleplayer world, but does update when rejoining a multiplayer server? Surely the player's current skin could easily be fetched upon world load? This issue should be reopened.