[ADMN] Spawn List 0.10 - The Original Powerful Item Spawning Plugin [1060]

SpawnList: Take Back Item Spawning!​

Version RC1.0 -"Where the hell have you been, SuperPerms?" edition.​

Donate | Jar + Zip | Jar Only | My Twitter | My Blog​

Visit our new home on dev.bukkit.org!​

ChangeList:

Code:

Vrc1.0: Updated for 1.7.3! SuperPerms! New Group System! I should update more!
V0.9.2: Fixed a second stupid.
V0.9.1: Fixed a stupid.
Vo.9: Fixed a few bugs. Changed how inheritance works. By the way, it works.
Vo.8: 1.5 update. I know I've fixed that bug now!
V0.7.3: Removed horrible inheritance. Added 1.4 items
V0.7.2: Less annoying puke, possible allowed fix.
V0.7.1: MOAR FIXES!!!1!!1!111!2!!!one!!
V0.7: Added /give. Hopefully fixed a bug.
V0.6: Changed Packages. Actually fixed things :3
V0.5: Thought I fixed a bunch of things.
V0.4: new onCommand format. slreload works from console. New enable/disable message.
V0.3: Added /slreload command. Added a toggle for the warning message. Cleaned up some language.
V0.2: Fixed spawning by number, added function to designate number of items spawned by default, changed default to 1.
V0.1: Release

Ladies and gentlemen, it is the return of item spawning as it once was! Take back control of your user's item spawning habits with SpawnList, the Bukkit ready version of GroupSpawnlist, readapted and ready to go! I created this plugin because as far as I could see there was no way to properly regulate item spawning in terms of what items your users could spawn. This plugin builds upon the item whitelist of hMod by adding these features:

• Additive or Deductive spawning! (Give a list of items you either want users to spawn or NOT want users to spawn)
• Permissions support! (Designate different spawn lists for each group!)
• It's own /item command!
• Reload without restart, now from console and in-game!
• Inheritance!

I hope that this will become your most used plugin. A few reminders in order to make this the best possible:

• You will need to disable any other /item commands that may exist in plugins like Essentials. Failure to do so might cause your users to get double the items they want.
• You will need to configure your config.yml file according to a few rules, which I will outline.
• Inheritance works as thusly: Parent group overrules children, but once it's true, it's done. Allow me to explain. If group A inherits groups B and C, then group A's policies will overrule groups B and C. However, if group B or C can spawn an item, then it is assumed that group A can spawn it as well. Keep this in mind.
• There is a new system for groups with the new superperms. If you use super perms, listen up! You need to define in your config.yml file the world, then the user, then the group. Groups can also have children. See the new config file style below, and respond with any questions.

Now, for the DL link, but first, if you like the plugin, Donate! Donators get access to my dropbox folder which contains everything I work on, including a few plugins that have never been released! Any amount is fine. Here are the links: Donate, Jar + Zip, Jar Only (Experimental)!


To configure:

• If you are using the Permissions plugin, here are the permissions used by Spawnlist:
  • spawnlist.item - Access the /item command
  • spawnlist.canspawnanything - If the user can spawn anything they want
  • spawnlist.spawnlisted - If you want the /item command to check the spawnlist for this user dead as of RC1.0 (why did I have this to begin with?)
  • spawnlist.reload - For users to have access to the /slreload command
  • spawnlist.give - Access to the /give command
• In the config.yml file, the format is this:

Code:

default-stack-size: 34 #change the default spawning amount

show-warning: 1 #show warnings, 1 = yes, 0 = no
superperms: false #change to true if you want to use superperms!
default: #leave this no matter what
allowed: #can be allowed or disallowed (NOT BOTH)
  - 1 #list numbers here
  - 2
  - 3
  - 4
 children:
   #children go here (try it out for me! only needed for superperms!)
#other groups here (LOWERCASE)

Remember, please post in this thread if the plugin works/doesn't work/makes you happy/sad/upset/laugh. I less then three feedback

Lego6245 of enigmasm.com

 

I am stuck at version 0.7.1 Whenever I got above that it tells them "You cannot spawn that"

 

Lego,

As you know, I am a new server manager and have recently climbed the learning curve associated with the initial configuration of a SMP server. You may not know, however, that I would like to use your plugin.

What issues can I expect, if any, regarding conflicts with the plugins I am currently using; Essentials, WorldEdit, WorldGuard and CraftBook (Soon to be replaced with Minecart Mania)?

Thanks in advance,

Mattb4rd aka BUG

 

@Mattb4rd First of all, no one is sure if a plugin conflicts with another. If it did then it would be posted on the thread. Secondly, I don't think that the plugins you have will do anything to Spawn List, as it only limits what you can or cannot spawn in terms of an item. There's a reason why we have bug reports in threads. It's best to test it out and see if you get an error. If you do, post here and you will gladly get some assistance.

 

Actually LEGO recommended disabling the item spawning capability of Essentials in his OP. I just missed it on the first read.

 

Sry if this has already been addressed but I checked the first 3 pages and the last one (7) and I got tired of looking.

Anyways, I am usuing Servercraft which does not allow FTP, the creation of arbitrary files, or folder creation. Thus, I am unable to upload your config.yml file inot the Spawnlist folder (under plugins). I am only able to upload your .jar file. Could you please make your JAR file create the folder with the .yml file already there when you upload the file. I know this can be done because all other plugins do this.

Thanks in advance,
Sam

 

Any word on support for 1.5? Powered rails and what not.

 

