Slimefun Legacy 4.1.45

Slimefun Legacy 4.1.45 — Automation & Energy Performance

Slimefun Legacy 4.1.45 is a focused performance and maintenance release based on live AlbionMC profiling. It trims repeated work from two of the next most visible hot paths while keeping established machine behavior, addon integrations, item metadata, and saved-world compatibility intact.

⚙️ Enhanced Auto Crafter

• Reuses the custom crafter interactor resolved for the current ticker pass instead of repeatedly reading the same block storage.
• Reuses stable per-pass machine values such as location and energy cost where safe.
• Keeps the defensive energy re-check after addon callbacks before committing a craft.
• Leaves existing recipe predicates, virtual-item handling, output-fit checks, and full ItemStack output cloning unchanged.
• Adds a null guard when resetting custom crafter integration state after block removal.

⚡ Energy Regulator / EnergyNet

• Avoids repeatedly walking connector/player-head presentation state while the network transport state has not changed.
• Topology and powered-state changes still refresh immediately.
• Adds staggered periodic revalidation so external or vanilla state changes are reconciled without forcing every loaded regulator to perform the same connector walk every cycle.
• Actual energy discovery, routing, transfer, capacity, and stored-energy semantics remain unchanged.

🧩 Compatibility and safety

• Paper 26.2 remains the primary supported platform.
• Purpur 26.2 is supported.
• Folia 26.2 remains experimental.
• Paper/Purpur 1.21.11 compatibility remains covered by the release gates.
• Built with Java 25 and verified to a Java 21 bytecode target.
• Existing addon-facing Slimefun APIs, item IDs, storage formats, and saved-world data are unchanged by this performance pass.

📦 Addons & dependencies bundle

This release also includes SFL_AddonsNDependencies.zip, the current Slimefun Legacy addon/dependency bundle carried forward from the validated 4.1.44 bundle.

The ZIP is provided as a convenient tested starting set for Slimefun Legacy servers. It is not required to run the Slimefun core, and server owners should still review the included addons, keep only the ones they actually use, and back up their server before replacing plugin files.

Release assets

• Slimefun-Legacy4.1.45.jar
• SFL_AddonsNDependencies.zip -BE SURE TO CHECK FOR NEW PLUGIN UPDATES!

This release intentionally stays narrow: measured automation and EnergyNet hot-path cleanup first, with larger recipe-matcher or inventory-indexing changes deferred until they can be proven safe for custom items and third-party addon behavior.

Slimefun Legacy 4.1.44

Slimefun Legacy 4.1.44 — Resonance Beacon Performance

Slimefun Legacy 4.1.44 formalizes the Resonance Beacon performance work validated on AlbionMC. The goal is to preserve every Beacon power and existing world while removing repeated work from the one-second ticker path.

Resonance Beacon runtime

• Added resolved Beacon-state caching so pyramid/profile, configured powers, effective tiers, and range are reused instead of repeatedly rebuilt during normal effect checks.
• Separated Beacon work into independent cadences: energy/lifecycle stays responsive while potion effects, utility effects, maintenance, tile boosts, crop growth, and Gravity Well work run on appropriate schedules.
• Distributed Gravity Well work across four slices to avoid concentrating entity scanning into one ticker pulse.
• Player field-state refresh now follows chunk transitions and explicit Beacon lifecycle/configuration changes instead of recalculating on every block-coordinate movement.
• Peaceful behavior relies on the existing event-driven protections plus explicit reconciliation when a Beacon becomes active or its configuration changes.
• Beam rendering is viewer-aware and bounded, cutting powered visual particle dispatches while leaving gameplay and energy behavior intact.
• Added /beacon perf and /beacon perf reset for focused runtime timing of state/cache, energy, visuals, player effects, monster effects, Gravity Well, furnace/spawner work, and crops.

Live production validation

AlbionMC live profiling with seven loaded BEACON_PLUS blocks measured:

