I have seen quite a few mods that change the way that you harvest trees in Minecraft... they all seem too "overpowered" and make collecting wood way too easy.
I realize I could suggest this to a modification coder, or even code a mod myself to do it...and believe it or not, I have tried taking one of the mods source and making it do this to no avail. Lack of familiarity with object layout, datatypes, available methods in Minecraft kept me from actually pulling it off.
A big peeve of mine with this game is that cutting down trees is just so remarkably silly. You cut out the bottom section of the tree, and it continues to stand. Nothing you do will make a tree fall the way they would in a real-world. I am not looking for falling tree blocks, or anything of the sort... Just something to make harvesting trees more realistic without becoming a chore.
When a player starts hitting a tree, a count should occur of all adjacent blocks of wood of that type and encompassed by the type of leaves the tree has associated with it could be done and the total number of "whacks" that it will take with your current tool could be calculated... meaning a small tree will take longer to cut down than a single block of wood. Damage to the tool you used should be calculated and applied as soon as the tree you are cutting down is destroyed. So for those really huge trees, you would have to whack on it for some time with a wooden axe to get it to fall, and your wooden axe would likely immediately break upon completing your cut.
It just seems to me that this system would make more sense and work out better than the way that is implemented currently...
Another thing that kind of bugs me about trees is the way saplings behave in the game... Saplings fall to the ground and sit there until they are either picked up by a player, or despawn. I know that "things happening" in this game require a player to be in range of the chunk for the chunk to be active, but why can't saplings fall and plant themselves immediately if it manages to reach the ground before the player leaves the chunk? If it does not reach the ground and planet itself it can go through the regular "I sat here too long without being picked up, time to despawn!" procedure...
I dunno, theres something really fun about the fact that it isn't realistic.
It makes minecraft more minecraft.
But I can see what you want. Just like with sugar cane and vines, or cactus where if you hit a block the ones above it get harvested as well.I dunno, theres something really fun about the fact that it isn't realistic.
It makes minecraft more minecraft.
But I can see what you want. Just like with sugar cane and vines, or cactus where if you hit a block the ones above it get harvested as well.
Rollback Post to RevisionRollBack
Creeper telling son how to love "WELL SON IT'S TIME YOU WENT AND HUGGED NOTCH"
I don't like the idea of saplings planting themselves, because that doesn't happen after you plant a tree. It happens naturally, and all happens in a very small area. And the way that tress work in Minecraft with their leaves will make this not happen, since the leaves spread out so much.
But with the destruction of it, I totally agree. I was thinking of the "adding up" of durability. But what if the tool has one break left and you break a whole tree?
I don't like the idea of saplings planting themselves, because that doesn't happen after you plant a tree. It happens naturally, and all happens in a very small area. And the way that tress work in Minecraft with their leaves will make this not happen, since the leaves spread out so much.
Actually, it wouldn't be as bad as you think... In the case that you have 4 saplings reach the ground from a single tree, only one sapling would actually "grow". As soon as it did, it would keep the other saplings beneath it from actually growing. That would keep another complaint I read in one of the mod threads about the world becoming "too populated" with trees...
In the real world, if I chop down and strip a tree of its fruit/nuts, and leaves...and take the "bulky" part of the tree (the trunk and branches) and leave the portion I stripped behind, there is a good chance that something I left would end up planted in the ground and sprouting a new sapling.
But with the destruction of it, I totally agree. I was thinking of the "adding up" of durability. But what if the tool has one break left and you break a whole tree?
That could be handled in a multitude of ways actually. I am in favor of the "easy way out"...which is to just let it occur, and destroy the axe once the tree "falls". The reason for this is that calculating it as you cut would require that block damage not reset if you stop hitting them before they are destroyed. I do not believe this game has a mechanic for remembering damage to blocks, and frankly that would just add a ton of overhead to remember a health amount for every block in a chunk that is currently loaded.
But! Another (quick-and-easy) solution would be to calculate the total "whacks" it takes to destroy the tree, and start counting whacks.. after XX number of whacks, the tool you are using takes the normal amount of durability for breaking a single wood block from the tool. If you start whacking on a tree that your tool does not have the durability to finish, it just breaks in the middle of the job, and you are left with having to do it again after you get a new tool. At that point, you start counting the "number of whacks" again from the beginning. Would be interesting if EPIC TREES required more than a single wooden axe to take out wouldn't it?
Actually, it wouldn't be as bad as you think... In the case that you have 4 saplings reach the ground from a single tree, only one sapling would actually "grow". As soon as it did, it would keep the other saplings beneath it from actually growing. That would keep another complaint I read in one of the mod threads about the world becoming "too populated" with trees...
In the real world, if I chop down and strip a tree of its fruit/nuts, and leaves...and take the "bulky" part of the tree (the trunk and branches) and leave the portion I stripped behind, there is a good chance that something I left would end up planted in the ground and sprouting a new sapling.
That could be handled in a multitude of ways actually. I am in favor of the "easy way out"...which is to just let it occur, and destroy the axe once the tree "falls". The reason for this is that calculating it as you cut would require that block damage not reset if you stop hitting them before they are destroyed. I do not believe this game has a mechanic for remembering damage to blocks, and frankly that would just add a ton of overhead to remember a health amount for every block in a chunk that is currently loaded.
But! Another (quick-and-easy) solution would be to calculate the total "whacks" it takes to destroy the tree, and start counting whacks.. after XX number of whacks, the tool you are using takes the normal amount of durability for breaking a single wood block from the tool. If you start whacking on a tree that your tool does not have the durability to finish, it just breaks in the middle of the job, and you are left with having to do it again after you get a new tool. At that point, you start counting the "number of whacks" again from the beginning. Would be interesting if EPIC TREES required more than a single wooden axe to take out wouldn't it?
I didn't know you meant after you chop a tree for the saplings to plant themselves. That would make a lot more sense.
And what if the axe just didn't work at all, as in the blocks just don't take damage? And you couldn't chop down those giant trees with a wooden axe?
I completely agree that cutting down trees without mods is slow and kinda silly. I like your idea but here is the problem with it. When you are first starting out, cutting down a tree would take forever with your fists, even a small one. It time it would take would confuse new players into thinking they can't cut down trees with their bare hands.
So here are two other options, one of which I know has been suggested before:
Cutting trees at their base makes them fall on their side
Cutting trees at their base makes the whole tree shift down one block (so you'll have to watch out for foliage falling on you and suffocating you.
I had another thought. Perhaps the base block for a tree should be a new block, a Buttress block. This block takes a long time to cut down (proportional to the size of the tree as the OP suggests) and when you do the whole tree minus foliage gets chopped down. However, if you cut the tree down from any other log block, it acts like it does now. This would allow new players to cut down trees with their fists, then come back and chop up the buttress logs with axes.
I realize I could suggest this to a modification coder, or even code a mod myself to do it...and believe it or not, I have tried taking one of the mods source and making it do this to no avail. Lack of familiarity with object layout, datatypes, available methods in Minecraft kept me from actually pulling it off.
A big peeve of mine with this game is that cutting down trees is just so remarkably silly. You cut out the bottom section of the tree, and it continues to stand. Nothing you do will make a tree fall the way they would in a real-world. I am not looking for falling tree blocks, or anything of the sort... Just something to make harvesting trees more realistic without becoming a chore.
When a player starts hitting a tree, a count should occur of all adjacent blocks of wood of that type and encompassed by the type of leaves the tree has associated with it could be done and the total number of "whacks" that it will take with your current tool could be calculated... meaning a small tree will take longer to cut down than a single block of wood. Damage to the tool you used should be calculated and applied as soon as the tree you are cutting down is destroyed. So for those really huge trees, you would have to whack on it for some time with a wooden axe to get it to fall, and your wooden axe would likely immediately break upon completing your cut.
It just seems to me that this system would make more sense and work out better than the way that is implemented currently...
Another thing that kind of bugs me about trees is the way saplings behave in the game... Saplings fall to the ground and sit there until they are either picked up by a player, or despawn. I know that "things happening" in this game require a player to be in range of the chunk for the chunk to be active, but why can't saplings fall and plant themselves immediately if it manages to reach the ground before the player leaves the chunk? If it does not reach the ground and planet itself it can go through the regular "I sat here too long without being picked up, time to despawn!" procedure...
-
View User Profile
-
View Posts
-
Send Message
Retired Staff-
View User Profile
-
View Posts
-
Send Message
Retired StaffIt makes minecraft more minecraft.
But I can see what you want. Just like with sugar cane and vines, or cactus where if you hit a block the ones above it get harvested as well.I dunno, theres something really fun about the fact that it isn't realistic.
It makes minecraft more minecraft.
But I can see what you want. Just like with sugar cane and vines, or cactus where if you hit a block the ones above it get harvested as well.
But with the destruction of it, I totally agree. I was thinking of the "adding up" of durability. But what if the tool has one break left and you break a whole tree?
Actually, it wouldn't be as bad as you think... In the case that you have 4 saplings reach the ground from a single tree, only one sapling would actually "grow". As soon as it did, it would keep the other saplings beneath it from actually growing. That would keep another complaint I read in one of the mod threads about the world becoming "too populated" with trees...
In the real world, if I chop down and strip a tree of its fruit/nuts, and leaves...and take the "bulky" part of the tree (the trunk and branches) and leave the portion I stripped behind, there is a good chance that something I left would end up planted in the ground and sprouting a new sapling.
That could be handled in a multitude of ways actually. I am in favor of the "easy way out"...which is to just let it occur, and destroy the axe once the tree "falls". The reason for this is that calculating it as you cut would require that block damage not reset if you stop hitting them before they are destroyed. I do not believe this game has a mechanic for remembering damage to blocks, and frankly that would just add a ton of overhead to remember a health amount for every block in a chunk that is currently loaded.
But! Another (quick-and-easy) solution would be to calculate the total "whacks" it takes to destroy the tree, and start counting whacks.. after XX number of whacks, the tool you are using takes the normal amount of durability for breaking a single wood block from the tool. If you start whacking on a tree that your tool does not have the durability to finish, it just breaks in the middle of the job, and you are left with having to do it again after you get a new tool. At that point, you start counting the "number of whacks" again from the beginning. Would be interesting if EPIC TREES required more than a single wooden axe to take out wouldn't it?
I didn't know you meant after you chop a tree for the saplings to plant themselves. That would make a lot more sense.
And what if the axe just didn't work at all, as in the blocks just don't take damage? And you couldn't chop down those giant trees with a wooden axe?
So here are two other options, one of which I know has been suggested before: