• v7.3.56 - drop items if the auto adding did not fit - defaults to false for backwards compatibility!

• v7.3.57 - add AuraSkill support

- v7.3.46 - add placeholders ta_global - ta_world - ta_cooldown - for toggle and cooldown status
- v7.3.45 - /ta config restore [config] | Restore a tree config to its default

v7.3.37 - fix an Aurelium related config warning, addresses github issue #90

v7.3.15 - add nyliums to the valid mushroom ground blocks

• v7.3.10 - fix NPE in the "prevent without tool" logic
• v7.3.9 - properly handle trees without leaves
• v7.3.8 - skip null trunk tree removal (why is this even happening?)
• v7.3.7 - call the TreeBrokenEvent with higher priority, extend TreeStructure API
• v7.3.6 - synchronize version numbers
• v7.3.1 - expand TreeBrokenEvent, add TreeBlockBrokenEvent and call both in the appropriate places

• v7.2.53 - address ticket 0062 - skip item spawn events of spammy items that are no saplings
• v7.2.52 - address ticket 0063 - tweak check for self-replant, add config for different tree types
• v7.2.51 - address ticket 0061 - noreplant did not take proper priority. Also, now noreplant and replant will trump each other on command

This is all for this month.

Maybe it is time to add more features and break things? The issue section has been so lonely lately

v7.2.2 - change package destination, no functional change
v7.2.1 - refactor several features into a library that gets shaded in

This build SHOULD be virtually identical to what is online with a small fix about sending messages about a new update called "vnull"

• v7.1.23 - do not shade GSON in - this has been in the server jar for years
• v7.1.22 - update updater to JSON logic, the checking happens online, uses one less connection, and messages only when updates are available
• v7.1.21 - repair the config reparation, update default configs and mark them as current
• v7.1.20 - fix several nether issues. no more custom apple drops, support for a ton of netherrack around

There has been a config messup introduced in the nether fix. If you used that bleeding edge build and fixed it yourself already, it will be skipped!

v7.1.19 - fix build numbering, introduce message prefix, apply it to messages that need it

There has been some resets in the language file, specifically the cooldown messages, as they now do no longer contain the plugin name and use the prefix instead.

The prefix can be changed in the language file, info->plugin_prefix

v7.0.148 - fix fast decay not working. removed safeguard to prevent foliage destruction, replace with hackfix

Hey there! Happy holidays!

I would like to find out if some features are used at ALL any more, so I added some more detailed stats. Maybe we can remove some things that one person requested ages ago and that might cause more trouble than it does good?

Help me find out by keeping the default settings. If this causes issues for you, you can disable the full metrics, or metrics at all, in the config.yml, there is a new bStats block starting this version

I created a discord server. Feel free to join it in case you encounter a problem!

https://discord.gg/DSNfjYA

These are the specific changes:

• v7.0.136 - version bump for debug reasons
  
• v7.0.135 - properly actually read map values when reading config values (probabilities)
• v7.0.134 - remove the former hackfix to try to make saplings appear after the cleanup - this only worked in some cases
• v7.0.133 - also delay saplings that try to plant themselves until after all self cleaning trees are done! - should wrap up tickets #57 and #57
• v7.0.132 - delay sapling replant until cleanup is done - addresses github issue #57 and issue #58
• v7.0.131 - handle sapling replant enforcement with appropriate priority and do not replant before the cleanup - addresses github issue #57

• v7.0.125 - fix a config loading error causing thick trees and mushrooms not being recognized as trees
• v7.0.124 - actually delay sapling protection instead of enhancing it and starting it when the first block is broken - addresses github issue #53

So sorry for all the troubles, thanks for the reports in the comments!

• v7.0.123 - warn when a config setting does not match the expected data type
• v7.0.122 - actually use sapling replant delay in ticks, not seconds! - addresses github issue #54
• v7.0.121 - only cancel the initial block break event if we kill it in the same instant anyway - addresses github issue #55

