1.0.0
Compatibility
Changes
⚡ Lightning Apocalypse — Turn the Storm Into Your Weapon ⚡
Lightning isn’t just a weather effect anymore — it’s your ultimate mob-clearing tool. This mod introduces a secret ritual: build a precise structure, meet the conditions, and unleash a lightning bolt that strikes the nearest mob. No random chaos — just controlled thunderous power.
📋 What You’ll Need
- Stormy weather — a thunderstorm must be active (or use
/weather thunderto force it). - Trident with Loyalty — the enchantment is a mandatory part of the ritual.
- 9 Lightning Rods — for the upper layer of the structure.
- 9 Copper Blocks — to form the base.
- A bit of experience — 1 XP point per strike (free in Creative mode).
🛠️ Step‑by‑Step Assembly
- Lay the foundation: place a 3×3 grid of Copper Blocks on the ground — this is your base.
- Build the upper layer: put a Lightning Rod on top of each Copper Block, forming a second 3×3 layer.
- Take position: stand right in the center of the structure.
- Equip the key item: hold the Trident with Loyalty in your main hand.
- Wait for the storm: ensure a thunderstorm is active (or trigger it with
/weather thunder). - Activate the ritual: perform a left‑click in empty air — no block needed.
💥 What Happens Next
- Lightning strikes the nearest non‑player entity (a mob) around you — never the player.
- Each strike costs 1 experience point (Creative mode users get it for free).
- The effect is immediate and dramatic: perfect for clearing out hordes of monsters in one electrifying hit.
😎 The Payoff
You’ve built the structure, waited for the perfect storm, and now you’re commanding lightning itself. One click — and ZAP! — the mobs are gone. Pure, satisfying power.
Now that’s how you bring the apocalypse! ⚡🔥
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:HqOAZ03k:IyIba834"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HqOAZ03k:IyIba834"
}

