Links
Tags
Creators
Details
Licensed MIT
Published last year
Updated 11 months ago
All versions
1.1+1.21.1
Release
Rejuvenation 1.1 for NeoForge 1.21.111 months ago 30
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Client and server
Changes
- You no longer need to stand in a beacon beam when rejuvenating.
- The player now swings their arm when using an item on a corpse.
- Corpse is now an optional dependency. Losing hearts and rejuvinating still work, but resurrection obviously doesn't.
- Added configuration for the amounts of max health, health gained, health lost and health respawned with, as well as the gamemode players are resurrected into
- Corpse compatibility can now be enabled or disabled in the config, as well as an option to prevent a player's last corpse from despawning, so they can always be resurrected.
Optional dependencies
Any compatible version
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:8vunPef8:cuQRYwCx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8vunPef8:cuQRYwCx"
}

