Tags
Creators
Details
1.2
Compatibility
Required content
Changes
📦 Version 1.2
📝 Developer Note
We ended up having to take a long pause from the development of all our mods, but we are now slowly coming back.
CobbleFurnies is already in active development again, and we are currently working on the next major update: CobbleFurnies 1.3 - Neon Update.
This update will bring several new decorative blocks, and we will start sharing teasers very soon. Thank you for your patience and for continuing to support the project.
🔧 Changelog
📦 Dependencies
- ⬆️ Fabric Loader: Updated from
0.17.2to0.18.4. - ⬆️ Fabric API: Updated from
0.116.6+1.21.1to0.116.10+1.21.1. - ⬆️ Fabric Kotlin: Updated from
1.12.3+kotlin.2.0.21to1.13.10+kotlin.2.3.20. - ⬆️ NeoForge: Updated from
21.1.113to21.1.233. - ⬆️ Kotlin for Forge: Updated from
5.3.0to5.12.0.
🍱 Stove
- 📖 Recipe Book: Fixed stove recipe book handling incorrectly using player inventory slots as crafting slots.
- 🧯 Stove: Fixed recipe-book crafting clearing/moving items from unrelated player inventory slots.
- 🔍 Stove: Recipe book ingredient scanning now only checks the actual 3x3 crafting grid.
- 🧹 Stove: Recipe book clearing now only clears the actual crafting grid instead of the whole stove container.
🪟 Curtains
- 🌐 Multiplayer: Fixed possible client/server desync when placing curtains.
- 👻 Curtains: Fixed possible ghost curtain blocks appearing client-side and disappearing after relog.
- 🧱 Placement: Curtain second half is now placed server-side after the real placement is accepted.
🐛 Bug Fixes
- 🌍 Locale: Fixed remaining locale-sensitive serialized names using
Locale.ROOT. - 🇹🇷 Turkish Locale: Fixed possible crashes caused by system locales such as Turkish changing blockstate/property names.
- 🧩 Block States: Fixed locale-sensitive names for:
CurtainVerticalPartMountTypePotColor
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:AXY1OO9m:54k31lEX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AXY1OO9m:54k31lEX"
}

