1.0
Compatibility
Changes
Known Issues and Configuration
Please note: Errors may exist; I am actively working on the forum page.
Configuration
To configure the plugin, you only need to edit the config.yml file and restart your server. The most critical value to adjust is damageIncrease.
For reference, here are some configuration examples:
- Default Setting: For my server, I use
0.005. With this setting, at day 500 of Minecraft (approximately 7 real-life days), a zombie inflicts 8 hearts of damage. - High Difficulty: If you prefer a more challenging experience, you might set
damageIncreaseto0.5. - Low Progression: For a slower progression, values like
0.001or0.0008are recommended.
Adjust these settings according to your desired difficulty and gameplay experience.
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:4OHHXn1b:gT8T9LA9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4OHHXn1b:gT8T9LA9"
}

