Tags
Creators
Details
All versions
17.7.0-alpha
Alpha
AE2 17.7.0-alpha [NEOFORGE]2 years ago 216
Compatibility
Minecraft: Java Edition
1.20.4
Platform
NeoForge
Supported environments
Client and server
Changes
New Block: Crystal Resonance Generator
- Generates 5 AE/t passively
- Only one per energy grid is allowed. This also means across grids connected with quartz fiber, only one will be active
- If a generator is suppressed by another on the same grid, it has a tooltip in Jade
- Generation rate is configurable
What's Changed
- Space+Click now only moves slots from the same group as the clicked slot by @shartte in https://github.com/AppliedEnergistics/Applied-Energistics-2/pull/7710
- Fix auto-crafting completion toast having broken background by @shartte in https://github.com/AppliedEnergistics/Applied-Energistics-2/pull/7711
- Fix crafting highlight in the pinned slot row in terminals by @shartte in https://github.com/AppliedEnergistics/Applied-Energistics-2/pull/7712
- Improve tracking of "missing ingredients" when performing recipe transfer from REI/EMI on dedicated servers by @shartte in https://github.com/AppliedEnergistics/Applied-Energistics-2/pull/7714
- Fix link-status overlay not matching number of visible rows in pattern access terminal by @shartte in https://github.com/AppliedEnergistics/Applied-Energistics-2/pull/7715
- Implement a crystal resonance generator (passive power generation for AE) by @shartte in https://github.com/AppliedEnergistics/Applied-Energistics-2/pull/7716
Full Changelog: https://github.com/AppliedEnergistics/Applied-Energistics-2/compare/neoforge/v17.6.6-beta...neoforge/v17.7.0-alpha
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Known incompatibilities
Any version
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:XxWD5pD3:uAI0bShS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XxWD5pD3:uAI0bShS"
}

