Sensible Toolbox
Sensible Toolbox adds a bunch of new items, tools, blocks, machines, an energy system, an item transfer system, plus a developer API to make it easy for other plugins to define their own items. It's heavily inspired by certain Forge-based mods, but of course requires no client modifications at all.
| All Downloads |
Videos
A nice tutorial/review of v0.0.1 by MusicTechnician:
Documentation
- Installation and Quickstart Guide
- Command Reference
- Configuration File
- Permissions Support
- Access Control and Block Protection
- Items and Blocks
- Block and Inventory Protection
- Developer API
- Credits - Plugins/Mods/Authors to thank
Known Plugin Incompatibilities
- MultiInv: if you're carrying any STB items when you switch inventories, those items will lose their data, since MultiInv doesn't currently preserve extended item attributes which STB uses to store item-specific information. The MultiInv author does plan to add attribute support so hopefully a newer version of MultiInv will resolve this in the future. For now the workaround is to store any STB items before you switch inventories.
- LWC: LWC is supported, but you must use a recent dev build of LWC with UUID support. Dev builds of LWC can be obtained from http://ci.griefcraft.com/job/LWC/. If you can't use a recent build, then you can disable LWC support: see Protection.
- WorldEdit, Movecraft or indeed any plugin which move regions of blocks around or directly clear regions without firing events: don't use them with any region which contains an STB block. The physical block will be moved or removed, but STB doesn't (can't) know that and will keep a record for the associated STB object in memory. This could lead to all sorts of problems.
Source Code
https://github.com/TheBusyBiscuit/sensibletoolbox
Auto-Updater and Metrics
All my Plugins are using an Auto-Updater to make sure, you're always
using the latest and hopefully most bug free version of my Plugin.
If you don't want this Plugin to be auto-updated, you can turn it off
in the config file at "options -> auto-update: true/false"
They also use a Metrics-System which collects the following Informations:
A unique identifier
The server's version of Java
Whether the server is in offline or online mode
The plugin's version
The server's version
The OS version/name and architecture
The core count for the CPU
The number of players online
The Metrics version
Opting out of this service can be done by editing
plugins/Plugin Metrics/config.yml and changing opt-out to true.
@mcnamarac86
The hopper->itemrouter->bsu setup is working fine here. Is your hopper possibly LWC- or WorldGuard-protected, preventing the item router from pulling?
Can you raise a ticket please - include the exact version you're using (if a dev version include the Jenkins build number). Can you try turning debug mode on -
/stb set debug_level 1
- and see what messages related to the item router get logged on the console.@mcnamarac86
And also I've tried to send to chests, furnaces, BSU's, HSU's, and other machines. Here is my setup that works:
BSU(Coal)(Locked)(Ignore Redstone)
V
Router (Locked)(Puller Up Whitelist Coal) (Sender Down Whitelist Coal)(Ignore Redstone)
V
Heat Engine(Ignore Redstone)(Locked)
and it feeds coal from a BSU to the heat engine fine.
NOW I have an auto lossless cactus farm, with this setup:
Hopper(East)
V
Router(Locked)(Ignore Redstone) (Puller Whitelist cactus East) (Sender Whitelist cactus South)
V
BSU (South)
can NOT get it to pull cactus from the hopper or from a chest at the end of the bank of hoppers and send it into the BSU.
I cannot get routers to work anymore since this recent update. I've tried crafting new routers and sender / puller modules. white list blacklist, all sort types, even taken routers that work, with working puller and sender modules. I cannot pull and send eggs or cactus. any ideas?
Thanks for the links to your Javadoc :), i dont know why i did'nt see your link before in the overview page ...
Another enhancement for the recipe book can be a permission to see a particular item, this can allow to make a hidden item without interferring admins users.
@DSang
Hmmm, there's no simple way of creating a custom recipe book right now, but I like that idea. I'll look into ways of allowing that - probably by extending RecipeBook (or AdvancedRecipeBook) and overriding a method which returns the subset of recipes to be shown.
For checking if a block is an STB block, use one of the getBlockAt() methods in http://desht.github.io/sensibletoolbox/me/desht/sensibletoolbox/api/SensibleToolbox.html. Probably worth bookmarking http://desht.github.io/sensibletoolbox/ too.
I should also note that the 0.0.4 API has changed a fair bit since the previous release, but it should now be reasonably stable.
I have some questions about your api,
What is the good way to create a new recipe book with only my news items ?
How distingue a STB placed block to a normal placed block ?
@mobilephone2003
Yeah it had occurred to me that a config value to set the default access for newly placed blocks would be a good thing. I will add that - expect to see it in a dev build pretty soon. It won't make it into v0.0.4 unfortunately, which is now uploaded and awaiting approval...
@desht
This is probably an odd request, but can we have it so machines can *only* be used by the players who placed them? Always locked to the player without public access? A bit like an LWC Chest?
Then could use /stb friend and /stb unfriend to add people similar to /cmodify
@mobilephone2003
Each STB item has a set of permission nodes allowing things to be done with that item: see http://dev.bukkit.org/bukkit-plugins/sensible-toolbox/pages/permissions/#w-item-specific-nodes (the next release will also add a node for crafting each item). All of these nodes are true by default, meaning in a new install, everyone has access to everything.
If you want to control stuff by permission group, you would need to add the nodes as false to that group in your permission plugin. I appreciate that could be a lot of config if you're blocking many items... I could look at adding a parent permission node for each item which includes all of the sub-nodes or some other way of making to easier to block many items... need to have a think about that. Update: added parent permission node "stb.allow.<item-id>" which will grant/deny all child nodes. So to stop someone (or a group) doing anything with (say) a Redstone Clock, just given the player or group stb.allow.redstoneclock: false, or the equivalent in whatever permissions plugin you use.
The recipe book does show items people can't craft at the moment (although bear in mind that the stb.craft.<itemid> node is only in the dev branch right now) but that's a good idea.
@desht
So far, amazing as expected. Can we restrict certain blocks to certain permission groups so they cant craft or use them? What's the best thing to do to prevent usage of any in the beginning? Will things people can't craft show in the recipe book?
Slowly transitioning the blocks in so people can learn what to make.
@mobilephone2003
Don't worry, there's plenty planned! Expected a v0.0.4 release pretty soon, it's in feature freeze and testing now.
This is awesome! Please continue development on it! Will report back with issues as they become apparent :)
@jaz000
Glad you're enjoying it! Replicating some of the Forge-based experience is very much what I'm after with STB.
I have a few minor bugs to report:
- re-filling the (wooden) combine hoe resets it's durability?
- On server restart mashers and smelters have another copy of their last output
- On server restart I get some labels around equipment as if from multimeter (I've not actually used the multimeter myself). This can be fixed by purging the HoloAPI directory on restart.
And I have some user feedback :
My friend asked me to never remove this from our server and I'm inclined to agree :-)
It's awesome. A bit like tekkit lite but maybe destined to get heavier, the choice of object textures and UI elements using the vanilla client is very clever ... and the sound of the masher ... awesome.
It doesn't feel to OP, farming tools just save a bit of time, mashing and smelting gives you a bit more, but no XP from the new smelter, have to use silk touch for some things, so it's no free lunch.
keep up the good work :-)
@Koolzskillz
It's not possible to disable crafting right now, but I'll add a per-item permission node to allow/disallow crafting of items. So next release will have a
stb.craft.recipebook
permission node, which will be true by default. You'll just need to set that node to false in whatever permission plugin you're using.There's already a command to get/give items: http://dev.bukkit.org/bukkit-plugins/sensible-toolbox/pages/commands/#w-obtaining-items - so you can do
/stb give recipebook 10
to get 10 recipe books, and then give them out as you want.Can I disable the crafting of the books, and a command to give them out? By book I mean recipe book
@delsolsi213
Sorry, really not a priority at all. What do you actually mean by "add support" anyway? if you mean get it working on CB 1.7.2 and earlier, then no - I have no plans to do that. I'm writing this for Bukkit 1.7.9+.
A major point of STB is to add at least a little of the modded Forge experience to CraftBukkit - if you're using MCPC/Cauldron, then much of what STB adds is better handled by Forge mods anyway.
@desht
Can you add support for mcpc/cauldron? :3
@RazorX2014
Yep, the sound muffler needs ProtocolLib to function.
have you removed sound muffler its not working now and i cant find or craft it.
Edit: must have disabled protocallib