VIP
VIP 登录列表!
信息
如果您遇到任何问题,请提交工单!
概述:
如果服务器已满且 VIP 尝试登录,最后登录的非 VIP 玩家将被踢出,以便让 VIP 登录。
功能:
- /vip add Player <priority> = 将玩家添加到 VIP 列表中,可选优先级
- /vip remove Player = 从 VIP 列表中移除玩家
- /vip enable = 启用插件
- /vip disable = 禁用插件
- /vip kick = 切换是踢出最后登录的玩家还是在线时间最长的玩家
- /vip permissions = 切换是使用 config.yml 还是权限 (VIP.VIP) 来判断玩家是否为 VIP
- 支持权限系统!
- 支持 MySQL
- 安装方法:只需将 VIP.jar 复制到插件目录并正常启动 CraftBukkit。config.yml 文件会自动创建。
配置
警告:如果您使用游戏内命令,配置文件中的所有注释都将被删除!这不受我的控制,因为这是 Bukkit 的行为……
优先级的含义是:如果某人优先级为 1,而另一人为优先级 2,那么优先级 2 的人可以踢掉优先级 1 的人,但优先级 1 的人不能踢掉优先级 2 的人!
不要给非 VIP 玩家任何优先级,他们将被视为 0!
此插件使用 4 种不同的方式来获取玩家的“优先级”:
- 您同时使用 MySQL 和权限系统:
- 您仅使用 MySQL,不使用权限系统
- 您仅使用权限系统,不使用 MySQL
- 您既不使用 MySQL 也不使用权限系统
方式 1:
在 MySQL 数据库的 'VIPPermissions' 表中添加新行:
ID: <留空>
permissionsnode: 在此处添加您希望赋予玩家的节点 (VIP.<节点>)
priority: 拥有该节点的玩家的优先级
方式 2:
在 MySQL 数据库的 'VIPUsers' 表中添加新行:
ID: <留空>
playername: 在此处添加玩家名称
priority: 玩家的优先级
方式 3:
为您的用户分配以下节点:
VIP.1
VIP.2
VIP.3
VIP.4
VIP.5
VIP.6
VIP.7
VIP.8
VIP.9
VIP.10
方式 4:
将您的用户添加到 config.yml 中,或输入 /vip add [玩家] <优先级>
权限:
- VIP.add = 允许玩家将其他玩家添加到 VIP 列表
- VIP.remove = 允许玩家将其他玩家从 VIP 列表中移除
- VIP.enable = 允许玩家启用插件
- VIP.disable = 允许玩家禁用插件
- VIP.kickToggle = 允许玩家在 VIP 登录时切换是踢出最近登录的玩家还是在线时间最长的玩家
- VIP.VIP = 玩家是 VIP(如果在 config.yml 中设置为 [COLOR=rgb(51, 102, 255)]true[/COLOR])
- VIP.1 - VIP.10 = 未使用 MySQL 时的默认优先级
插件指标 (Plugin Metrics)
此外,从版本 3.0.0 开始,将包含 PluginMetrics。通过 Metrics 收集的数据可以在 查看,并且您始终可以通过在 config.yml 中将 enable-metrics 更改为 false 来选择不加入!

Metrics 具体读取/发送了什么?(摘自 Metrics 网站)
Metrics 无法以任何方式控制插件,除非插件作者实现了特定的插件代码。
不会下载任何内容,因此您获得的就是插件作者实现的内容。
以下数据以某种方式从服务器读取:
- plugins/Plugin Metrics/config.yml 的文件内容(如果不存在则创建)
- 当前在线玩家数量(不是最大玩家容量)
- 服务器版本字符串(与您在 /version 中看到的一样)
- 受 metrics 支持的插件的版本
- Mineshafter 状态 - 它不能正确传播 Metrics 请求,但这只是一个非常简单的检查,不会读取文件系统
以下数据被发送到 :
- 实现类的 Metrics 修订版
- 服务器的 GUID
- 当前在线玩家数量(不是最大玩家容量)
- 服务器版本字符串(与您在 /version 中看到的一样)
- 受 metrics 支持的插件的版本
- 支持插件实现的任何自定义数据。这是可变的,我不对此负责,但通常只是特定于插件的数据(例如对于 LWC,数据库类型:MySQL 或 SQLite,以及使用的语言环境(英语、德语))。
更新检查:
此插件将自动检查更新并保持您的版本最新。
您可以通过在配置中将 auto-update 设置为 false 来禁用此功能。
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 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 :
- 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.
评论 0
登录后参与评分
还没有评论,来抢沙发吧