PathWeaver

This is a large jump from 0.1.2. The headline: PathWeaver now actually runs on most packs, instead of switching itself off.

Why it used to do nothing

PathWeaver refuses to run a search off-thread when another mod has modified the code that search executes. That rule is correct, and it is also why the mod was inert on most modpacks — a single popular mod anywhere in your pack switched it off entirely. Fabric API, which PathWeaver itself requires, was enough to do it.

0.3.0 replaces that all-or-nothing behaviour with a setting, and does the work to open the gate honestly rather than by ignoring it.

Compatibility risk (new setting, default Audited)

Replaces the old overrideCompatibilityScan checkbox. Existing configs migrate automatically.

• Strict — structural proofs only. Denies any pack containing Fabric API, so it usually does nothing. Not the default, for that reason.
• Audited (default) — also accepts bounded evidence. Four distinct mechanisms sit behind it and they are not equally strong; the settings screen and the compatibility matrix name each one separately rather than calling them all "proven".
• Everything — no checks. Runs uninspected mod code on workers. Back up your world.

Newly audited and working: Lithium (ships in most performance packs and used to disable this mod on sight), Diagonal Blocks, and Farmer's Delight — whose stove receives the world and provably never reads it, so its answers are precomputed and frozen. Mods that simply mark a block dangerous are now handled generically, with no per-mod entry and no audit needed.

Measured, on the configuration you actually get

Six paired runs, interleaved and order-reversed, no harness intervention: mean tick time 78–96 ms → 49–50 ms (median 41%, range 36–48%), p99 726–1096 ms → 338–390 ms, effective tick rate 10.4–12.7 → 20.0 TPS, with no overlap between arms. The last pair was re-run on the exact jar published here and landed inside every one of those ranges.

Swimming measured separately: p99 −65%, main-thread cost per search −8×, mean tick time unchanged — because 1024 fish never saturate the server. That is the mod's real shape: it removes spikes, it does not raise averages.

Also verified at 371-mod pack scale: 331 mixin configs scanned, zero parse failures.

Settings

• Compatibility risk is a dropdown now, not a cycling button whose long labels scrolled past unreadably.
• Tooltips say what to do, not what the setting mechanically is, and name the four settings measured to make no difference so you can leave them alone.
• Two values can silently defeat the mod — a near-zero staleness threshold, and an inflated in-flight limit. Both now warn loudly at startup and are still honoured exactly as configured. You are told it is a bad idea; you are not overruled.
• repathElisionEnabled is gone. It defaulted to on while the tolerance it depended on defaulted to 0, so it advertised itself as enabled and did nothing. Path reuse is now one control where 0 means off. Behaviour is unchanged.

Fixes worth calling out

• Everything now genuinely means everything: it previously left most of a modded pack's mobs synchronous while reporting that nothing was being checked.
• The compatibility tier is frozen at startup. Saving a different tier mid-session used to leave startup denials waived while per-request checks tightened — a session started at Everything and saved to Strict kept dispatching work Strict forbids. It now applies on restart, which is what the setting always claimed.
• Several published performance claims were corrected downward after re-measurement. The earlier "44.8%" rested on a single unusually heavy baseline run.

Honest status

Still alpha. A worker reads live chunk and mob state through a read-only view, not a copy. The compatibility matrix states every exemption, exactly what was checked, and where a claim rests on a bounded sample rather than a proof.

This release went through seven rounds of independent review, plus one that refused to start because the release tag pointed at the wrong commit. Several findings were changes that looked right, passed all 217 tests, and were wrong anyway — including one that contradicted the document justifying it.