SaplingAssist

• v0.7.3
  • Now compiled for bukkit 1.6.4.
  • Moved the [*FILTERS] description from the bottom to the middle of the plugin usage description. This gives a cleaner look.
  • Did some future-proofing by updating some code that I noticed was using deprecated methods. (Block.getData()/setData() still used.)
  • Added sapling protection (wip)
    - For now it is hard-coded to 30sec, will be added to the config in the next version! (Need to update all the commands etc to support it.)
    - The metadata associated with the protection is automatically removed if the block breaks or the sapling grows up.
    - Added a small sound when you try to break a protected sapling (You will be able to toggle it in the next version).

• v0.7.2
  • Now compiled for bukkit 1.6.2.
  • Pending sapling-replant tasks now happen instantly on server shutdown.
  • Altered the behavior for useCurrentWorld:false so that it uses currentworld anyway if setting already exist for it.
  • Removed the example from the in-game command help (it was very confusing before you realized you had to scroll up to see the rest).
  • Bug fix: Apparently there was an issue with server-default settings not working on 1.6.2 (delay always became 1 second).
    - This would only manifest when there was neither any settings for the player nor any settings for the world, so took some time for me to notice it was broken.
    ...Was using a config.get(path, defaultValue) - but despite the path existing it always returned the defaultValue.
    ...The code is now: if config.contains(path) get(path) and returning the default in the else-statement, which works as intended.
  • Bug fix: Possible null-pointer exception if a player tried to access settings on a player that doesn't exist, without specifying the world.
    - (This would not occur if run from console - only if executed from in-game chat.)

(Shortened the change log to the two latest version - view older files for the complete change log.)

• Config merge feature is still experimental (and it will never be 100% perfect - that is impossible).
• It's a little spam-ish in the console on server start (this is the merge being added on-top of previous functions - doing something about it is just low priority since it's only cosmetic)
• The sapling-protection is not yet configurable, but v0.7.3 contains no new bug fixes compared to v0.7.2, because I haven't found any new bugs in v0.7.2 :), so if you don't want sapling-protection just stick to v0.7.2 and wait for the next release.
  (v0.7.2 is 1.6.4 compatible!)