Tags
Creators
Details
Licensed ARR
Published 8 months ago
All versions
2.6.1
Release
Punchy 2.6.1 (Fabric) - 1.21.115 days ago 18.3K
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Changes
Punchy v2.6.1 released.
Focused on gameplay consistency, animation fixes.
Fixed
- Fixed First Person Model compatibility so setting the FPM hide angle above 85 displays
never, keeps the slider layout stable, and allows both the Punchy arm and First Person Model body to render together (Thanks for reporting the bug on Discord johmer b). - Fixed Hand Menu global arm tuning temporarily reverting to factory values while arm tuning was bypassed during equip/offhand action flows (Thanks for reporting the bug on Discord ReveriREM).
- Fixed stick mining behavior in the compatibility tuning template (Thanks for reporting the bug on Discord Crafty).
- Fixed boat paddles staying hidden on the boat after switching out of first-person view (Thanks for reporting the bug on Discord ねこくま and KyaTran).
- Fixed sword crit attacks using both hands while playing in left-hand mode (Thanks for reporting the bug on Discord shbashi Δ).
- Fixed walk-on-water animations resetting custom Hand Menu arm tuning while entering water (Thanks for reporting the bug on Discord ¸,ø¤º°
𝓜𝓻.𝓒𝓪𝓽2134°º¤ø,¸ [MC], ). - Fixed Punchy Puppies / Tiny Takeover crashing during startup on Forge 1.20.1 and NeoForge 1.21.1 (Thanks endI0 for reporting the bug on Discord).
- Fixed baby mob pickup support for Punchy Puppies / Tiny Takeover on Forge 1.20.1 and NeoForge 1.21.1 (Thanks strix for reporting the bug on Discord).
- Fixed carried baby mobs playing walk animations while the player moves, keeping them in idle pose while held (Thanks afuea and MaηυGσσX for reporting the bug on Discord).
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:8aoMKplv:6XunCL0y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8aoMKplv:6XunCL0y"
}

