SimpleReserve
SimpleReserve
Simple, easy-to-use Reserve slot plugin
Tired of not being able to offer VIPs reserved slots or being unable to join your own full server? SimpleReserve provides an easy way to add that functionality with bukkit permission support.
Features
- Simple to use reserve slots plugin with bukkit permission support
- Provides functionality for 2 reserve slot methods:
- Full method: Users with 'simplereserve.enter.full' may enter past the imposed player limit
- Kick method: Users with 'simplereserve.enter.kick' may enter a server when full by kicking the first player found that is able to be kicked. Users with the 'simplereserve.kick.prevent' permission are immune to being kicked(Utilize inheritance!)
Config Overview
The config file for SimpleReserve is very simple and will be auto-generated on first run. The file should contain:
reserve: type: both full: cap: 5 reverttokick: false kick-message: Kicked to make room for reserved user! full-message: The server is full! reserve-full-message: All reserve slots full!
Types:
- full - A type of full limits the reserve plugin to allowing people with the proper Permissions to join even when the server is full.
- kick - Conversely, a type of kick will only allow people with the proper Permissions to join a full server by kicking the first player it comes across that does not have Permission to prevent being kicked.
- both - A type of both can use either the full server or kick method, but the full method takes precedence if a user has that Permission.
- none - "none" type effectively eliminated the reserve slot functionality, allowing you to disable it without removing the plugin.
- if you put something else as the type, the plugin will automatically regenerate it back to "both". Please note this.
You may also customize the messages sent by the plugin for different situations using the 'kick-message' and 'full-message' config nodes.
Permissions Overview
Permissions for SimpleReserve are...well...simple. There are only 3 Permissions to worry about.
'simplereserve.enter.full' - Permission required to give "full" joining capabilities. Allows joining above limit. 'simplereserve.enter.kick' - Permission required to allow joining full server by "kick" method--kicks first player it can. 'simplereserve.kick.prevent' - Prevents player from being able to be kicked by someone joining using the "kick" method
Examples
- Lets say you have 4 usergroups. Guests(default), Users, Moderators, and Admins. You want to give Admins and Moderators joining full server via "kick" method, but you only want to be able to kick at the expense of guests.
Permissions:
Note that Users only have the prevent permission. Any groups that inherit from Users will also have the same permission. Now to ensure we're using the right type of reserve slot, the config.yml would look like:
groups: Guests: default: true info: prefix: '' suffix: '' build: false inheritance: permissions: Users: default: false info: prefix: '' suffix: '' build: true inheritance: Guests permissions: - 'simplereserve.kick.prevent' Moderators: default: false info: prefix: '' suffix: '' build: true inheritance: Users permissions: - 'simplereserve.enter.kick' Admins: default: false info: prefix: '' suffix: '' build: true inheritance: permissions: - '*'
reserve: types: full,kick,both,none type: kick
- Same situation but we want to be able to join over capacity instead of kicking. We only need to change Mod's 'simplereserve.enter.kick' permission to 'simplereserve.enter.full' and change "type: kick" to "type: full" in config.
- We can also use * to allow either method(DEPENDS ON PERMISSIONS PLUGIN), and just change the type to and from kick and full as desired. will allow whichever type is configured.
'simplereserve.enter.*'
- We could also allow mods to join using the kick method and admins to join using full. In config we'd set type to both, and give mods 'simplereserve.enter.kick' Permission only. In this case, Admins have both kick and full Permission, which will default to using full when both are available, and mods can join using the Permission they have.
As you can see, almost any desirable Situation is achievable.
Screenshots
Users attempting to join full server with no Permission to enter: User being kicked to make room for a reserved member: No kick-able players for "kick" join method:
Console output for full type joining:
20:17:46 [INFO] [SimpleReserve] Allowed player tj007razor to join full server!
Project & Source
See our project page for activity and source.
@Cal_Of_Duty
From what I can tell is GroupManager does not register player's permissions in time for SimpleReserve, something which should be happening based on bukkitperms.
It is tested with Privileges and bPerms, which are properly using the permissions API.
@taylorjb
I use GroupManager. Here is my Member section of the groups.yml (copied onto all worlds): http://pastie.org/7836516
And I get no errors from it (GroupManager) on startup. Here is my SimpleReserve config.yml: http://pastie.org/7837512
And finally, here is my startup: http://pastie.org/7841032
@Cal_Of_Duty
Something is probably wrong with either your permissions plugin or your configuration, the plugin works perfectly fine in the latest 1.5.2 beta build. I tested both full and kick functionality.
Mind posting your permissions config and your SimpleReserve config, and possibly a server log? Also, what permissions plugin are you using?
Not working for me on 1.5.2, I gave my members the permission node s'simplereserve.enter.kick' and 'simplereserve.kick.prevent' so they'd kick a default member upon joining if the server is full - not working for me :/
@Marium0505
It should.
EDIT: Yes, it works on 1.5.2.
Does the plugin work on 1.5.2?
@Plyskeen
That is the maximum number of players over the standard cap to allow on the server when allowing "reserved" members to join a full server.
Hi,
What is the utility of the "cap:" line ?
@saxons12
I would have to play with AuthMe and adjust the priority of the even listener, but lowering it could cause other conflicts.
@RSGTechno
Could you define "not working"?
Not working with 1.5.1
Will this work with AuthMe? I used VIPLoginPriority before and it caused 2 players having the same nick, because it had higher priority over AuthMe and it allowed logins before AuthMe could check if the player with the same nick was already online. This is a very important issue. Please reply, asap.
Thanks!
@jayteescout
If you have not moved on to a new plugin yet, are you still having this issue?
I'm trying to give a donor on my server perms to log on when the server is full, but he is unable to, I've tried everything. I can do it and even though I tried giving him the same perms, he cant. I am using permissionsBukkit, I'll include the config file for both permissionsB and simplereserve so you guys can see if there's any problems with either of those. Btw I tried /reload and restarting the server.
PermissionsB: users: jayteescout: permissions: simpleprefix.command.*: true groups: - admin psychoactive: permissions: simplereserve.enter.full: true groups: - VIP groups: default: permissions: permissions.build: true admin: permissions: permissions.*: true inheritance: - user VIP: permissions: permissions.build: true simplereserve.enter.full: true inheritance: - default messages: build: '&cYou do not have permission to build here.' debug: false
SimpleReserve: reserve: type: both full: reserve: full: cap: 0 reverttokick: false cap: 5 kick-message: Kicked to make room for reserved user! full-message: Full? Get a VIP slot, $5/month! http://bit.ly/VnW2lC
Is this a Bukkit plugin, or a forge mod? I need a mod that works with forge that I can use on a Feed The Beast Direwolf20 server .
did you ever find one? i'm looking for the same thing on 1.10.2
If the plugin does still work as Minecraft and Bukkit update, could you please change the lastest release name to reflect that? As in "R: SimpleReserve v0.5.0 for CB 1.3.2-R0.1 Sep 15, 2012" would become "R: SimpleReserve v0.5.0 for CB 1.4.6-R0.2 Dec XX, 2012". It would probably help keep people from thinking that this great plugin could be outdated and broken.
Any updates :)?
does this plugin work with 1.4.6? i just installed it. set the cap to 5 when i had 14 players on. reloaded it and make one of my builders leave and try to log back in and he could.
nvm i think it works with the 1.4.6 R0.1 Beta build. at least it looks like it loaded correctly. I'll test it later. :)
@taylorjb
sorry the error i was having was unrelated, thanks for the reply though