Tags
Creators
Details
1.2.0
Compatibility
Changes
LateGame+ v1.2.0
Major content update introducing the Debris Resonator, new configuration options, and internal QoL & code cleanup improvements.
✦ Additions
Debris Resonator
A rechargeable locator for naturally generated Ancient Debris in the Nether.
- Battery-driven search window: 1 800 s (default). Displays remaining charge even when powered off.
- Scan tiers:
- Close: 0–5 blocks
- Medium: 5–10 blocks
- Far: 10–16 blocks (~1 chunk)
- Too Far: 16–32 blocks (~2 chunks)
- Out of Range: >32 blocks
Each tier features dedicated model states and audio cues.
- Dimension restriction: Can only activate in the Nether; attempting elsewhere triggers a localized warning and burnout sound.
- Cooldowns:
- Successfully Mining the tracked Debris: 25 s — When you successfully mine the block that the debris resonator was tracking.
- Target missing: 10 s — when the tracked debris no longer exists or was player-placed.
- Distance limit: 60 s — when the player leaves the 32-block range.
- Recharge (via Netherite Anvil):
- Echo Shard: restores full charge; consumes 1; costs 5 XP levels.
- Amethyst Shard: restores
maxBattery / 60per shard (min 1 s); costs 1 XP per shard. Partial repairs stack to full capacity. - Automatically reverts to OFF if recharged from DEPLETED state.
⚙ Configuration
Available through Mod Menu, YACL, or manual JSON editing.
New config keys
{
"debrisResonatorMaxBatterySeconds": 1800,
"debrisResonatorCooldownSelfSeconds": 25,
"debrisResonatorCooldownOtherSeconds": 10,
"debrisResonatorCooldownFarSeconds": 60,
"debrisResonatorRangeY": 2,
"debrisResonatorSoundVolume": 1.0
}
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:V7Se8tsd:oGXuiv5N"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:V7Se8tsd:oGXuiv5N"
}

