Tags
Creators
Details
Licensed LGPL-3.0-only
Created 4 years ago
All versions
2.4.1-1.12
Release
Not Enough Pets 2.4.1 for JE 1.122 years ago 5,600
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client and server
Changes
- Bugfix: Crash when spawning wild wolf variants on a server. This is due to a function being switched to client-side only in 1.12.
- Added Chinese
zh_cnlang file by Omgise
Changelog from 2.4.0 (now deleted):
- IMPORTANT: due to the newly-added dog breeds, the spawn egg registry has been shuffled around. NEP spawn eggs in your world likely have changed.
- Replaced "Brown Wolf" with "Rusty Wolf" and "Cream Wolf" with "Chestnut Wolf"
- Added Black Mountain Feist, Ashen Wolf, Black Wolf, Snowy Wolf, Spotted Wolf, Striped Wolf, and Woods Wolf
- The new wolf variants will now spawn in various biomes, rather than as village strays.
- Changed scale of all dog breeds—mostly up. Wolves remain default size.
- Bounding boxes now scale with age and breed size
- Untamed stray cats no longer attack chickens
- Updated dog collar texture and fixed underside of parrot wing textures
- The string list config entries now no longer print their default values in the description
- Feeding Items: Dog now includes raw and cooked cod and salmon, and ore dictionary raw and cooked fish by default
- Added config options to allow wild (not stray) ocelots and wolves to switch to random skins when tamed, kind of like old vanilla behavior, if you wanted that for some reason
- Bugfix: tiny chance of bred cats/dogs/parrots getting a different skin from its parents will now actually be random instead of ID 0
- Bugfix: top of Tuxedo cat's legs (normally not visible) are now black instead of white
- Implemented some rendering and code optimizations
- Slightly updated in-game logo
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:flsPN5I7:tGK4Yz6y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:flsPN5I7:tGK4Yz6y"
}

