ToolBelt_0.7.5
Details
-
FilenameToolBelt.jar
-
Uploaded by
-
UploadedApr 14, 2013
-
Size110.27 KB
-
Downloads949
-
MD5e9b9199743cf10113399f4d4ee3a59d4
Supported Bukkit Versions
- CB 1.5.2-R1.0
- CB 1.5.2-R0.1
- CB 1.5.1-R0.2
Changelog
Update Release 0.7.5
Update Release 0.7
- Update to support updated slab block in Minecraft 1.4.6
- Added Tree Tool (Disabled by default)
- Match Minecraft spawn protection (Was one block too large)
- Added a simpler example of ranks
Update Release 0.6.1
Update Release 0.6
- Update to support new (and updated) blocks in Minecraft 1.4.2
- Leap tool can now have a limited number of uses
- Leap tool fall damage protection changed (default only protects against next fall)
Update Release 0.5
- Fix text display issue when permissions:true but no permissions plugin is installed
- Support Minecraft 1.3 block types
- Ruler tool now uses paper instead of string (This is because of tripwires)
- Significant code cleanup, added javadoc, converted to maven. (No functional change with respect to these commits)
For older change logs, check the previous file uploads
0.7.5 The config file has had a few changes to support the new block types in Minecraft 1.5. In addition to the instructions for 0.7 below:
- tools.global.stopCopy has had 149 and 150 added (the two Comparator OFF/ON blocks)
- tools.dupe.keepData has had 155 added (the Quartz block)
0.7 The config file has had a couple of changes, but those don't matter unless you want to add the tree tool. Either regenerate the config.yml and uncomment the tools.bind.tree line, or just add the tree settings from plugins/ToolBelt/help/tree.txt into the appropriate sections.
- tools.bind.tree added, with default GOLD_HOE (294) and is disabled.
- tools.tree.possible added with and empty list as default. This allows for all tree types to be generated. For more assistance look at help/tree.txt
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.