Sable: Destructive

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 (or sable=NOT LOADED with 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 shockwaveMinMagnitude or shockwaveMinAttackerMassUnits.
  • 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-only compileOnly/localRuntime entries in build.gradle were 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_bucket NPE 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 to RegisterEvent or 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