• Pre-optimization sample: 8.17 ms total / 1.17 ms average per Beacon in a 0.5-second /sf tick top window.
• Post-optimization samples: 0.48 ms, 0.73 ms, and 0.42 ms total for the same seven-Beacon count.
• Three-sample post-optimization mean: 0.54 ms total / ~0.078 ms per Beacon.
• Observed reduction versus the 8.17 ms baseline: about 93% in Beacon ticker time.
• Slimefun core in those three post-optimization samples averaged ~7.30 ms, versus 14.56 ms in the earlier comparison sample.

These are production observations from one server workload, not a universal performance guarantee. Exact cost varies with configured powers, loaded chunks, entities, crops, viewers, hardware, and other plugins.

Focused Beacon timings after reset

The clean post-reset diagnostic window reported:

• State/cache: 1.2241 ms average, 14 samples
• Energy: 0.0043 ms average, 154 samples
• Visuals: 0.0078 ms average, 154 samples
• Player effects: 0.0012 ms average, 93 samples
• Monster effects: 0.0591 ms average, 33 samples
• Gravity Well: 0.0503 ms average, 89 samples
• Furnace/spawner: 0.0323 ms average, 55 samples
• Crops: 0.1058 ms average, 55 samples

The result is that Gravity Well no longer justifies being split into a separate machine, and player-effect/visual costs are now negligible enough that further Beacon changes are not currently warranted.

Behavior preserved

• BEACON_PLUS item/block ID and saved data are unchanged.
• All existing Resonance Beacon powers remain available; Gravity Well remains a Beacon power.
• Existing pyramid requirements, resonance behavior, Extra Range/Extra Power semantics, electric mode, and energy demand remain intact.
• Existing addon-facing Slimefun APIs are unchanged by the Beacon performance work.
• Paper 26.2 remains the primary runtime target, Purpur 26.2 is supported, and Folia 26.2 remains experimental.

Next performance targets

With Beacon cost reduced, the next production profiling targets are Energy Regulator and Enhanced Auto Crafter. No additional Beacon optimization is planned unless live data shows a new regression or a specific effect becomes dominant again.

Slimefun Legacy 4.1.43

Slimefun Legacy 4.1.43 — External Model Compatibility

Slimefun Legacy 4.1.43 is a focused compatibility update for addons that borrow visual models from ItemsAdder or other custom-item systems.

Fixed

• Preserve an item's existing CustomModelData when Slimefun has no custom model override configured for that Slimefun ID.
• Prevent SlimefunItemStack.clone() from indirectly stripping externally supplied model data from real player-held items.
• Restore correct held-item visuals for addon weapons that use an ItemsAdder base material/model while retaining their Slimefun identity.

Addon compatibility

This specifically supports the corrected ItemsAdder integrations in:

• SF_SlimefunWarfare 1.0.3
• SF_MilitaryArsenal 1.1.5

Military Arsenal 1.1.5 also identifies the Antimatter Rifle by its Slimefun ID instead of requiring the original vanilla material, so applying an ItemsAdder model no longer disables rifle firing or cooldown handling.

Behavior preserved

• Explicit Slimefun custom model mappings still override the item with the configured model data.
• A Slimefun model value of 0 now means "no Slimefun override" rather than "erase external model data."
• Existing Slimefun IDs, recipes, saved data, machine behavior, and addon APIs are unchanged.

Platform targets

• Paper 26.2 — primary
• Purpur 26.2 — supported
• Folia 26.2 — experimental
• Java 25 build/runtime validation
• Java 21 bytecode target

Slimefun Legacy 4.1.42

Slimefun Legacy 4.1.42 — Beacon Performance

Slimefun Legacy 4.1.42 is a focused production-performance update built from the 4.1.41 stable baseline. It targets the remaining periodic Resonance Beacon (BEACON_PLUS) cost seen in live AlbionMC profiling without changing established beacon gameplay, storage, or addon-facing behavior.

Resonance Beacon performance

A live /sf tick top sample on the 4.1.41 production line measured:

• total Slimefun ticker-profiler time: 30.88 ms across 2,996 blocks
• Slimefun-owned ticker time: 14.70 ms across 230 blocks
• BEACON_PLUS: 7.33 ms across 10 beacons, or 0.73 ms average per beacon

