ReviveSystem v2.0
一款功能齐全的 Minecraft 极限模式与半极限模式服务器复活系统。
ReviveSystem 为死亡的玩家提供第二次机会——但只能通过团队合作和战略决策来实现。当玩家死亡时,他们不会被永久淘汰。相反,他们会进入旁观者模式,并必须等待其他玩家将其复活。这既保留了极限模式的紧张感,又避免了因永久死亡而产生的挫败感。
兼容: Paper, Spigot, Bukkit — Minecraft 1.21 至 26.2+
目录
- 工作原理 — 逐步详解
- 头颅机制(额外生命值)
- 物品与合成配方
- 所有命令
- 所有权限
- 完整配置指南
- 语言与消息
- 安装指南
- 常见问题解答
- 故障排除
工作原理 — 逐步详解
以下是典型游戏会话中发生的确切情况:
1. 玩家死亡
当玩家在您的世界中死亡时,会自动发生以下三件事:
- 掉落头颅:在死亡位置掉落一个物理物品(带有其皮肤的玩家头颅)。
- 进入旁观者模式:他们可以四处飞行和观看,但无法与世界互动、破坏方块或执行影响游戏玩法的聊天命令。
- 出现死亡信息界面:显示其等级和总游戏时间的 GUI 窗口,该窗口会在 5 秒后自动关闭(可配置)。
此时玩家处于“死亡”状态,等待复活。
2. 如何复活死亡玩家
有两种方法可以让死亡玩家回归:
方法 A:重生点(灵魂沙上的玩家头颅)
- 另一名玩家拾取死亡玩家掉落的头颅。
- 在合成台中用灵魂沙将其包围(头颅在中心,周围全是灵魂沙)。
- 这会生成一个重生点——一种特殊的头颅物品。
- 当他们将这个头颅放置在地面上时,死亡玩家会被传送到该位置并复活。
- 放置的头颅会在 2 秒后消失。
方法 B:管理员命令
- 服务器管理员或操作员可以使用命令
/revive <playername> 立即复活任何死亡玩家。
3. 复活后
- 玩家以配置的生命值数量返回生存模式(默认:满 10 颗心)。
- 他们的死亡计数和复活状态会被保存。根据服务器配置,他们可以被复活一定次数或无限次。
- 他们的所有进度(经验值、持有的物品)遵循正常的 Minecraft 死亡规则。
头颅机制(额外生命值)
这是一个独立的可选功能,与复活系统配合使用:
- 当玩家拾取掉落的玩家头颅(来自他人的死亡)并将其作为头盔佩戴时,他们会获得 +20 额外生命值(额外的 10 颗满心,总共 20 颗满心)。
- 一条聊天消息会告知他们有关额外生命值的信息。
- 授予**“昂首挺胸!”(Kopf hoch!)**进度(以提示框通知形式出现)。
- 播放升级音效。
- 当玩家取下头颅时,他们的生命值恢复为正常状态(10 颗满心)。
- 额外生命值的数量、音效和音量均可配置。
头颅保护
掉落的玩家头颅是宝贵的复活令牌。默认情况下,它们可以被熔岩和爆炸摧毁。您可以在配置文件中更改此设置:
head.kill-at-lava: false → 头颅能抵御熔岩
head.kill-at-explosion: false → 头颅能抵御爆炸(TNT、苦力怕等)
物品与合成配方
重生点
| 属性 |
值 |
| 基础物品 |
玩家头颅(带有死亡玩家的皮肤) |
| 显示名称 |
§b[PlayerName] 的重生点 |
| 效果 |
放置以复活特定玩家 |
合成配方:
[灵魂沙] [灵魂沙] [灵魂沙]
[灵魂沙] [玩家头颅] [灵魂沙]
[灵魂沙] [灵魂沙] [灵魂沙]
将死亡玩家掉落的头颅放在中心,周围环绕 8 个灵魂沙方块。
所有命令
| 命令 |
描述 |
权限 |
/revive |
显示帮助和可用命令 |
所有人 |
/revive <player> |
立即复活一名死亡玩家 |
revivesystem.use |
/revive reload |
重新加载配置和消息文件,无需重启服务器 |
revivesystem.admin |
/rev |
/revive 的别名 |
同 /revive |
命令示例
/revive Steve → 复活玩家 "Steve"
/revive reload → 重新加载所有配置文件
/rev Alex → 简写形式:复活 "Alex"
所有权限
| 权限 |
描述 |
默认值 |
revivesystem.use |
允许使用 /revive <player> 命令 |
所有人 |
revivesystem.head |
允许使用头颅机制(额外生命值) |
所有人 |
revivesystem.admin |
允许使用 /revive reload 和管理员命令 |
仅 OP |
完整配置指南
首次启动服务器后,将创建文件 plugins/ReviveSystem/config.yml。以下是每个选项的详细说明:
# ============================================================
# ReviveSystem 配置 v2.0
# ============================================================
# 所有消息的语言。选项:de, en, es
# 您也可以创建自己的语言文件(见下方的语言部分)
language: de
# ============================================================
# 头颅机制设置
# ============================================================
head:
# 设置为 false 以完全禁用头颅机制
# (额外生命值、进度、音效——全部禁用)
enabled: true
# 玩家佩戴头颅时获得的额外红心数量。
# 20 = +10颗完整红心(总计:20颗完整红心 = 40点生命值)
# 10 = +5颗完整红心(总计:15颗完整红心 = 30点生命值)
# 40 = +20颗完整红心(总计:30颗完整红心 = 60点生命值)
bonus-hearts: 20
# 掉落的玩家头颅在落入岩浆时是否会被销毁?
# true = 是,头颅会燃烧并永久消失
# false = 否,头颅免疫岩浆伤害
kill-at-lava: true
# 掉落的玩家头颅是否会因爆炸(TNT、苦力怕)而销毁?
# true = 是,爆炸可以摧毁头颅
# false = 否,头颅受到爆炸保护
kill-at-explosion: true
# 玩家戴上头颅时播放的声音。
# 必须是有效的 Minecraft 声音名称。
# 示例:ENTITY_PLAYER_LEVELUP, UI_TOAST_CHALLENGE_COMPLETE,
# ENTITY_ENDER_DRAGON_GROWL, BLOCK_BEACON_ACTIVATE
advancement-sound: ENTITY_PLAYER_LEVELUP
# 声音的音量(0.0 = 静音,1.0 = 正常,2.0 = 响亮)
advancement-sound-volume: 1.0
# 声音的音调(0.5 = 低沉/缓慢,1.0 = 正常,2.0 = 高亢/快速)
advancement-sound-pitch: 1.0
# ============================================================
# 复活系统设置
# ============================================================
revive:
# 玩家在死亡多少次后进入旁观者模式?
# 1 = 第一次死亡后(默认,最硬核)
# 2 = 第二次死亡后(更宽容)
# 3 = 三次机会用完即止
deaths-required: 1
# 死亡信息 GUI 保持打开的时间(以刻为单位)。
# 20 刻 = 1 秒。默认值:100 刻 = 5 秒。
spectator-gui-duration: 100
# 玩家死亡时是否掉落头颅?
# true = 是,玩家会在死亡位置掉落带有其皮肤的头颅物品
# false = 不掉落头颅(禁用重生点机制)
drop-head-on-death: true
# 玩家可以被复活多少次?
# 设置为 -1 表示无限次复活,或设置为任意正整数(如 1、2、3)作为限制。
max-revives: 1
# 玩家复活后获得的生命值。
# 20.0 = 满血(10颗完整红心)
# 10.0 = 半血(5颗完整红心)
# 2.0 = 奄奄一息(1颗完整红心)
revive-health: 20.0
# ============================================================
# 数据与性能设置
# ============================================================
data:
# 每隔 X 秒自动保存玩家数据。
# 300 = 每 5 分钟(推荐)
# 60 = 每分钟(更频繁,磁盘 I/O 略高)
# 0 = 禁用(仅在数据变化时保存)
auto-save-interval: 300
语言与消息
ReviveSystem 开箱支持多种语言:德语 (de)、英语 (en) 和 西班牙语 (es)。
更改语言
- 打开
plugins/ReviveSystem/config.yml
- 将
language: de 更改为你所需的语言代码(例如 en 或 es)
- 运行
/revive reload 或重启服务器
自定义消息
所有消息都存储在插件文件夹中的 YAML 文件中:
plugins/ReviveSystem/messages_de.yml — 德语
plugins/ReviveSystem/messages_en.yml — 英语
plugins/ReviveSystem/messages_es.yml — 西班牙语
你可以直接在这些文件中编辑任何消息。使用 § 颜色代码进行格式化:
§a = 绿色,§b = 青色,§c = 红色,§e = 黄色,§7 = 灰色
§l = 加粗,§o = 斜体,§n = 下划线
可用占位符:
%player% — 玩家名称
%level% — 玩家等级
%playtime% — 总游戏时长(小时)
%deaths% — 死亡次数
%hearts% — 额外红心数量
创建新语言
- 复制
messages_en.yml 到 messages_xx.yml(将 xx 替换为你的语言代码)
- 翻译所有消息
- 在
config.yml 中设置 language: xx
- 运行
/revive reload
安装指南
要求
- 正在运行的 Minecraft 服务器,基于 Paper、Spigot 或 Bukkit
- Minecraft 版本 1.21 或更高版本(已测试至 26.2)
- Java 21 或更高版本
逐步安装说明
- 下载 最新的
ReviveSystem.jar 文件
- 停止 你的 Minecraft 服务器(如果正在运行)
- 将 JAR 文件复制到服务器的
plugins/ 文件夹中
- 启动 服务器
- 验证 插件是否加载成功,检查控制台输出是否包含:
ReviveSystem v2.0 aktiviert!
- 配置 插件,通过编辑
plugins/ReviveSystem/config.yml
- 使用
/revive reload 重载 —— 无需重启服务器!
从 v1.0 更新
如果你是从 ReviveSystem v1.0 更新:
- 你现有的
playerdata.yml 完全兼容 —— 不会丢失数据!
- 旧的没有 PDC 标签的玩家头颅仍会被识别
- 新的配置选项将以默认值自动添加
- 你旧有的配置值(
kill_at_lava, kill_at_explosion)需要手动迁移到新格式(head.kill-at-lava, head.kill-at-explosion)
常见问题解答
通用问题
问:玩家死亡时会发生什么?
他们会掉落自己的头颅物品,进入旁观者模式,并看到显示其等级和游戏时长的简短信息屏幕。他们可以四处飞行观察,但无法与世界互动。
问:死亡的玩家还能聊天吗?
是的!聊天不受限制。死亡的玩家可以与存活玩家沟通以协调他们的复活。
问:如果没有人复活一名死亡的玩家会发生什么?
他们将无限期地停留在旁观者模式中,直到有人复活他们,或者管理员使用 /revive <player>。
问:我在成为旁观者之前可以有多个生命吗?
当然可以!在 config.yml 中更改 revive.deaths-required。设置为 2 表示两条命,3 表示三条命,依此类推。
问:玩家可以被多次复活吗?
是的!你可以通过 revive.max-revives 配置选项设置最大复活次数。将其设置为 -1 允许无限次复活。
问:该插件会影响原版成就吗?
不会。“Kopf hoch!” 成就位于其自己的命名空间(revivesystem:)中,不会干扰任何原版 Minecraft 成就。
故障排除
| 问题 |
解决方案 |
| 插件未加载 |
请确认您正在运行 Java 21+ 以及 Paper/Spigot 1.21+ |
| 头颅未给予额外生命之心 |
请检查 config.yml 中的 head.enabled: true,并确认头颅具有正确的格式 |
| 消息语言错误 |
更改 config.yml 中的 language 设置,并执行 /revive reload |
| 配置更改未生效 |
执行 /revive reload 以应用更改,无需重启服务器 |
支持
如需支持、反馈或建议,欢迎通过 Discord 联系我:desertlox
(功能包将在未来推出)
许可证
本插件不开源。保留所有权利。
ReviveSystem v2.0
A full-featured revival system for Minecraft Hardcore and Semi-Hardcore servers.
ReviveSystem gives dead players a second chance — but only through teamwork and strategic decisions. When a player dies, they aren't permanently eliminated. Instead, they enter Spectator Mode and must wait for another player to bring them back. This keeps the Hardcore feeling intact while preventing frustration from permanent death.
Compatible with: Paper, Spigot, Bukkit — Minecraft 1.21 through 26.2+
Table of Contents
- How It Works — Step by Step
- The Head Mechanic (Bonus Hearts)
- Items & Crafting Recipes
- All Commands
- All Permissions
- Full Configuration Guide
- Language & Messages
- Installation Guide
- Frequently Asked Questions
- Troubleshooting
How It Works — Step by Step
Here's exactly what happens during a typical gameplay session:
1. A Player Dies
When a player dies in your world, three things happen automatically:
- Their head drops as a physical item at their death location (a Player Head with their skin).
- They enter Spectator Mode — they can fly around and watch, but they cannot interact with the world, break blocks, or chat commands that affect gameplay.
- A death info screen appears — a GUI window showing their Level and total Playtime, which automatically closes after 5 seconds (configurable).
The player is now "dead" and waiting for revival.
2. How to Revive a Dead Player
There are two ways to bring a dead player back:
Method A: The Respawn Point (Player Head on Soul Sand)
- Another player picks up the dead player's dropped head.
- They surround it with Soul Sand in a crafting table (head in center, soul sand all around).
- This creates a Respawn Point — a special head item.
- When they place this head on the ground, the dead player is teleported to that location and revived.
- The placed head disappears after 2 seconds.
Method B: Admin Command
- A server admin or operator can use the command
/revive <playername> to instantly revive any dead player.
3. After Revival
- The player returns to Survival Mode with the configured amount of health (default: full 10 hearts).
- Their death count and revival status are saved. Depending on the server configuration, they can be revived up to a certain limit or infinitely.
- All their progress (XP, items they had) follows normal Minecraft death rules.
The Head Mechanic (Bonus Hearts)
This is a separate, optional feature that works alongside the revive system:
- When a player picks up a dropped player head (from someone's death) and puts it on as a helmet, they receive +20 bonus hearts (10 extra full hearts, for a total of 20 full hearts).
- A chat message tells them about the bonus hearts.
- The "Kopf hoch!" advancement is awarded (appears as a toast notification).
- A level-up sound plays.
- When the player takes the head off, their hearts go back to normal (10 full hearts).
- The bonus hearts amount, sound, and volume are all configurable.
Head Protection
Dropped player heads are valuable revival tokens. By default, they can be destroyed by lava and explosions. You can change this in the config:
head.kill-at-lava: false → Heads survive lava
head.kill-at-explosion: false → Heads survive explosions (TNT, Creepers, etc.)
Items & Crafting Recipes
Respawn Point
| Property |
Value |
| Base Item |
Player Head (with dead player's skin) |
| Display Name |
§bRespawn Point of [PlayerName] |
| Effect |
Place to revive the specific player |
Crafting Recipe:
[Soul Sand] [Soul Sand] [Soul Sand]
[Soul Sand] [Player Head] [Soul Sand]
[Soul Sand] [Soul Sand] [Soul Sand]
Place a dead player's dropped head in the center, surrounded by 8 Soul Sand blocks.
All Commands
| Command |
Description |
Permission |
/revive |
Shows help and available commands |
Everyone |
/revive <player> |
Revives a dead player instantly |
revivesystem.use |
/revive reload |
Reloads config and messages without server restart |
revivesystem.admin |
/rev |
Alias for /revive |
Same as /revive |
Command Examples
/revive Steve → Revives the player "Steve"
/revive reload → Reloads all configuration files
/rev Alex → Short form: revives "Alex"
All Permissions
| Permission |
Description |
Default |
revivesystem.use |
Allows using the /revive <player> command |
Everyone |
revivesystem.head |
Allows using the Head Mechanic (bonus hearts) |
Everyone |
revivesystem.admin |
Allows /revive reload and admin commands |
OP only |
Full Configuration Guide
After the first server start, the file plugins/ReviveSystem/config.yml is created. Here's every option explained:
# ============================================================
# ReviveSystem Configuration v2.0
# ============================================================
# Language for all messages. Options: de, en, es
# You can also create your own language file (see Language section below)
language: de
# ============================================================
# Head Mechanic Settings
# ============================================================
head:
# Set to false to completely disable the head mechanic
# (bonus hearts, advancement, sound — everything)
enabled: true
# How many BONUS hearts the player gets when wearing a head.
# 20 = +10 full hearts (total: 20 full hearts = 40 HP)
# 10 = +5 full hearts (total: 15 full hearts = 30 HP)
# 40 = +20 full hearts (total: 30 full hearts = 60 HP)
bonus-hearts: 20
# Should dropped player heads be destroyed when they fall in lava?
# true = yes, the head will burn and be lost forever
# false = no, the head is immune to lava damage
kill-at-lava: true
# Should dropped player heads be destroyed by explosions (TNT, Creepers)?
# true = yes, explosions can destroy heads
# false = no, heads are protected from explosions
kill-at-explosion: true
# The sound that plays when a player puts on a head.
# Must be a valid Minecraft sound name.
# Examples: ENTITY_PLAYER_LEVELUP, UI_TOAST_CHALLENGE_COMPLETE,
# ENTITY_ENDER_DRAGON_GROWL, BLOCK_BEACON_ACTIVATE
advancement-sound: ENTITY_PLAYER_LEVELUP
# Volume of the sound (0.0 = silent, 1.0 = normal, 2.0 = loud)
advancement-sound-volume: 1.0
# Pitch of the sound (0.5 = deep/slow, 1.0 = normal, 2.0 = high/fast)
advancement-sound-pitch: 1.0
# ============================================================
# Revive System Settings
# ============================================================
revive:
# After how many deaths should the player become a spectator?
# 1 = after the first death (default, most hardcore)
# 2 = after the second death (more forgiving)
# 3 = three strikes and you're out
deaths-required: 1
# How long (in ticks) the death info GUI stays open.
# 20 ticks = 1 second. Default: 100 ticks = 5 seconds.
spectator-gui-duration: 100
# Should a player head drop when a player dies?
# true = yes, a head with the player's skin drops at the death location
# false = no head drops (disables the Respawn Point mechanic)
drop-head-on-death: true
# How many times can a player be revived?
# Set to -1 for infinite revives, or any positive number (e.g. 1, 2, 3) for a limit.
max-revives: 1
# Health the player gets after being revived.
# 20.0 = full health (10 full hearts)
# 10.0 = half health (5 full hearts)
# 2.0 = barely alive (1 full heart)
revive-health: 20.0
# ============================================================
# Data & Performance Settings
# ============================================================
data:
# Auto-save player data every X seconds.
# 300 = every 5 minutes (recommended)
# 60 = every minute (more frequent, slightly more disk I/O)
# 0 = disabled (data is only saved when it changes)
auto-save-interval: 300
Language & Messages
ReviveSystem supports multiple languages out of the box: German (de), English (en), and Spanish (es).
Changing the Language
- Open
plugins/ReviveSystem/config.yml
- Change
language: de to your desired language code (e.g., en or es)
- Run
/revive reload or restart the server
Customizing Messages
All messages are stored in YAML files in the plugin folder:
plugins/ReviveSystem/messages_de.yml — German
plugins/ReviveSystem/messages_en.yml — English
plugins/ReviveSystem/messages_es.yml — Spanish
You can edit any message directly in these files. Use § color codes for formatting:
§a = green, §b = aqua, §c = red, §e = yellow, §7 = gray
§l = bold, §o = italic, §n = underline
Available placeholders:
%player% — Player name
%level% — Player level
%playtime% — Total playtime in hours
%deaths% — Number of deaths
%hearts% — Bonus heart count
Creating a New Language
- Copy
messages_en.yml to messages_xx.yml (replace xx with your language code)
- Translate all messages
- Set
language: xx in config.yml
- Run
/revive reload
Installation Guide
Requirements
- A Minecraft server running Paper, Spigot, or Bukkit
- Minecraft version 1.21 or newer (tested up to 26.2)
- Java 21 or newer
Step-by-Step Installation
- Download the latest
ReviveSystem.jar file
- Stop your Minecraft server (if it's running)
- Copy the JAR file into your server's
plugins/ folder
- Start the server
- Verify the plugin loaded by checking the console for:
ReviveSystem v2.0 aktiviert!
- Configure the plugin by editing
plugins/ReviveSystem/config.yml
- Reload with
/revive reload — no server restart needed!
Updating from v1.0
If you're updating from ReviveSystem v1.0:
- Your existing
playerdata.yml is fully compatible — no data loss!
- Old player heads (without PDC tags) will still be recognized
- The new config options will be added automatically with default values
- Your old config values (
kill_at_lava, kill_at_explosion) will need to be manually transferred to the new format (head.kill-at-lava, head.kill-at-explosion)
Frequently Asked Questions
General
Q: What happens when a player dies?
They drop their head as an item, enter Spectator Mode, and see a brief info screen showing their level and playtime. They can fly around and watch but cannot interact with the world.
Q: Can a dead player still chat?
Yes! Chat is not restricted. Dead players can communicate with living players to coordinate their revival.
Q: What happens if nobody revives a dead player?
They stay in Spectator Mode indefinitely until someone revives them or an admin uses /revive <player>.
Q: Can I have multiple lives before becoming a spectator?
Yes! Change revive.deaths-required in config.yml. Set it to 2 for two lives, 3 for three, etc.
Q: Can players be revived multiple times?
Yes! You can configure the maximum number of revivals via the revive.max-revives config option. Setting it to -1 allows infinite revivals.
Q: Does the plugin affect vanilla advancements?
No. The "Kopf hoch!" advancement is in its own namespace (revivesystem:) and does not interfere with any vanilla Minecraft advancements.
Troubleshooting
| Problem |
Solution |
| Plugin doesn't load |
Check that you're running Java 21+ and Paper/Spigot 1.21+ |
| Head doesn't give bonus hearts |
Check that head.enabled: true in config.yml and the head has the correct format |
| Messages are in the wrong language |
Change language in config.yml and run /revive reload |
| Changes to config don't apply |
Run /revive reload to apply changes without restart |
Support
For support, feedback, or suggestions, feel free to contact me on Discord: desertlox
(Feature with the Advancement pack coming in the future)
License
This plugin is not open source. All rights reserved.
评论 0
登录后参与评分
还没有评论,来抢沙发吧