GateKeeper
GateKeeper 允许服务器管理员控制玩家何时可以进入下界和末地。可以通过击杀怪物、挖掘方块、掉落物、村民交易、游戏时长、世界年龄、物品栏物品或指定的日期和时间来构建进度规则。
功能特性
- 灵活的条件要求: 使用
ALL(所有条件都必须满足)或 ANY(满足任一条件即可)组合条件。支持嵌套分组以创建如“进行 50 次交易并击杀 500 只敌对怪物或挖掘 2,000 个石头方块”之类的规则。
- 自定义目标和数量: 追踪任何支持的方块、物品或怪物——不仅仅是菜单中显示的示例。在管理员菜单中添加和编辑规则,或使用其自定义命令按钮将命令粘贴到聊天框中,进行调整后执行。
- 实用的玩家和管理员菜单:
/gatekeeper progress 向玩家显示他们的目标、计数器和完成状态。/gatekeeper settings 打开分页的管理员控制面板,用于预设、条件编辑、语言设置、进度模式、公告以及传送门保护。
- 个体或全服进度追踪: 按玩家、全局或两者均需满足的方式追踪符合条件的目标。下界和末地的计数器可以分开或共享,且末地的进度可以保留至下界解锁后再继续计算。
- 特定或分组的怪物: 可统计单一怪物、选定的几种类型、任意怪物,或配置好的组别,如
hostile(敌对)或 peaceful(和平)。
- 防止挖掘不拾取漏洞:
blocks_mined 统计成功的方块破坏次数。items_mined 统计由挖掘产生的掉落物;拾取或丢弃物品不会增加进度。
- 可选的 PlaceholderAPI 支持: 将访问状态和条件进度暴露给记分板、菜单、聊天格式化器以及其他兼容 PlaceholderAPI 的插件。
- 维度保护: 配置下界传送门生成、末地传送门框架、传送门旅行以及通过末影珍珠进入锁定维度的保护机制。
- 英文和俄文消息: 默认语言为英语。可在管理员菜单中切换语言,或自定义消息文件。
快速入门
- 在运行 Java 17 的 Paper 服务器上安装 GateKeeper。PlaceholderAPI 为可选组件。
- 启动服务器并以管理员身份运行
/gatekeeper settings。
- 选择一个预设,或打开某个维度的条件列表并添加你的目标。
- 玩家可以使用
/gatekeeper progress 或 /gatekeeper status 查看自己的进度。
设置存储在 plugins/GateKeeper/config.yml 中。英文和俄文消息分别位于 plugins/GateKeeper/messages.yml 和 plugins/GateKeeper/messages_ru.yml;编辑这些文件后运行 /gatekeeper reload 即可应用更改。
在游戏中添加自定义条件
打开 /gatekeeper settings,选择下界或末地,然后打开 Conditions → Custom command。点击聊天建议将其粘贴到命令行中,修改目标或数量,然后按回车键。例如,要求挖掘 1,000 个泥土方块:
/gatekeeper condition add nether blocks_mined dirt_1000 1000 material=DIRT
要更改现有规则,请打开它并选择自定义命令选项。如果跟踪范围保持不变,编辑规则的目標或数量会保留其已保存的计数器。删除规则不会清除其存储的计数器;菜单中的重置操作需要确认。
命令格式:
/gatekeeper condition add <dimension> <type> <id> <amount> [property=value ...]
/gatekeeper condition set <dimension> <id> <type> <amount> [property=value ...]
示例:
/gatekeeper condition add nether mob_kills zombie_hunt 25 entity=ZOMBIE
/gatekeeper condition add nether mob_kills hostile_hunt 500 mob-group=hostile
/gatekeeper condition add nether mob_kills mixed_hunt 50 entities=ZOMBIE,SKELETON
/gatekeeper condition add nether blocks_mined dirt 1000 material=DIRT
/gatekeeper condition add nether items_mined diamonds 20 material=DIAMOND
/gatekeeper condition add nether villager_trades trades 50 scope=GLOBAL
/gatekeeper condition add nether calendar_date release 1 date=2030-01-01T00:00:00 timezone=Pacific/Honolulu
/gatekeeper condition set nether dirt blocks_mined 2000 material=DIRT
有效的维度为 nether 和 the_end。支持的条件类型包括 mob_kills、blocks_mined、items_mined、inventory_item、villager_trades、played_days、world_days 和 calendar_date。目标可以通过属性设置,如 material=DIRT、entities=ZOMBIE,SKELETON、mob-group=hostile,或配置的方块组 group=stone。parent=<group-id> 可将新规则添加到现有的嵌套组中。
配置示例
在维度的 unlock-conditions 下添加 conditions 列表。该列表将替换该维度的旧版标量要求。
dimensions:
the_end:
unlock-conditions:
logic: ALL
conditions:
- id: zombie-hunt
type: mob_kills
entity: ZOMBIE
amount: 25
- id: skeleton-hunt
type: mob_kills
entity: SKELETON
amount: 10
- id: stone-mining
type: blocks_mined
group: stone
amount: 1000
- id: diamond-drops
type: items_mined
material: DIAMOND
amount: 20
- id: villager-trades
type: villager_trades
amount: 5
- id: playtime
type: played_days
amount: 20
- id: seasonal-release
type: calendar_date
date: "2030-01-01T00:00:00"
timezone: "America/Los_Angeles"
使用 logic: ALL 要求满足每一项,或使用 logic: ANY 允许满足其中任意一项。type: group 条目可以包含其自己的 logic 和 conditions 以形成嵌套规则。
条件类型
mob_kills — 击杀特定实体、任意实体(entity: ANY)、一组实体列表(entities: [ZOMBIE, SKELETON]),或已配置的生物群系组。
blocks_mined — 破坏特定方块、多种方块之一,或已配置的方块组。
items_mined — 通过挖掘方块产出物品掉落;随意拾取散落的物品不计入。
inventory_item — 在背包中包含已配置的物品材料之一。
villager_trades — 与村民或流浪商人完成交易。
played_days — 累计玩家的游戏时间,以 24,000 tick 的 Minecraft 天为单位。
world_days — 等待主正常世界达到指定的 Minecraft 天数年龄。
calendar_date — 等待至本地日期和时间。timezone: AUTO 使用服务器的时区;也可指定如 Asia/Omsk 或 America/Los_Angeles 等 IANA 时区。
进度设置
settings.progress.mode 设置事件计数目标的默认行为:AUTO 遵循 settings.mode,INDIVIDUAL 追踪每位玩家,GLOBAL 在整个服务器共享进度,BOTH 要求个人和全局计数器均达成目标。单个规则可通过 scope: INDIVIDUAL、GLOBAL 或 BOTH 覆盖此默认值。游戏时长、世界年龄、背包检查和日历日期则分别基于各自自然的玩家、世界或服务器上下文。
设置 settings.progress.dimension-scope: SHARED 可在下界和末地之间为匹配的规则 ID 共享计数器;DIMENSION 则保持它们独立。settings.progress.unlock-order: NETHER_THEN_END 会暂存末地的计数器进度,直到解锁下界访问权限;INDEPENDENT 允许两个维度独立推进进度。played_days 基于每位玩家的游戏时长,world_days 基于主正常世界,calendar_date 基于配置的时区。
来自刷怪笼和其他来源的生物击杀按正常方式计入。人工生成过滤已被禁用。
命令
| 命令 |
描述 |
/gatekeeper progress |
打开玩家进度菜单。 |
/gatekeeper status [player] |
查看自己的访问状态,或在拥有权限的情况下查看其他玩家的。 |
/gatekeeper settings |
打开管理员设置菜单。 |
/gatekeeper condition add ... |
添加自定义条件。需要 gatekeeper.admin 权限。 |
/gatekeeper condition set ... |
根据 ID 编辑条件。需要 gatekeeper.admin 权限。 |
/gatekeeper unlock <player> <dimension> |
授予访问权限;将 <dimension> 替换为 nether 或 the_end。 |
/gatekeeper lock <player> <dimension> |
撤销访问权限;将 <dimension> 替换为 nether 或 the_end。 |
/gatekeeper reload |
重新加载配置和消息。 |
别名:/gk、/worldlock 和 /wlock。
权限
| 权限 |
用途 |
默认 |
gatekeeper.use |
使用主命令。 |
所有人 |
gatekeeper.admin |
管理条件和访问权限、重载以及打开设置。 |
操作员 |
gatekeeper.status.others |
查看其他玩家的状态。 |
操作员 |
gatekeeper.bypass.nether |
绕过下界限制。 |
无 |
gatekeeper.bypass.the_end |
绕过末地限制。 |
无 |
gatekeeper.bypass.end |
gatekeeper.bypass.the_end 的别名。 |
无 |
gatekeeper.bypass.* |
绕过所有 GateKeeper 维度限制。 |
无 |
PlaceholderAPI
PlaceholderAPI 是可选的,需单独安装。当检测到其存在时,GateKeeper 会注册占位符,供其他兼容 PlaceholderAPI 的插件使用:
%gatekeeper_mode%
%gatekeeper_unlocked_nether%、%gatekeeper_unlocked_the_end%
%gatekeeper_progress_nether%、%gatekeeper_progress_the_end%
%gatekeeper_required_nether%、%gatekeeper_required_the_end%
%gatekeeper_remaining_nether%、%gatekeeper_remaining_the_end%
%gatekeeper_mob_nether%、%gatekeeper_mob_the_end%
%gatekeeper_rule_nether_<rule-id>_progress%
%gatekeeper_rule_nether_<rule-id>_required%
%gatekeeper_rule_nether_<rule-id>_complete%
请将 <rule-id> 替换为条件的配置 ID。末地规则的占位符使用 the_end 替代 nether。例如,测试占位符可使用 /papi parse me %gatekeeper_rule_nether_zombie-hunt_progress%。
兼容性
GateKeeper 专为 Paper 和 Java 17 构建。PlaceholderAPI 为可选组件,未随插件捆绑。
反馈与项目概览
报告错误或建议功能。
GateKeeper
GateKeeper lets server administrators control when players can enter the Nether and The End. Build progression rules from mob kills, mined blocks and drops, villager trades, playtime, world age, inventory items, or a scheduled date and time.
Features
- Flexible requirements: Combine conditions with
ALL (every condition is required) or ANY (one condition is enough). Nest groups to create rules such as “trade 50 times and either kill 500 hostile mobs or mine 2,000 stone blocks.”
- Custom targets and amounts: Track any supported block, item, or mob—not just the examples in the menu. Add and edit rules in the admin menu or use its Custom command button to paste a command into chat, adjust it, and run it.
- Useful player and admin menus:
/gatekeeper progress shows players their goals, counts, and completion state. /gatekeeper settings opens paginated admin controls for presets, condition editing, language, progress modes, announcements, and portal protection.
- Individual or server-wide progress: Track eligible goals per player, globally, or with both counters required. Nether and End counters can be separate or shared, and End progress can be held until the Nether is unlocked.
- Specific or grouped mobs: Count one mob, several selected types, any mob, or a configurable group such as
hostile or peaceful.
- Mining without pickup exploits:
blocks_mined counts successful block breaks. items_mined counts drops produced by mining; picking up or dropping an item does not add progress.
- Optional PlaceholderAPI support: Expose access state and condition progress to scoreboards, menus, chat formatters, and other PlaceholderAPI-compatible plugins.
- Dimension protections: Configure protection for Nether portal creation, End Portal frames, portal travel, and Ender Pearl travel into locked dimensions.
- English and Russian messages: English is the default. Switch languages in the admin menu or customize the message files.
Quick start
- Install GateKeeper on a Paper server running Java 17. PlaceholderAPI is optional.
- Start the server and run
/gatekeeper settings as an administrator.
- Choose a preset or open a dimension's condition list and add your goals.
- Players can view their progress with
/gatekeeper progress or /gatekeeper status.
Settings are stored in plugins/GateKeeper/config.yml. English and Russian messages are in plugins/GateKeeper/messages.yml and plugins/GateKeeper/messages_ru.yml; edit them and run /gatekeeper reload to apply changes.
Add a custom condition in game
Open /gatekeeper settings, select Nether or The End, then open Conditions → Custom command. Click a chat suggestion to paste it into the command line, edit the target or amount, and press Enter. For example, to require mining 1,000 dirt blocks:
/gatekeeper condition add nether blocks_mined dirt_1000 1000 material=DIRT
To change an existing rule, open it and choose the custom command option. Editing a rule's target or amount keeps its saved counter when its tracking scope stays the same. Deleting a rule does not erase its stored counter; reset actions in the menu require confirmation.
Command format:
/gatekeeper condition add <dimension> <type> <id> <amount> [property=value ...]
/gatekeeper condition set <dimension> <id> <type> <amount> [property=value ...]
Examples:
/gatekeeper condition add nether mob_kills zombie_hunt 25 entity=ZOMBIE
/gatekeeper condition add nether mob_kills hostile_hunt 500 mob-group=hostile
/gatekeeper condition add nether mob_kills mixed_hunt 50 entities=ZOMBIE,SKELETON
/gatekeeper condition add nether blocks_mined dirt 1000 material=DIRT
/gatekeeper condition add nether items_mined diamonds 20 material=DIAMOND
/gatekeeper condition add nether villager_trades trades 50 scope=GLOBAL
/gatekeeper condition add nether calendar_date release 1 date=2030-01-01T00:00:00 timezone=Pacific/Honolulu
/gatekeeper condition set nether dirt blocks_mined 2000 material=DIRT
Valid dimensions are nether and the_end. Supported condition types are mob_kills, blocks_mined, items_mined, inventory_item, villager_trades, played_days, world_days, and calendar_date. Targets may be set with properties such as material=DIRT, entities=ZOMBIE,SKELETON, mob-group=hostile, or a configured block group=stone. parent=<group-id> adds a new rule to an existing nested group.
Configuration example
Add a conditions list under a dimension's unlock-conditions. The list replaces that dimension's legacy scalar requirements.
dimensions:
the_end:
unlock-conditions:
logic: ALL
conditions:
- id: zombie-hunt
type: mob_kills
entity: ZOMBIE
amount: 25
- id: skeleton-hunt
type: mob_kills
entity: SKELETON
amount: 10
- id: stone-mining
type: blocks_mined
group: stone
amount: 1000
- id: diamond-drops
type: items_mined
material: DIAMOND
amount: 20
- id: villager-trades
type: villager_trades
amount: 5
- id: playtime
type: played_days
amount: 20
- id: seasonal-release
type: calendar_date
date: "2030-01-01T00:00:00"
timezone: "America/Los_Angeles"
Use logic: ALL to require every entry or logic: ANY to allow any one entry. A type: group entry can contain its own logic and conditions for nested rules.
Condition types
mob_kills — kill a specific entity, any entity (entity: ANY), a list (entities: [ZOMBIE, SKELETON]), or a configured mob group.
blocks_mined — break a specific block, one of several blocks, or a configured block group.
items_mined — produce item drops by mining blocks; loose item pickups do not count.
inventory_item — have one of the configured item materials in the inventory.
villager_trades — complete trades with villagers or wandering traders.
played_days — accumulate player playtime in 24,000-tick Minecraft days.
world_days — wait for the primary normal world to reach the configured age in Minecraft days.
calendar_date — wait until a local date and time. timezone: AUTO uses the server's timezone; an IANA zone such as Asia/Omsk or America/Los_Angeles can be specified.
Progress settings
settings.progress.mode sets the default for event-counted goals: AUTO follows settings.mode, INDIVIDUAL tracks each player, GLOBAL shares progress across the server, and BOTH requires both personal and global counters to reach the goal. A counted rule can override the default with scope: INDIVIDUAL, GLOBAL, or BOTH. Playtime, world age, inventory checks, and calendar dates use their natural player, world, or server context.
Set settings.progress.dimension-scope: SHARED to share counters for matching rule IDs between Nether and The End; DIMENSION keeps them separate. settings.progress.unlock-order: NETHER_THEN_END holds End counter progress until Nether access is unlocked; INDEPENDENT lets both dimensions progress separately. played_days is based on each player's playtime, world_days on the primary normal world, and calendar_date on the configured timezone.
Mob kills from spawners and other sources count normally. Artificial-spawn filtering is disabled.
Commands
| Command |
Description |
/gatekeeper progress |
Open the player progression menu. |
/gatekeeper status [player] |
Check your access status or, with permission, another player's. |
/gatekeeper settings |
Open the admin settings menu. |
/gatekeeper condition add ... |
Add a custom condition. Requires gatekeeper.admin. |
/gatekeeper condition set ... |
Edit a condition by its ID. Requires gatekeeper.admin. |
/gatekeeper unlock <player> <dimension> |
Grant access; replace <dimension> with nether or the_end. |
/gatekeeper lock <player> <dimension> |
Revoke access; replace <dimension> with nether or the_end. |
/gatekeeper reload |
Reload configuration and messages. |
Aliases: /gk, /worldlock, and /wlock.
Permissions
| Permission |
Purpose |
Default |
gatekeeper.use |
Use the main command. |
Everyone |
gatekeeper.admin |
Manage conditions and access, reload, and open settings. |
Operators |
gatekeeper.status.others |
Check another player's status. |
Operators |
gatekeeper.bypass.nether |
Bypass Nether restrictions. |
Nobody |
gatekeeper.bypass.the_end |
Bypass The End restrictions. |
Nobody |
gatekeeper.bypass.end |
Alias for gatekeeper.bypass.the_end. |
Nobody |
gatekeeper.bypass.* |
Bypass all GateKeeper dimension restrictions. |
Nobody |
PlaceholderAPI
PlaceholderAPI is optional and must be installed separately. When it is present, GateKeeper registers placeholders that other PlaceholderAPI-compatible plugins can use:
%gatekeeper_mode%
%gatekeeper_unlocked_nether%, %gatekeeper_unlocked_the_end%
%gatekeeper_progress_nether%, %gatekeeper_progress_the_end%
%gatekeeper_required_nether%, %gatekeeper_required_the_end%
%gatekeeper_remaining_nether%, %gatekeeper_remaining_the_end%
%gatekeeper_mob_nether%, %gatekeeper_mob_the_end%
%gatekeeper_rule_nether_<rule-id>_progress%
%gatekeeper_rule_nether_<rule-id>_required%
%gatekeeper_rule_nether_<rule-id>_complete%
Replace <rule-id> with the condition's configured ID. End rule placeholders use the_end in place of nether. For example, test a placeholder with /papi parse me %gatekeeper_rule_nether_zombie-hunt_progress%.
Compatibility
GateKeeper is built for Paper and Java 17. PlaceholderAPI is optional. It is not bundled with the plugin.
Feedback and project overview
Report a bug or suggest a feature.
评论 0
登录后参与评分
还没有评论,来抢沙发吧