Don't use a plus sign in the version tag. If you really need to use more versions, use [X-Y] or [X,Y].

 

With 733 released, will we see an update some time soon? Thanks in advance.

 

This might be noob question. But how do I disable the /item command from essentials? Do I just do it in permissions? Is that enough?

 

I get this error (not only with Spawnlist, but with some other plugins, too - whilst other plugins like Essentials work properly)

Code:

[SEVERE] Could not load 'plugins/Spawnlist.jar' in folder 'plugins':
java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:36)
at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:24)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:134)
at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:160)
at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:108)
at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:85)
at org.bukkit.craftbukkit.CraftServer.reload(CraftServer.java:287)
at com.earth2me.essentials.commands.Commandreloadall.run(Commandreloadall.java:34)
at com.earth2me.essentials.commands.EssentialsCommand.run(EssentialsCommand.java:56)
at com.earth2me.essentials.Essentials.onCommand(Essentials.java:567)
at org.bukkit.command.PluginCommand.execute(PluginCommand.java:35)
at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:85)
at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:247)
at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:394)
at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:379)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:285)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:394)

Running on Linux Debian x64, CraftBukkit Build #733
Java Information:

Code:

java version "1.5.0_22"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_22-b03, mixed mode)

I appreciate all kind of help or solution

greetz

//edit same error with 0.8

 

1.5 update coming soon for everyone. Sorry for the delay. It's AP Season <3

 

In your main essentials config.yml, there is a "disabled commands" section. Just add the command "- item" to that list and the conflicts disappear. I have it working like that.

 

Updated to Version V0.8!

Changes:
FIXED THE BLOODY DISABLED SPAWNING BUG OMG (Editor's Note: Lego forgot that Java is very picky about nulls, and implemented a much safer, more accurate check)
Added 1.5 items.
Procrastinating Studying.

 

Great! Thanks for the quick reply. I will try that!!

 

can someone show me a config & permissions that work. i don't know what i am doing wrong, and maybe i just don't understand how this works.

This is what i have and "builders" can not spawn anything but '4'

My spawnlist config

Code:

default-stack-size: 1
show-warning: 1
default:
 allowed:
  - 4
builders:
 allowed:
  - 1
  - 3
  - 5
  - 12
  - 13
  - 14

my permissions groups

Code:

groups:
    Default:
        default: true
        info:
            prefix: ''
            suffix: ''
            build: false
        inheritance:
        permissions:
            - 'spawnlist.item'
            - 'spawnlist.spawnlisted'
    builders:
        default: false
        info:
            prefix: 'Builder'
            suffix: 'br'
            build: true
        inheritance:
            - Default
        permissions:
            - 'spawnlist.item'
            - 'spawnlist.spawnlisted'

 

@Jabbic Update your plugin to v0.8

 

@lego6245

I think that is the version i have. I just downloaded it today about 2 hours ago. is there a way to check what version i am running?

 

@Jabbic Whenever you start it up, it should print out what the version number is. Most current is V0.8. I'd re download and check.

 

@lego6245
i am running v 8

 

This seems like a great plugin but I'm rather confused. How to I block certain items to be spawned?

 

@jmcneely Use disallowed: instead of allowed:

Will update to V0.8.1 to fix a problem people have been having.

Forget Vo.8.1, I'm skipping to 9!

Changes:
Fixed puke.
Fixed inheritance.
Fixed allowed vs disallowed.
Oh the joys of cooking.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

@ lego6245 Still confused. I disallowed 51 yet in my testing I could still spawn 51. Here is my config file, please help.

Code:

default-stack-size: 64
show-warning: 1
default:
 disallowed:
  - 51

I'm just not to clear on how the config file should be set up to disallow an item/block.

 

Are you an admin or op, @jmcneely ?

 

Yes but I don't want even admin to be able to spawn some item. Some of my admins like to pull pranks by spamming with water and other things, which I don't like but I hate being the bad guy. So I just want to prohibit everyone, but me, to spawn 8, 9, 10, 11, and 51.

 

Well, the plugin allows people who are OPs to spawn whatever they want. So, perhaps you can make sure that they are not OPs in the server but Admins in permissions?

 

@lego6245 That might work, I didn't think about that. I'll try that today, thanks.

EDIT: It doesn't seem to be working. I am not on the op list, I am in group "Admin" this group has both spawnlist.item and spawnlist.give permission nodes, and my spawn list config file is set up like so:

Code:

default-stack-size: 64
show-warning: 0
default:
 allowed:
  - 1
  - 2
  - 3
  - 4
admin:
 disallowed:
  - 8
  - 9
  - 10
  - 11
  - 51

 

They also need the 'spawnlist.spawnlisted' permission @jmcneely

Also, make sure your running V0.9 because that might help.

 

Having some trouble getting the list to work, seems like the same thing as jmcneely. Defaults on my server have the 'spawnlist.item' and 'spawnlist.spawnlisted' permissions. But regardless of what I put on the allowed or disallowed lists they can spawn whatever they want. They are not OP and I am running V0.9.

 

HAHAHAHAHHAH OH WOW I MADE A STUPID

V0.9.1 released
Added a BANG to fix a problem.

@Sabata this might fix your problem. Also, make sure the default in both config files has the same spelling + capitalization.

 

Downloaded V0.9.1 and I still can't seem get disallow to work. I set up the third permission node and even started testing on a empty server with the only one other plugin being permissions. Yet same results, I don't know what I'm doing wrong.