Ben Mintz
- bmintz
- bmintz
- America/Chicago
- Yes
- No
Added Labels: accessibility ghast
Changed Environment:
Not applicable to this bug
java -versionopenjdk version "1.8.0_66-internal" OpenJDK Runtime Environment (build 1.8.0_66-internal-b17) OpenJDK 64-Bit Server VM (build 25.66-b17, mixed mode)lsb_release -aDistributor ID: Ubuntu Description: Ubuntu 15.10 Release: 15.10 Codename: wily
Changed Description:
Abstract
Wooden trapdoors cannot be opened by hand if placed at y=255.
Steps to reproduce
1. /tp ~ 255 ~
2. /setblock ~ ~ ~ stone
3. Place a wooden trapdoor on the side (top or bottom half) of the stone block.
4. Press use itemExpected behavior
The trapdoor opens.
Actual behavior
The trapdoor opens for a split second (I assume one tick) and an error message is shown: "Height limit for building is 256 blocks"
(see attached screenshot)Note that both trapdoors can still be opened by redstone.






Although the missing break textures are now fixed, please re-open this; barrier blocks are still invisible while holding the barrier item in 1.9.
@farrelabrar
OK so if hearing persons can't locate Ghasts I don't believe it makes sense to give that capability to those who need subtitles. The experience should be the same, i.e. if players can't normally locate Ghasts by sound deaf players shouldn't be able to locate them by the "equivalent".
@farrelabrar
Except both hearing players and deaf players can locate creepers. That's fine, I never suggested removing that.
Right. Hearing players can't locate them either. The subtitles should not provide functionality that audio doesn't IMO. So if hearing players can't figure out where ghasts are by sound, deaf people shouldn't be able to figure out where they are by subtitles.
I feel like I'm talking in circles here.
OS info updated in the environment section.
Confirmed working again in Ubuntu 16.04 LTS and launcher 1.6.61.
Confirmed for 1.10.2
Confirmed for 16w32b
EDIT: oh lol i didn't see your comment until after i said confirmed for 16w32b
I wonder if there are plans to fix this for 1.11?
noooo! this breaks AFK fish farms!
Yes I know. If I had seen your comment earlier I wouldn't have also said confirmed for "16w32b".
@farrelabrar I think I may not have been clear enough before.
My proposed fix is not to remove the arrows for all mobs, just the ghast. And again, the audio from a ghast is supposed to stay the same no matter the distance or direction of the ghast from the player, so subtitles should not give away the location either. But as for hearing players, if they can hear the location of a mob, the subtitles should absolutely say so as well.
My proposed fix would not remove the arrows entirely.
I can confirm.
Me
What about monster spawners, say on a superflat world? Or barrier blocks?
I think that even if there weren't blocks such as these, this is still a bug because in the future there may be more blocks
that can't be obtained from the menu.
What if someone removed the only dragon egg?
I definitely don't think this is WAI. Even if these examples I just listed weren't available (leaving command blocks and the like), I still think this is a bug since Minecraft should be able to tell which blocks you should and shouldn't be able to get from the creative menu.
Confirmed for 17w14a
I'm confused. Why is this a bug?
If a command block executes `function foo:bar` as @p, doesn't @p become the sender of the function?