MC-1574Can't destroy glass in Adventure Mode
Glass blocks and glass panes have no tool associated with them, so they can't be destroyed in adventure mode.
Created Issue:
Can't destroy glass in Adventure Mode
Glass blocks and glass panes have no tool associated with them, so they can't be destroyed in adventure mode.
- Unresolved
- Open
- Public
- Unconfirmed
- adventure_mode
- 1.4.1 1.4.2
Added Assignee: ![[Mojang] Jeb (Jens Bergensten)](../../../data/assets/gravatar/jeb.jpeg)
[Mojang] Jeb (Jens Bergensten)
[Mojang] Jeb (Jens Bergensten)
Added Linked Issues:
relates to
Added Linked Issues:
relates to
Deleted Comment:
If you can't break glass in Adventure Mode then explain how I did yesterday accidentally, on Adventure Mode. This isn't a bug.
Added Labels: adventure-mode
Removed Labels: adventure_mode
Removed Labels: adventure-mode
A better solution to the unbreakable glass panes and glass issue from MC-1574 would be to assing pickaxe as the necessary tool to break glass. Otherwise some unwanted situation could happen in Adventure Mode.
E.g.:
- Secret areas visible through glass can be accesed by breaking the glass.
- Unreachable areas (houses with windows) could be entered.
- Cristal domes that allow light inside could be trespassed, players exit the map.
umm this is not a bug....no blocks are breakable in Adventure mode...unless theres a bug allowing it
@ForceablePlace: See http://www.minecraftwiki.net/wiki/Adventure_Mode : 12w34a Certain blocks can now be removed and placed again with correct tools
Wait, does this fix mean we'll be able to break glass in any situation in adventure mode? With more of these changes, we seriously need a mode where the player can not break the map!
Stop! Hammer-time!
What is the fix of this (not really) issue?
Hopefully hammers!
I noticed glass is now breakable in adventure with your fists. Is that the fix of this (not really) issue, because if it is, it sucks since you can now break redstone/all the other stuff in adventure mode, which will break every map that uses adventure mode.
Can we unfix this "bug" please?
@Alijah has a good point