Tags
Creators
Details
Licensed ARR
Published 7 months ago
Updated 3 weeks ago
All versions
2.0
Release
Punchy! x Tiny Takeover 2.04 months ago 263
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Punchy! x Tiny Takeover released 2.6.0.
Focused on the new carry interaction, multiplayer visibility, pet rendering improvements, Punchy Tool Tuning support, and compatibility with Fresh Animations Player.
Added
- Added Punchy! x Tiny Takeover support for Minecraft 1.21.1 and 1.20.1.
- Added a new carry interaction for supported baby mobs and hamsters.
- Crouch + right-click with an empty hand to pick them up.
- Works with supported baby mobs and Adorable Hamster Pets hamsters.
- Added full first-person and third-person rendering while carrying baby mobs or hamsters.
- Added multiplayer visibility so other players can properly see carried pets.
- Added proper inventory and hotbar visuals for carried baby mobs and hamsters.
- Added Punchy Tool Tuning support for carried pets.
- Baby mob and hamster hand positions can now be adjusted through Punchy’s F8 tuning menu.
- Each carry type has its own tuning setup for better positioning.
- Added compatibility with Fresh Animations Player.
- The carried-pet arm pose now works correctly with the Fresh Animations player resource pack.
- Added compatibility support for EMF player arm models when using Fresh Animations.
Improved
- Improved carried pet animations so baby mobs and hamsters stay still while being held.
- Improved third-person arm posing so the player’s arm points forward while holding a baby mob or hamster.
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:FDqBVN2B:x71QnkfR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FDqBVN2B:x71QnkfR"
}

