Tags
Creators
Details
26.2.0.3+fabric-26.2
Compatibility
Required content
Changes
-
Hotfixed crash on revive when Shogi isn't installed
-
Hotfixed "Hold to Rescue" overlapping with the rescue progress message
-
Added
/knockoutcommand to instantly knockout a player -
Fixed knockout screen opening even if
allowAcceptingFateisfalse -
Shogi Support: Added
hardcorerevival:can_reviverule (andhardcorerevival:can_be_revivedrule)- This feature requires Shogi to be installed. It will be ignored if Shogi is not present.
- For example, a rule like
{ "hardcorerevival:can_revive": "item_cost('minecraft:golden_apple')" }inconfig/hardcorerevival.rules.jsoncan be used to make revival cost a Golden Apple. - The complete Shogi effect catalog can be used.
-
Shogi Support: Added
hardcorerevival:revivedrule- This feature requires Shogi to be installed. It will be ignored if Shogi is not present.
- You can use this rule to fully customize what happens after a player is revived.
- This rule overrides default behavior (like the configured hunger values and status effects) if specified.
-
Added
rescueRespawnFoodLevelDecreaseoption which decreases food level by an exact amount instead of only maxing it out -
Added
disableInNonHardcoreoption which disables knockouts outside of hardcore worlds -
Added
hardcorerevival:bypasses_knockoutdamage type tag as an alternative to theinstantDeathSourcesconfig option -
Fixed instant death sources not bypassing damage damage protection while knocked out
-
Fixed
rescueRespawnFoodLevelincreasing food above what it was before instead of only maxing food out at that level
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:HqKoXaXz:V1L67FIi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HqKoXaXz:V1L67FIi"
}

