OUKA
Xhigh ModelFabric mod
The Xhigh model.
The Sovereign Mod Marketplace.
ALGORAB 6Six marks. Hover or tap one to read about it.
Fabric mod
The Xhigh model.
Algorab Store 3.0
Press a card and it grows into its article; press Get and the ring turns. The real app's flow, with nothing downloaded.
The Sovereign Predator of Reality · Beyond Ouka
→The Xhigh model.
→The High model.
→The Vernal Genesis: Refined Essentials for Every Journey.
→Palworld Dedicated Server Core · Zero Client Mod
→Luxury, lightweight, Minecraft-style optimisation.
→0
Everything is up to date
Demo · a simulation for this website. Nothing is downloaded.
Available now
Algorab is a desktop app that keeps your mods up to date automatically, verifying every download against this Wiki by SHA-256 - the Wiki remains the only source it trusts.
macOS 14 or later, Apple silicon · Swift and SwiftUI
734b20e9984ecf263c54c8312728bf667557f572b1f36d7fa982500d9580d454Windows 10 or later, 64-bit · C++20 and Qt 6.5 or later
12a8a574c04cd68afcdce38068ffca3693d5f79eec0af5fa1ae1e5349a9d7eec64-bit Linux · C++20 and Qt 6.5 or later
4e2e51f5897f16af4a622bb9e843decd846cd1ff25d701843b0ccdc9dccf93f1Support for the Java version of Algorab Store is ending. Algorab 6 replaces it.
Max Model · Fabric mod
The Sovereign Predator of Reality · Beyond Ouka
Available · 1.6.1945 · Minecraft 26.3 · Fabric
Halia →Medium Model · Vanilla++ Essential
The Vernal Genesis: Refined Essentials for Every Journey.
Available · 2.4.2009 · Minecraft 26.3 · Fabric
Tsubomi →Server-Side Engine
Palworld Dedicated Server Core · Zero Client Mod
Available · 1.0.0 · Palworld · Dedicated Server
Noctua →Optimisation mod
Luxury, lightweight, Minecraft-style optimisation.
Available · 2.0.0 · Minecraft 26.3 · Fabric
Aureum →A new app for macOS, Windows and Linux. It replaces Algorab Store on Java.
Algorab is a small desktop app that keeps your mods up to date automatically. It checks this Wiki for the current release, downloads updates for you, and verifies every file it downloads against a SHA-256 checksum published here before it touches your mods folder. This Wiki is the only source it trusts.
This guide was written for earlier versions of Algorab. Algorab Store 3.0 has new screens, so some steps may differ.
Keeping mods up to date by hand means re-visiting the Download page, comparing version numbers, downloading a new file, and putting it in the right folder every time a release ships. Algorab automates that: it reads this Wiki's release manifest, compares it against what you already have installed, and fetches only what's changed.
Every download the launcher makes is checked against a SHA-256 checksum published by this Wiki before it's used. If a downloaded file doesn't match, the launcher will not install it. The Wiki is the launcher's only source of truth for what the "current" release is.
If you've already installed mods manually, you don't need to start over. On first run, the launcher lets you choose the folder your mods already live in instead of creating a new one. Point it at your existing mods folder and the launcher will treat that installation as the one it manages from then on.
In automatic mode, the launcher checks this Wiki's release manifest on its own and installs new versions as soon as they're available, so your pack folder stays current without you having to do anything.
In manual mode, the launcher still checks for updates, but waits for you to review and confirm before it downloads or installs anything — useful if you'd rather choose exactly when an update lands, for example to avoid interrupting a play session.
As of version 1.1.0, clicking Update writes the new mod files directly into your pack's mods folder, and the launcher will not show "Update complete" unless it has re-checked the folder afterwards and confirmed the expected files are really there. If something goes wrong partway through, it reports failure instead of a false success.
To see the change for yourself on macOS: open the folder shown under General (⌘+⇧+G in Finder, then paste the path), look inside mods, and check the version number in each cherry-*.jar filename before and after clicking Update.
If you're updating from a pack folder that was last touched by a launcher older than 1.1.0, the very first update may leave one old-versioned jar sitting alongside the new one for that mod (the launcher didn't yet have a record of which files it had previously placed). This clears up on its own from the next update onward. If it bothers you sooner, it's safe to delete the older-numbered cherry-*.jar by hand once the new one is confirmed present.
If an update leaves your pack in a state you don't want — a mod misbehaving, or an update you'd rather undo — the launcher keeps a backup of your previous pack state so you can restore it. Use the launcher's restore option to roll your pack folder back to the backed-up version rather than trying to fix files by hand.