Tags
Creators
Details
v8.2.0-alpha
Compatibility
Changes
Ender IO 8.2.0-alpha
This is the first release for a new way of delivering improvements to Ender IO. 8.2 builds will be kept in alpha until we're satisfied with the changes, however we'll still continue to deliver bugfixes to Ender IO 8.1. As such, each 8.2 alpha release will mention what 8.1 version it is based on.
In this release we're introducing the ability to connect different tiers of conduit together in the same network - this is configurable by modpack developers.
Note due to this change, it will not be possible to downgrade to Ender IO 8.1.x after loading a world. Doing so will result in loss of data.
We'll also be releasing an early official port of Endergy compatible with Ender IO 8.2+.
Release Base: This release contains all changes from v8.1.2-beta.
Features
- Energy, Item, Fluid and Chemical conduits of different tiers can now connect to one-another. Transfer speeds will be reduced when travelling through a lower tier of conduit.
- Conduits will always use the shortest path to a destination, even if a faster path exists but is a larger distance to travel
- Distance is now calculated in conduit blocks, rather than comparing coordinates of the start and endpoints of a path
- To support this change, Energy conduits are peer-to-peer again. As such they no longer have an energy buffer (and any previously stored energy will unfortunately be voided - sorry!)
- This can be enabled/disabled per-conduit type in the config for the mod.
- Removed fluid/chemical locking, all fluid and chemical conduits support any number of fluids/chemicals at a time
- All tiers of fluid and chemical conduit support priority, just like their item and energy counterparts
- Added the limited item filter
- Moved grinding ball data from components to a NeoForge data map
- Add-on's like Ender IO Kube JS will need time to update and support this change.
Experiments
Experiments are new features locked behind feature flags, these are work-in-progress and shouldn't be enabled on your primary world.
- The Ender IO
- Early work in progress
Optional dependencies
Supplementary resources
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:49ZofO4f:HEAa9wqx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:49ZofO4f:HEAa9wqx"
}





