1.0.9
Compatibility
Changes
YAPI Auto Bark 1.0.9
Release Summary
Version 1.0.9 focuses on release stability, compatibility reliability, and improved generated recipe consistency.
This update fixes resolved compatibility mappings not always being written into the generated datapack and improves the internal generation pipeline to ensure detected mappings are preserved correctly.
Changes
Fixed
- Fixed generated compatibility mappings sometimes resolving correctly but not being written as recipe JSON
- Fixed recipe generation performing a secondary registry pass that could lose resolved mappings
Improved
- Recipe generation now writes directly from the resolved stripping snapshot
- Built-in compatibility mappings are now injected after automatic scanning for improved reliability
- User override mappings are now applied directly to the resolved stripping map
- Improved datapack regeneration consistency
Generation
- Retained Windows-safe generated-pack replacement system
- Retained generated-pack cache invalidation for:
- mod list changes
- mod version changes
- generator version changes
- override file changes
Notes
- Auto Bark only generates recipes for blocks with valid item registry entries
- Some third-party mods may still require manual overrides if they use non-standard stripping implementations
- Resource reload warnings from unrelated mods are not caused by Auto Bark unless explicitly referenced in the log
Tested Environment
- Minecraft 1.20.1
- Forge 47.x
- Farmer’s Delight 1.20.1-1.2.11a
- Java 17
Verification
Confirmed generated pack manifest:
- modVersion:
1.0.9 - generatorVersion:
10 - Successfully generated hundreds of bark recipes in large test modpacks
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:tb6E9a0l:DiKlLg2W"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tb6E9a0l:DiKlLg2W"
}

