Links
Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated last month
All versions
0.2.0
Release
Carry Baby Animals 0.2.0 for Minecraft 26.1.25 months ago 185
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Server-side
Client and server
Required content
Any compatible version
Changes
- Client-side carried-baby visuals now look better, with gentler arm placement, safer first-person positioning for large babies, subtle movement, animal-specific reactions, and clearer sleepy/asleep poses.
- Carried baby cats and ocelots now curl up into a more recognizable sleeping pose when they get sleepy.
- Nursery Mode now helps keep carried babies out of trouble by refusing set-downs in unsafe spots like lava, fire, cactus, cramped spaces, and dangerous drops.
- Nursery Mode bypass now defaults to off when Fabric Permissions API is installed, so permission providers must explicitly grant
carrybabyanimals.nursery.bypass. - Setting a carried baby down near a matching adult can now show a little Parent Reunion moment with hearts and a warm action-bar message.
- Server owners can now use full entity IDs in
allowedAnimalsandblockedAnimals, making it easier to opt into compatible baby animals from other mods without enabling modded animals by default. - With Carry Baby Animals installed on the client, players can now edit visual settings directly through ModMenu.
- ModMenu now includes a connection status indicator that shows whether the server also has Carry Baby Animals installed, including version and build details when available.
Optional dependencies
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| carrybabyanimals-0.2.0-sources.jar | Unknown | 114.92 KiB |
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:prXdm4Xq:DYDW42xo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:prXdm4Xq:DYDW42xo"
}

