Links
Tags
Creators
Details
release2.0
Compatibility
Changes
Hey everyone! A major update for ReviveSystem is here. This is the biggest update since the initial release, focusing on three areas: performance, customization, and compatibility.
Here's everything you need to know.
What is ReviveSystem?
ReviveSystem is a plugin for Minecraft Hardcore and Semi-Hardcore servers that gives dead players a second chance โ but only through teamwork.
The core loop is simple:
- ๐ You die โ you drop your head and enter Spectator Mode
- ๐ค A teammate picks up your head, crafts a special item, and revives you
- โค๏ธ You return to Survival with full health โ your second life begins
There are three ways to be revived:
- Revive Item โ Craft a Nether Star from Player Head + Gold + Emerald + Totem of Undying
- Respawn Point โ Surround a dead player's head with Soul Sand, then place the result to teleport and revive them
- Admin Command โ Server operators can use
/revive <player>
Bonus Feature: Head Mechanic โ Wear a dead player's head as a helmet to get +20 bonus hearts (configurable). You'll also unlock the "Kopf hoch!" advancement and hear a level-up sound.
What's New in v2.0?
๐ Performance Overhaul
Your server will run smoother than ever:
- Async saving โ Player data saves on a background thread, no more lag spikes
- Smart saving โ Only writes to disk when data actually changes
- Better item detection โ Uses Minecraft's PersistentDataContainer (PDC) instead of checking display names. More reliable, faster, won't break if items are renamed
- Explosion optimization โ Head protection now only checks nearby entities instead of scanning the entire world
- Config caching โ Settings are loaded once, not re-read on every game event
โ๏ธ Full Customization
Almost everything is now configurable in config.yml:
| What you can change | Example |
|---|---|
| Bonus hearts from head mechanic | 10, 20, 40 โ whatever you want |
| Deaths before spectator mode | 1 (hardcore), 2, 3, or more |
| Health after revival | Full hearts, half hearts, or barely alive |
| Self-revive | Allow or deny |
| Head drops on death | Toggle on/off |
| Level-up sound | Any Minecraft sound, custom volume & pitch |
| Auto-save interval | Every 1 min, 5 min, or disabled |
| Death GUI display time | 2 seconds, 5 seconds, 10 seconds |
| The entire head mechanic | One toggle to enable/disable everything |
๐ Editable Language Files
All plugin messages are now in external YAML files that you can edit without recompiling:
messages_de.ymlโ German (default)messages_en.ymlโ Englishmessages_es.ymlโ Spanish
Want a different language? Just copy one of the files, translate it, and set your language code in the config. Done.
๐ Live Reload
Changed a setting? You no longer need to restart the server.
Just run: /revive reload
All config values, messages, and settings are updated instantly.
๐ Wide Compatibility
The plugin now works on Minecraft 1.21 all the way to 26.2+ (Paper, Spigot, Bukkit). It automatically detects your server version and adapts.
How to Update
If you're running Beta 0.2:
- Replace the old JAR with
revivesystem-2.0.jarin yourplugins/folder - Start the server โ all new config options appear automatically
- Your existing player data is fully compatible โ nothing is lost!
If this is a fresh install, just drop the JAR in plugins/ and the datapack in datapacks/. Start the server and you're good to go.
Commands & Permissions
| Command | What it does | Who can use it |
|---|---|---|
/revive |
Shows help | Everyone |
/revive <player> |
Revives a dead player | revivesystem.use (everyone) |
/revive reload |
Reloads all config & messages | revivesystem.admin (OP only) |
Crafting Recipes
Revive Item (Nether Star)
[Player Head]
[Gold] [Emerald] [Gold]
[Totem of Undying]
Respawn Point
[Soul Sand] [Soul Sand] [Soul Sand]
[Soul Sand] [Player Head] [Soul Sand]
[Soul Sand] [Soul Sand] [Soul Sand]
Questions?
If you run into any issues or have suggestions, reach out on Discord: desertlox
Enjoy the update! ๐ฎ
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:ct0RCd3D:j7sIhlVT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ct0RCd3D:j7sIhlVT"
}