4.1.41 had already removed unnecessary full chunk-entity scans for player-only beacon powers on Paper-family servers. The remaining hot path included the powered yellow beam renderer.

4.1.42 beam dispatch optimization

• Reduce the powered full-height beam from a maximum of roughly 82 Bukkit particle dispatch calls per beacon pulse to 30 on tall worlds.
• Cap vertical beam sampling at 22 dust segments instead of 64.
• Keep electric sparks at every fourth retained segment, for at most 6 segment spark calls.
• Keep the existing two core/aura particle calls.
• Increase the vertical spread and bounded dust count of retained segments so the beam still visually fills the world-height column instead of simply deleting most of the visual.
• Keep work bounded for custom-height worlds rather than letting particle API calls grow with world height.

For 10 powered beacons, the renderer's maximum server-side particle API dispatches drop from roughly 820 to 300 calls per one-second pulse window before accounting for beacon staggering.

This is a source-level dispatch reduction. A new post-fix millisecond result is intentionally not claimed until the release JAR is measured on a live server under comparable conditions.

Behavior preserved

This update does not change:

• the historic BEACON_PLUS item/block id
• Resonance Beacon ownership or saved-world data
• the 29 configurable power behaviors
• pyramid tier requirements or material resonance
• beacon range or Extra Range behavior
• electric-mode power demand or consumption
• the once-per-20-game-ticks gameplay pulse cadence
• Gravity Well strength or entity eligibility
• player, monster, furnace, spawner, crop, XP, repair, flight, or other effect semantics
• addon-facing Slimefun APIs

The 4.1.41 player-only fast path, deterministic startup pulse staggering, potion refresh de-churn, tile-entity cache, placement spacing, interaction routing, and existing gameplay correctness gates remain intact.

Release baseline

• Candidate: 4.1.42
• Previous stable regression baseline: 4.1.41 at 2b0a30bd11f05bee0b434da21097fbc8b50234f3
• Historical compatibility floor: 4.1.15 (advisory)

Platform targets

• Paper 26.2 — primary
• Purpur 26.2 — supported
• Leaf 26.2 — Paper-family runtime coverage
• Folia 26.2 — experimental
• Paper/Purpur 1.21.11 — compatibility coverage retained
• Java 25 build/runtime validation
• Java 21 bytecode target

Release asset

• Slimefun-Legacy4.1.42.jar

4.1.42 deliberately remains a targeted maintenance release. No broad machine rewrite, migration, item-id change, or saved-data conversion is included.

Slimefun Legacy 4.1.41

Slimefun Legacy 4.1.41 — Maintenance & Compatibility

4.1.41 continues from the 4.1.40 stable production baseline with targeted maintenance, Paper 26.2 compatibility hardening, diagnostics fixes, and measured performance improvements.

Performance and stability

• Correct negative-Y coordinates reported by /sf tick top.
• Reduce Electric Smeltery idle ticker overhead without changing recipes, speed, energy, output, or cargo behavior.
• Cache Slimefun Auto Crafter recipe wrappers so selected recipes do not rebuild ingredient predicate objects every machine tick while still reading each machine's stored recipe id and enabled state live.
• Reuse one vanilla inventory snapshot for each complete Auto Crafter recipe match instead of calling Inventory#getContents() for every ingredient predicate.
• Reuse one Smart Port inventory view per temporary crafter interactor and one Smart Port contents snapshot per recipe match, avoiding repeated BlockMenu#toInventory() and inventory snapshot work for every ingredient.
• Cache normal-vs-virtual item resolution lazily per candidate slot during each core Enhanced Auto Crafter recipe attempt. Normal stacks go directly to the already-built recipe predicate after their first resolution, while virtual stacks retain the existing virtual-item-aware matching path. The optimization is intentionally restricted to the exact core EnhancedAutoCrafter class so addon subclasses and custom matching overrides are unchanged.
• Remove a duplicate storage lookup from CrafterInteractorManager#getInteractor() while preserving its existing null behavior.
• Reuse already validated EnergyNet capacities during charge writes.
• Index registered networks by exact regulator location so Energy Regulator and Cargo Manager tickers avoid scanning the global network list for their own network.
• Cache unchanged vanilla player-head EnergyNet presentation state between ticks. State changes still apply immediately while periodic self-heal validation is deterministically staggered across the 20-tick window to avoid regulator validation bunching.
• Route Resonance Beacon player-only pulse work through the world's player list on Paper-family servers instead of enumerating every entity in every loaded covered chunk. Mob effects and Gravity Well retain full entity enumeration when required, and Folia retains its region-local path.

