Amethyst Mod Manager 2.5.3 Reaches General Availability
Amethyst Mod Manager keeps moving. ChrisDKN shipped v2.5.3 today, a release that nudges the Linux-native mod tool toward nearly 100 supported games and adds two things modders have wanted: mod-update rollbacks and a bit of privacy hardening.
The core pitch hasn't changed. Amethyst is a Qt-based manager written from the ground up to work natively on Linux, SteamOS, and the Steam Deck, rather than being a Windows tool dragged through Proton. It talks to Nexus Mods and Thunderstore, sorts plugin load orders with a bundled copy of libloot, and deploys mods via symlinks, hardlinks, or a virtual file system so your base install stays clean and restorable. As its author puts it, it's "a native Linux mod manager for a variety of games."
That's a modest description for something that now claims coverage of roughly 90 explicitly listed titles. It spans Bethesda games, Cyberpunk 2077, Baldur's Gate 3, the RE Engine family, Stardew Valley, and a widening set of Unreal Engine 5 and BepInEx titles. The new additions in 2.5.3 are Voices of the Void, The Witcher 3: Remastered, and Balatro.
What's actually in 2.5.3
The standout feature is the mod-update rollback. You can now revert a bad upgrade straight from the change-version menu, which keeps you from digging through history to find a working state. Pair that with a new ignore-update flag in the Nexus right-click menu, and you've got a fair amount of control over how mods behave across updates.
There's also a script-extender version warning for Skyrim SE and Fallout 4. Amethyst will flag a mod when its script-extender DLL targets a different game version than what you've deployed. It's the sort of thing that catches a mismatch before it becomes a broken load order at 2 a.m.
Privacy is the other theme. System usernames are now redacted from generated logs, which matters if you've ever pasted a log into a support thread and accidentally handed over your login name. A handful of smaller touches round it out: configurable date formats for non-MM/DD locales, collapsible framework banners, and the ability to group mods into an empty or "cosmetic" container instead of forcing you to start with an installed mod.
Performance is where this release earns its keep, honestly. A long-standing bug let LOOT sorting time out and stall for nearly three minutes on big lists. That's gone, along with related stalls. Amethyst also fixes Wabbajack crashes triggered by overly long paths and an Oblivion file-timestamp bug that kept loose files from loading.
One quirk worth flagging. Drag-and-drop behavior changed so mods dropped into a collapsed separator land at the top rather than the bottom, so glance at the changelog once before assuming your order shifted on you.
Where things stand
v2.5.3 is the latest in what's been an aggressive 2.x cycle. It follows v2.5.0's Wabbajack support on Sep 18, a Hades update four days later, and a September 25 patch before landing today's release. The broader line has taken in a from-scratch Qt rework, a third deploy method via VFS, and a full conflict-detection rewrite, pushing the repo past roughly 2,779 commits. Three have since advanced past commit a043afe on main, if you're tracking.
The release cadence does make you wonder what comes next. v2.4.0 reworked conflict detection; v2.3.0 added Elden Ring and VFS support. Amethyst is reinforcing itself as one of the most ambitious Linux-native mod managers out there, though the single-maintainer model keeps it in a fragile spot no matter how polished the updates get.
If you're on Linux and tired of running Windows-only managers through Proton, it's worth a look. Keep in mind that Amethyst may prompt for a keyring password to store your Nexus API key, but that stays in your OS keyring rather than plain text. It's available as an AppImage, Flatpak, and AUR package, with RPM and ZST builds also floating around.
Head here to the release page for the installer script and Flatpak reference, along with a full changelog if you want to dig into the details yourself.
