Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated 3 hours ago
All versions
1.12.2-2.1.0.0
Release
Environmental Tech 1.12.2-2.1.0.021 hours ago 19
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Requires ValkyrieLib 2.1.0.x.
New
- Void miner outputs are configured in
config/environmentaltech/recipes/void_miner/<miner>/<tier>.json, which holds only your changes, so new defaults reach existing configs. An old full table is converted automatically. - The Absorption Modifier can be crafted.
- Mica shares the
blockMicaore name with Environmental Materials' Mica, so either works in both mods' recipes.
Changes
- Luck modifiers: n modifiers mine 1 to n+1 items per operation. A single Luck modifier used to add nothing but energy cost.
Fixes
- A lightning rod formed with any block entity in its rod slots, such as flower pots.
- Nanobot beacons take flight and fly speed back when a player leaves their range, changes dimension, loses the modifier, or the beacon stops. Flight from creative mode or other mods is left alone.
- A void miner tier with a single output and a matching lens crashed the server (configuration only).
- Accuracy modifiers were ignored after a void miner formed, until its chunk reloaded.
- Void miner output beyond the item's stack size was lost.
- Players more than 16 blocks from a void miner saw an outdated beam.
- The light grey lens now boosts Betweenlands limestone, and
light_grayis accepted as a target name. - A void miner override adding an item already covered by an ore-dictionary entry was ignored, and ids like
minecraft:wool:*produced invalid items. - The Absorption Modifier's name was misspelled.
Performance
- Void miners cache their structure lookups, controllers read their modifiers once per formation, and nanobot potion effects are only refreshed when needed.
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:dGdhZiPO:enmbNs8f"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dGdhZiPO:enmbNs8f"
}

