
Bssentials GroupManager 是 Essentials 的 GroupManager 的一个分支,已更新以支持 1.10 和 Bssentials
Group Manager 是一种权限实现方案。它允许你为组设置权限,并将用户添加到这些组中。其结果是你可以拥有多个具有指定命令访问权限的层级。这对大多数 Minecraft 服务器非常有用,因为它让你能够创建自定义的阶层系统。如果没有它,你可能难以控制用户对服务器的管理权限范围。
_____________________________
你还需要安装 Bssentials
_____________________________
基本理念
Group Manager 允许你通过创建尽可能多的不同组和子组来有效地管理用户的权限。这种配置可以简单也可以复杂,取决于你的需求。
最传统的系统(如下所示)采用组继承机制,新玩家从顶层开始,而服务器主位于底层。在规模较小的服务器上,你可能会合并管理员(Moderator)和高级管理员(Admin)的权限组,但大多数人对于 Admin 应该拥有哪些权限、以及 Moderator 又该获得哪些权限,往往持有不同意见。
Newbie
Newbie 组包含最基本的权限节点,应在所有新玩家登录时安全地赋予他们。
Player
Player 组涵盖了已建立身份的玩家可以使用的所有命令。这通常包括涉及经济系统、基础传送以及其他基础功能的命令。
Moderator
接下来的两个组可以根据你的偏好进一步合并或拆分。通常情况下,最低级别的 Moderators 拥有踢出用户(kick)和关押用户(jail)的权限,而更高级别的 Moderators 则可以获得封禁 IP(IP ban)、隐身(turn invisible)以及生成创造模式物品(spawn creative mode items)的权限。
Admin
Owner
Owner 组通常拥有所有权限/命令,并且通常是唯一能够使用控制插件、定义组以及关闭/重启服务器的命令的人。
Initial Install
Group Manager 的安装过程相当简单:
安全地停止服务器。
将 GroupManager 插件放入你的 plugins 文件夹中。(EssentialsGroupManager.jar/GroupManager.jar)
启动并再次停止服务器。
设置/修改初始的 config.yml 文件。
重启服务器(要在游戏内应用 GroupManager 配置文件的更新版本,请输入 /manload)。
配置文件
另见:Group Manager/Config
首次下载 GroupManager 时,通常只有 .jar 文件。第一次运行 GroupManager 时,它将生成配置文件,您可以随意编辑这些文件。
标准配置通常与上述详细说明的结构非常相似,但在使用前您至少需要对配置进行一些修改。您至少要添加自己为管理员。
首次生成配置文件时的目录结构大致如下:
plugins/
GroupManager/
config.yml
globalgroups.yml
backups/
worlds/
world/
groups.yml
users.yml
每个配置文件中应包含的内容详情可在配置页面找到。
权限
GroupManager 配置的核心是权限节点。这是 GroupManager 的主要目的,用于精确控制玩家能够或不能执行的操作。每个插件都有其自己的权限节点集,直接对应于该特定插件的命令。
Essentials 在其命令参考中维护了一份完整的权限列表。对于其他插件,您需要查阅其相关文档。
权限节点
所有支持权限插件的插件,都会拥有各自的权限节点。
通用语法:<插件名称>.<命令名称>
示例语法:essentials.tp(允许玩家使用 Essentials 的 /tp 命令进行传送)
Essentials 是插件的名称,而命令为 /tp
父级节点并不总是插件的名称,因此在创建组之前请进行检查。此功能允许插件拥有相同的命令名称,但在指定哪个插件的命令作为默认命令时不会发生冲突。
示例:essentials.god 和 worldguard.god
摘要节点
Group Manager 支持摘要节点,即使用通配符来启用所有已注册的子权限。
您也可以单独授予 '*' 通配符,而不指定特定插件。这将使指定组能够访问所有插件的所有命令。注意:除非通过否定节点进行排除,否则存在冲突的命令会变得不稳定。请自行承担风险。此外,并非所有插件都正确注册了它们的权限。
否定节点
Group Manager 支持否定节点,允许您撤回对某些命令的访问权限。这在继承关系中非常有用。
bssentials.command.heal.other :允许访问 /heal player 命令
-bssentials.command :仅移除 /heal 命令(用于治疗自身)的访问权限
在需要使用大型通配符权限时,这非常有用。例如,为管理员授予所有命令的权限,然后再移除对 GM 命令的访问权限。将摘要节点与否定节点结合使用,可以轻松移除对众多子命令的访问权限。
-bssentials.command.heal:移除对 /heal 命令的访问权限
异常节点
Group Manager 支持异常节点,这些节点将覆盖负向节点,允许你强制恢复对命令的访问权限。这在先轻松移除所有命令的访问权限,再逐个重新添加时非常有用。
示例权限
Group Manager 提供了多种示例权限文件:
Group Manager Groups :: Group Manager GlobalGroups
变量
Group Manager 允许你定义变量以及权限。这些是组内独有的值,通常用于插件根据组别来改变行为。主要有两个常见的例子:“前缀”(prefix)和“后缀”(suffix)变量,以及“建造”(build)开关。
聊天插件
大多数聊天插件会读取前缀和后缀变量,从而允许你根据玩家当前的组别为其赋予自定义名称。
EssentialsChat 会将前缀和后缀附加到用户名上,从而允许你为用户名添加标签或颜色。
如果你希望设置较长的聊天前缀,我建议你查看我们的聊天格式化指南,该指南展示了如何在聊天中创建长前缀,而在玩家名称中显示短前缀。
此处列出了可用的颜色代码列表。
一些示例:
prefix: '[A]' : 生成简单的 <[A]User>
prefix: '&e' : 生成带颜色的 <User>
反破坏
部分插件支持基于组别的“反破坏”保护。与聊天颜色类似,Group Manager 本身不提供此功能,但 EssentialsProtect 等插件提供了该功能。
通常构建状态如下所示:
build: false 禁用方块放置/破坏。
build: true 启用方块放置/破坏。
迁移
通常情况下,从大多数权限插件迁移过来相当简单。请首先尝试以下步骤,如果无效,手动修正组别也相当容易。
将 EssentialsGroupManager.jar 或 GroupManager.jar 移入你的 plugins 目录。
从你的 plugins 目录中移除之前的权限插件 jar 包。
复制之前的组配置文件。
打开 Group Manager 文件夹并导航至世界文件夹(plugins/worlds/<你的世界名称>)。
粘贴两份权限配置文件副本。
将其中一份重命名为 users.yml,另一份重命名为 groups.yml,覆盖任何现有文件。
重启服务器。
Group Manager 命令
Group Manager 插件关联了大量命令。这些命令可用于在游戏中或通过服务器控制台修改用户组并将用户分配到相应组别。
另见:Group Manager/Commands
基本用户命令
当你已经设置了组别,只想将用户分配到组别时,这些命令非常有用。
/manuadd: 将玩家移动到目标组。(如果不存在则添加到文件中)
/<command> <player> <group>
groupmanager.manuadd
/manudel: 移除任何用户特定的配置,使其恢复为默认组。
/<command> <player>
groupmanager.manudel
/manpromote: 允许提升玩家在继承树中的位置。此命令仅允许用户在玩家继承的组之间移动。
/<command> <player> <group>
groupmanager.manpromote
/mandemote: 允许降低玩家在继承树中的位置。此命令仅允许用户在玩家继承的组之间移动。
/<command> <player> <group>
groupmanager.mandemote
/manwhois: 告知用户所属的组。
/<command> <player>
groupmanager.manwhois

