Tags
Creators
Details
4.6.24+A-26.2
Compatibility
Required content
Changes
[4.6.24+A-26.2] - 2026-06-05
Summary
The "Library Dependency Realignment" update.
- Dependency Constraint Update: Updated
fabric.mod.jsondepends block to require"dasik-library": ">=1.8.0"(preventing startup crashes with older library versions due to missing genetics API classes). - Library Realignment: Re-aligned and compiled against
DasikLibraryv1.8.1.
[4.6.23+A-26.2] - 2026-06-04
Summary
The "Genetics Library Migration" update. Abstracts and migrates all selective breeding, inbreeding, and outcross recovery calculations to DasikLibrary v1.8.0.
- Genetics Centralization: Migrated
WolfPersistentDatagenetics fields to the library-provideddasik-library:geneticsattachment type. - Thin Mod Architecture: Delegated breeding calculations, inbreeding checks, and outcross recovery rules to
GeneticsEngine.inheritGenetics, keeping the mod lightweight and clean.
[4.6.22+R-26.2] - 2026-06-04
Summary
- Release Promotion: Promoted all recent codebase optimizations and refactoring alignments to a stable production Release.
- Genetics & Breeding Info: Players can selectively breed dogs over generations to optimize attribute combinations (such as breeding massive high-health Aggressive watchdogs or fast Pacifists), creating unique and specialized companions.
- Naming Polish: Renamed the debugging GameRule from
betterdogdebuggingto namespacedvanilla-outsider-better-dogs:bd_debugging(along with english and indonesian translation key updates). - API Cleanups: Replaced legacy
Identifier.parsecalls with the modernIdentifier.fromNamespaceAndPathAPI, pre-allocating static fields insideWolfStatManagerto eliminate dynamic parser allocations. - Config Sync: Synchronized the template config JSON with all newly introduced configuration settings.
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:e7H8SUmG:snLdsxRx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:e7H8SUmG:snLdsxRx"
}




