All versions
6.2.0
Release
revive_me-1.21.11-6.2.02 months ago 3
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
1.21.11-6.2.0
Additions
-(Config) Damage_Source_Whitelist - What damage sources that can bypass fallen state
-(Config) Can_Pick_Up_items - if fallen players can grab items
Changes
-FixCommand and ReviveCommand now accounts for multiple players
-You can now remove Penalty timer with effect command regardless of Can_Remove_Penalty_Timer config
Fixes
-Revive effects can now be properly hidden
1.21.11-6.1.1
Additions
-(Config) Max_Total_Revives - Max amount of time you can be revived
-(Config) Max_Player_Revives - Max amount of times someone else can revive you
-(Config) Revive_Radius - Radius teammates must be within for you to enter the fallen state
Changes
-(Config) Time_Left can now go to -1 to disable it
-(Config) Max_Self_Revives has been moved to General Fallen State Settings
-Fallen Effect now warns people if it can be removed if they leave and rejoin a world
-Removed Cancel_Revive_On_Damage since it wasn't being used
-Every effect can now be hidden through config
-Blocked keybinds are now checked once you enter the fallen state
Fixes
-Revive Me! now removes effects one at a time instead of all at once
-Fallen Penalty now happens on the 2nd down
-OpenGL Key error no longer spams in log
-Reviver's capability is properly synced on successful revive
1.21.11-6.0.13
Changes
-Penalty Timer now warns people once if it can't be removed
-Split up Self Revive methods inside Fallen Capability
Fixes
-Controllable should now work properly again
-Refresh revive items config now works properly
-No longer can use self revive if it's disabled
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:e1Ub5iPm:8hcqdE8c"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:e1Ub5iPm:8hcqdE8c"
}


