1.7.2
Compatibility
Changes
Built against Sable 1.2.2 (the API surface we use is stable from 1.1.3 → 1.2.2 — no source changes required, this is a recompile + diagnostics release).
What's new
-
Startup self-check. The very first INFO line in the log now reads
[Sable: Destructive] addon=1.7.2 sable=1.2.2(orsable=NOT LOADEDwith a loud warning if Sable is missing). Future API-mismatch reports become a two-line paste instead of a full log dump. -
/sable-dv diag— live counters for "is the shockwave alive?":- Server waves emitted + packets actually sent
- BreakQueue throughput (offered / processed / pending / dropped by capacity vs. dedup)
- SubLevelMassResolver cache hit/miss/fallback rates
- Detected Sable runtime version
The command also prints a hint based on what it sees:
- Zero waves → magnitude / mass gate is filtering everything.
Lower
shockwaveMinMagnitudeorshockwaveMinAttackerMassUnits. - Waves but zero packets → no players inside
shockwaveClientHorizonBlocks. Stand closer or raise it. - Both non-zero → server is healthy; if the client sees nothing, install the addon CLIENT-side too.
-
Compiled against Sable 1.2.2 (
libs/sable-neoforge-1.21.1-1.2.2.jar). The 1.1.3-onlycompileOnly/localRuntimeentries inbuild.gradlewere swapped over so the IDE dev-runtime now matches the version most users have installed via Modrinth.
Crash report note (NOT Sable: Destructive)
- The Create / Registrate
chocolate_bucketNPE crash users have been seeing is a known Create 6.0.10 bootstrap-ordering bug. Our mod is not in that stack trace — we don't subscribe toRegisterEventor touch Create, Registrate, items, fluids, or advancements. Typical fix: remove duplicate Aeronautics jars (bundled + standalone), or redownload the Create jar if corrupt.
Requirements
- Minecraft 1.21.1, NeoForge 21.1.227+, Sable 1.1.3 or newer (tested on 1.2.2 — earlier 1.1.x still loads at runtime, only the registered Sable APIs we use need to exist).
MIT License
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:s8kSCCgD:LhQgdpcb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s8kSCCgD:LhQgdpcb"
}

