你的朋友告诉你,为夏天开一个新的生存多人服务器(SMP)。结果其中一个朋友忍不住直接冲上去单刷末影龙。大家瞬间失去动力,这个 SMP 最终……死了……
听起来很耳熟吗?
那么 Cooperative End Access 就是为你准备的!
如果你试过了并且同意我的观点,那么请向世界分享你的认同——而“世界”指的就是 Reddit。
功能特性
- 从源头防止单人通关: 一个人无法再单独激活末地传送门。全队成员必须各自贡献自己的末影之眼。
- 确保末影龙作为团队挑战被击败: 新的 proximity(邻近)机制保证了参与激活的人数不止一名。
- 透明地限制进入末地的权限: 无需强硬的后台管理员干预。只需和朋友们一起游玩即可!
什么是 Cooperative End Access?
Cooperative End Access 是一款适用于运行在 Paper、Fabric 和 NeoForge 上的 Minecraft 1.21 至 26.2(Paper)以及 Minecraft 26.1 至 26.2(Fabric/NeoForge)的生存多人服务器(SMP)插件。它旨在帮助好友群体在不破坏沉浸感地重启服务器以切换 allow-end 参数的情况下,共同限制末地的访问权限,以便进行最后一次合作战斗。
该插件通过限制每位玩家能在要塞末地传送门结构中放置的末影之眼数量,并要求所有玩家在场时传送门才能开启来实现这一目标。
如何使用此插件?
- 前往 Modrinth 下载适合你 Minecraft 版本的最新版本插件。
- (针对 Fabric/NeoForge)从 Modrinth 下载对应平台的依赖项。
- 将其放入你的
plugins/ 目录(Fabric/NeoForge 则为 mods/)。
- (重新)启动服务器。
你最好在 SMP 刚开始时就添加此插件。目前该插件不提供定位或关闭现有末地传送门的工具,也无法回溯追踪已放置的末影之眼。
引入了哪些游戏机制?
一个末地传送门结构不再能由单一玩家填充。每位玩家在标准的 5x5 末地传送门结构中可放置的末影之眼数量有限(由 max_eyes_per_player 设定)。
填满全部 12 个末地传送门框架并不会像原版那样立即开启末地传送门。在结构中放置单个末影之眼会将该玩家标记为该特定传送门的“贡献者”。要开启传送门,所有对该特定末地传送门有贡献的玩家也必须出现在传送门房间内。如果任何贡献者离开传送门房间,传送门将关闭。
玩家也可以移除自己放置在框架中的末影之眼。如果在传送门开启状态下移除末影之眼,传送门将关闭。
一旦首次击败末影龙,末地传送门将恢复为原版功能。
我不应该对此插件抱有什么期望?
在技术层面……
- 此插件不处理形状怪异的末地传送门框架结构。它期望你使用的是标准末地传送门结构(5x5,所有框架向内)。
- 此插件不处理已经放置在框架中的末影之眼(插件添加前玩家放置的或自然生成的)。
- 此插件不处理已经存在且处于开启状态的末地传送门。请自行破坏它们。
- 此插件不处理在添加插件之前已经击败过末影龙的情况。
- 如果你希望在击败末影龙后复现此插件的功能,我建议使用以下便捷命令:
find ./plugins -maxdepth 1 -type f -name 'CooperativeEndAccess-*.jar' -delete
在社会层面……
- 此插件不能保证你的 SMP 能存活超过一周。
- 此插件不能保证如果你突然在未告知的情况下将此插件强加给朋友,他们不会生气。
- 此插件不能保证合作开启末地实际上会很有趣。
- 此插件不能保证你的朋友不会在没有你的情况下击败末影龙,但它能保证,如果他们真的在没有你的情况下击败了末影龙,那一定是大家一起完成的——除了你。
有哪些配置选项?
你可以通过在服务器上运行一次该插件来生成配置文件,从而对其进行配置。然后,你可以在(相对于服务器根目录)找到插件的配置文件:
plugins/CooperativeEndAccess/(Paper)
config/cooperativeendaccess/(Fabric 和 NeoForge)
以下是默认的 config.yml。它详尽地记录了此插件接受的所有配置参数。
# 单个玩家可向单个传送门结构贡献的最大末影之眼数量
# 自动限制在 0 到 12 之间(尽管为什么你会选 0??)
max_eyes_per_player: 3
# 距离语义:
# - 小于 0 的距离(例如 -1)被视为无限制范围,忽略维度。
# 换句话说,只要在服务器内就足以触发效果。
# - 所有距离均为从传送门中心计算的 3D 欧几里得距离。
# 为保持传送门开启状态,已承诺的玩家距离传送门的最大距离(方块数)
activation_radius: 16.0
# 已承诺的玩家距离传送门的最大距离(方块数),用于接收动作栏更新
action_bar_radius: 60.0
音量最小值限制为 0.0f,音高限制在 [0.5f, 2.0f] 之间(这是原版 Java 版施加的限制)。
sounds:
末地传送门生成时播放的声音
portal_open:
key: "minecraft:block.end_portal.spawn"
source: "block"
volume: 1.0
pitch: 1.0
末地传送门坍塌时播放的声音
portal_close:
key: "minecraft:block.beacon.deactivate"
source: "block"
volume: 1.0
pitch: 0.5
玩家进入 activation_radius 范围时播放的声音
player_enter:
key: "minecraft:block.amethyst_block.chime"
source: "player"
volume: 1.0
pitch: 1.0
玩家离开 activation_radius 范围时播放的声音
player_leave:
key: "minecraft:block.amethyst_block.break"
source: "player"
volume: 1.0
pitch: 0.5
使用 MiniMessage 格式。详见 Paper 的文档
messages:
当玩家尝试放置的眼球数量超过 max_eyes_per_player 时显示的个人聊天错误消息
max_eyes_error: "<red>你已经为此传送门贡献了你的一份力量!"
当玩家移除眼球时显示的个人聊天警告消息
rescind_warning: "<yellow>你收回了你的眼球。传送门状态可能会坍塌。"
当玩家尝试移除其他玩家的眼球时显示的个人聊天警告消息
占位符:<name> - 拥有该眼球的玩家(例如:"Megumin")。
non_owner_rescind_warning: "<red>这个眼球是由 <name> 放置的。你无法将其移除。"
当玩家放置眼球时显示的个人聊天通知消息
committed_notice: "<green>你现在已与此传送门绑定。"
首次击败龙后服务器广播的聊天通知消息
dragon_defeat_notice: "<gold>巨龙已陨落。末地传送门现已永久稳定!"
当已绑定的玩家身处末地时显示的操作栏文本
占位符:<name> - 位于末地的已绑定玩家(例如:"Sumi"),通过眼球插入顺序隐式选择。
stabilized_action_bar: "<bold><light_purple>✔ 由 <name> 稳定"
当传送门处于开启状态时显示的操作栏
active_action_bar: "<bold><green>✔ 传送门已激活"
当传送门等待所有已绑定玩家到场以开启时显示的操作栏
占位符:<names> - 缺失的已绑定玩家姓名的逗号分隔列表(例如:"Notch, Elaina, Mizuhara")
waiting_action_bar: "<gold>等待中: <white><names>"
你也可以在 [`./core/src/main/resources/config.yml`](https://raw.githubusercontent.com/ganyuke/CooperativeEndAccess/refs/heads/multiplatform/core/src/main/resources/config.yml) 中找到此文件。
## 如何反馈你的插件存在问题?
请通过 [插件的 GitHub 仓库](https://github.com/ganyuke/CooperativeEndAccess/) 中的 [问题追踪器](https://github.com/ganyuke/CooperativeEndAccess/issues) 报告我的 spaghetti code 存在的问题。
## 如何为此插件提交功能建议?
如果你为此编写了代码,只要我觉得它不会使本插件的范围膨胀,我会很乐意接受相关的拉取请求。
向此仓库提交贡献即表示你同意你的贡献按照 [`LICENSE`](https://raw.githubusercontent.com/ganyuke/CooperativeEndAccess/refs/heads/multiplatform/LICENSE) 文件中公布的许可证进行授权。
Your friends tell you to spin up a new SMP for the summer. One friend can't help themself and rushes to beat the dragon immediately. Everyone loses motivation and the SMP ends up DYING...
Sound familiar?
Then Cooperative End Access is for you!
And if you try it and you agree, then please share that agreement with the world, and by "the world", I mean Reddit.
Features
- Prevent soloing at the source: one person can no longer open an End Portal alone. The whole team must contribute their own Eye.
- Ensure the Dragon is fought as a team: new proximity mechanics guarantee that the Order of the Stone is more than one member.
- Restrict access to the End transparently: no heavy-handed admin intervention needed. Just play together with your friends!
What is Cooperative End Access?
Cooperative End Access is a modification for survival multiplayer servers (SMPs) running Paper, Fabric, and NeoForge for Minecraft 1.21 to 26.2 (Paper) and Minecraft 26.1 to 26.2 (Fabric/NeoForge). It is intended for friend groups that want to restrict the End for one last fight together without an immersion-breaking server restart to toggle allow-end.
The plugin accomplishes this goal by restricting the number of Eyes of Ender that each player can place in a stronghold Ender Portal structure and requiring all players to be present before the portal can open.
How do I use this plugin?
- Download the latest version of this plugin for your Minecraft version off Modrinth.
- (For Fabric/NeoForge) Download dependencies for your platform off Modrinth.
- Move it to your
plugins/ directory (or mods/ for Fabric/NeoForge).
- (Re)start the server.
You should ideally add this at the very start of your SMP. This plugin does not currently provides tools to locate or close existing Ender Portals or retroactively track existing Eyes of Ender.
What gameplay mechanics does this introduce?
An End Portal structure can no longer be filled by a single player. Each player has a limited number of Eyes of Ender (set by max_eyes_per_player) that they can place in a standard 5x5 End Portal structure.
Filling all 12 End Portal frames will not immediately open the End Portal like in vanilla. Placing a single Eye of Ender in a structure marks that player as a "contributor" to that particular Portal. All contributors to a particular End Portal must also be present in the portal room for the portal to open. If a contributor were to leave the portal room, the portal will close.
Players may also remove their own Eyes of Ender that they placed into a frame. Removing an eye while a portal is open will close it.
Once the Ender Dragon is defeated for the first time, End Portals will revert to their vanilla functionality.
What should I not expect from this plugin?
On a technical level...
- This plugin does not handle weirdly-shaped End Portal frame structures. It expects you to be playing with a standard End Portal structure (5x5, all frames inward).
- This plugin does not handle existing Eyes of Ender placed in the frames (player-placed before the plugin was added or naturally-spawned ones).
- This plugin does not handle existing, open End Portals. Break them yourself.
- This plugin does not handle having killed the dragon before adding the plugin.
- If you would like to replicate the functionality of this plugin after killing the dragon, I recommend using this handy little command:
find ./plugins -maxdepth 1 -type f -name 'CooperativeEndAccess-*.jar' -delete
On a social level...
- This plugin does not guarantee that your SMPs will survive more than one week.
- This plugin does not guarantee that your friends won't be upset if you suddenly spring this plugin on them without telling them.
- This plugin does not guarantee that opening the End cooperatively will actually be any fun.
- This plugin does not guarantee that your friends won't beat the Ender Dragon without you, but does guarantee, if they do beat the Ender Dragon without you, that'll be together, minus you.
What configuration options do I have?
You can configure this plugin by running the plugin on your server once so it generates its configuration files. Then, you can find the plugin's configuration files at (relative to your server root directory):
plugins/CooperativeEndAccess/ (Paper)
config/cooperativeendaccess/ (Fabric and NeoForge)
Below is the default config.yml. It exhaustively documents all configuration parameters that this plugin accepts.
# Maximum eyes one player can contribute to a single portal structure
# Automatically clamps to range between 0 and 12 (though why would you pick 0??)
max_eyes_per_player: 3
# Distance semantics:
# - Distances below 0 (e.g. -1) are treated as unlimited range, ignoring dimension.
# In other words, presence in server is enough to trigger the effects.
# - All distances are 3D Euclidean distance from the portal center.
# Maximum distance (in blocks) committed players may be from the portal for it to remain open
activation_radius: 16.0
# Maximum distance (in blocks) a committed player may be from the portal to receive action bar updates
action_bar_radius: 60.0
# For sound keys, see [Paper's documentation](https://docs.papermc.io/paper/dev/command-api/arguments/registry/#sound)
# or [visit the Minecraft Wiki](https://minecraft.wiki/w/Sounds.json#Sound_events).
# For types of sources, use the "Technical name" on the [Minecraft Wiki's Sound page](https://minecraft.wiki/w/Sound#Categories).
# Volume is clamped to 0.0f at minimum and pitch is clamped to [0.5f, 2.0f] (which are limitations imposed by vanilla Java Edition).
# See the [Minecraft Wiki's /playsound page](https://minecraft.wiki/w/Commands/playsound#Arguments) for more details.
sounds:
# Sound played when the End Portal is created
portal_open:
key: "minecraft:block.end_portal.spawn"
source: "block"
volume: 1.0
pitch: 1.0
# Sound played when the End Portal collapses
portal_close:
key: "minecraft:block.beacon.deactivate"
source: "block"
volume: 1.0
pitch: 0.5
# Sound played when a player enters the activation_radius
player_enter:
key: "minecraft:block.amethyst_block.chime"
source: "player"
volume: 1.0
pitch: 1.0
# Sound played when a player leaves the activation_radius
player_leave:
key: "minecraft:block.amethyst_block.break"
source: "player"
volume: 1.0
pitch: 0.5
# Uses MiniMessage format. See [Paper's documentation](https://docs.papermc.io/adventure/minimessage/format/)
messages:
# Personal chat message error when player tries to place more eyes than max_eyes_per_player
max_eyes_error: "<red>You have already contributed your share to this portal!"
# Personal chat message warning when player removes an eye
rescind_warning: "<yellow>You took your eye back. The portal state may collapse."
# Personal chat message warning when player tries to remove another player's eye
# Placeholder: <name> - The player who owns the eye (e.g. "Megumin").
non_owner_rescind_warning: "<red>This eye was placed by <name>. You cannot remove it."
# Personal chat message notice when player places an eye
committed_notice: "<green>You are now committed to this portal."
# Server-broadcasted chat notice once the dragon has been defeated for the first time.
dragon_defeat_notice: "<gold>The Dragon has fallen. End Portals are now stabilized permanently!"
# Action bar text shown while a committed player is in the End
# Placeholder: <name> - A committed player present in the End (e.g. "Sumi"), chosen implicitly by eye insertion order.
stabilized_action_bar: "<bold><light_purple>✔ Stabilized by <name>"
# Action bar shown when a portal is open
active_action_bar: "<bold><green>✔ Portal Active"
# Action bar shown when a portal is awaiting all committed players to be present before opening
# Placeholder: <names> - comma-delimited list of committed player names missing (e.g. "Notch, Elaina, Mizuhara")
waiting_action_bar: "<gold>Waiting for: <white><names>"
You can also find this file in ./core/src/main/resources/config.yml.
How do I tell you that your plugin is broken?
Report issues with my spaghetti code through the issue tracker on the plugin's GitHub repository.
How do I submit features for this plugin?
If you wrote the code for it, I'll happily accept a pull request for it if I feel like it doesn't bloat the scope of this plugin.
By submitting a contribution to this repository, you agree that your contribution is licensed under the same license as this repository, as published in the LICENSE file.
评论 0
登录后参与评分
还没有评论,来抢沙发吧