SilkSpawners - Harvest mob spawners with silk touch
Thanks for MILLIONS of downloads!
This plugin requires Java >=8!
A sign shop addon for buying and selling spawners can be found here: https://www.spigotmc.org/resources/12028/
Ever wanted to move a mob spawner? With SilkSpawners, you can now pick up and move monster spawners.
If you use a pickaxe with the silktouch enchantment you will receive the spawner again.
You can control each mob spawner, allow crafting and of course mod support.
I'm happy to hear about your opinion, just leave a comment with a feature request, bug, improvement or just a personal opinion.
As a reminder I want to say that I worked very long on this and really appreciate a 'thank you' in form of a donation! (See details on the bottom or the button on the top)
Thanks @smsunarto||Scott Moses Sunarto
- NEW A sign shop addon can be found here: https://www.spigotmc.org/resources/12028/
- Added BarAPI support (for 1.9+ only: support for Vanilla implementation)
- per Type spawner name and explosion chance!
- Support Minecraft from 1.8.X to 1.19.4
- Configure a percentage of dropping a spawner on explosions (TNT & creeper)
- Spawner retains creature type
- Works on any spawner
- Crafting of each spawner (own recipe for every mob if wanted)
- Showing of creature type when spawners are placed, broken or held
- Commands for
- Changing a spawner in hand or sight
- Getting a new spawner (or egg) in the hand NEW: With offline player support!
- Console support
- Left-click spawner with spawn egg to change type (consuming egg or not)
- If enabled, right click with an egg and a MonsterSpawner of this type will appear
- Permissions support
- Support for
- Custom mobs added by client/server mods
- Spawning any entity with spawn eggs (dragons, non-creature entities, etc.)
- Dumping entity ID map on startup for debugging mods
- Compatible with
++and Spigot (see spawnersUnstackable)
- MCPC(+) and ported mods (auto-detects IDs)
- Not Enough Items (newer builds only)
- Flexible creature type names on input (pigman, zombiepigman, pigzombie, etc. all accepted), official names on output (Magma Cube, not "LavaSlime")
- Colored item names
- Localization of all messages
- There is an economy addon to charge the users when they change a spawner: SilkSpawnersEcoAddon
Third party features, all of them can be disabled
Please take a look at the detailed information about bStats below!
- bStats for usage statistics
- Auto Updater (connecting to http://dev.bukkit.org for updating checking)
- can be disabled if you switch autoUpdater to false in the config.yml
See the config here!
You can find a list of permissions and creatures here!
Only the bukkit permissions are supported!
I highly recommend that you use a plugin for permissions like bPermissions
If no permission system is found, all commands are for OPs only!
If you suffix a mob name with egg you will receive an egg instead.
NEW NEW NEW NEW
/ss help - Displays the help menu.
/ss list|all - Displays all available creatures.
/ss view - Displays information about the viewed spawner.
/ss reload|rl - Reloads the configuration files.
/ss change|set <newMob> - Changes the spawner you are currently holding or viewing at.
/ss give|add <player> <mob> [amount] - Gives a spawner or egg to the player. Amount is optional.
/ss selfget|i <mob> [amount] - Gives a spawner or egg to you. Amount is optional.
NEW NEW NEW NEW
English (default) by timbru31
German by timbru31
Dutch by Jeroendedoem
Indonesian by smsunarto
Norwegian by Riaz
Swedish by Syrianen
Italian by xMarioAnak
Spanish by JUMBONET
Turkish by xwerswoodx
French by Don_Sensileone
/ Portuguese by Luligabi
Polish by PLKaratusPL
Russian by EV.Jack
Feel free to share your localizations and they will be added here, just leave a comment with a link to a translated localization.yml!
Thank you for contributing!
Downloads/Source Code/Dev Builds
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.
(Latest dev builds/bleeding edge builds) - - Dev builds from Jenkins
(Source code hosted on GitHub) - - Source Code
Future Plans (a.k.a. ToDo)
Maybe add economyDeveloped an addon, SilkSpawnersEcoAddon Better API?Added in 3.1, custom event
- If sign shops are not working, you may want to try my custom sign shop addon: https://www.spigotmc.org/resources/12028/
- Mobs like Ghasts or Giants are too big for the spawner, this a Minecraft bug and I can't fix that
- Some older Essentials versions/ports are not updated properly for 1.8. There is a maintained fork called EssentialsX you should try.
- If you use Gui Sign Shop and users are unable to place spawners, you need to grant them the guishop.spawner permission from Gui Sign Shop
- Holographic Displays makes Slime spawners non functional
- UltraCosmetics, causes some spawners to non function: https://github.com/iSach/UltraCosmetics/issues/259
You can find more information here!
SilkSpawners is equipped with an API. You can find more information here!
- Adds support for Minecraft 1.19.x
- Various dependencies (such as bStats, WorldGuard, FactionsUUID) have been updated
- Adds support for Minecraft 1.18.2
- Adds a new permission silkspawners.list.* that filters the list output of /silkspawners list
- The tab completion now respects the users permissions and does not suggest mobs that are not available
- Fixes a bug where spawners obtained outside SilkSpawners were not recognized correctly (1.18 only)
- Various dependencies (such as bStats, WorldGuard, FactionsUUID) have been updated
@mushroomhostage for his awesome plugin! I'm glad you allowed me to maintain it!
Thanks to all the testers with the 3.0 dev versions!
Feel free to use this banner!! :)
Statistics (from bStats)
I worked really hard on this plugin and I'm very happy about any donation.
Support me & buy me some beer, this makes me happy and keeps me interested in this plugin.
Donation chain: -> I receive some money -> Buy coffee -> Work longer -> Faster Updates -> Your benefit!
There is a button on top of this page (right to the different tabs)
I'm accepting bitcoins, too! :)
This plugin is released under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) license!
Information about the data usage collection bStats
./plugins/bStats/config.yml contains an option to opt-out.
The following data is read and sent to https://bstats.org and can be seen under https://bstats.org/plugin/bukkit/SilkSpawners
- Your server's randomly generated UUID
- The amount of players on your server
- The online mode of your server
- The bukkit version of your server
- The java version of your system (e.g. Java 8)
- The name of your OS (e.g. Windows)
- The version of your OS
- The architecture of your OS (e.g. amd64)
- The system cores of your OS (e.g. 8)
- bStats-supported plugins
- Plugin version of bStats-supported plugins
SilkSpawners now no longer resets the config file as of 1.0 - can you retest with the latest version? Previously you may have had to stop the server, edit the config, and restart, but this should now be fixed.
EDIT: It turns out this was a problem happening in other plugins too. I'll look into maybe reporting this as an R4 bug.
Silkspawners is not allowing me to change the config file, no matter which parameter I change. Every time I reload the plugin or the server, the config file is reset back to the default. This means I can't get permissions working with this plugin because I can't set usePermissions: true.
I'm using CB 1.1-R4 and PermissionsEx 1.18.
The missing Material.MONSTER_EGG was a bug in the Bukkit port of ModLoaderMP – I worked around it in SilkSpawners 0.5 by hardcoding the item ID, but it wasn't feasible to apply this workaround to the crafting recipe.
But the good news is I reported this bug to Maeyanie and she fixed it in ModLoaderMP 1.1 r3 (change log "Updated Material to 1.1-R4, fixes monster eggs."), so spawners should now be craftable in SIlkSpawners with CraftBukkit 1.1-R4 + ModLoaderMP 1.1 r3. Let me know if it doesn't work for you in this configuration and I'll see what I can do (its fine in my testing, also note it should work fine in unmodded CraftBukkit of course.)
Can you create a ticket with your detailed configuration information, including versions of SilkSpawners, CraftBukkit, and the contents of config.yml and any permission settings? I'm testing breaking a spawner on 1.1-R4 with 0.5, with a tool without Silk Touch, and am getting spawn eggs as expected. If you're using permissions make sure usePermissions is set appropriately.
Are you using the latest version (0.5)? There was a critical fix in 0.4.1 to make SilkSpawners ignore block break/place/interact events cancelled by other plugins.
Its now fixed.
I was running R3 modded with IC2 etc xD
I suppose I should include that in my bug reports.
For some reason Im not being notified when someone replies to me.
Is that normal?
For some reason I cant craft a monster spawner with Egg surrounded by Iron Bars.
craftableSpawners: true - right?
bad glitch you might want to know about...... you can lock a sign on top of the mob spawner with LWC and then break the spawner over and over and basically get as many as you want
Can't seem to get the spawner to drop an egg, everything else seems to function as should except that, any ideas?
The missing Material.MONSTER_EGG error should be fixed in SilkSpawners 0.5.
This error does not occur on a vanilla craftbukkit-1.1-R3.jar (as far as I know), but I have seen it on a modded CraftBukkit (with ModloaderMP, MCForge, IndustrialCraft and others) so 0.5 now will use a hardcoded item ID for spawn eggs as a workaround. Please let me know if 0.5 fixes the problem for you or if you're still seeing errors - thanks.
edit: reported bug: [ModLoaderMP 1.1 CB1.1R4] Missing Material.MONSTER_EGG, causes NoSuchFieldError
I wasn't checking for cancelled events. Please let me know if this fixes the problem: http://dl.dropbox.com/u/57628348/SilkSpawners-0.4.1/SilkSpawners.jar - if so I'll post an update.
The plugin doesn't respect WorldGuard regions, and Players can dupe the spawners. Will this be fixed in an update?
The error suggests you are running an older version of CraftBukkit, do you have 1.1-R3?
No problem, I understand your frustration, its one of my first plugins and I haven't gotten the conventions nailed down yet, so I appreciate your comments :)
@mushroomhostage Thanks sorry if i came off a bit bossy or rude it was not my intention at all I just wanted to Explain my reason for asking for the changes to be made.
Apart from the error below me here it all looks good :D
Good points all around, thanks for the feedback. I just submitted SilkSpawners 0.4, which should fix most of these problems.
I changed the permissions to "false" in the latest version. My intention in setting them "true" was to allow easy installation, no configuration required (I'm one of the lazy ones that doesn't prefer using a permission plugin :)), but I see what you're saying about unintentional granting of permissions. To achieve both of our goals, I added a usePermissions option – if false (default), it will use true or op as before, but you can change it to true to consult plugins.yml, where all the permissions now default to "false".
Restricting crafting of spawners is unfortunately more complicated. As far as I can tell it is not yet possible with the Bukkit API (at least according to this thread). I wasn't thinking it'd be much of a problem since you need the spawn eggs to craft the spawners, although in creative mode you can acquire the eggs without the spawners.. For now you can set craftableSpawners to false to disable it globally, and I changed the default to false to prevent unintentional crafting on new installs. If it becomes possible in the future to control crafting using permission nodes, I'd definitely like to add it.
You are of course right about the filename conventions, wasn't sure if it would conflict, but I have changed the next upload to be named SilkSpawners.jar, without a version suffix, and all my future uploads will follow this convention (makes it easier for me, too).
Hopefully 0.4 will work out better for you, please let me know how it goes or if there are any other problems I should address in the next release.
I have just spent the last hour trying to work out why my default users have permissions to pickup spawners and craft them and what not when I DID NOT give them permissions to do that.
I found out why you are using plugin.yml incorrectly You are forcing Normal players TO have permissions Regardless if the server owner gives them out or not thus overriding the server owner NOT GOOD AT ALL!!.
You need to make the Default: true Lines in the plugin.yml Say Default: False When they are true it Bypasses all permission management plugins and gives normal players permissions with out A the server owner Knowing and B Very hard for the server owner to remove with out opening the Jar file and looking at the plugin.yml to see what is set to true. Most plugins as a general rule DO NOT force Permissions onto Players like this instead they leave it up to the server owners to handle the giving out of permissions And that is what It should be. as only the server owner knows what is right for his or her server. So in the next release could you Please stop giving permissions to Players by default and let the server owners decide what each player gets with their permissions plugin of choice.
You may say but what about people with out a permissions plugin well then its their loss for being so lazy as to not have one.
For Now i will be editing the plugin.yml of my copy putting it back in the jar and uploading it to the server once more.
Please Conform to plugin standards and remove the lines in the next update. the plugin will be better for it and your support work will be reduced.
One Last thing Can you please Stop Changing the Jar file name Bukkit dose rarely change theirs and no plugin i know of changes theirs every release has the same name this is to make updating the plugin easy for the server owner as you can just drag and drop and replace with the name changed it dose not replace thus making it harder.. Please just drop the version number from the name of the jar.
Plugin released! The "enchanted spawners" technique works great on 1.1 to store the creature metadata.
Since a build around the official 1.0 release, Spawners don't store meta data, so any conventional method for spawners to retain their type isn't possible.
The Developer of Creaturebox came up with a way to "enchant" spawners to retain their type, but I haven't seen it work.
Good luck :/
I am really looking forward to this plugin. This is just what I was looking for 8-)
This looks perfect for my needs none of the others did every thing i wanted and this dose it all + more :D
Will be a must have for me. once released