Config settings might have been messing up and will show a warning on server startup, telling you which file and which setting you need to check. It will now try to force parse numbers properly. It still might lead to wrong values so look out for warnings when loading the configs

v7.0.113 - reinstate sapling protection - addresses github issue #53

Ever since version 7, this seems to have been broken. Thanks to DjeyMute on GitHub for the notice

Full changelog:

• v7.0.112 - properly restrict the plugin if set in the config - addresses issue #52
• v7.0.111 - debug when a plugin cancels the breaking of the tree
• v7.0.110 - add more debug for when a tree determination fails

• v7.0.109 - update the default ymls
  
• v7.0.108 - add a warning when an invalid material has been entered; fix 2 entries in the natural block list
  
• v7.0.107 - add more tools to the cooldown calculation; abort tree determination if an invalid block has been found
• v7.0.106 - add netherite axe to tool list and drop factors, addresses issue #50
• v7.0.105 - fix a nether related possible infinite loop

Nether Update Part X

Netherite items will be retroactively added to your configs, if you did not do so already.
The cooldown calculation now supports the new axes, leaves and all valid tools for them (hoes, shears, swords) and even stripped logs (but these would not allow for auto felling with the default setting for the plugin!

Weird destruction of trees in columns

The plugin would in some cases allow to auto destroy a single column of a tree if an invalid block when it would actually want to do nothing at all - if an unknown block was too close. These blocks included cocoa beans and azure bluets as I mistyped their names in the lists. These lists will also automatically be updated, if you did not do so already.

Now I stopped the tree determination alltogether if a player placed block / invalid block is found. The thin tree definitions would still allow an invalid thick tree to partially be killed because it assumed we are in a tree farm that just is not thick enough to be a full thick tree

NullPointerException

Finally there was a small bug that could lead to a NullPointer if an invalid item was added to the list - some contributed by me, some by other users. They will be informed where exactly the issue is so they can fix it now

• v7.0.104 - revert changes made while testing
• v7.0.103 - undo changes to tool "hoe" for nether, as this does not apply at all. Logs still are axeable and the rest is, too.

I was under the impression, because not reading properly, that you HAD to use hoes on the new nether trees... Logs still have AXE as best tool, and the rest of the blocks also work well with just an axe... so we remove the hoe settings in the nether.yml (defaulting to regular tree settings then) --- config will be updated automatically by removing the tool list and the Custom Drop Factor list

This has been tested in the new nether, I am pretty happy with it.

Feel free to report bugs happening. Please do not report bugs with TreeAssist lower than version 100. Nether trees were NOT implemented until just now, as I could not test how they work at ALL.

Now I could and I fixed some things. Existing configs will be fixed to reflect proper nether values!

Please note that for nether, the proper tool is the HOE ...

• v7.0.99 - sync jenkins and github - sorry for any confusion
• v7.0.98 - only auto-plant saplings when this is set in the config!
• v7.0.97 - delay fast leaf decay if delay is set
• v7.0.96 - convince FallingBlocks to not drop themselves after falling

1) FallingBlocks used to spawn leaf items which should only happen when the player uses Silk Touch
2) Fast Leaf Decay is now hooked into the auto destruction delay, so if you want destruction tick delay, this also now is applied to the fast leaf decay!
3) Saplings would always be planted of the config setting - oups

Documentation:

• Main Config
• Tree Config

Notable changes:

• Complete rewrite of tree determination and tree definition.
• Outsourcing of over 30 config.yml nodes to the new trees/default.yml node.
• The folder `trees` contains all tree definitions. The examples should help set up custom definitions.
• config.yml rewrite with attempted migration and warning in case there are wrong entries.
• config.yml has custom comments in hopes to clear up some confusion.
• Support and defaulting to the new material IDs, e.g. `minecraftak_sapling` instead of `OAK_SAPLING`.
• Migrating of all chances to probabilities - instead of percentages we use factors where 1.0 is 100% chance.
• Reorganization of Utils class, separation into separate utility classes
• JavaDocs for every public and every important method
• TreeAssist events fully documented, added some more configurability, and changed the replacement event to work with Material instead of its name
• mcMMO hooks now should support all block types, mcMMO should decide what kind of EXP to add
• `noreplace` command renamed to `noreplant`, including permissions and config nodes
• config default for "Only When Bottom Broken First" changed, as this setting never worked anyway
• logs should break from bottom up (thick trees look much better now)
• leaves should break from inside out
• destruction should be much faster now as we check for duplicates

