According to Wiki, basalt should not be destroyed by ghast fireballs (seems logical, because, also according to Wiki, basalt has a blast resistance of 4.2, and ghast fireballs a blast damage of 4), but ghast fireball's do break basalt (I noticed when trying to build a shelter for a giant warped fungus farm).
Steps to Reproduce:
Build a wall out of basalt
Spawn a ghast
Let the ghast shoot a fireball at the wall
Observed Results:
The basalt is destroyed by the fireball.
Expected Results:
The basalt should not be destroyed by the fireball.
Linked issues
is duplicated by 3
Attachments
Comments 15
migrated
On second thought, I would say, it's ok, as it is, regarding, how easy it is, to mine large amounts of basalt. Even though basalt isn't undestroyable, it's still much better then netherrack, maybe the Java version should be changed instead. More important is, that MCPE-65522 get's fixed (see comment from sydney russel), this makes building large structures a pain/impossible.
On second thought, I would say, it's ok, as it is, regarding, how easy it is, to mine large amounts of basalt. Even though basalt isn't undestroyable, it's still much better then netherrack, maybe the Java version should be changed instead. More important is, that MCPE-65522 get's fixed (see comment from sydney russel), this makes building large structures a pain/impossible.
This should definitely be kept. You can use ghasts to automatically break basalt because of this, which is otherwise nearly impossible on bedrock edition and you can make fun farms out of this. Catching a ghast and getting it in the right place would be an interesting challenge as well. It's a great alternative to java TNT duping, but way less cheaty and a bunch more fun.
This should definitely be kept. You can use ghasts to automatically break basalt because of this, which is otherwise nearly impossible on bedrock edition and you can make fun farms out of this. Catching a ghast and getting it in the right place would be an interesting challenge as well. It's a great alternative to java TNT duping, but way less cheaty and a bunch more fun.
@Blobs2 ZloyXP actually has a working basalt farm of this type at the moment on the truly bedrock server. I think if you look up his twitch and youtube you will be able to chart and appreciate the sheer amount of work that went into capturing the ghasts and figuring out how to get them aligned, etc.
The sheer effort and perseverance that it takes to get such a farm working has earned feature status for the ghast farm don't you think?
There does, however, appear to be an issue for those thinking they could take shelter under basalt but since the wither no longer works for obsidian farms - perhaps.... ghast fireballs could be made more powerful in the overworld only (1201?).
The only thing is that I don't remember encountering hints that there is existing code that might enable this behaviour thus far but it would seem to be the ideal compromise.
@Blobs2 ZloyXP actually has a working basalt farm of this type at the moment on the truly bedrock server. I think if you look up his twitch and youtube you will be able to chart and appreciate the sheer amount of work that went into capturing the ghasts and figuring out how to get them aligned, etc.
The sheer effort and perseverance that it takes to get such a farm working has earned feature status for the ghast farm don't you think?
There does, however, appear to be an issue for those thinking they could take shelter under basalt but since the wither no longer works for obsidian farms - perhaps.... ghast fireballs could be made more powerful in the overworld only (1201?).
The only thing is that I don't remember encountering hints that there is existing code that might enable this behaviour thus far but it would seem to be the ideal compromise.
Confirmed that after 1.16.100 update on Bedrock android, ghasts can still blast basalt blocks causing them to break when hit by a ghast fireball. Tested on both local gameplay and on realms.
A short time after my comment post, Mojang announced a new beta release where this behavior is apparently fixed. We'll have to check again after next full release/hotfix, whichever route they go on this item.
This bug is fixed in the latest beta version, and the fix will be included in a future update when that is ready for full release (no specific date can be given). We will leave this ticket open as a point of reference until the fix has been fully released.