• 9.0.0-alpha.5 6cd6e9af32

    Pre-Release 9.0.0-alpha.5
    Some checks failed
    virustotal.yml / virustotal (release) Has been cancelled
    Create GitHub Pre-Release after GitLab tag mirror / Preparations (push) Waiting to run
    Create GitHub Pre-Release after GitLab tag mirror / JAR and media (push) Blocked by required conditions
    Create GitHub Pre-Release after GitLab tag mirror / PreRelease (push) Blocked by required conditions
    Create GitHub Pre-Release after GitLab tag mirror / News on Discord (push) Blocked by required conditions
    Test / build (push) Waiting to run
    Pre-release

    Griefed released this 2026-08-15 20:05:04 +02:00 | 0 commits to main since this release

    9.0.0-alpha.5 (2026-08-14)

    ✂️ Refactor

    • Remove dead code after modscan-rewrite (0df7b28)
    • api: build ScannedMod complete instead of assigning into it (7a37426)
    • api: compare scanned mods by jar, not by filename (8d0022c)
    • api: read the exclusion filter once instead of three times (198ff2b)
    • api: remove the unreachable copy-loop from the Quilt arm (9459b0c)
    • api: rename ScanResult.kt to ScannedMod.kt (4793620)
    • clientside: rename Sideness to DeclaredSupport (90fed95)

    📔 Docs

    • close out the audit after the tidy-up branch (6a88369)
    • correct the stale app and web-frontend test counts (13d63a9)
    • move the dated narrative history out of CLAUDE.md into REFACTOR-LOG.md (0e31fd2), closes gitlab-runner#27496
    • record the I-6 fix and correct the suite count (39a285c)
    • record the modscanning hardening and correct the modloader-fallback claim (1f93755)
    • update the refactor audit to reflect the remediation (51a8db3)
    • api: correct ReadmeExamplesTest's stale and invented references (3fabed7)
    • api: document the scanned-mod types (d6b86ee)
    • clientside: record why DeclaredSupport and Sideness stay separate (6fc8c26)
    • grinder: add a clone-to-results quickstart (385532b)

    📦 Other

    • Add clientside-only mods to the list. Thanks to @ModernGamingWorld @szszabi2002 @Joly0 for the reports! (5a03123)
    • api: drop the unused SupportedModloaders.quilt import (d9a9778)

    🦊 CI/CD

    • run the frontend Vitest suite as part of check (33a6361)
    • deps: bump org.jetbrains.kotlin:kotlin-test-junit5 (f4e4e20)
    • deps: bump org.junit.platform:junit-platform-launcher (3b17c1f)

    🧪 Tests

    • Use correct syntax to test contents (d185fd7)
    • api: pin auto-exclusion and Quilt de-duplication in ModListCompiler (7279962)
    • api: pin dependency extraction and Forge platform-side inference (5eb1edd)
    • api: pin that an unrecognised modloader still yields every mod - RED (b8f809f)
    • api: pin that the dependency rescue reaches clientside mods - RED (d8dfeb4)
    • api: pin the Quilt arm against a fabric-only jar (581ca46)
    • api: pin the SERVER default for a descriptor without an environment (793b8fc)
    • api: pin the unreadable-jar sideness and modID fallback (010db69)

    🛠 Fixes

    • Aggregate Quilt-scan results to prevent double-entries (35cb727)
    • Prevent duplicate entries (7004f3c)
    • Prevent the modID being the same by acquiring it from the mod-file (2ec5ff2)
    • Quilt mod with no env is not treated as SERVER (bf226c2)
    • Vastly improve automated modscanning to catch and process sideness more reliably, as well as taking care of dependencies (0a12d41)
    • api: include every mod when the modloader is unrecognised (2eafe1b)
    • api: let the dependency rescue reach clientside mods (35c5787)
    • api: log the Quilt entry being replaced, not its replacement (b855873)

    About Pre-Releases

    Do not release or publish a server pack generated using a pre-release of ServerPackCreator to your users.
    If you do, and it turns out that your server pack doesn't work because of a bug in ServerPackCreator, that's on you for using a pre-release.

    When using pre-release installers, make sure to uninstall the previous pre-release first. Otherwise, the installers
    own version checks may trigger an error out of my control. After uninstalling, install the newly downloaded one and
    you're good to go.

    Only use the installers if you are versed in system-administration, manually editing and removing services, editing registries,
    so on and so forth.

    Alphas

    Alphas are feature-incomplete and very likely to have bugs. Consider them broken by default. Use at your own risk!

    Betas

    Betas are feature-complete and probably have bugs. Additional features may be added during the beta-phase of any given release, though.


    If you are updating from version 5 or older and used the installers, then make sure to uninstall any previous version(s)
    before using the installers for versions 6 and newer.

    Additional Installer-Notes

    It is recommended to have administration-privileges when using the Windows and macOS installers.
    I am not a member of the Apple Developer Program and won't pay for codesign-certificates, therefor installers are unsigned.
    Running a given installer may produce warnings depending on what OS you are using. You may choose to install it anyway, please be aware though that doing so is, in general, not a safe practice. For ServerPackCreator, though, it is unfortunately the only way to run the installer.

    macOS DMG

    MacOS will complain about potential security risks and refuse to install and run ServerPackCreator. To circumvent this, please see the official guides depending on your version of macOS: Ventura, Monterey or newer.

    Windows EXE

    Hit "More information" if the Windows SmartScreen-message pops up. Afterward, a button will appear which will let you run the installer anyway.

    Downloads