Links
Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated 4 months ago
All versions
1.0.3
Release
Thunderbolt_lib 1.0.34 months ago 10
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Tracks AE2 Lightning Tech 1.0.3. Purely additive — every 1.0.2 API symbol and behavior is preserved, so existing plugins recompile unchanged.
Added
- Frozen ID constants —
com.qianchang.ae2lt_api.api.ids.AE2LTBlockEntityIds(six AE2LT block-entity IDs plusLIGHTNING_GRID_MEMBERS, the five grid-connected machines) andAE2LTRecipeIds(six recipe-type IDs). Plugins can now reference AE2LT registry IDs without compiling against AE2LT's main jar. - Native API detection bridge —
com.qianchang.ae2lt_api.api.bridge.AE2LTNativeBridgeprobes at runtime whether AE2LT's own first-party API (com.moakiee.ae2lt.api, namespaceae2lt) is loaded. The two API surfaces stay namespace-distinct; this library does not perform implicit conversion between them. LightningEnergyTier.CODEC(MojangCodec) andLightningEnergyTier.STREAM_CODEC(vanillaStreamCodec<RegistryFriendlyByteBuf, _>) — wire-format-compatible with AE2LT's ownLightningTier, so packet and NBT data round-trip cleanly between the two APIs.LightningEnergyTier.fromOrdinal(int)— static ordinal decoder for packet round-trips.LightningCollectedEvent.isNaturalWeather()plus a matching 5-argument constructor.
Changed
mod_versionandAE2LTCapabilities.API_VERSIONbumped to 1.0.3.AE2LTLightningCollectorEventBridgenow propagates the natural-weather flag through toLightningCollectedEvent.AE2LTCapabilitiesJavadoc clarifies the deliberate namespace split between this library (ae2lt_api:lightning_energy) and AE2LT's own first-party capability (ae2lt:lightning_energy).
Compatibility
- All 1.0.2 public signatures, serialization names, capability IDs, and recipe IDs are preserved.
LightningCollectedEvent's 4-argument constructor still works and defaultsnaturalWeathertofalse.- Migration: bump the dependency version coordinate — no source changes required.
Full diff: CHANGELOG.md
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:g9oaYcWN:fEHZ7nbl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:g9oaYcWN:fEHZ7nbl"
}

