Zuriki
Assigned
Reported
MCPE-146637
Extremely poor Raytracing performance
Cannot Reproduce
MC-65389
Collision catching walking up non-full blocks (stairs, slabs, etc)
Duplicate
MC-64484
Fire charge plays no sound due to incorrect sound file reference
Fixed
MC-48223
Adding mobs to the scoreboard results in IOException caused by packet length (multiplayer)
Cannot Reproduce
MC-46614
Crash on loading converted level
Duplicate
MC-12693
Command "/testfor" outputs a true signal even after re-running command when a player is teleported
Cannot Reproduce
MC-2673
Shift-Clicking smelted ores out of furnace can cause minor visual bug
Fixed
Comments
Why is this closed? It is still present in 14w32b.
Not intended behaviour. Other mobs don't deal damage.
I was basically spamming their twitter with this since 31a. Glad to see it's finally fixed.
As a work around you can use ~-0.5 ~-0.5
Confirmed still in 14w32a (how did they miss this with the new beacon update?)
Still affecting 14w32a. Updated ticket.
Confirmed for 14w32a
The issues are not related. MC-61245 is about the hitbox of stairs specifically in relation to them being placed or destroyed. This does not affect the example above because the stairs in the example I gave are acting in accordance to how they should act in versions unaffected by MC-61245 and the hitbox of stairs is entirely irrelevant to this issue.
This issue is about player movement across any non-full block and more specifically relates to the special-case snapping the player to elevated surfaces when the destination surface is elevated by 0.5m or less.
Yeah, someone a bit too eager to dismiss without really reading the ticket.
Alternative video link if you can't watch the one above: https://www.youtube.com/watch?v=3vDrRzoOSdY
Confirmations (incorrectly closed): MC-65360 , MC-65285
Not related to: MC-61245 !!
Re-open this issue!
As explained on MC-65360; this is not a dupe of MC-61245 which pertains to the hitbox of placing stair blocks but that is not the collision issue which is happening here, which is caused by "catching" on what should be completely flat walls - another way you can test this is by using half-slab stairs which have the same issue, if you walk into them at a 45deg angle you will "catch" on the wall and it will block your movement - this is not the same behaviour as in previous versions of the game and is not the same issue as MC-61245.
Re-open this issue!
This is not a dupe of MC-61245 which pertains to the hitbox of placing stair blocks but that is not the collision issue which is happening here, which is caused by "catching" on what should be completely flat walls - another way you can test this is by using half-slab stairs which have the same issue, if you walk into them at a 45deg angle you will "catch" on the wall and it will block your movement - this is not the same behaviour as in previous versions of the game and is not the same issue as MC-61245.
Unable to reproduce. Probably performance issue related to your specific set-up?
Unable to reproduce.
Command used:
/replaceitem entity @p slot.hotbar.7 ice 1 0 {display:{Name:"Hello"}}Tried both replacing another block (sand), an item (spawn egg) and the same block (ice).
Working as intended.
Could be considered working as intended since in reality all you've done is excessively stress the game by spawning too many entities.
Also affects silverfish. The head height of these mobs (F3 + B, it's the red line) is just below the level of soul sand, causing them to suffocate.
Unable to reproduce. Able to get mobs to spawn all the way up to Y=255.
This issue can be closed, turns out the issue was caused by a Windows 10 issue - waking from hybrid shutdown not properly initializing the GPU.
GPU functionality was deteriorated (eventually evident in other applications) and the issue resolved after performing a hard shutdown and restart.