Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 3 weeks ago
All versions
3.0.0-beta.6+26.1.x-neoforge
Beta
Energized Power - 26.1.x - v3.0.0-beta.6 [NeoForge]4 months ago 117
Compatibility
Minecraft: Java Edition
26.1.x
Platform
NeoForge
Supported environments
Client and server
Changes
- Add 3 new soil types (Clay, Netherrack, Nylium)
- Add Nether Flower soil type tag
- Add Plant Growth Chamber recipe for Wither Rose
- It is now possible to swap upgrade modules with higher tiers by SHIFT + clicking in machine GUIs (Also possible without opening the Upgrade View)
- It is now possible to insert and swap upgrade modules by SHIFT + clicking machine blocks without opening the machine's GUI
- Insertion of fluids into output-only tanks is no longer possible (Extraction is still possible from input-only tanks)
- Fix Clay was missing in the Water Crops soil type tag
- Fix Pale Moss was not defined as soil recipe [26.1.x and 26.2.x only]
- Fix JEI recipes were sometimes not synced until the world was left and re-entered [Fabric 26.1.x and 26.2.x only]
- Fix stack size of the soil slot in the Plant Growth Chamber was not limited to 1 [Fabric only]
Breaking changes:
- Insertion of fluids into output-only tanks is no longer possible
Updates from an older Energized Power version:
- Automatic config upgrade is supported from EP v2.18.2 or newer (including 3.0.0 beta versions) with
config_version>=2.18.0 - To apply the new config values manually, you should rename the
common.confin theconfig/energizedpowerdirectory tocommon-old.conf
Please note that this is a beta version:
- v3.0.0 is still in development
- Over the next beta releases you can expect
- a new machine tier and new machines,
- some recipe changes, and some balance changes
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:6pku8gW1:kvUHgeO8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6pku8gW1:kvUHgeO8"
}

