Slimefun Legacy 4.1.60

Slimefun Legacy 4.1.60 is a focused Stabilization & Validation Integrity release. It does not add a new gameplay system; it hardens the 4.1.59 Recovery Center/Doctor work, the maintained addon bundle, and the release/compatibility evidence used before publishing a build. Recovery Center and Doctor stabilization

The 4.1.59 Recovery Center remains the operator-facing recovery surface and keeps the same admin-only safety boundaries.

The Recovery Center remains gated by slimefun.command.doctor (operator by default) and hidden from normal players.
Resource-pack sender control, resource-pack item adoption, stored-item texture repair, and exact Legacy model-removal remain separate operations.
Mutating lanes continue to require explicit confirmation/fingerprint gates.
/sf doctor report now includes the active guide provider:
    Classic Slimefun Guide when maintained JEG is absent;
    JEG version plus enabled/disabled state when JEG is installed.
The public support report remains intentionally limited to support-safe diagnostics and does not dump paths, IPs, credentials, player data, coordinates, raw configuration, or raw exception text.
Doctor Next Steps continues routing unresolved findings to specialist lanes rather than implying that a generic repair fixes every issue.

No new automatic migration or automatic item-model cleanup was introduced. Exact addon-bundle validation

The canonical SF_Addons_1.21.11-26.3.zip release bundle now has stronger source identity guarantees.

The maintained release matrix currently covers 45 addons.
Matrix-pinned addons keep their explicit full source_commit.
For maintained addons that are intentionally left flexible during normal development, the bundle workflow resolves repository HEAD to a full Git SHA at the beginning of the build and locks that exact SHA for the remainder of the run.
Every collected addon records its exact source commit and JAR SHA-256 in bundle metadata.
The package step rejects any addon whose built commit differs from the locked source commit.
Bundle packaging validates maintained addon identities and manifest metadata instead of hard-coding addon version filenames; Networks is validated through its networksexp metadata record and canonical JAR entry, so normal version updates do not create false packaging failures.
The final 4.1.60 addon refresh targets the current maintained builds: Networks 1.0.30 (classic storage-routing behavior plus automatic Network Monitor storage discovery), Supreme 1.0.14 (machine recipe-scan optimization), and MagicExpansion 1.1.7 (JEG guide visibility fix). The bundle workflow locks the exact source SHA resolved for each addon at the start of the run.
Canonical naming rules remain enforced, including the existing DracFun Reborn and WorldEditSlimefun naming exceptions.
Archived/duplicate addon families remain excluded; Magic 8 Ball stays core-integrated and historical DracFun remains replaced by DracFun Reborn.
Magic Legacy (SF_Magic_RSC) is intentionally not shipped in the canonical addon ZIP. MagicExpansion remains bundled and keeps its optional Magic Legacy integration for servers that install Magic Legacy separately.

The exact-bundle full-stack path has been proven on master: the workflow downloads the exact triggering addon artifact, builds the matching Slimefun candidate core, and boots the canonical stack twice on both Paper 26.2 and Paper 26.3. Bundle revision 89 is the final release-source refresh; it intentionally changes no addon policy and exists to force the canonical bundle and reproducible-release validation to rerun against the exact documentation-locked release SHA. Release-source integrity

4.1.60 makes the core JAR and addon bundle source relationship explicit and release-blocking.

The addon bundle manifest records core_source_commit.
The reproducible release workflow only accepts a successful canonical addon-bundle workflow run whose headSha exactly equals the core release GITHUB_SHA.
The release workflow rejects a bundle whose manifest core commit differs from the release commit.
Ordinary addon-bundle builds no longer mutate already-published Slimefun Legacy releases.
Candidate validation may run automatically, but GitHub Release publication is manual-only through explicit workflow dispatch.
Publication is limited to the canonical raw core JAR plus the validated canonical addon ZIP.
The core release build is performed twice from the exact source commit and must be byte-for-byte identical before publication can continue.
Java 21 remains the distributable bytecode target while the maintained build/runtime toolchain uses Java 25.

Release-note changes now trigger the canonical addon-bundle build and reproducible candidate validation, preventing a documentation-only release-prep commit from silently changing the final release SHA without rebuilding the matching bundle. Performance diagnostics

The live profiler now gives administrators more useful evidence before changing machine behavior.

/sf tick top item rows include P95, maximum single-machine time, and the coordinate of the hottest machine for each displayed item type.
Requested detailed samples collect named EnergyNet internal phases only while profiling is active, so normal ticks and aggregate telemetry keep the existing low-overhead path.
Energy regulator samples now separate network discovery, generator work, capacitor supply, consumer distribution, remainder storage, transport-state synchronization, and hologram work.
Generator time remains separately profiled and excluded from the regulator's item timing exactly as before; the phase view is diagnostic context rather than a change to EnergyNet accounting or gameplay.
These diagnostics are intended to distinguish one pathological machine/network from a broad addon-wide slowdown before optimization work is attempted.

CI and infrastructure hardening

Compatibility evidence is now more resistant to infrastructure noise without hiding real regressions.

Required addon Maven compatibility builds retry only recognized transient repository/network failures such as HTTP 429/5xx, connection resets, timeouts, and temporary DNS failures.
Retry attempts refresh dependencies and retain immediate failure for real compile/linkage errors.
Required addon compatibility concurrency was reduced to lower repository pressure.
Paper 1.21.11 API compile validation similarly retries only recognized transient repository/network failures.
Exact addon-bundle full-stack workflow_run validation has its own concurrency identity so unrelated master pushes do not cancel the provenance run.
Failed/cancelled addon-bundle source runs are ignored by the exact-bundle full-stack handoff instead of creating misleading missing-artifact failures.
The Velocity 26.2 identity/persistence smoke now waits for the requested Doctor research-state line before evaluating the result, preventing a partial-console-output race from being reported as lost research.
The hardened proxy matrix passed in workflow run 35935589786: Velocity modern + Paper 26.2, Velocity modern + Paper 26.3, and archived Waterfall + Paper 26.2 all completed successfully.

Platform policy

The supported platform policy is unchanged for this release.

Production baseline: Paper 26.2.
Supported compatibility floor: Paper/Purpur 1.21.11.
Secondary validation: Purpur/Folia/Leaf 26.2, with Folia remaining experimental.
Proxy path: Velocity modern forwarding remains the maintained proxy path.
Paper 26.3: remains an alpha/pre-release compatibility target and is not promoted to the production baseline by 4.1.60.

A stable Paper 26.3 release and an explicit baseline-promotion decision are still required before changing the production support line. Compatibility and persistence safety

4.1.60 does not intentionally change:

Slimefun item IDs;
research IDs;
storage keys;
database schema;
saved-world format;
normal Cargo/Energy behavior;
normal machine recipes or processing semantics.

The release-blocking previous-stable compatibility baseline is the exact released 4.1.59 commit:

3169bb8c67973b16c46316fdc4fe875df88351d1

The canonical 4.1.60 release is expected to publish exactly: Slimefun-Legacy4.1.60.jar SF_Addons_1.21.11-26.3.zip Please go to https://github.com/wickidcow/Slimefun-Legacy/releases/tag/v4.1.60 to obtain fully supported plugin addons.