Links
Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 2 years ago
Updated 2 years ago
All versions
3.2
Release
Modification Update2 years ago 33
Compatibility
Minecraft: Java Edition
1.21–1.21.4
Platform
Data Pack
Changes
Additions
- Added the ability to change which item is used to heal, and revive players. you can easily change it by going to
data\incrementalhardcore\tags\item\healing_item.jsonanddata\incrementalhardcore\tags\item\revive_item.jsonrespectivley. - Added the
ReviveHealthsetting which changes the number of maximum hearts you get from a revive between2,4,6, andCustomwhich will give you the command to change it to any value between2-20 - Added a system that checks for a version difference that will effect compatibility, then attempt to automatically convert the old version to the new one, when available.
Changes
- Changed the default healing item from
minecraft:netherite_ingottominecraft:netherite_scrap - Changed the default number of hearts you get from a revive from
6to2 - Changed the namespace of
MaxHealth,temp,DeathDetecttoINH.MaxHealth,INH.temp,INH.DeathDetect. This will require you to manually transfer over your players data. There is a tool for it, you can read more about that below. - Changed
Versionto3
How to migrate user data
To migrate your user's data you need to make sure they are on the server, then run the command (/function incrementalhardcore:old_version/version_2_data_transfer) If it is ran again, it will only transfer the data of players who have not already had their data transferred. This will also clear the incompatible version warning upon loadBug Fixes
- Fixed being able to revive offline players
- Fixed healing offline players not taking effect until their health was updated while online
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:Vyz2ru2g:w1Z01QuT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Vyz2ru2g:w1Z01QuT"
}

