1.2.0-1.21.11
Compatibility
Changes
Patch Notes - Version 1.2 (For Minecraft Fabric 1.21.11)
-
Added compatibility with Fabric for Minecraft 1.21.11
-
Includes implementations from previous Fabric versions up to 1.2, alongside some extra elements from 1.3 including (but not limited to) the following:
-
Commands:
- /getSaturation - shows current saturation level.
- /addSaturation - adds (or subtracts, using negative input) saturation.
- /setSaturation - directly changes saturation to a fixed amount.
-
Gamerules:
- hungerLimitsSaturation: Controls whether hunger affects saturation. If true, limit the player's saturation level to never exceed the current hunger level.
- Set to false to allow saturation levels above 20.
- maxSaturation: Controls the max saturation limit for players. Set to -1 or lower to disable this limit.
- Can set below the food limit (between 0 and 20), with 0 disabling the saturation mechanic entirely.
- alwaysHungry: Determines whether players can eat any food regardless of hunger level in Survival or Adventure mode.
- maxExhaustion: Controls the max exhaustion level before hunger or saturation depletion. Set to 0 to disable exhaustion.
- saturationEffectDecayRate: Controls the decay rate of a player's saturation gain through status effects. Larger numbers means higher decay rate; set to 0 to keep saturation gain as constant.
- Traditional Minecraft settings: hungerLimitsSaturation = true, maxSaturation = 20, alwaysHungry = false, maxExhaustion = 4, saturationEffectDecayRate = 0.
- Note that disabling exhaustion means players will never lose hunger or saturation. To prevent infinitely increasing saturation, set a maxSaturation if exhaustion is disabled.
- hungerLimitsSaturation: Controls whether hunger affects saturation. If true, limit the player's saturation level to never exceed the current hunger 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:AgApeolo:Fpnu2icV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AgApeolo:Fpnu2icV"
}

