Tags
Creators
Details
Licensed CC-BY-4.0
Published 2 years ago
Updated 3 months ago
All versions
0.13
Alpha
Tough Environment 0.13 - 1.21.18 months ago 88
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
- Added default recipes for items that would be crafted with nuggets instead of replacing the vanilla recipes.
- Added authors(ivangeevo) to the mod files, so they should display properly in places where they should be displayed
- Fixed a bug where stone bricks from stone crafting with chisel would consume the chisels
- Fixed the Loose Diorite's item name displaying wrong as being "Granite"
- Changed/Generally improved Mod Menu configuration option screens to better show how configuration options work
- Changed all configuration options setting to be handled with Supermartijn642's Config Lib internally instead of Cloth Config API, which is used only for client side config options.
- Changed the "Block Breaking Restriction" configuration option to be called "Strata Based Block Breaking Restrictions" to better reflect what it does
- Reworked breaking speed modifications on how they are calculated and how configuration options interact between each other. They are now handled with Fabric Entity Atrributes API instead of mixins. Generally, the feeling of the game should stay the same, but it should be closer to how it feels in BTW CE
- Refactored pretty much the whole code; mainly for readability and cleaning up, but also so it's more in order with other mods from the BTWR project
- Removed the "TURNED_TO_FALLING_BLOCKS" block tag and associated functionality to make any block a falling block, because it was a bad modification and caused other problems. It will be pushed back until a better solution is found
- Updated the mod to Fabric Loader 0.17.3 BTWR: Shared Library 0.6.4
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:sAUDpGlh:CeB2EiUZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sAUDpGlh:CeB2EiUZ"
}


