Skip to content

Slimefun Legacy 4.1.36

Choose a tag to compare

View all tags
@github-actions github-actions released this 23 Aug 02:13
v4.1.36
1cfb60c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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

Assets 3
Loading