Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 2 years ago
Updated 6 months ago
All versions
1.4.0-Forge-1.19.2
Release
Cozy's Improved Wolves v1.4.06 months ago 156
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Forge
Supported environments
Client and server
Changes
Version 1.4.0 of Cozy's Improved Wolves is here for Minecraft Forge 1.19.2!
Added
-
New config toggles
- Mute/disable the wolf teleport sound when wolves teleport to the player.
- Disable the gender system, along with any feature effects tied to gender.
- Disable revive mechanics (when disabled, wolves no longer drop collars on death).
- Enable/disable tamed wolf fall damage.
- Enable/disable extended/debug logging (non-essential logs are now gated behind this).
- Allow normal taming (removes the requirement for Ancient Bones).
-
Cloth Config integration
- Added an in-game config menu via Cloth Config for easier customization.
- Improved configuration documentation to better explain each setting.
-
Wolf reset/respec (config-controlled)
- Optional feature: use a Totem of Undying on a tamed wolf to reset its attributes and gender, rerolling both.
Changed
- Item textures updated
- Updated all item textures using the new community-created set.
Fixed
- Wolf armor
- Fixed wolf armor not applying correctly.
- Achievements pass
- Reviewed and corrected achievement triggers/criteria to ensure they function as intended.
Compatibility
- Safe adoption of existing vanilla tamed wolves
- When installing in an existing world, already-tamed vanilla wolves are now handled safely to prevent breakage or persistent issues.
Performance
- Optimization & bugfix sweep
- General performance improvements and a broad bugfix/cleanup pass across the mod.
Optional dependencies
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:N4PW8UQo:L3HgqAYg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:N4PW8UQo:L3HgqAYg"
}


