• v6.0.66 - actually use the sapling blocks we calculated
• v6.0.65 - fix acacia bottom determination
  
• v6.0.64 - implement implementation method to check for log types and use where appropriate
• v6.0.63 - rewrite the bottom block logic by introducing a sapling block logic - this will help with "Destroy Only Blocks Above" finally doing what it should

Today I did a bit of a rewrite in the method to determine the bottom block of a tree. Before, this was also hooked to the sapling determination, where having an invalid ground would even result in the auto destruct failing completely.

Now the tree determination (used for destruction) and the sapling block determination are separate, finally - like promised a long time ago - allowing for players to destroy any block apart from the bottom block (some exceptions with acacia trees, they are pretty picky and weird) and based on the config both sapling replace and auto removal will work now.

In the mushroom department, I noticed that the materials have changed a bit, so I accounted for the weird setup of the blocks there, implementing a new method that mushrooms override to double check for their respective materials.

Overall, this update is supposed to cause less false positives that could lead to trees reaching into others killing both, and it will allow for the logically correct way of using the config to allow or disallow automatic destruction even if players do not break the lowest block.

Note however that if you want to allow this AND you want saplings to replace, you might need to also activate " Sapling Replace.Enforce" because depending on your server speed or the tree size, in one second it might not be done removing the trunk that is added at the end of the "to break" list, so it has to enforce a sapling into a place maybe taken by a log not broken yet.