Bukkit

In reply to wizardevan:

 There's a bug with newer versions of Spigot. I committed a fix to gitlab but I haven't had time to finish the other things I was doing and release a new version.

In reply to JmanHei:

In reply to somMelon:

 Yes it looks like they broke something in Spigot by removing a necessary function for some reason. I have fixed it in the git repository and it will be in the next release. I've just been a little busy lately to test it further and finish what I wanted to do before the next release but I'll try to push a fix for just this error in the next few days or so whenever I get a chance.

In reply to somMelon:

The error will occur for other things as well whenever it tries to update the data on the spawner.

Hey everyone, just thought I'd post an update about the next version of Spawner.

This will be Spawner 3.0 and will work only on 1.13.x servers. I'm very close to getting it finished now. I admit I did get sidetracked with web development work for clients for a bit there but full speed ahead on this for now and hopefully until it's done.

Currently I'm fixing the config updater and that's almost done. When migrating your config from 1.10, 1.11 or 1.12 to the new format you will have to run a command such as /spawner config update v1_12_R1 and then it should update all necessary files. I don't know if anyone is running an older server version than 1.10 but it might work to migrate anyway if you pass in a different version to the command like /spawner config update 2.8.3 for example.

Right now I'm attempting to make drops migrate properly (which I'm not sure actually worked or not before but nobody reported anything) and then hopefully that will be all done and working right. I'm not actually sure that I can make all drops migrate properly due to the API changes so you might have to go through them. Note that you can now set global drops as well as per-entity drops.

I'm thinking that future config updates won't require running a command. It only will this time because I had to think of some way to know which version to upgrade from. Since people might potentially have multiple folders with multiple config versions it might not be good to try guessing which one to use and do it automatically. Maybe I could just say to move your config.yml and language.yml into the plugins/Spawner folder instead of being in a v1_12_R1 subfolder and whatnot and then it could automatically migrate when the server starts but for now I just added a command to do it. So hopefully it won't cause any issues for the time between your server starting and you running the config update command.

Some entity names have changed again so things had to be rewritten a bunch and I've also had to drop support for multiple versions, which was making things complicated anyway even if it was kinda neat. So since all that was going on anyway I decided to do a bunch of the things on the 3.0 todo list while I was at it. I plan to complete them all by the time the beta is ready but I'll release an alpha soon first.

Tab auto completion works now but it'll be disabled by default because it could be a tiny performance hit, especially if there's a lot of people typing commands on your server.

Using the spawners in the world and running the commands seems to work fine from my limited testing, which I will have to do more of. I'm not sure if some of the config options will work correctly so I'll have to finish testing those after.

I've rewritten the commands and config system. The commands and permissions will be pretty much the same besides some new ones. The config is split into multiple files to make it less confusing and easier to find things when you want to fine-tune them:

• config.yml - Global options.
• entities.yml - for all the entity level options if you want to override the global options such as drops, frequency, luck, cost, etc.
• commands.yml - for command cost and cooldowns.
• language.yml - for customizing the text like always.

All of that will be editable with commands such as /spawner config set tabcomplete true or /spawner config set entities give_cost 100 and so on.

I also have to finish adding some more features listed in the issues but those may come after an alpha release so people can test things out.

Maybe I'll be done in the next few days or so if things go well. Then I'll release an alpha version for testing and people can report bugs if they find them.

Then I'll also have to update the documentation and whatnot so people know how to actually use it. I'm going to put that all on GitLab and have minimal information displayed on the plugin release page here so that it's easier to update it all in one spot.

Well that got a little long, but I thought people might like the info. Hopefully it let's me post it.

Also, check out PaperMC if you haven't already, it seems really awesome! https://papermc.io/

In reply to Genius_Hole:

In reply to Genius_Hole:

In reply to Genius_Hole:

In reply to Genius_Hole:

In reply to Genius_Hole:

spawner.mine.all

spawner.break.all

If you give only those perms to the player it should do what you want. However if you want players to be able to place them again you also have to add spawner.place.all

Or you can just give them spawner.player and they would only have access to do player level things like break and mine and place. They can only run /spawner help, /spawner list, or /spawner which will try to get a message about the spawner type they are looking at in the world which they can also get by clicking the spawner in the world. They can't give spawners to other players or do any of the other things the other permissions are for unless you give them other permissions.