All versions
4.2.14
Release
Youkai's Homecoming-unofficial-port 4.2.142 months ago 4,752
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
4.2.14
New Features
- Added stairs + stairs composition: right-clicking a stair with another material's stair in hand now produces a combined stair. The extra half returns to the player as a vertical slab of the second material.
- Added
disableCompositeBlocksclient config: hides the Composite Blocks creative tab entries from creative inventory and JEI. Placed blocks and right-click assembly are unaffected. Requires a game restart to take effect. - Added
disableComposeMechanicserver config: disables the right-click compose mechanic entirely. Existing composite blocks are unaffected.
Bug Fixes
- Fixed the compose mechanic being silently broken since porting:
CombinedBlockSet.init()was never called, so the block-to-set lookup table was empty and no right-click composition worked. - Fixed BIRCH wood type registering
BRICK_STAIRSas its stair block (copy-paste typo), which prevented birch stairs from participating in any composition. - Fixed hats, hairbands and Cirno wings leaking into the Composite Blocks creative tab. The default creative tab is now restored to the main mod tab after composite blocks are registered.
- Fixed Curios head/back slot definitions clobbering Curios defaults: added the missing
curios:tagvalidator so that accessory tooltips correctly show the slot hint and third-party head-accessory mods keep working. - Added a Curios can-equip fallback so this mod's hats/hairbands/wings can still be equipped even when another mod attaches a narrow validator to the head slot (e.g. GoetyDelight's doll-only rule).
- Fixed a misleading Curios query name (
hasWingswas used for head-slot checks); consolidated the query and cleaned up related slot-check logic.
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:gjywHTJ3:bH1t3HEd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gjywHTJ3:bH1t3HEd"
}