Live profiler validation

A broader shared Auto Crafter hot-path rewrite was rolled back after live AlbionMC profiling showed the same six ENHANCED_AUTO_CRAFTER machines rise from roughly 1.56 ms to 3.18 ms total. The known-good ticker flow was restored rather than keeping a synthetic micro-optimization that regressed real server performance.

A stable targeted build later measured:

• total ticker time: 18.85 ms across 2,590 blocks
• Slimefun-owned ticker time: 5.36 ms
• ENHANCED_AUTO_CRAFTER: 2.38 ms / 6 machines / 0.40 ms average
• ENERGY_REGULATOR: 1.25 ms / 21 regulators / 0.06 ms average
• ELECTRIC_SMELTERY_2: 0.66 ms / 12 machines / 0.06 ms average

A later 10-tick sample showed the same six Enhanced Auto Crafters at 1.73 ms / 0.29 ms average, but also exposed a periodic BEACON_PLUS sample spike of 9.01 ms across eight beacons. That observation led to the player-only Resonance Beacon pulse-routing optimization above. Short Energy Regulator samples also varied when periodic vanilla-state validation aligned, leading to the staggered 20-tick validation phase.

The latest pre-RC production-side sample measured:

• total ticker time: 19.31 ms across 2,918 blocks
• Slimefun-owned ticker time: 5.69 ms across 178 blocks
• ENHANCED_AUTO_CRAFTER: 2.16 ms / 6 machines / 0.36 ms average
• ENERGY_REGULATOR: 1.55 ms / 24 regulators / 0.06 ms average
• ELECTRIC_SMELTERY_2: 1.16 ms / 13 machines / 0.09 ms average

This latest sample is from the prior live test JAR and therefore does not include the final lazy Enhanced Auto Crafter match-mode cache. The final optimization is release-gated by the full CI matrix rather than requiring another production restart before RC.

Compatibility and behavior

• Include Leaf 26.2 in the Paper-family runtime smoke matrix.
• Add slimefun.update-notifications, defaulting to OP, so operators and explicitly permitted non-OP administrators are notified when a newer published Slimefun Legacy GitHub release is available.
• Restore deterministic Resonance Beacon interaction routing: normal main-hand right-click opens the custom Resonance Beacon menu, sneak-main-hand right-click keeps the yellow beam visual toggle, and off-hand interaction is consumed so vanilla Beacon handling cannot replace the custom menu.
• Require Resonance Beacons to be placed more than three chunks apart in the same world. Placement inside the three-chunk square radius is cancelled before Slimefun creates block data and the player receives a clear too-close message. Activator enable/upgrade behavior is unchanged.
• Add required Resonance Beacon interaction and placement-spacing verification to Runtime Gameplay Correctness CI.
• Harden vanilla Auto Crafter recipe handling for Paper 26.2 build SlimefunGuguProject#120 and Paper commit 1797fbccf1f1afffe934943b76ecb1f8d6c2cfcc, which introduced RecipeChoice.PredicateChoice. Shaped recipe accounting and previews now use the generic RecipeChoice representative-stack contract rather than assuming every choice is MaterialChoice, while actual ingredient matching continues to use the recipe's predicate semantics.
• Preserve existing item IDs, saved-world data, addon-facing behavior, and established gameplay semantics.
• Avoid migrations and broad behavioral rewrites in the 4.1.x maintenance line.

Paper 26.2 build SlimefunGuguProject#120 validation

