ChangeSilkTouch
9,151 Downloads
Last Updated: Apr 22, 2012
Game Version: CB 1.6.2-R0.1
+2
ChangeSilkTouch
Description
This mod allows you to change what blocks are able to be broken and collected with a SilkTouch tool.
By default, it makes SilkTouch tools work on monster spawners, (though they will not keep their monster type) but the configuration is very flexible, and can be used to make any type of block drop a stack of any other type of block if you so desire.
It is fairly simple, and I intend to keep it fairly simple. Feature requests for anything beyond the described functionality of this plugin will likely be denied. (But file bugs about anything that you see wrong!)
Note: This means that it is not getting permissions support.
Documentation
Source
Source is available on github and a binary is available here.
everytime i pick up a spawner and place it, it puts down a pig spawner how can i change this? thanks
Hi there, could you please update your source code, thanks =)
@user_83
No, it is not a known problem, and it is highly unlikely that this is caused by this plugin. If you see any strange behavior on the server side, this plugin could be suspect, but it client crashes rarely-if-ever originate from server plugins.
Hey there, great plugin, super helpful with preciousstones. I turned my server on after a while of inactivity to test out some plugins, and every time I use silktouch on a lapis ore the client crashes. Is this a known problem?
@funfair91
I honestly am not sure what you are trying to ask/say. It kind of looks like you might be asking me to support integration with PreciousStones, which will not happen. Either that, or you expect lapis lazuli to not break when not using silktouch because of this plugin, which is not supported. This plugin changes how the silktouch enchantment affects blocks, and that is it. It does not change how blocks are mined when you're not using silktouch.
Hi, i am using this together with precious stone. However the plugin destroy the lapis even when it is not in silktouch. I noticed that when i destroy the lapis ore used as preciousstone it will destroy the protection but not the ore, then i will have to break it again and the lapis become lapis dye.
@funfair91
You've got it. As long as that is on separate lines and formatted correctly and such, that should work.
Hi, i would like to know, if i wanted diamond block to drop only the ore is it? blockType: 56 dropType: 264 count: 1
@cppchriscpp
Yeah its become something of a desease, everything seems to need a call home feature these days ( refering to software in general) i can understand it being helpfull for some but at least let it be disabled by default. The problem is generally all are enabled by default. Let the end user decide if it should be turned on.
@titen96
I do not install code to spy on my users; especially things that phone home on first use without the ability to disable it. No, this will not be happening ever.
@cppchriscpp
hey cpp, i think that implementing mcstats will help ya out in knowing how many people use this plugin.
@Mannollo
The plugin does retain data values, but that is not how monster spawners work. This plugin will not add that functionality. There is a plugin called SilkSpawners that will, however. Search for it on here. It should do what you want. (Remove the spawner item from your ChangeSilkTouch config if you decide to use both.)
hey good plugin ! thanks you.
however it would be great if broken block's data can be memorized
example : zombie monster give zombie again and so on ...
appears to be working thus far :)**
@Mhjort
This will require no modifications for 1.3, and will continue functioning just like it did with 1.2.5, etc.
Awesome plugin, I hope you'll maintain this for 1.3 as well :)
@user_151271
Sorry to double-post on you, but I actually just decided to bite the bullet and do it. Version 1.2 is now available via the link above. I've uploaded it to dev.bukkit.org as well, but it hasn't been approved yet. Data values are now supported. I tested with your config since I already had it around.
Here's a proper configuration file to drop lapis ore (I set the count to 3 for testing; do what you will with that though.) with the new version: http://pastebin.com/dhvBrfc7 - obviously, you'll need to update to use it, but there you go.
@user_151271
Hey, I just got a chance to try out your config, and actually, almost everything is perfect. Are you sure you have the config file in the right place? It should be in plugins/ChangeSilkTouch/config.yml by default.
I tried mining coal and got coal ore, and I tried mining diamond and got diamond ore. Oddly enough though, mining lapis resulted in a gold ore block, which makes sense based on your config. For lapis, you have the dropType as 14, which equates to gold ore. Unfortunately, you may be out of luck on getting that one to work correctly with the current version.
You can get the drop type to be an ink sac, but you won't be able to get it to drop lapis ore, as you'd need to set a data value on the drop, which is not yet supported. People have been asking for that for a while though, so I think I'll take a quick look at adding this functionality in. Expect a new key of dataValue: (number) in the configs soon.
@cppchriscpp
Wow, thanks for the fast response. No errors on start-up and bukkit shows that the plugin is active. I seem to only be having problems when I try to make blocks drop their respective ores. With that current config, they drop the same block that is mined, like how Silk Touch would normally work. My goal is to essentially disable Silk Touch on certain blocks using your plugin.
@user_151271
Hey,
From a quick inspection, everything looks right to me. I can't actually take an in-depth look into the problem right now, but I'll see what I can do when I scrounge up a bit of time.
To help me out though, what exactly seems to be going wrong? Are there any errors on startup, or does it just not seem to be functioning? Also, what happens when you mine one of the blocks with a silktouch tool? Does it drop nothing, or drop what it would normally drop, or what?
I don't believe the plugin currently prevents the default drops from dropping from the mined block, which was an oversight on my part. I'll need to fix that when I do my next update. If this is the problem, I am now aware of it and intend to fix it, but please let me know anyway.
Hopefully I'll be able to address your issues in the next day or so, but if not, I'll get to them as soon as I'm able.