All versions
1.1.0
Release
Feathers Actions 1.1.02 months ago 24
Compatibility
Minecraft: Java Edition
1.20.1–1.20.6
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Fixed
- Mining Fatigue now actually applies while mining (was silently failing due to a broken player-state check)
- Boat stamina now actually drains while rowing (same root cause as above)
- Hunger/stamina regen now drains saturation before the hunger bar, instead of draining hunger directly
- Melee hits that drain your last stamina now apply Weakness III + Mining Fatigue I (previously just Weakness I)
- Fixed a memory leak where per-player stamina data was never cleared on disconnect (matters for long-running servers with many players over time)
Changed
- Melee stamina cost is now hit-only — swinging at air no longer costs stamina
- Running out of stamina while climbing now throttles your climb speed instead of freezing you in place
- Running out of stamina while rowing now caps the boat's speed (it glides to a stop) instead of stopping it dead
- Mining stamina cost is now purely time-based — the old per-block surcharge is gone, so Haste/Efficiency players aren't penalized extra for breaking more blocks per minute
- Punching with a bare fist or a non-weapon item now costs a small amount of stamina (was free), and applies the same Weakness III + Mining Fatigue I debuff as a weapon swing when it drains you to 0
Added
- Elytra gliding now drains stamina continuously; running out forces you out of flight and locks the elytra until you recover
- Boosting with a firework rocket while gliding costs extra stamina on top of the normal glide drain to discourage rocket-spam flying
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:IQdHTReZ:NZrfFhey"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IQdHTReZ:NZrfFhey"
}