Bssentials GroupManager is a fork of Essentials's GroupManager, updated for 1.10 and Bssentials
Group Manager is an implementation of permissions. It allows you to set up permissions for groups, and add users to these groups. The result is you can have multiple tiers which have access to specified commands. This is useful for most Minecraft servers, as it lets you create a custom caste system. Without it, you may struggle to control the extent of server control your users have.
_____________________________
You need to also install Bssentials
_____________________________
The Basic Idea
Group Manager allows you to effectively manage users' permissions by letting you create as many different groups and sub-groups as you could possibly need. This configuration can be as simple or as complicated as you make it.
The most traditional system (shown below) uses group inheritance, starting with new players at the top, and owners on the bottom. On smaller servers you might end up merging the moderator and admin rolls, but most people will have different opinions when it comes to which powers the admin should receive access to, and which powers moderators should receive as well.
Newbie
The newbie group contains the very basic permission nodes, and should be safe to give all newly joined players upon login.
Player
The player group covers all the commands that established players can use. This usually includes commands which involve the economy, basic teleportation, and other basic commands.
Moderator
The next two groups can be merged or split even further based on your preference. Typically the lowest moderator rank has access to kick users, and jail a user, while higher ranks gain access to IP ban players, turn invisible, and spawn creative mode items.
Admin
Owner
The owner group usually has access to all permissions/commands, and is usually the only one with commands that control plugins, define groups, and ability to shut down/restart the server.
Initial Install
The install process for Group Manager is rather simple:
Safely stop the server.
Place the GroupManager plugin into your plugins folder. (EssentialsGroupManager.jar/GroupManager.jar)
Start and stop the server.
Set up/modify the initial config.yml file.
Restart the server (To apply updated versions of GroupManager's configuration file ingame, type /manload).
Config Files
See also: Group Manager/Config
When you first download Group Manager, you will generally only have the .jar files. The very first time you run Group Manager, it will generate the config files which you can then edit at will.
The standard config is usually something which is very similar to the layout detailed above, but you will need to edit the configuration at least a little before use. You will at the very least want to add yourself as admin.
The directory structure when you first generate the config files will look something like this:
plugins/
GroupManager/
config.yml
globalgroups.yml
backups/
worlds/
world/
groups.yml
users.yml
Detail as to what goes in each config file can be found on the config page.
Permissions
At the very core of Group Manager's configuration are the permission nodes. These are the entire point of Group Manager, and control exactly what a player can and can't do. Each plugin has its own set of permission nodes, directly relating to the commands from that specific plugin.
Essentials maintains a complete list of permissions in its Command Reference. For other plugins you will need to check their related documentation.
Permissions Nodes
Every plugin which supports a permissions plugin, will have their own permission nodes.
General Syntax: <plugin name>.<command name>
Example Syntax: essentials.tp (Enables a player to teleport using Essentials' /tp command)
Essentials is the name of the plugin and the command is /tp
The parent node won't always be the name of the plugin, so check before creating your groups. This feature allows plugins to have the same commands, but not conflict with each other when specifying which plugin's command to designate as default.
Example: essentials.god and worldguard.god
Summary Nodes
Group Manager supports summary nodes, that is using a wildcard to enable all registered sub-permissions.
You can also give the '*' wildcard by itself, without specifying a plugin. This causes the specified group to have access to every command from every plugin. Note: Conflicting commands will become unstable unless negated by a negative node. Use at your own risk. Not all plugins properly register their permissions as well.
Negative Nodes
Group Manager supports negative nodes, allowing you to retract access to commands. This can be useful with inheritance.
bssentials.command.heal.outher : Allows access to /heal player
-bssentials.command : Removes access to just /heal (to heal you)
This can be useful when using the large wildcard permissions, such as giving an admin every command, but then removing access to the GM commands. Combining a summary node with a negative node can remove access to numerous sub-commands with ease.
-bssentials.command.heal : Removes access to /heal
Exception Nodes
Group Manager supports exception nodes, these will override negative nodes, allowing you to forcefully regain access to commands. This can be useful for easily removing access to all commands, then adding each one back individually.
Example Permissions
There are a number of example permissions files available for GroupManager:
Group Manager Groups :: Group Manager GlobalGroups
Variables
Group Manager allows you to define variables as well as permissions. These are values which are unique to the group. They are typically used in plugins to alter behaviour, based on groups. There are two major examples of this: the 'prefix' and 'suffix' variable and the 'build' toggle.
Chat Plugins
Most chat plugins will read the prefix and suffix variable to allow you to give players custom names based on their current group.
EssentialsChat will append the prefix and suffix to the person's username, allowing you to either provide a tag or colour to the user's name.
If you want to make longer chat prefixes, I'd recommend checking out our Chat formatting guide, which shows you how to create long prefixes in chat, but short prefixes in player names.
A list of what colour codes can be found here.
Some examples:
prefix: '[A]' : Produces a simple <[A]User>
prefix: '&e' : Produces a colored <User>
AntiGrief
Some plugins support group based 'antigrief' protection. Like with the chat colours, Group Manager doesn't provide this functionality. Plugins such as EssentialsProtect do.
Typically the build status is given as:
build: false disables building/destroying of blocks.
build: true enables building/destroying of blocks.
Migration
Normally converting from most permission plugins is a rather simple affair. Try the following steps first, but if they don't work, it's rather easy to manually correct the groups.
Move EssentialsGroupManager.jar or GroupManager.jar into your plugins directory.
Remove the previous permission plugin jar from your plugins directory.
Copy the previous groups file.
Open the Group Manager folder and navigate to the world folder (plugins/worlds/<your world name>).
Paste two copies of the permissions configuration file.
Rename one to users.yml and one to groups.yml, overwriting any existing files.
Restart the server.
Group Manager Commands
There are a large number of commands associated with the Group Manager plugin. These can be used to modify and assign groups to users ingame, or from the server console.
See also: Group Manager/Commands
Basic User Commands
These commands are useful for when you already have a group set up and you just want to assign users to groups.
/manuadd: Move a player to desired group.(Adds to the file if not exists)
/<command> <player> <group>
groupmanager.manuadd
/manudel: Remove any user specific configuration. Make him default group.
/<command> <player>
groupmanager.manudel
/manpromote: Allows promoting a player up the inheritance tree. This command will only allow the user to move the player between groups they inherit.
/<command> <player> <group>
groupmanager.manpromote
/mandemote: Allows demoting a player down the inheritance tree. This command will only allow the user to move the player between groups they inherit.
/<command> <player> <group>
groupmanager.mandemote
/manwhois: Tell the group that user belongs.
/<command> <player>
groupmanager.manwhois
评论 0
登录后参与评分
还没有评论,来抢沙发吧