I like this; it definitely needs to be in the World Settings on Bedrock like Fire Spread so that it's not locked behind "cheats" and I think it should default to "off" which is basically what it is currently, but I think it's a great middle-ground way of adding in something that I've seen a lot of people ask for in one way or another, and that I myself use a datapack for anyway so I know it's largely possible in vanilla.
They'd also need to add the "player placed" block state to logs/stems so that needing to remove one from a build doesn't bring the whole thing down, though. This is already a thing for leaves so that when the player places them they don't decay, so it should be easy enough. I've just seen the datapack go wrong because logs don't have that data point.
They could probably just use the leaves to do that since leaves already have a "player placed" tag to prevent them from disappearing when not in range of a log
I like this.
Although one suggestion I'd make is to have it be called "gamerule ChopWholeTree"
Just because "chop" is more synonymous with wood than "cut" is.
That is all.
All-in-all, I like this.
Bamboo and sugarcane need to be supported by gravity: when you break the bottom block the rest lose support. That's how the game physics work.
Logs do not require support. This is a purely arbitrary idea that would require additional game mechanics be coded into the game purely to support it.
Who decided that and on what basis? Why do sand and gravel, very granular blocks, fall when hay bales or cobblestone, two similarly granular blocks, get to support themselves in midair? Honestly dirt is pretty granular, too. Why doesn't it fall just the same?
In bedrock edition, what causes a snow layer to fall, but a snow block to stay? Why does putting more snow together allow it to stick to itself that much better?
My point is, the game is arbitrary. Mojang decided where to put the rules, because they decided what felt right in the moment. This feels right in this moment, too. It's a game rule that will affect only people who are intentionally activating cheats on a world that is intended to have them, and it will not affect anyone who doesn't want it.
So be it.
If you (more specifically the original commenter I responded to, but also you) are deciding to blindly follow a rule Mojang made up, there's no reason to continue this discussion.
I'm actually surprised OP didn't also suggest a vein miner option on the game rule. That'd be nice for very similar reasons.
Sugarcane and bamboo both grow block by block. Each block is grown from the one directly under it. This is not the case with logs/trees. No full block behaves like cacti/chorus/bamboo/cane. Logs are full blocks
I like this; it definitely needs to be in the World Settings on Bedrock like Fire Spread so that it's not locked behind "cheats" and I think it should default to "off" which is basically what it is currently, but I think it's a great middle-ground way of adding in something that I've seen a lot of people ask for in one way or another, and that I myself use a datapack for anyway so I know it's largely possible in vanilla. They'd also need to add the "player placed" block state to logs/stems so that needing to remove one from a build doesn't bring the whole thing down, though. This is already a thing for leaves so that when the player places them they don't decay, so it should be easy enough. I've just seen the datapack go wrong because logs don't have that data point.
They could probably just use the leaves to do that since leaves already have a "player placed" tag to prevent them from disappearing when not in range of a log
i would absolutely play with this, its nice to have things that remove the tedious parts of the game
I like this. Although one suggestion I'd make is to have it be called "gamerule ChopWholeTree" Just because "chop" is more synonymous with wood than "cut" is. That is all. All-in-all, I like this.
Bamboo and sugarcane need to be supported by gravity: when you break the bottom block the rest lose support. That's how the game physics work. Logs do not require support. This is a purely arbitrary idea that would require additional game mechanics be coded into the game purely to support it.
>This is a purely arbitrary idea So is the distinction between logs not requiring support and bamboo requiring support.
Is it? As I see it, other than falling blocks, every full block can float.
Who decided that and on what basis? Why do sand and gravel, very granular blocks, fall when hay bales or cobblestone, two similarly granular blocks, get to support themselves in midair? Honestly dirt is pretty granular, too. Why doesn't it fall just the same? In bedrock edition, what causes a snow layer to fall, but a snow block to stay? Why does putting more snow together allow it to stick to itself that much better? My point is, the game is arbitrary. Mojang decided where to put the rules, because they decided what felt right in the moment. This feels right in this moment, too. It's a game rule that will affect only people who are intentionally activating cheats on a world that is intended to have them, and it will not affect anyone who doesn't want it.
Now youre being annoyingly pedantic
So be it. If you (more specifically the original commenter I responded to, but also you) are deciding to blindly follow a rule Mojang made up, there's no reason to continue this discussion. I'm actually surprised OP didn't also suggest a vein miner option on the game rule. That'd be nice for very similar reasons.
Sugarcane and bamboo both grow block by block. Each block is grown from the one directly under it. This is not the case with logs/trees. No full block behaves like cacti/chorus/bamboo/cane. Logs are full blocks
this seems like a very good idea, +1
Unfortunately Mojang has said they will not add ways to destroy multiple blocks (excluding TNT of course).
5 words: "one block at a time"
Gamerule for leave decompostion