SuperSimpleSpawners
This is a very simple plugin.
- It enables you to use spawn eggs to place spawners of the same type.
- It enables spawners to drop spawn eggs of the same type when broken.
Permissions:
Spawners drop eggs (permission: sss.drop.*)
Eggs place spawners (permission: sss.place.*)
Both (permission: sss.*)
Specific drop (permission: sss.drop.entity_type)
Specific place (permission: sss.place.entity_type)
The names for entity_type must be the LOWERCASE form of how they appear here: http://jd.bukkit.org/apidocs/org/bukkit/entity/EntityType.html
Require Silk Touch enchant: (permission: sss.silk_touch)
WITHOUT THESE PERMISSIONS IT WILL BEHAVE NORMALLY EVEN IF YOU'RE OP OR HAVE '*'
If you don't have a SuperPerms manager click below because you need one unless you know you don't.
http://dev.bukkit.org/server-mods/bpermissions/
Get the latest on jenkins:
http://ci.onarandombox.com/job/SuperSimpleSpawners/
Github: https://github.com/dumptruckman/SuperSimpleSpawners
Any chance of a plugin update for 1.3.1 I love this plugin so much, its amazing!
But in 1.3.1 when you dig up a spawner you get kicked from the server with the message "Internal server error" and when you join back the egg is there.
I just wanted to throw this out there so it doesn't confuse others as well. In the entity list, I don't think you need to include the underscore ("_") for spaces. At least for cave spiders I had to remove it.
I think it's very awkward that I have to set permissions to switch between spawning monsters and placing spawners. Maybe you could make this easier by doing what the "egg in dah box" guy does - when I right-click a redstone torch with an egg, I get a spawner. Otherwise, I get the entity. Then you could safely default your permissions to op without confusing anyone.
That way still no config or slash commands, and also no permissions unless the server owner is delegating.
@bigscary
You do not need a permission plugin for this.. You can open permissions.yml in your server folder and add:
It is simple because there are no commands and no configuration. Just permissions, which typically, with only needing ONE permission, people do not consider difficult. There are always other plugins if you feel you want something more heavy weight.
edit: Sorry forgot to answer regarding specific permissions.. They are so you can only grant SPECIFIC monster types. So say you only want zombie spawners to turn into eggs, you give the player sss.drop.zombie
I don't get it. What's this specific place and specific drop thing? Is there a slash command? If yes, why not at least default the slash command to ops, and tell us what the slash command is?
I was hoping this would be a lot simpler. I wanted to just install the plugin, use spawn eggs to create a few spawners for my server "dungeon", then uninstall the plugin. But now I see I need to select and install a permissions plugin, learn how to use it and configure it, then finally place the spawners, then uninstall both plugins.
It would be a lot easier if you had a quick slash command to toggle between "normal spawn eggs" and "spawn eggs place spawners", and default it to ops. Then a server owner wouldn't have to deal with the permissions plugin unless he wanted to delegate creating spawners to another player.
@BrentonD
Sorry, that's outside the scope of this plugin. Refer to the name: SuperSimpleSpawners
i was wondering if i could make some other items make the spawner drop? Like if i want to make it were tnt can blow it up and the egg will drop. is there a way to do that?
I am sure this is common sense to some people but I will share it for the sanity of the uninformed. If you are having an issue where silk touch seems to be activated with all groups, regardless of the perms you haven't set, just set the perm "-sss.silk_touch". I am new to all of this but it should subtract the necessity of silk touch. I just thought of it and will test it. If I don't edit this post, then it worked.
i like supersimple spawners :)
*do i get my money now*cough*cough*
@nicka1011
Well... The whole point is that I treat the PlayerInteractEvent like a BlockPlaceEvent instead. So, I don't care if the interact event is canceled... I'm only looking to see if the BlockPlaceEvent that this plugin throws is canceled.
@dumptruckman
oh yeah...woops...it seems i have been counting it the wrong way round for a while...i assumed that low was called last because it doesnt need to run as fast :/ ...thanks for telling me...i should probably update my plugins..but in that case you should change the event priority to highest and check for cancellation so that it will work with essentials signs as zeek and me were discussing :) -Nicka101
@nicka1011
Lowest is called first :)
@dumptruckman
no worries man...but to clarify at lowest priority its more likely to be cancelled as it is called last and therefore after everything else likely to cancel the event. -Nicka101
@nicka1011
At LOWEST priority it's almost certain the event is not canceled to begin with. The reason why I removed checking for that is because it's really trying to act like ONLY a block place event. But thanks for the grass stuff, i was wondering how to go about that.
@Toxxicjtag
Newer Versions of the plugin will not allow placing in protected land anymore as that was a bug. also this plugin isnt designed so it can do things that specific. if you want that functionality, add it yourself or pay someone to add it for you :). -Nicka101
@ZeekDaGeek @dumptruckman I updated the playerInteract to allow placement in vines, snow, tallgrass and fire and also pays attention to if the event is cancelled to begin with. http://pastebin.com/Y3jzHbn0
It seems that sss doesnt follow factions, and people can place spawners in territory unclaimed by them/enemyed to them. Makes it so they bring a spawner, place it in there land (now must be left,) but can use it to place on a door, and break it.
Would like to see something of like a factions version.
Other than that, great plugin!
@dumptruckman
Fair Point although really you should pass a new ItemStack to the function rather than the actual stack being changed to spawner which could result in data being lost if a plugin attempts to edit the value of the itemInHand
@ChainSawXL @nicka1011
Yes, ChainSaw, I believe your issue was a known bug in an older version. Please update.
nicka1011: The only reason I switched it to a spawner for the event is because spawn eggs are not a block you can place. I figured that if the item in hand wasn't an actual placeable block, some plugins have the potential to be confused.
@dumptruckman
As A Side Note to What Chainsaw Said, I Figured I Would Go Invesigate. As A Result, I have a few Suggested Changes :). http://pastebin.com/5g0iHZEL http://pastebin.com/KTupgMSk Just a Few Minor Changes Although I Couldnt Find any reason that ChainSawXL Would have issues with it taking the entire stack if he is using an up-to-date version. -Nicka101