SalvageSmelter
SalvageSmelter
[ English | Français ]
SalvageSmelter allows you to smelt down tools and armor made of iron, gold or diamond into raw materials. the quantity of materials returned is dependent on the durability of the item being smelted, for example iron boots at 50% durability would return 2 Iron ingots. At 49% durability they would return 1 iron ingot. Gold tools can yield nuggets instead of ingots to allow for more accuracy in determining the value of an item, and any item not worth at least 1 of it's raw materials will produce a piece of charcoal.
Features
- [NEW] Optional sign-based permissions. when
require-signs: true
in the config.yml furnaces will require [SALVAGE] signs on them. - Automatic updates!
- Configurable Recipes
- Smelt iron, gold and diamond armor, as well as tools. enchanted, named or damaged, doesn't matter.
- works great with hoppers!
Commands
- /salvagesmelter reload - reload the configuration
- /salvagesmelter debug - toggles debug mode on/off
Permissions
- salvagesmelter.admin - allows access to the /salvagesmelter command.
- salvagesmelter.createsign - allows players to create [SALVAGE] signs.
Tutorials
Для русскоязычных пользователей видео от Rissman
Source Code & Development Builds
Source code is available on Github
Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk.
SalvageSmelter Development Builds
Other Plugins
- PortableHorses - your trusty steed in your back pocket.
- Scribe - Transfer enchantments from items to books using an anvil
- http://dev.bukkit.org/bukkit-plugins/dig-for-dollars/DigForDollars - Get paid to mine!
- PotatoBombs - Allows players to craft poisonous potatoes into devastating and hillarious magical landmines.
- Autocrafter - Turns droppers into redstone powered crafting tables.
@Dragonkin01
Must be a different plugin protecting them, SalvageSmelter doesn't do anything to prevent explosions or destruction of furnaces in any way.
@CommodoreAlpha
No, this requires the bukkit api, it's server-side only.
Would this work with a client mod like Metallurgy? (e.g. you can specify item "x" to give back "n" amount of item "y" if its damage value is anywhere from "a" to "b")
@metalhedd
I have an issue on my server where the salvage smelter is invulnerable. Whenever the sign is placed on the furnace, all explosions within a short radius are rendered ineffective, even against sand and other blocks. In addition, the furnace refuses to break with a pick unless the sign is broken first. This has the potential for irritation and exploit on a pvp server like mine. Could you address this please?
As an aside, I appreciate the work you've done thus far. We make use of portable horse and scribe, which has added a great deal of dimension to our gameplay. Thanks for sharing your brilliance with us. :)
@jpell1221
There is already a recipe-group system which works on permissions. you can assign certain furnace recipes to different groups, and only people with the right permission nodes can use that recipe in the SalvageSmelter. The downside of this, is that it prevents hoppers/droppers from being able to move things into a furnace, because they can't be checked for permissions.
Do you think you can create a permission for using the furnace?
Thank you for keeping this updated. This is a great, simple plugin.
@switorik
Fixed in 0.1.7, waiting for approval now.
@switorik
This looks to be caused by Craftbukkit's recent changes to furnace recipes. Thanks for catching it, I'm working on a solution now.
@ha11oga11o
Apparently, if your items are damaged they won't smelt in 1.7.2. Working on a fix.
For some reason, damaged items will not smelt for me. Named and enchanted items work fine.
@metalhedd
No no crash,
but when i place item on furnace it simply not smelting it anymore :(
@ha11oga11o
it works, but some earlier craftbukkit builds had a bug which caused it crash on startup. if you're getting an error open a ticket
seems this not working for 1.7.2 or im doing it wrong?
@switorik
I think craftbukkit has been doing some work with FurnaceRecipe's that could have exposed the issue in more recent builds. it probably just ignored the cauldron previously.
Thanks for helping me out, I changed it and now it works like normal.
The only thing I don't get is that it was working for a while before it broke.
Anyways, I appreciate the help and I love your plugin.
@switorik
CAULDRON should be CAULDRON_ITEM in your config.yml
the CAULDRON is the block version, not the item, so it can't be used in a recipe (or rather it can but it kills minecraft :))
I'm adding a check to prevent that sort of misconfiguration now.
@switorik
Its definitely your config file. when I copy it to my server it crashes 2 other plugins which attempt to iterate the server's recipes. when I revert to the default config.yml the problems go away.. I'm working on narrowing it down to which section of the config right now.
I added a few extra things but it worked until I updated it. Then after I updated the server and went back, it wouldn't run at all.
http://pastebin.com/8UkhSvtx
edit: I recreated the issue on my offline/personal server when I updated to the latest build, however when I went back to the previous build it seemed to work again. I tried it on my online server and it still does not work.
@switorik
I just tested against craftbukkit #2978 and the plugin appears to be working properly. The crash looks like it could be related to an invalid smelting recipe, have you customized the SalvageSmelter config.yml at all? can you paste bin that as well?
I updated my server to build #2978 and I believe salvagesmelter caused it to crash. I then reverted back to my last successful build and it still crashed the server. I disabled salvagesmelter and the server runs fine.
I'm not sure what changed or if it is caused by salvagesmelter, but I thought I'd share my error just in case.
http://pastebin.com/288dGNRh
@UnDrac
That's not how events work. When an InventoryMoveItemEvent gets called, every single plugin that's registered for it will get called. SalvageSmelter, Prism, LWC, and literally every single other plugin will be called the same number of times.
Your problem is not SalvageSmelter, it was mostly likely just the victim of a garbage collection lag-spike. If you can produce data showing 100 out of 100 lag spikes occur at the same spot, then we have a problem, but with an average of 2.6ms / tick, SalvageSmelter is very light. (a tick is 50ms)
This is actually already possible by using recipe-groups, but the feature hasn't really been documented at all. Basically, add a section like this to your config.yml:
all the recipes listed here will require the permission node:
salvagesmelter.group.a-group-name
and will not be accepted via hopper / dropper