The final pre-RC source head was boot-tested twice on the real stable Paper 26.2 build SlimefunGuguProject#120 server with Java 25. Both boots completed successfully, /sf doctor upgrade reported no BLOCKED status, and the second boot observed clean-shutdown persistence. The production build, Runtime Gameplay Correctness, Paper 26.2 runtime smoke, Purpur/Folia/Leaf 26.2 runtime smoke, Paper/Purpur 1.21.11 compatibility, Public API Compatibility, and Slimefun/Addons Compatibility gates all passed before the RC metadata rollover.

Platform targets

• Paper 26.2 — primary; stable build SlimefunGuguProject#120 explicitly runtime-tested
• Purpur 26.2 — supported
• Leaf 26.2 — runtime smoke tested
• Folia 26.2 — experimental
• Paper/Purpur 1.21.11 — legacy compatibility tested
• Java 21 bytecode target; Java 25 build/runtime validation

Release candidate

projectVersion and the compatibility registries are aligned at 4.1.41 for the release candidate. The validated 4.1.40 release commit e6561c97862ac0ef2b61a3657467b81edf62aafd is now the release-blocking previous-stable baseline.

No additional feature or performance changes are planned for 4.1.41 after this rollover unless release-gating CI or live RC validation exposes a release blocker.

Slimefun Legacy 4.1.40 — Performance & Stability

Slimefun Legacy 4.1.40 — Performance & Stability

Slimefun Legacy 4.1.40 is the stable production baseline for the current Legacy line, focused on smoother runtime performance, better diagnostics, and keeping established Slimefun behavior intact on modern servers.

⚡ Resonance Beacon performance

• Player beacon potion effects now last 30 seconds and are refreshed only when roughly 15 seconds remain, instead of being reapplied every one-second beacon pulse.
• Expensive furnace/spawner tile-entity discovery is cached for 15 seconds while boosts continue to operate from live block states on the normal gameplay cadence.
• Reuses the same loaded-chunk footprint across beacon effect families instead of rebuilding it repeatedly during one pulse.
• Resonance Beacons receive deterministic startup offsets so multiple loaded beacons do not synchronize their expensive work onto the same tick.
• Player-state cleanup now runs when a beacon actually transitions from powered to unpowered instead of repeatedly rescanning the same area.
• Powered beam rendering is bounded to prevent particle dispatch cost from scaling excessively with world height.
• Existing Gravity Well, furnace, spawner, crop, XP, repair, flight, and other beacon behavior remains active without reducing the normal gameplay pulse rate.

⏱️ Diagnostics and server-owner tooling

• /sf tick top remains available for profiling high-cost Slimefun machines.
• Hotspot reports include actionable machine coordinates so expensive chunks can be located quickly.
• Existing ticker freeze, inspection, circuit-breaker, and compatibility diagnostics remain intact.

🛡️ Stability and compatibility

• Paper 26.2 is the primary supported platform.
• Purpur 26.2 is supported.
• Folia 26.2 remains experimental.
• Paper/Purpur 1.21.11 compatibility checks are retained.
• Built with Java 25 and verified to a Java 21 bytecode target.
• Existing Slimefun item IDs, saved-world data, machine behavior, and addon-facing compatibility remain the priority.

📦 Release asset

• Slimefun-Legacy4.1.40.jar

4.1.40 is intended to be the stable baseline for production servers. Future 4.1.x updates can focus on targeted maintenance, compatibility, and measured performance improvements without requiring disruptive migrations.

✨ Slimefun Legacy 4.1.39 — Search & Tick Tools

✨ Slimefun Legacy 4.1.39

Smarter Search • Safer Ticker Diagnostics

A compact stability update focused on smoother Guide search and better tools for server owners.

🔎 Search Improvements

• Smart Search OFF now uses classic Slimefun search exactly.
• Repeated Search → Back navigation reuses cached results instead of repeatedly rebuilding them.
• Search cache/history is bounded and cleaned up to avoid unnecessary growth.

⏱️ New /sf tick

• Inspect ticker status, machine locations, failing machines, and specific Slimefun blocks/items.
• Use /sf tick top to find expensive machine tickers with the existing profiler.
• Safely /sf tick freeze and unfreeze using Legacy's existing pause system.
• Read the current tick rate without changing live cadence.
• No heavy queue, executor, or broad ticker-path rewrite.

