ToolBelt_0.1

Details

  • Filename
    ToolBelt.jar
  • Uploaded by
  • Uploaded
    Mar 27, 2012
  • Size
    53.71 KB
  • Downloads
    336
  • MD5
    c33a32eed4563271fe218e8a354eff06

Supported Bukkit Versions

  • CB 1.1-R8
  • CB 1.1-R4

Changelog

Initial commit to bukkit.org

Working duplication, data scroll, paint, and leap tools.

Update BETA2 The original file had an issue where it spawned a [SEVERE] error on the console when a user scrolled over an empty item slot.

Update BETA3 The paint tool now has an optional whitelist. Read the tool: paint: onlyAllow: comment in config.yml for information on its use.

Update Release

  • Support for region plugins (like WorldGuard), logging (like LogBlock or HawkEye), and more (like NoCheat).
  • New tool, PickHax, similar to VoxelDoop's Jackhammer.
  • Scroll tool now always shows the block change for the player performing the scroll action.
  • Tool specific configuration help has now been pulled into plugins/ToolBelt/help/<tool>.txt
  • Paint tool's range is now more configurable.
  • Global block restrictions in config.yml
  • Significant printout improvements.

LogBlock has issues when scrolling a material from data value 0 to any other data value. A patch has been sent and accepted to LogBlock, so hopefully the next version will not have this issue (Build #112). HawkEye reportedly does not share the same problem.

The ranged addition to painting is blocked if you have NoCheat on your server. If you run across this issue, try giving nocheat.checks.blockplace.reach to the user in question. This likely will also happen with other such plugins, try and look for similar restrictions that might be causing the problem.

Players near someone using the scroll tool might not see data value updates in certain situations. If the map area is reloaded from the server (going far away and coming back, logging off and back on) the data change is visible.

If a player has access to the VoxelSniper tools, crouching and right-clicking performs unexpectedly. This is an issue with VoxelSniper, and I am trying to work with them to get this resolved. In the mean time you can:

  • Change the tool painting is bound to from the SLIME_BALL to COAL or some other material.
  • Disable VoxelSniper privileges for those that have the Paint tool.
  • Set Tools: paint: rangeCrouch: to 0 in config.yml to disable any sign of crouch painting, and tell your users not to try it.