VIP

VIP Login List!

Info

Please post a ticket, if you encounter any issue!

Overview:

If the server is full and a VIP tries to log in, the last non-VIP player to log on gets kicked, letting the VIP log in.

Features:

/vip add Player <priority> = adds Player to the VIP list with the optional priority
/vip remove Player = removes Player from the VIP list
/vip enable = enables the plugin
/vip disable = diables the plugin
/vip kick = toggles whether to kick last logged player or longest logged player
/vip permissions = toggles whether to use config.yml or permissions (VIP.VIP) to determine whether or not a player is a VIP
Supports Permissions!
Supports MySQL
To install, simply copy the VIP.jar to your plugin directory and start CraftBukkit normally. The config.yml file will be created automatically.

Configuration

Warning: If you use ingame-commands, all comments in your configuration will be deleted! This is not under my control, as bukkit is doing this...

Priority means, if someone is priority 1 and someone other is priority 2 than 2 can kick 1 but 1 cannot kick 2! Do not give Not-VIP's any priority, they will then count as 0! This plugin uses 4 different ways of getting the "priority" of a player:

You use MySQL and Permissions:
You use MySQL without Permissions
You use Permissions without MySQL
You don't use MySQL or Permissions

Way 1:

Add new lines to the Table 'VIPPermissions' in your MySQL-Database:

ID: <leave blank>
permissionsnode: add the node you want to give your players here (VIP.<node>)
priority: the priority a player with this node has

Way 2:

Add new lines to the Table 'VIPUsers' in your MySQL-Database:

ID: <leave blank>
playername: add the name of the player here
priority: the priority the player has

Way 3:

Give your users the Nodes:

VIP.1
VIP.2
VIP.3
VIP.4
VIP.5
VIP.6
VIP.7
VIP.8
VIP.9
VIP.10

Way 4:

Add your users to the config.yml or type /vip add [player] <priority>

Permissions:

VIP.add = allows player to add a player to the VIP list
VIP.remove = allows player to remove a player from the VIP list
VIP.enable = allows player to enable the plugin
VIP.disable = allows player to disable the plugin
VIP.kickToggle = allows player to toggle whether most recently logged or longest logged player gets kicked when a VIP signs in
VIP.VIP = player is a VIP (if set to [COLOR=rgb(51, 102, 255)]true[/COLOR] in config.yml)
VIP.1 - VIP.10 = Default priority if not using MySQL

Plugin Metrics

Also, beginning with version 3.0.0 there will be PluginMetrics included. The data collected by Metrics can be viewed at http://mcstats.org/ and you can always opt-out by changing enable-metrics to false in config.yml!

What is exactly read/sent by Metrics? (Copy from the metrics website)

It is not possible for Metrics to control the plugin in any way except for plugin-specific code the plugin author implements. Nothing is downloaded, so what you get is what the plugin author implemented.

The following data is read from the server in some way or another:

File Contents of plugins/Plugin Metrics/config.yml (created if not existent)
Players currently online (not max player count)
Server version string (the same version string you see in /version)
Plugin version of the metrics-supported plugin
Mineshafter status - it does not properly propagate Metrics requests however it is a very simple check and does not read the filesystem

The following data is sent to http://mcstats.org:

Metrics revision of the implementing class
Server's GUID
Players currently online (not max player count)
Server version string (the same version string you see in /version)
Plugin version of the metrics-supported plugin
Any custom data the supporting plugin implements. This is variable and I am not responsible for this however usually it is just plugin-specific data (e.g for LWC, the database type: MySQL or SQLite, and Locale used (english, german)).

Update checking:

This plugin will automatically check for updates and keep your version up to date. You can disable this in the config by setting auto-update to false.