Tags
Creators
Details
0.5.0
Compatibility
Required content
Changes
After a long wait, Consistency+ 0.5.0 is here for Minecraft 1.18.2! In case you missed the release candidates, here's a quick summary of what 0.5.0 adds:
Updated to 1.18.2. Prior versions are now unsupported, but may get backports if needed.
New Block Sets:
- Netherrack/Nether Brick
- Crimson Wart/Red Nether Brick
- Warped Wart
- Basalt
- Bone
- Withered Bone
- All 4 Copper oxidization stages + waxed
New Items/Changes to existing items:
- Withered Bones now drop from wither skeletons, and can be made into withered bone meal/withered bone blocks. Withered bone meal currently lacks function outside of being a crafting ingredient. Every block set now has a 'brick' item that can be crafted by placing a brick block in the crafting table.
- Netherite and Copper nuggets can be created from smelting the respective equipment, and some previously un-smeltable iron/gold based equipment can now be smelted down into the corresponding nugget types
- The Warped Wart Plant now functions properly and can be obtained by un-crafting a warped wart block. Crimson Wart blocks can now also be un-crafted.
- Netherite nuggets no longer burn in lava and fire, in case you decide you want to give your nuggets a hot bath
- More items can be turned into dyes as a quality of life change, and "Glow Dye" can now be created from glow ink, glowstone dust, and glow berries.
Many textures for block sets have been revamped by our artists:
- Obsidian
- Crying Obsidian
- Tuff
- Calcite
- Dripstone
- Blackstone
- Deepslate
- Dark Prismarine
- End Stone
- Basalt
- Purpur
- Netherrack
- Crimson Wart
- Warped Wart
And of course, some bugs have been stomped into the ground.
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:nDHcEOt3:4OFhn0vU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nDHcEOt3:4OFhn0vU"
}