🧩 Compatibility

Paper 26.2 • Purpur 26.2 • Folia 26.2 experimental • Java 21+ runtime target

📦 Slimefun-Legacy4.1.39.jar
🔖 Release build: 0c6959b

Keeping the classic Slimefun4 experience alive on modern Minecraft — with stability first.

Slimefun Legacy 4.1.38 — Test Notification, Wiki & EnergyNet Update

Slimefun Legacy 4.1.38 — Test Notification, Wiki & EnergyNet Update

This 4.1.38 refresh is a test-oriented release for the GitHub update notification path while also carrying the latest Slimefun Legacy Wiki and EnergyNet improvements.

Highlights

• Update notification test: keeps the clean 4.1.38 version format so servers on 4.1.37 can detect a newer published release.
• Beacon Plus Auto Repair hotfix: respects each item's actual custom maximum damage and clamps invalid damage values before repair, preventing Paper's Damage cannot exceed max damage exception with custom gear.
• Legacy Wiki links: Slimefun Guide item Wiki buttons now point to the rendered Slimefun Legacy GitHub Wiki.
• EnergyNet powered heads: player-head EnergyNet components mirror active energy transport to vanilla powered=true/false when the underlying head supports that block state.
• Electrical visualizer: EnergyNet uses yellow INSTANT_EFFECT particles for a more electrical visual while Cargo and other network visualizers keep their existing appearance.
• Chunk-load topology repair: unloaded EnergyNet discovery frontier positions are preserved and retried after their chunks load, fixing nodes that could report Connected but fail to visualize until a neighboring node was broken and replaced.

Compatibility

• Paper 26.2 primary
• Purpur 26.2 supported
• Folia 26.2 experimental
• Paper/Purpur 1.21.11 compatibility checks passed
• Built/tested with Java 25 and verified to Java 21 bytecode target

Release asset

• Slimefun-Legacy4.1.38.jar

Testing note: servers already running a previous 4.1.38 JAR will not receive another update warning because the semantic version is unchanged. Replace the JAR manually to test this refreshed 4.1.38 build. Servers still on 4.1.37 should detect 4.1.38 as newer.

Slimefun Legacy 4.1.37

Slimefun Legacy 4.1.37 — Search Performance, Guide Categories & Energy Visualizer

Slimefun Legacy 4.1.37 is a focused performance, compatibility and quality-of-life release. It substantially reduces repeated work in Slimefun Guide searches, adds addon-friendly guide category inheritance, and adds an opt-in gold particle visualizer directly to the Energy Regulator.

⚡ Guide search performance

Both the classic Slimefun search and the Enhanced Guide now use a shared cached search index.

• Stable searchable metadata such as item name, ID, addon and lore is normalized and cached instead of rebuilt for every query.
• Enhanced search keeps a pre-sorted name view instead of sorting the full registry on every search.
• id:, addon:, group:, category: and recipe: filters short-circuit so unrelated metadata is not resolved.
• Player-sensitive group and recipe labels are resolved lazily only when a query actually needs them.
• Classic search preserves its existing registry-order behavior and result cap.
• Enhanced search preserves smart-search fields, sorting and pagination while doing substantially less repeated work.

This work addresses reports of noticeable MSPT increases while using Slimefun search on servers with large addon registries.

🗂️ Guide category inheritance for addons

Slimefun Legacy now supports optional high-level guide category metadata directly on an ItemGroup.

• Addons can call ItemGroup#setCategory(...) once and every item in that group inherits the declared guide category.
• ItemGroup#getCategoryId() exposes the declared category to guide integrations.
• Canonical category IDs are provided for weapons, tools, armor, machines, energy tech, resources, magic, food, logistics, decoration and misc.
• Enhanced Guide searches can use category: to find every item in a declared category.
• Normal smart searches also consider cached category IDs without adding expensive per-search metadata work.
• Enhanced Guide item lore now distinguishes the traditional Slimefun Group from the new high-level Guide Category.
• Existing addons do not need to opt in, and no existing ItemGroup behavior is removed.

