*One caveat to the leafdecay compatability: if leafdecay speed = 6 then it does not log the decayed leaves in CoreProtect (I am working on this issue). If you're looking for a similar functionality to leafdecay speed 6 but want leafdecay logged in coreprotect, then use speed 5 and radius 2 together.
​

Log Pile Method (tgType=5) – When a tree is chopped down, the logs on the tree fall in a pile. See below for the applicable config variable “pileSpread”, which sets how spread out the logs are when they fall in a pile. You can set this method by “/tgconfig set type 5”. Also, can set the spread by “/tgconfig set pilespread [0,1,2,3,4,5,6]. All issues aforementioned with jungle trees, large trees, vines, etc. should be solved. The biggest issue now is when multiple trees are cut down at the same time, one of them only drops a few logs. Due to my limited ability to test the plugin, I cannot truly tell how big a problem this is, please let me know if you run into any issues ASAP.

Leaf Decay – Will make leaves in proximity of the tree chopped down decay quickly, so that you don’t need to wait 3-7 minutes for all leaves to decay on their own. See config variables below for the speed and radius at which leaves decay. Speed meaning how fast the leaves decay, 4 is fast and 1 is slow. Radius meaning how wide the area around the tree is that searches for leaves. 1 is a small area and 4 is a large area. I suggest keeping leafDecay.radius at 1 or 2 as any higher than that, and surrounding trees might be adversely affected.

Additional structure protection – checks for “natural” blocks beneath potential trees (“natural” blocks being dirt/grass/grass path/farmland/podzol/mycelium/coarse dirt). Thus, if you ever have any problems with houses getting chopped down, simply replace dirt/grass/etc blcoks beneath the logs on your house with cobblestone, stone, or another block I did not list above. This additional structure protection does depend on your houseProtection setting, meaning that the higher your houseProtection is, the more strict the plugin is with checking for “natural” blocks. If you have houseProtection=0, the plugin will still search for “natural” blocks, but as long as 1 of the tree’s base logs is on a “natural” block the treefeller logic will work. As I said above, this setting cannot be turned off in the config as it’s baked into the plugin, but if you set houseProtection to 0 you should barely notice this unless you’re dealing with many trees that are planted on blocks besides those I listed above (e.g. floating trees, trees planted ON water, etc.).​

pileSpread – Works with the new LogPile method. Values 0,1,2,3,4,5,6 will work, and the settings work like you think they would. For example, pileSpread=0 will give you the closest pile grouping, while pileSpread=6 will make the pile of logs more spread out.

LeafDecay.enabled– Whether leafDecay is turned on or off. Set to true or false.

LeafDecay.speed – How fast leaves decay that are left behind from lumberjack methods. A value of 1 is slow, and 4 is fast. Valid config values are 1,2,3,4. Default is 4, the value you set is strictly preference.

LeafDecay.radius– How large the area around the tree is that is scanned for leaves. 1 is a small area, 4 is a large area around the tree. Valid config values are 1,2,3,4. Default is 2, I suggest leaving it at 2, but it’s a free country.

oreSweeper – Just changed up the config variables and section where they’re stored. Should be self-explanatory. *I haven’t added support yet for fortune or silk touch enchantments, but unbreaking should be supported.​

Changed the way the code interacts with the config.yml. Again, if you only use in-game commands, this won't be of interest to you.

Before this update, available tgTypes were 1, 2, 3, 4 ,2.1, 4.1, and 4.2. Now, the only official tgType methods are 1 Lumberjack, 4 Basic Gravity, 2.1 Lumberjack Natural (logs & leaves), 4.1 Gravity (All Logs), and 4.2 Gravity (all logs with metadata). If you want the LumberJack natural or random methods (formerly tgTypes 2 and 3), there are new config settings to enable them. For LJ Natural see the 'fallMethod' config variable; and for LJ Random see the 'randomLogDrop' config variable.​

allowedWorlds - these are worlds that the plugin will work in, you should be able to add any world you want. Do this directly in the config.yml or use command '/tgconfig worlds add/remove [world]'

fallMethod - this is a variable that only applies to the Lumberjack method (where tgType = 1). Possible values for this variable are POP, BREAK, or NATURAL. Change this setting in-game with '/tgconfig set fallmethod [value]'.
POP and BREAK replace the tree's logs with an air block, and then drops a stack of logs. NATURAL breaks the tree's logs naturally, and thus the logs are dropped naturally.
POP breaks the tree logs all at once, so there is no runnable that spreads out the tree break event across multiple ticks. This may cause lag with larger trees. BREAK uses a runnable that spreads out the tree break event across multiple ticks, which should help in reducing lag. NATURAL breaks the tree's logs naturally, use this setting to replicate the former tgType 2 Natural method. You can still use the old command '/tgconfig set type 2'.

