1.1.0
Compatibility
Changes
1.1.0 — 2026-10-23
Mineable entities, reworked (breaking)
Mining an entity now behaves exactly like mining a block: the same speed math, tool and tier rules, cracks, sounds, particles, loot, tool damage and Jade tooltip. The old API is gone with no replacement shim.
- Opt in by implementing
MineableEntity(or extendingAbstractMineableEntity) and returning aMineableProperties(hardness,harvestAsblock state, loot table, optional sounds/particles overrides, tool damage). Nothing is attached to, injected into or checked on any other entity. Seedocs/mineable-entities.md - Mining is server-authoritative with per-player progress. The client only sends START/ABORT/STOP; the server validates reach and line of sight against the entity's bounding box, applies spawn protection and adventure-mode rules, and runs the vanilla block break pipeline. Creative breaks instantly with no drops
- Loot is rolled as block loot (
LootContextParamSets.BLOCK,harvestAsas the block state), so Fortune, Silk Touch andmatch_toolwork. Looting no longer applies - New highlight: a live outline of the entity's animated, rotated model parts, also used for crosshair picking, built from vanilla buffers only (Sodium/Embeddium/Iris safe by construction)
- New cancellable
MineableEntityBreakEventand themilkywaylib:entities_minedcustom stat (stat.milkywaylib.entities_mined) - Block-breaking explosions break mineable entities like blocks: when the blast at that distance beats their
harvestAsblock's blast resistance they break and drop block-style explosion loot (EXPLOSION_RADIUSis passed, sosurvives_explosionworks). Explosions that keep blocks leave them alone - Mineable entities are immune to all damage except
#minecraft:bypasses_invulnerability(/kill, void) - Datapack overrides for already-mineable types at
data/<ns>/mineable_entities/<entity_path>.json(hardness,harvest_as,loot,sounds,particles,tool_damage); problems and files for non-mineable types go toDatapackDiagnostics. Overrides are read on the server; clients on a dedicated server predict with the code values and snap to the server's crack stage - Jade shows the block-style tooltip (title, required tool with check or cross, break progress on the box edge) and hides health and armor
- Removed:
MineableEntityAPI,MineableEntityData,MineableEntityManager,MineableMobEntity,MineablePartEntity,MineableEntityProvider, themineable_entityattachment,MixinIEntityExtension,EntityPersistentDataAccessor,MineableEntityDamageHandler,ModelPartHitboxExtractor, the old mining and progress packets and handlers, and the old highlight and render handlers - The network protocol version is now
1.1.0: client and server must both run MilkyWayLib 1.1.0
Fixes
- Fixed the likely cause of a crash with Create: Aeronautics (popping a balloon) and other mods with complex entities. Mineable-entity lookup ran a full save of every entity as it spawned, was tracked, attacked or rendered, including other mods' half-built ones, and shared an unsynchronized cache between the client and server threads. Mineable entities now opt in through an interface, so other mods' entities are never read or touched
- Joining a server no longer reloads your player file twice. The spawn-dimension hook re-read the save from disk and re-applied it to the player on every join, so every other mod listening for player loading ran three times. It now reuses the game's own load
- Fixed a crash on launch with any other mod that changes enchantment level names. Milky Way Lib's Roman-numeral fix for levels above X was a hard redirect, which crashes when two mods do it; it now chains with other mods
- Fixed a possible crash while entering a world with custom-fluid splash effects: the client and server could build the fluid list at the same time and read it half-built
- Creative-tab section tooltips no longer crash if another mod hands back a read-only tooltip list
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:3xkG1Dfb:YLmlGXWX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3xkG1Dfb:YLmlGXWX"
}

