DeityProtect 是什么?
这个插件是 WorldGuard 的一个轻量级基于区块的版本,仅供需要基于区块权限系统的插件使用。由于没有游戏内界面,该插件旨在供开发者为了简便而使用。
最初是为 ImDeity Kingdoms 服务器 开发,用于我们自建的城镇系统,但我们在此发布它以简化部分玩家的生活。
这个插件能让我做什么?
对于服务器管理员:除非你是开发者并使用其 API,或者你安装了使用该 API 的插件,否则此插件对你没有任何作用。否则它将在后台运行。
对于开发者:此插件的设置使得保存区块、设置所有者等所有后台逻辑都通过插件完成。你所要做的只是用一个简单的布尔运算符告知插件谁拥有该区块的权限。其余工作将由插件完成。一旦我有机会记录该项目,我将更新 Github Wiki 以说明如何使用此插件。
功能:
- 简洁性。开发者在设计自己的系统时浪费了大量时间,而实际上一个系统就能搞定一切
- 有两个插件使用该系统?没问题!系统将为你区分两者
- 完全可配置的错误输出位于 DeityProtect/language.yml 配置文件中
工作原理?
有四种主要的 PermissionTypes(权限类型)可以更改:EDIT(放置/破坏方块)、USE(使用任何物品)、ACCESS(踏入区块)和 PVP(战斗)。这些都需要传入一个名称,并要求你自己判断该玩家是否拥有权限。还有一种额外的类型 MOB_SPAWNING(生物生成),但名称尚未适用于此类,未来可能会更具体化。
要求:
命令
- /deityprotect reload - 重新加载配置文件和语言文件(需要 deityprotect.admin 权限)
权限
- deityprotect.admin - 授予 /deityprotect reload 访问权限
- deityprotect.override - 赋予 deityprotect 内所有权限的覆盖权
配置
deityprotect:
worlds:
world: # 与值相关的世界名称
default_edit_perm: true # 是否在未认领的土地上允许编辑权限
default_use_perm: true # 是否在未认领的土地上允许使用权限
default_access_perm: true # 是否在未认领的土地上允许访问权限
default_mob_spawn_perm: true # 是否在未认领的土地上允许生物生成权限
default_pvp_perm: true # 是否在未认领的土地上允许 PvP 权限
使用此插件的插件
额外链接
文档:即将编写

What is DeityProtect?
This plugin is a light-weight chunk-based version of WorldGuard that is solely to be used by plugins who require a chunk based permission system. With no In-game interface this plugin is designed for developers to use for simplicity sake
Original developed for the ImDeity Kingdoms server for our in-house built Town system, however we are releasing it here to simplify some peoples lives
What does this plugin allow me to do?
For Server Admins: This plugin will not do anything for you, unless you are developer and using its API OR if you have a plugin installed that uses its API. Otherwise it will sit in the background.
For Developers: This plugin is setup so that all of the background logic behind saving chunks and having owners etc etc is done through the plugin. All you have to do is let the plugin know who has permission on the chunk with a simple boolean operator. The rest will be done by the plugin. I will update the Github Wiki on how to use this plugin once i get a chance to document the project.
Features:
- The simplicity. Developers waste plenty of time designing their own systems, when in reality one system can do all
- Have 2 plugins using the system? No problem! The system will distinguish between the two for you
- Completely configurable error output located in the DeityProtect/language.yml config file
How does it work?
There are 4 main types of PermissionTypes that can be altered EDIT (block place/break), USE (Any type of using an item), and ACCESS (walking onto a chunk) and PVP (fighting). These all take in a name and require you to be the one to determine if said player has permission or not. There is an additional type for MOB_SPAWNING, however the name does not apply to this class yet, it may get more specific in the future.
Requirements:
- DeityAPI (With a valid MySQL connection)
Commands
- /deityprotect reload - Reloads the config and language files (Requires deityprotect.admin)
Permissions
- deityprotect.admin - Gives access to /deityprotect reload
- deityprotect.override - Gives an override to every permission within deityprotect
Configuration
deityprotect:
worlds:
world: # World name that pertains to the values
default_edit_perm: true # Whether to allow the edit permission on unclaimed land
default_use_perm: true # Whether to allow the use permission on unclaimed land
default_access_perm: true # Whether to allow the access permission on unclaimed land
default_mob_spawn_perm: true # Whether to allow the mob-spawn permission on unclaimed land
default_pvp_perm: true # Whether to allow the pvp permission on unclaimed land
Plugins that use this
Extra Links
Documentation: Will be written soon

评论 0
登录后参与评分
还没有评论,来抢沙发吧