Amethyst Mod Manager v2.6.4 Ships With V Rising Support and MAKO v5 Integration
The Linux mod manager just got its most feature-dense release. It also runs on one person's calendar.
Amethyst Mod Manager shipped v2.6.4 today, landing exactly one day after its final beta. The stable build tops a 2.6.x series the project is describing as its most feature-dense yet. For a tool kept alive by a single maintainer, that velocity is genuinely impressive.
The headline additions aren't flashy. V Rising joins the supported-games roster, MAKO integration moves to v5, and Proton/UMU launch logs become optional by default. The real substance sits in the five bug fixes. Those address edge cases you only find after actually running a full install, deploy, and recovery cycle.
What changed
V Rising is the one genuinely new entry. It's Stunlock Studios' open-world vampire survival RPG, a game that crossed five million sales earlier this year and plays reasonably on portable hardware. Native support means you can now deploy mods, manage load order, and keep everything on Linux without leaning on a Windows compatibility layer.
The Proton/UMU logging tweak is more housekeeping than feature. Logs used to generate by default every time you launched a Windows game through Proton or the UMU launcher. They're off out of the box now, which trims clutter and disk writes for anyone who doesn't need them. Still on, if you do.
MAKO v5 is a dynamic overload tool that lets you flip between entire load-order setups on the fly. Amethyst has spent a fair amount of effort getting Windows-era mod tooling to behave under Wayland, and this keeps it in step with the newest MAKO release and its API.
The fixes are where this build earns its keep.
Case-sensitive name collisions were the kind of bug that makes you wonder how it slipped through. Mods that differed only by capitalization, like MyMod versus mymod, were sharing file listings and deployment ownership. One mod would quietly take another's files. Not great.
Video playback from the mod-files tab was broken. That's restored, so trailers and previews work again.
A "missing source" error used to break installs of Wabbajack preset lists using legacy BSA filenames. Those lists can bundle hundreds of mods, so unblocking this frees up a large slice of the preset workflow.
Flatpak launch options for gamescope, MangoHud, and GameMode were failing during direct launches, which bites Steam Deck users who go straight from the manager instead of through Steam. A missing game folder previously blocked deployment recovery and removal outright. Both are now handled gracefully.
Keep in mind that these are the unglamorous fixes. They're exactly what separate a reliable tool from a fragile one.
The bigger picture
Under the hood, Amethyst runs on Python and PySide6 for the GUI, with a Rust extension called amethyst_filegraph doing the performance-heavy file work. That's why building from source needs both a Python interpreter and a Rust toolchain.
The headless API is arguably the most powerful feature for advanced users. Backed by JSON-RPC 2.0 over newline-delimited JSON, it lets external apps and scripts drive most functions without opening a GUI or importing Python modules. You can list games, manage profiles, authenticate to Nexus, install collections, sort load order with LOOT, and launch games, all in batches of up to 256 items.
So it's arguably competing with proper paid mod managers on capability, though the lack of a team behind it does temper the enthusiasm a bit. However, at the same time, the software is quite good, and the free-as-in-beer licensing doesn't hurt.
v2.6.4 ships as AppImages and a Flatpak. The x86_64 AppImage is roughly 127 MiB, the aarch64 build (which covers the Steam Deck) lands near 119 MiB, and the Flatpak bundle sits around 95 MiB. The AppImage comes with an auto-updater; run the installer script and the app will flag new releases, then re-run it to update itself.
One caveat with the Flatpak from a bundle: it skips the 32-bit compat extensions that Windows tools like Proton and Wine need. They install automatically on first launch, or you can add them by hand. There's no uninstall script yet, so removal means clearing files from ~/.config/AmethystModManager and sibling folders by hand.
Head here to the GitHub releases page for the full asset list and install links.
