Jackify automates Wabbajack modlist installs on Linux and Steam Deck

The whole modlist workflow, not just a downloader

Jackify is described as a Linux application for installing and configuring Wabbajack modlists on Linux and the Steam Deck, and it provides what it calls a complete end-to-end workflow: downloading, installing, Steam shortcut creation, Proton prefix setup and post-install configuration. That list is the real scope of the project. A modlist is not one file. It is a manifest, an installer, a texture conversion step, a set of configuration edits and a launcher, and each of those has platform specific parts that break on Linux. Jackify's job is to run that whole chain, and the README is explicit that both interfaces provide identical functionality, so the CLI is not a stripped down subset of the GUI. The supported games are named: Skyrim Special Edition, Fallout 4, Fallout New Vegas, Oblivion, Starfield and Enderal. Other games including Cyberpunk 2077 and Baldur's Gate 3 are download and install only for now, with full automation described as future work. The audience is therefore narrower than Wabbajack itself. It is Linux players running large curated lists, and the Steam Deck user for whom the manual steps are the main reason a list never gets installed.

An alpha disclaimer that tells you what will go wrong

The disclaimer section is unusually direct and it is the most useful part of the README for anyone deciding. Jackify is called a hobby project in early alpha development, to be used at your own risk. The software is provided as is without any warranty or guarantee of functionality. Features may be incomplete, unstable, or change without notice. Support is best effort through community channels, and functionality on your specific system is not guaranteed. The document also tells you to back up your important data before using it, and it makes the sharpest admission in the list: a successful installation does not guarantee a working modlist, because Linux introduces hardware, driver and system-specific variables that cannot be accounted for. If a modlist installs but does not run correctly, the documentation points you to a specific Discord channel rather than to the modlist author, unless that author explicitly supports Linux. That is a candid description of where the responsibility sits, and it is the reason to treat this as a tool for experienced Linux Steam Deck users rather than a first project.

Some modlists cannot be automated at all

Beyond the general risk, there is a specific one: not all modlists can be fully automated. The README names Fallout New Vegas lists as an example of modlists that require manual steps Jackify cannot automate, or has not automated yet, and it tells you to always check the install guide of the modlist itself to see what might be needed. Most modlists are also not officially supported on Linux, so Jackify makes a best effort and compatibility is not guaranteed, and it will vary between modlists, hardware and system configuration. That is a three-way uncertainty, and it is worth being honest about how it affects your plan. Jackify removes the mechanical work, not the modlist's own requirements. A list whose guide assumes a Windows tool, a specific registry edit or a manually placed asset will still need that step. A list where Jackify reports success is a list where the automated part succeeded, which is a weaker claim than the list works.

Downloading the AppImage and checking what you got

Installation is a manual download rather than a package manager entry. The quick start starts with downloading the latest release from the Nexus Mods page, then extracting the AppImage from the 7z archive, then making it executable and running it:

chmod +x Jackify.AppImage
./Jackify.AppImage

For command line use, the same binary takes a switch:

./Jackify.AppImage --cli

Because the file arrives as a downloaded artifact rather than from a distribution's package repository, verifying it is on you. Each release includes a SHA256SUMS file on the GitHub releases page, which you download into the same folder as the AppImage and then check:

sha256sum -c SHA256SUMS

The expected output is Jackify.AppImage: OK, and the README is unambiguous about the failure case: if you see a failure, do not run the file. A full step-by-step guide with screenshots lives in the wiki User Guide.

Runtime requirements that rule out the Snap Steam

The requirements section lists the constraints that decide whether this runs on your machine at all. It needs a Linux system, and most modern distributions will work, with Steam installed and configured, and the Snap version of Steam is not supported. Protontricks is required for modlist configuration. GE-Proton 10-14 is highly recommended for ENB compatibility, with other Proton versions possibly working. A Nexus Mods account is needed, with Premium required for fully automated downloads and Non-Premium supported with manual browser steps. FUSE2 compatibility through libfuse.so.2 is required for AppImage execution. And on Ubuntu or Debian based distributions, including Ubuntu, Kubuntu, Linux Mint, Pop!_OS, Zorin OS and elementary OS, the Qt platform plugin library has to be installed with sudo apt install libxcb-cursor-dev. That last dependency is the sort of thing that stops an AppImage from launching on a fresh desktop, and it is why the requirement list reads the way it does.

A shared backend with a custom fork of wabbajack-cli

The architecture section describes a separation between frontend and backend. Backend services hold pure business logic with no UI dependencies. Frontend interfaces, meaning the CLI and the GUI implementations, share that same backend. The native engine is powered by jackify-engine, described as a custom fork of wabbajack-cli, for Linux performance and compatibility, and texture conversion with Texconv for hash matched conversion requires Proton. Steam integration works by direct manipulation of shortcuts.vdf rather than through the Steam client API. Two design choices are worth noting. Sharing one backend between the CLI and the GUI is what makes the claim of identical functionality plausible rather than aspirational, and it means the CLI is the safer surface to script. Using a fork rather than upstream wabbajack-cli means behaviour can diverge from upstream, which is a maintenance consideration for anyone tracking the Wabbajack ecosystem. Jackify also stores its files and configuration under ~/Jackify/ and ~/.config/jackify/.

Releases, licence and how the project wants contributions

The repository is not archived and the last push was on 2026-10-06, with releases v0.8.1.3 on 2026-10-06, v0.8.1.2 on 2026-09-21 and v0.8.1.1 on 2026-09-11, so the cadence on these patch level versions is frequent. The licence deserves a note. The README states the project is licensed under the GPLv3 License and points to the LICENSE file, and pyproject.toml records license as GPL-3.0-or-later, while GitHub's own classification of the repository licence does not fall into one of its standard categories. The file is therefore the authority on the terms rather than the summary in the README. On contributions, the README says that at this early stage the author would prefer GitHub Issues for bug reports and suggestions rather than pull requests, and that this will likely change as the project matures. There is a CONTRIBUTING document with the details, plus a THIRD_PARTY_NOTICES.md file at the repository root, which is the place to look for what is vendored.

Editorial conclusion

Adopt Jackify when you play Wabbajack modlists on Linux or a Steam Deck and want the install steps handled by a tool built for that platform, especially for a large list where manual setup is the main barrier. Do not adopt it for a modlist whose guide requires manual work Jackify has not automated, such as Fallout New Vegas lists, or for a Steam installation you rely on the Snap package for. Verify first that your Steam install is not the Snap version, that GE-Proton 10-14 and Protontricks are present, that your Nexus account tier matches the download mode you need, and that the SHA256SUMS file for your download matches before you run the AppImage.

Frequently asked questions

Official sources

1. Issues
2. Omni-guides/Jackify on GitHub
3. README
4. Releases