This is an additive compatibility feature inspired by newer Slimefun guide work while preserving Slimefun4's familiar ItemGroup-first guide architecture.

✨ Energy Regulator network visualizer

Right-click an Energy Regulator to open its new visualizer control.

• Toggle the connected Energy Network overlay on or off from the regulator itself.
• Uses a clean warm-gold DUST particle effect.
• The overlay is player-specific; other players do not see your visualization.
• Only one regulator is selected per player at a time.
• Rendering is range-limited, pulsed every 10 ticks and capped at 160 particles per pass.
• The visualizer does not intentionally load chunks.
• The existing legacy blue network display behavior remains available for existing callers.

The feature remains subject to the server's existing network-visualizer configuration switch.

🛡️ Compatibility

No existing Slimefun item IDs, recipes, research IDs, machine storage formats, database schemas or saved-world formats are intentionally changed in 4.1.37. Normal Cargo and Energy transfer semantics remain unchanged.

• Paper 26.2 / Minecraft 26.2 — primary supported line
• Purpur based on Paper 26.2 — supported
• Folia based on Paper 26.2 — experimental
• Paper/Purpur 1.21.11 — compatibility line
• Java 25 — supported production runtime
• Slimefun-owned classes continue targeting Java 21 bytecode

The updated 4.1.37 candidate passed the project build, gameplay correctness checks, Public API compatibility, Paper 26.2 runtime smoke, Purpur/Folia 26.2 runtime smoke, Paper/Purpur 1.21.11 compatibility, cross-fork probes and the full addon compatibility matrix before being merged.

📦 Upgrading

4.1.37 is intended as a straightforward drop-in upgrade from 4.1.36.

1. Stop the server normally.
2. Back up worlds, Slimefun data and databases.
3. Replace the previous Slimefun Legacy JAR with the latest 4.1.37 JAR from this release.
4. Start the server normally.
5. Do not use /reload for the upgrade.

---Note: IE2, SlimeTinker, Dynatech, FastMachines, Fluffy Machines, Networks Exp, and Slimefun Advancements have been updated too!

Slimefun Legacy 4.1.37 — faster guide searches, smarter addon organization, clearer power networks.

Slimefun Legacy 4.1.36

Slimefun Legacy 4.1.36 — The Update Release

Slimefun Legacy 4.1.36 marks an important maintenance milestone for the project. This release introduces a safe, GitHub Releases-only update notification system while also serving as a good snapshot of how far Slimefun Legacy has come from the original Slimefun 4 codebase.

💚 What is Slimefun Legacy?

Slimefun Legacy is an unofficial, independently maintained continuation of Slimefun 4 for modern Paper-based Minecraft servers.

It keeps the familiar Slimefun experience — machines, electricity, Cargo networks, automation, reactors, magic, backpacks, custom tools, equipment, and hundreds of items — without requiring players to install a client mod.

The goal of Slimefun Legacy is not to reinvent Slimefun. It is to preserve the classic Slimefun experience and addon ecosystem while carefully maintaining it for modern servers.

Slimefun Legacy is maintained for AlbionMC and the wider Slimefun community, with respect for the original Slimefun project and the developers and contributors who built the ecosystem that made it possible.

Slimefun Legacy is an unofficial downstream fork and is not an official release of the original Slimefun project, Slimefun United, or the SlimefunGuguProject. It is not affiliated with Mojang or Microsoft.

🛠️ How Legacy has evolved from original Slimefun 4

Since branching from the original Slimefun 4 codebase, Slimefun Legacy has focused primarily on maintenance, compatibility, stability, recovery, and modernization rather than changing what makes Slimefun feel like Slimefun.

General improvements now include:

