Tags
Creators
Details
All versions
1.20.1-1.1.0
Release
Aetherworks Refracted 1.20.1-1.1.02 years ago 200
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Additions
- Added the Hoe of the Villatic Harvest, an aetherium hoe that excels at farming crops.
- Added the Hoe of the Hyalopterous Shepherd, an aetherium hoe that excels at animal handling.
- Added the Agrarian Liners augment, which prevents you from trampling farmland when applied to boots.
- Added Suevite Small Bricks block set.
- Added Suevite Small Tile block set.
- Added the "Same Block" config list, which allows certain aetherium tools to treat the specified blocks like they are others, I.E. treating Azalea Leaves as if they were Flowering Azalea Leaves, and vice versa, for vein-mining with the Axe of the Sonorous Archives.
Changes
- Aetherium items no longer change modes via sneak+use. They now change modes via keybind (default: V).
- Added a keybind reminder to the tooltips of aetherium items with different modes.
- Added overlay messages when changing modes of aetherium items.
- All recipes now use item tags as input where applicable.
- Added tags to the fluids.
- The forge heater and cooler now use tags to determine what blocks and fluids are allowed beneath them.
- All molten metals are now allowed under the forge heater.
- Mixing recipes now use the minimum quantity of fluid, like normal Embers recipes.
- Tweaked Suevite Tile texture to better tile.
Fixes
- Suevite now properly drops cobblestone when not silk touched, and itself when silk touched.
- Aetherium tools now have the proper "perform actions", so they are counted as the appropriate tool type by various mods.
- Water now properly flows out of waterlogged blocks.
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:6SRwIHdF:ODxLHyKW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6SRwIHdF:ODxLHyKW"
}

