All versions
1.1.s2
Release
The Ebutale 1.1 Snapshot 24 months ago 32
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Added:
- Custom Shields
- Brute Bedrock, replaces bedrock
- Metashroom and Squireshroom now spawn naturally
- Dusty palm and eburisian baobab wood types
- new biome - eburis rainforest
- new stones: dampcrag and verdurite
- added ambreite
- fog in dustlands and aridlands
- duststorms in dustlands
- custom crafting tables for each wood type
- custom furnaces for each stone type
- custom barrels for each type
- eburisian silver hopper
- eburisian tin and copper rails
- pink steel
- pink steel anvil and tritium anvil
- functionality for altar wayfinder
- added rainforest vegetation
- more mobs - dust tarantula, shade spider, blizzret, cucurbito, marshy potcrawler and lush potcrawler,
- dampcrag and verdurite golems
- added brute bedrock - replacing bedrock
- added basic crafting materials
Changed:
- Textures of flimsium ingot and nugget, reduced brightness of silver
- Updated reinforced/toughened bow and fishing rod textures to fit in
- Mytrium block texture
- Wooden door and trapdoor textures
- removed active rift inceptor and powered rift altar items
- each ore for each stone can now be smelted in to their respecitve ingot
- made tritium block more tough
- brutestone tools recipe now uses cobbled brutestone
- carved glumkin and glum o lantern textures
- dust devils now only spawn when a duststorm is happening
- dusty reed was in natural blocks instead of ebutale vegetation
Fixed:
- Mushwood Door having an incorrect top texture
- Some leaves not being in the creative tab
- raw tritium did not smelt
- wyrms and torrid mosquitos were not spawning correctly
- pebbles not in creative tab
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:HmcHFGgW:C8vElC1g"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HmcHFGgW:C8vElC1g"
}

