Amethyst Mod Manager v2.4.3 Lands, Fixes Critical Fallout: New Vegas Mod Install Path
The Linux-native tool tackles a long-standing TTW installer hurdle with a supply-chain-aware fallback system.
ChrisDKN just pushed Amethyst Mod Manager v2.4.3 to GitHub, and if you run a Linux rig that plays Bethesda titles, this one actually matters. The release zeroes in on a specific, maddening bug: the Tales of Two Wastelands installer was dead in the water for Linux users. Instead of quietly patching a file path, the developer rewrote the download logic from the ground up.
Amethyst has been carving out a niche since the repo opened in February, less than eight months ago. It runs natively on PySide6, avoids Wine entirely, and tries to mimic that familiar MO2-style drag-and-drop workflow. Roughly a hundred games land in the supported list, spanning Skyrim, Fallout, Cyberpunk 2077, Baldur’s Gate 3, Unreal Engine titles, BepInEx Unity games, and Stardew Valley. The x86_64 AppImage sits at 117 MB, which is remarkably lean for the feature set.
The Fix Goes Deeper Than a Path Tweak
The TTW patch isn't a two-line symlink adjustment. The commit that ships with v2.4.3 adds seventy-eight lines and scrubs fourteen, but the architectural shift is the real story. The previous code only polled GitHub release assets for a Linux binary. When that asset was missing, the installer simply gave up. Now, it falls back to GitHub Actions artifacts, scanning up to five pages of workflow runs on the upstream repository for mpi-installer-linux-x86_64.
More importantly, it does not blindly trust those artifacts. The new code validates that builds originate from the main branch, verifies SHA-256 digests against GitHub's published hashes, and only touches successful workflow completions. That is supply-chain paranoia in the best possible sense. The code also bundles its own CA bundle for consistent TLS across distros, meaning you will not see odd certificate errors if your system store is running behind.
Keep in mind that the TTW project is one of the heaviest Bethesda modding communities out there, so this kind of breakage tends to cascade quickly. Issue #502, which tracked the exact problem on Bazzite GNOME, was closed by the reporter today after a quick test of the new build. For Linux players still treating New Vegas as a permanent residence, that is a relief.
What Is Coming
The development pace is staggering for a project this young. We have already seen forty-plus distinct version entries in under a year. v2.4.3 followed v2.4.2 by a few days, which itself shipped a Steam Workshop downloader wizard and patched a Loot sorting freeze. Because ChrisDKN never does things halfway, v2.5.0-beta.2 dropped minutes after the stable release. The beta adds Wabbajack modlist browsing, batched small downloads to keep the UI from flickering, a tweaked game configure menu, and a bump to the Flatpak runtime on KDE 6.11.
If you need this on your system, the AppImage is available directly, as is the .zsync for faster updates. Flatpak fans can pull it straight from the project's GitHub Pages host, and Arch users already have amethyst-mod-manager sitting in the AUR.
It is not without its growing pains. Issue #507 flags a customtkinter dependency that still trips up NixOS users, and #503 highlights how profile-specific saves demand exact folder name matches for certain games. The rapid release cadence means you will occasionally hit minor regressions, though the developer tends to push hotfixes within forty-eight hours.
For Linux gamers who just want a working, native mod manager that does not require a Proton workaround to launch, Amethyst is arguably the strongest option in the ecosystem right now.
Head here to grab v2.4.3, and head over to the releases page if you want to test the Wabbajack-enabled beta. Report regressions in the issues tab, and keep an eye on the daily build pipeline if you rely on this for heavy modlists.
