Links
Tags
Creators
Details
0.2.4
Compatibility
Required content
Changes
Blocks with more than 16 states now emit metadata-preserving drops.
Block.dropStacks handed the vanilla nibble (bits 0-3) to getDroppedItemId/getDroppedItemMeta, so a block whose flattened state index spills into the chunk sidecar could not recover its full state at drop time. A new register.BlockDropStateMixin swaps the nibble for RetroStates.get(...).getIndex() whenever the block has an explicit state definition wider than the nibble; decode it in your hook with RetroStates.fromIndex(this, meta). Vanilla blocks, implicit-meta blocks, and <=16-state blocks are untouched.
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:iFaqJ8QH:sDVudcPf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iFaqJ8QH:sDVudcPf"
}