dropMethod - this is a variable that only applies to the Lumberjack method (where tgType = 1). Possible values for this variable are ITEMDROP or INVENTORY. Change this setting in-game with '/tgconfig set dropmethod [value]'.
ITEMDROP drops a stack of logs where the player first hit the tree, whereas the INVENTORY setting moves the logs directly into the player's inventory (and saplings if saplingdrop = true).

randomLogDrop - this is a variable that only applies to the Lumberjack method (where tgType = 1), but will not work with the lumberjack natural method. This setting can be true or false. Change this setting in-game with '/tgconfig toggle randomLogDrop'.
This function used to be fulfilled in previous versions by tgType = 3, or the Lumberjack Random method. When chopping a tree, you will get anywhere from 80% to 120% of the logs that were actually on the tree. You can still use the command 'tgconfig set type 3' to turn on this random lumberjack method on.

oreSweeper - I added this for fun and to use on my own server. It has pretty much the same code as the Lumberjack Natural method but it works with all ores, and you cannot customize any settings. Right now, the code abides by all Vanilla pickaxe rules (e.g. a wood pickaxe cannot mine iron ore, a stone pickaxe cannot mine diamond ore, etc.), except for enchantment rules - so if you have a fortune, silk touch, unbreaking pickaxes, I would not use this feature. I will account for enchantments in future updates.​

Summary:​

Changed the way the code interacts with the config.yml. Again, if you only use in-game commands, this won't be of interest to you.

Before this update, available tgTypes were 1, 2, 3, 4 ,2.1, 4.1, and 4.2. Now, the only official tgType methods are 1 Lumberjack, 4 Basic Gravity, 2.1 Lumberjack Natural (logs & leaves), 4.1 Gravity (All Logs), and 4.2 Gravity (all logs with metadata). If you want the LumberJack natural or random methods (formerly tgTypes 2 and 3), there are new config settings to enable them. For LJ Natural see the 'fallMethod' config variable; and for LJ Random see the 'randomLogDrop' config variable.​

allowedWorlds - these are worlds that the plugin will work in, you should be able to add any world you want. Do this directly in the config.yml or use command '/tgconfig worlds add/remove [world]'

fallMethod - this is a variable that only applies to the Lumberjack method (where tgType = 1). Possible values for this variable are POP, BREAK, or NATURAL. Change this setting in-game with '/tgconfig set fallmethod [value]'.
POP and BREAK replace the tree's logs with an air block, and then drops a stack of logs. NATURAL breaks the tree's logs naturally, and thus the logs are dropped naturally.
POP breaks the tree logs all at once, so there is no runnable that spreads out the tree break event across multiple ticks. This may cause lag with larger trees. BREAK uses a runnable that spreads out the tree break event across multiple ticks, which should help in reducing lag. NATURAL breaks the tree's logs naturally, use this setting to replicate the former tgType 2 Natural method. You can still use the old command '/tgconfig set type 2'.

dropMethod - this is a variable that only applies to the Lumberjack method (where tgType = 1). Possible values for this variable are ITEMDROP or INVENTORY. Change this setting in-game with '/tgconfig set dropmethod [value]'.
ITEMDROP drops a stack of logs where the player first hit the tree, whereas the INVENTORY setting moves the logs directly into the player's inventory (and saplings if saplingdrop = true).

randomLogDrop - this is a variable that only applies to the Lumberjack method (where tgType = 1), but will not work with the lumberjack natural method. This setting can be true or false. Change this setting in-game with '/tgconfig toggle randomLogDrop'.
This function used to be fulfilled in previous versions by tgType = 3, or the Lumberjack Random method. When chopping a tree, you will get anywhere from 80% to 120% of the logs that were actually on the tree. You can still use the command 'tgconfig set type 3' to turn on this random lumberjack method on.

oreSweeper - I added this for fun and to use on my own server. It has pretty much the same code as the Lumberjack Natural method but it works with all ores, and you cannot customize any settings. Right now, the code abides by all Vanilla pickaxe rules (e.g. a wood pickaxe cannot mine iron ore, a stone pickaxe cannot mine diamond ore, etc.), except for enchantment rules - so if you have a fortune, silk touch, unbreaking pickaxes, I would not use this feature. I will account for enchantments in future updates.


​

- none
- scream
- falling
- treefiddy
- creepy
- LOTR​

​