Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 4 months ago
All versions
2.0.0
Release
Incapacitated 2.0.011 months ago 15.6K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
- Added Keybinds for giving up while incapacitated (ctrl+delete on neoforge, delete on fabric by default)
- Fixed a bug where the revive progress bar wouldn't reach the end.
- Added a GUI rendered down counter
- With client configs to toggle it, toggle the colors, and change its position
- Added ShouldDieOnOverkillDamage - on by default, if the player takes more damage than your max health and current health combined, they die immediately instead of being incapacitated
- Added DANGERManipulateGoalToAvoidDownPlayers, to prevent mobs from targetting down players.
- Removed the GlowingWhileDown, added the effect to the incapEffectData config
- Added optional config to allow you to add potion effects to players when they're revived.
- Adding blame to incapacitation and revive messages
- These messages also don't display if the death messages gamerule is disabled
- ShouldBlameIncapacitations and ShouldBlameRevives in the config control if the blame mechanic is used.
- Commands should no longer necessarily require a player selector, if a player is running it.
- All Comma Separated Value configs are now tags
- InstantKills -> damage_type > no_incap.json
- FoodReviveList -> item > revive_food.json
- FoodAdrenalineList -> item > adrenaline_food.json
- FoodHealList -> item > healing_food.json
- Additionally added:
- damage_type > no_mercy.json - When the merciful config is on, what damage types bypass the invulnerability (for damage that shouldn't be ignored such as falling in the void)
- entity_type > not_for_hunting.json - When Hunter is enabled, what entities shouldn't count?
- The Hunter config is now an integer instead of a boolean
- Disabled when set to 0
- Any number above 0 is the amount of kills a user needs to get while down to self-revive
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:CmDgNtOI:bA1eq6c8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CmDgNtOI:bA1eq6c8"
}


