Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 2 years ago
All versions
1.12.2-1.0.0-rc2
Beta
Realistic Block Physics [1.12.2-3.0.0-rc2]2 years ago 230
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Note: Some changes require regenerated config files to take effect.
Changelog [1.12.2-3.0.0-rc2]
Improvements
- Improved logic for falling block relocation
- Reduced forced chunk loading when calculating block physics
Fixes
- Fixed fence gates breaking when opened [config change]
- Introduced missing block definition for ladders, which could cause structures to float [config change]
- Introduced missing block definition for lanterns, which could cause structures to float [config change]
- Fixed an issue where blocks that were crushed by falling blocks wouldn't drop their resources
- Removed physics for wall signs to prevent them from immediately breaking upon placement
- Fixed hoppers from preventing themselves, and some other blocks, from being stacked on top [config change]
- Fixed a crash which would occur when setting a dimension's default block definition to one which did not contain any blocks by default
- Fixed an issue which caused the default block definition of a dimension to override the existing block definitions
- Fixed snow powder blocks from immediately breaking when updated [config change]
- Fixed falling blocks not making sounds when sliding
Changes
- Changed the default "leaves" block definition to specify blocks via IDs instead of tags, as a temporary solution to Dynamic Trees compatibility issues [config change]
- Changed wooden blocks to now be able to float on liquids by default [config change]
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:45TL8yoG:r2J48FxG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:45TL8yoG:r2J48FxG"
}

