Admin Diagnostics, Storage Integrity & Curiosities

Slimefun Legacy 4.1.46 expands administration, diagnostics, storage safety and built-in expedition gameplay for modern Slimefun servers. It gives server owners better tools for finding expensive machine areas, inspecting ownership, isolating problematic tickers and safely diagnosing or repairing orphaned secondary storage rows, while Adventurer's Curios gains the new Arachnid Ward Torch for non-lethal cave protection. The release preserves Slimefun's established item IDs, machine data model and addon-facing compatibility goals. 🕷️ Arachnid Ward Torch

Added the Arachnid Ward Torch to the built-in Adventurer's Curios collection.
Hold it in either hand for an 8-block mobile ward while exploring caves and mineshafts.
Place it as a Soul Torch for a larger 12-block stationary ward around tunnels, mines and work areas.
Spiders and Cave Spiders inside active coverage drop protected-player targets and are pushed away instead of taking damage.
Held and placed coverage does not stack. Where both affect the same spider, only one repel impulse is applied and the larger placed ward takes priority.
Spider jockeys are displaced naturally through the spider mount.
Protection uses loaded Slimefun block data plus bounded local entity checks. It does not perform global entity scans or force-load chunks.
Held and placed radii are configurable in configSFLAddons.yml; setting either radius to 0 disables that mode, and values are safety-clamped to 32 blocks.

🧭 Chunk and ownership diagnostics

Added /sf chunkinfo for inspecting Slimefun data associated with a chunk without brute-force scanning every physical block position.
Reports stored Slimefun block records, unique item IDs, addon ownership, ticker registrations, pending removals and unresolved registrations where available.
Added /sf chunkinfo top and /sf chunkinfo top <world> to rank chunks by registered Slimefun ticker locations.
The hotspot ranking intentionally reports registration density, not measured timing cost; /sf tick top remains the live profiler view.
Newly placed Slimefun blocks now record the placing player's UUID as ownership metadata when possible.
Added /sf owner with query, claim, clear and transfer controls for administrators.
Legacy blocks without ownership metadata remain explicitly unowned until an administrator chooses to claim or transfer them.
Diagnostics do not force-load chunks just to inspect them.

⏱️ Targeted ticker controls

Added /sf tick freeze at and /sf tick unfreeze at to pause or resume the ticking machine a player is looking at.
Added /sf tick freeze <ITEM_ID> and /sf tick unfreeze <ITEM_ID> to pause or resume one ticking Slimefun item type server-wide.
Added /sf tick frozen to report global pause state, targeted machine pauses, targeted item-type pauses and circuit-breaker pauses separately.
Targeted pauses skip future callbacks instead of queueing them for replay, avoiding a resume-time backlog spike.
Paused machines stay registered and their stored data is not removed or rewritten.
Existing global /sf tick freeze and /sf tick unfreeze behavior remains available.

🗄️ Storage integrity diagnostics

Added /sf doctor storage status and /sf doctor storage scan for explicit backend ownership checks.
The scanner compares normal block and universal primary records with their secondary data and inventory owners.
Reports orphan secondary owners in BLOCK_DATA, BLOCK_INVENTORY, UNIVERSAL_DATA and UNIVERSAL_INVENTORY without scanning Minecraft blocks or force-loading chunks.
Scans are on-demand only and use the existing storage read executor.
Active write queues and deferred delayed-writing queues are sampled at both scan boundaries so a noisy storage state is never treated as repair evidence.

✅ Two-pass confirmation and repair planning

A single scan is never enough to authorize repair.
Pass 1 records the exact orphan-owner sets from all four secondary storage scopes.
Pass 2 requires an exact matching quiet scan at least 30 seconds later; matching counts alone are not sufficient.
Candidate drift or non-quiet storage invalidates confirmation.
/sf doctor storage plan [page] renders the complete confirmed scope-qualified candidate set in bounded pages.
Every confirmed plan receives a stable SHA-256 fingerprint of the exact candidate set.
/sf doctor storage verify <full-fingerprint> performs a fresh read-only revalidation and creates a short-lived final verification window only when the exact candidate set and quiet-boundary checks still match.

🛡️ Guarded orphan-secondary repair

Added /sf doctor storage repair <full-fingerprint> as the final explicitly destructive step.
Repair requires the existing exact-match 2/2 confirmation, the exact full SHA-256 plan fingerprint and a current successful final verification.
The successful verification is consumed once a destructive repair attempt is accepted.
Slimefun acquires final read and write-submission barriers and re-scans the exact candidate set immediately before mutation.
Repair refuses candidate owners that are still represented by loaded Slimefun block or universal data.
A mandatory lossless backup is written before any delete begins; backup failure aborts the repair.
Backup records preserve every selected field with explicit type information and Base64 encoding, including binary inventory payloads.
Repair deletes only verified orphan secondary rows. It never deletes BLOCK_RECORD or UNIVERSAL_RECORD primary roots.
Targeted owners are checked again after deletion, and the confirmation state is reset after the attempt so stale evidence cannot be reused.
If deletion fails after mutation starts, the backup is retained and the server logs a high-visibility warning rather than silently retrying.

Delayed-writing requirement for destructive repair

Read-only scan, confirmation, plan and verification support delayed writing normally. The destructive repair command in 4.1.46 deliberately requires delayedWriting.enable: false in block-storage.yml followed by a restart. This fails closed rather than risk a deferred mutation being created outside the final write barrier and recreating a row after cleanup. 📖 Guide and contributor hardening

Fixed Guide Style switching when Settings & Info is opened without a physical Slimefun Guide in the main hand.
Prefers an actual off-hand guide when present and otherwise keeps temporary session-guide state separate from unrelated held items.
Hardened the Contributors / Founders menu so malformed or blocked player-head textures fall back safely instead of preventing the menu from opening.
External contributor skin resolution is disabled by default and can be explicitly enabled with a bounded lookup timeout.
Added administrator controls for blocked contributor-head names.

🧩 Compatibility and runtime safety

Restored the SlimefunItemStack compatibility bridge needed by older addon code while keeping the behavior narrowly scoped.
Paper 26.2 remains the primary supported platform.
Purpur 26.2 is supported.
Folia 26.2 remains experimental, with region-owned scheduling retained for machine and chunk-sensitive callbacks. Arachnid Ward physical sweeps remain local to the owning chunk on Folia.
Paper/Purpur 1.21.11 compatibility remains covered by release gates.
Built with Java 25 and verified to a Java 21 bytecode target.
Public API compatibility, representative addon compatibility, runtime gameplay correctness, Paper 26.2, Paper/Purpur 1.21.11 and Purpur/Folia/Leaf runtime smoke gates remain release requirements.

📦 Updated addon bundle

SFL_AddonsNDependencies.zip has also been refreshed with the current validated builds, including:

Supreme 1.0.3
Slimefun Warfare 1.0.5
Galactifun 1.0.5
Networks Expansion 1.0.13
FluffyMachines 26.2.11
MobCapturer 1.0.4
FastMachines 1.0.3
Genetic ChickEngineering 1.0.1
Military Arsenal 1.1.6
RykenSlimeCustomizer 3.1.7-Legacy4

📦 Release assets when on Github.com/wickidcow

Slimefun-Legacy4.1.46.jar
SFL_AddonsNDependencies.zip

The reproducible-release workflow builds the JAR twice from the exact source commit and requires byte-for-byte equality before publishing. Release refreshes preserve the already validated current 4.1.46 addon bundle rather than rolling it backward.

The storage repair command is intentionally conservative. Review /sf doctor storage plan, retain normal server backups and only use destructive repair for a fully confirmed orphan-secondary plan you understand.