• Modern Paper support with Purpur compatibility and ongoing Folia work
• A modern Java build/runtime environment while preserving compatibility-focused bytecode targets for addons
• An English-first player experience without requiring Slimefun Translate
• Stronger compatibility safeguards for existing Slimefun addons and legacy API entry points
• Expanded automated compatibility, runtime, API, and release verification
• Safer machine, ticker, inventory, entity, chunk, database, and shutdown lifecycles
• Machine circuit breakers and recovery tools designed to prevent one broken machine or addon callback from destabilizing an entire server
• Improved Cargo and Energy handling, diagnostics, and performance safeguards
• A modernized Enhanced Guide with search, bookmarks, machine recipe browsing, and safer addon integration
• /sf doctor diagnostics for runtime health, dependencies, integrations, storage recovery, compatibility, and item repair
• Better visibility into addon dependency problems, linkage errors, runtime failures, and compatibility status
• Storage and item recovery tools for servers migrating from older or translated Slimefun installations
• Modern scheduler and platform compatibility paths for Paper-family servers
• Rebar/Pylon capability diagnostics without hard-linking experimental external APIs
• Reproducible release verification and stronger release gating
• Continued preservation of legacy item IDs, recipes, saved-world data, machine storage, and addon-facing behavior wherever practical

The overall direction remains simple: keep classic Slimefun alive, stable, recognizable, and usable on modern servers.

🔔 4.1.36: GitHub Release update notifications

The headline feature of 4.1.36 is a dedicated update notification service based only on published GitHub Releases from wickidcow/Slimefun-Legacy.

What it does

• Checks GitHub's official releases/latest endpoint
• Performs the first check asynchronously during server startup
• Rechecks once per hour on long-running servers
• Notifies the console when a newer published Slimefun Legacy release is available
• Can notify online server operators once per release tag
• Understands modern tags such as v4.1.36 as well as older SlimefunLegacy4.x.x tags
• Links directly to the real GitHub Release page
• Ignores ordinary commits, development branches, Actions builds, and draft releases

What it does not do

Slimefun Legacy will never automatically replace or download over the running JAR through this service.

The old community/upstream auto-download route is deliberately disabled, even if an older configuration still contains:

options:
  auto-update: true

Update discovery now stays tied to reviewed, published Slimefun Legacy GitHub Releases.

🧭 Important upgrade note

4.1.35 does not contain this new update checker. Server owners currently running 4.1.35 will need to discover and install 4.1.36 manually.

Once a server is running 4.1.36 or newer, the new notification service can alert operators when later published releases such as 4.1.37 become available.

🛡️ Safe and failure-tolerant

The GitHub request runs away from the main server thread. A GitHub outage, API error, timeout, or temporary network problem will not prevent Slimefun from enabling.

A dedicated verify_github_release_updater.py invariant is now part of the Legacy verification suite to protect the release-only endpoint, asynchronous startup behavior, version parsing, notification behavior, and the disabling of the old updater path.

✅ Compatibility

• Paper 26.2 / Minecraft 26.2 — primary supported line
• Purpur based on Paper 26.2 — supported
• Folia based on Paper 26.2 — experimental
• Paper/Purpur 1.21.11 — supported compatibility line
• Java 25 — supported production runtime
• Slimefun-owned classes continue targeting Java 21 bytecode for compatibility

The 4.1.36 release candidate passed the Legacy build, compatibility, public API, runtime gameplay, Paper 26.2, Purpur/Folia 26.2, and Paper/Purpur 1.21.11 validation gates before release.

📦 Upgrading from 4.1.35

4.1.36 is intended to be a straightforward drop-in upgrade from 4.1.35.

No Slimefun item IDs, recipe IDs, machine storage formats, player-data formats, or database schemas are changed by the new update service.

1. Stop the server normally.
2. Back up your worlds and Slimefun data.
3. Replace the previous Slimefun Legacy JAR with the 4.1.36 JAR.
4. Start the server normally.
5. Do not use /reload for the upgrade.

---

❤️ Keeping Slimefun alive

Slimefun Legacy exists because Slimefun has had an enormous community, addon ecosystem, and development history behind it. This fork aims to preserve that work rather than erase it — keeping the classic gameplay recognizable while doing the maintenance necessary for today's Paper servers.

Thank you to the original Slimefun developers, past and present contributors, addon developers, server owners, testers, and players who continue to keep the ecosystem alive.

Slimefun Legacy 4.1.36 — The Update Release