The Vanilla Experience (Mod) (Forge)

The Vanilla Experience (Mod) (Forge)

118k Downloads

Tree Harvester should be able to be configured to have higher costs than vanilla.

blainegrissom opened this issue ยท 2 comments

commented

Information

Minecraft version: 1.21
Modloader: Forge / Fabric

Mod name: Tree Harvester

Feature description

I find it strange that you can configure Tree Harvester to have much lower costs to use over vanilla, but you are not able to increase the costs for using the mod. I feel that you should be able to add durability and exhaustion beyond vanilla as a tradeoff for using the feature, otherwise there is no reason to ever not use the mod. I added the mod for users in my server upon request, but I would like to add some form of tradeoff so that it's not just overpowered and completely removing the incentive to break trees normally.

commented

I would also very much like this feature, for both durability and exhaustion, as well as leaves broken per tick to be slower than one per tick as that is still 20 a second. Would be very great for a balancing feel and shouldn't be too hard to implement I imagine.

commented

Hey!

I appreciate the suggestion! While I'd love to add all features submitted on the issue-tracker, I've got to prioritize working on them due to having limited time. In order to see which features users would like to see most, I've created https://serilum.com/mods/requests, which shows a table with all feature request submitted.

I'm aware that this is not the reaction you were looking for, but the reality is that I can't keep up with the demand. I try to do as much as I can.

Users are able to upvote requests by reacting to the first issue comment on this GitHub page with one of the ๐Ÿ‘ ๐Ÿ˜€ ๐ŸŽ‰ โค๏ธ ๐Ÿš€ ๐Ÿ‘€ emoji's. The request with the most unique reactions, will be shown at the top. You can of course add the reactions yourself too, but don't have to :). The author of the feature is already counted as +1.

I won't only focus on popular features in the upcoming years, but it does help with prioritizing. I'll probably work on a combination of popular and interesting/needed/fun submissions.

I'll close this issue with "not planned" as a way to separate an open feature request from an actual completed issue. This does not actually mean it's not planned! Incompatibilities and bug reports will still remain open.

When the feature is implemented, I'll again post a comment and close it as "completed".

Thank you for taking the time to submit the suggestion! โค๏ธ