Tags
Creators
Details
7.1.0-alpha
Compatibility
Changes
Ender IO 7.1.0-alpha - Facades & Performance Improvements
⚠️ This upgrade is more experimental than typical releases, please backup and exercise caution. ⚠️
This release reintroduces the much-awaited conduit facades, supporting all of the original types of facade (hardened, transparent etc.) as well as integration for AE2 facades. In addition, there are swathes of bug fixes and performance improvements.
Info for Pack Devs
We'd recommend avoiding the 7.1 releases for now, we've made a number of changes to machines which cannot be rolled back to 7.0.x without (minor) machine data loss. We'll remove this warning once we're satisfied with the stability.
Info for Players
Please backup your saves before trying out this build of Ender IO, rolling back will result in loss of some data (IO Config, Redstone Control and similar settings). Please report any and all issues to us on GitHub. Thanks a lot!
Features
- Added conduit facades
- Add recipe to rebind powered spawners
- Rewritten machine networking, should improve performance but may introduce issues.
- Forced connections for redstone conduits
Bug Fixes
- NamedFluidContents Codec should've allowed optional FluidStacks (Fixes VAT)
- Alloy smelting recipe matcher could match wrongly
- Soul binder JEI shows outputs swapped around
- Hidden travel anchors do not work as elevators
- Conduits broken after new sync system was added
- Crash when right-clicking a machine in spectator mode
- Unable to extract levels from XP Obelisk if it is not XP Juice inside.
- Travel anchor HUD not rendering
- Some conduit recipes not working
- Logic error preventing charging of machines
- Mislabelled Redstone Mode tooltip
- Alloy smelter not working properly for recipes with multiple smelting outputs.
- Fixed some redstone filter problems
- Painted slabs use the wrong tint
Miscellaneous Tasks
- Tag crafter as connectable to redstone conduits
- Replace log4j loggers with slf4j
Optional dependencies
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:PP6ddFb2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:49ZofO4f:PP6ddFb2"
}





