1.4.0
Compatibility
Changes
The command /sable-dv mode <name> switches the behavior of the collision system as a whole. The default mode is now detaching.
What is there
/sable-dv mode delete- blocks only break (VANISH). No new sub-levels. The inertial chain works, and the world breaks through VANISH./sable-dv mode default— alias todetaching(new default)./sable-dv mode detaching— new default behavior. The hit detaches the block from the parent sub-level and spawns a separate sub-world that inherits the speed and flies apart in different directions. Nothing is destroyed — the pieces are physically detached. Self-damage and inertial chain are disabled. The world (terrain) breaks through VANISH (the world cannot be torn off as a sub-level)./sable-dv mode delete-detaching— combo: the starting block detaches, the inertial chain additionally breaks the blocks deeper. Maximum chaos.
What is fixed
- Shockwaves (shockwave) no longer trigger at every sneeze. Now there are two independent thresholds:
- Minimum approach speed (
shockwaveMinApproachSpeed, default 18 m/s) - cuts off settle/jitter contacts. - Minimum energy (
shockwaveMinEnergy, default 8 MJ instead of 250 kJ) - cuts off light impacts. - The shockwave system itself is now disabled by default
(
shockwaveEnabled = false). To enable it, use/sable-dv set shockwaveEnabled true.
- Minimum approach speed (
- Epic Shatter on Impact - A boulder thrown into a mountain now really shatters:
- On a hard impact, the cluster collapses to single blocks (small pieces instead of a single large brick).
- Each broken piece has a random spread along all axes + a random rotation, scaled by the approach velocity.
- Kick limits raised:
detachKickScale 0.4 → 1.5,detachMaxKickSpeed 6.0 → 25.0. - New parameters
detachShatterScatter(default 6.0) anddetachSpinScatter(default 6.0) - adjustable scatter and spin.
What is removed
- The typo
delete-detachinggis no longer accepted. Only canonical names:delete,default,detaching,delete-detaching.
Compatibility
- Old 1.3.0 worlds are loaded as is. If TOML had
collisionMode = "default"— behavior is nowdetaching(by new default). - Mod API (Addon API) has not changed, API_VERSION remains 1.
Requirements
- Minecraft 1.21.1
- NeoForge 21.1.227+
- Sable 1.1.3+
Authors
- Code: Xylos_Official
- Visual part: Viaquelt
- Based on Sable by ryanhcode
License MIT
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:s8kSCCgD:Qi1rLBON"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s8kSCCgD:Qi1rLBON"
}