This version will be excluded from the automatic update, so even if you rely on this to work, please manually upgrade this time and check for errors or warnings. Thank you

v6.0.91 - address a NPE because of the new support of not 4-trunk spruce

v6.0.77 - make sure config values for mcMMO and Jobs are read - only try to load mcMMO and Jobs if required and requested

Thanks to Rooz for the suggestion and verifying that it works as intended

• v6.0.75 - remove debug outputs that we do not need
• v6.0.74 - remove "wood_axe" and "gold_axe" remnants
• v6.0.73 - make trees literally fall down - off by default for testing, happy falling!

Use "Main.Use Falling Blocks" to enable the new feature!

v6.0.72 - change default tools to 1.13 material names (woodEN and goldEN axe) - add converter for these nodes. Please check your lists for outdated names

Thanks to mineyfray for the heads up

• v6.0.71 - disable check by setting lookup time to <= 0. Even if the result is the same this actually skips database lookups!
• v6.0.70 - Expand lookup time to all Block Lists
• v6.0.69 - Implement lookup time for Core Protect
• v6.0.68 - "Block Statistics" config nodes for Pickup and Block Mine statistics, defaulting to false!
• v6.0.67 - more sapling block fixes - in some cases the bottom block would stay

First off, we did some stability fixes to the sapling block detection, then we added support for hooking into the minecraft block statistics. This allows server owners to have using the plugin count up the block break and pickup statistics, if activated (!)

Then there was a small pull by pop (thanks for the idea) which lead to actually every block list supporting a maximum lookup time, defaulting to one day. You can allow for longer lookup or shorter lookup time, for example if you know that no block is older than 3 hours, why look for the last 24 hours?

Hope everything turns out right, I could not test the build because I do not have a database driven server any more to test this. But it should be basic enough to not be a total disaster

Fingers crossed!

• 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.

v6.0.62 - Update to an mcMMO version that is more suitable (1.5 => 2.1)

Yeah, this is the issue when you don't run a server yourself anymore with all the possible plugins to hook into. Thanks for reporting this, we now use the latest version, at least API wise, of mcMMO.

Feel free to reply to this thread if you have any feature suggestions.

v6.0.61 - Add bStats and a working command autocomplete system

I am dipping into metrics again, replacing the discontinued mcstats in favor of bStats.

Also, the initial reason I started today was the auto complete feature. It really irked me that it returned players for each argument, now it returns players where appropriate (almost never) and offers helpful command predictions based on your permissions and the (sub-)arguments available.

Enjoy!

Testing this on 1.14 revealed some issues in the 1.13 support I claimed. Now everything should be fine! Also, I rewrote the custom tree definition system to be more stable and more sane. Instead of 3 separate lists that allowed for IDs, required data and more, we now just use the strings that are supported by the 1.13 API, also we group the definitions together in nested lists. An example will be added in the form of a birch tree.

• v6.0.60 - Custom tree definitions now are in a list of lists in the config, grouped together properly and saved together, in the file and in the API
• v6.0.58 - Finalize the custom tree system so it is operational for now.
• v6.0.57 - Implement addcustom and removecustom in accordance to the 1.13 API - everything is based on strings like minecraft:dirt, should work backwards compatibly with properly defined material values!
• v6.0.56 - Fix mushroom implementation 1.13 compatibility
• v6.0.55 - Fix plugin.yml typos
• v6.0.54 - Fixed a bug where items not explicitly in the tools list could be used to cut down a tree

This version will run on 1.13 servers and should work just fine on 1.14 when it is stable.