Repository navigation
Installing & Updating
Downloads are on the releases page and on the Merframe website.
Pick the .exe (NSIS installer) or the .msi. Windows may warn you on install that the application is not known. This is normal, and I'm not willing to pay Microsoft to make it go away.
AppImage is the preferred way of running the application. Due to how GitHub serves files, you must set the execution permission yourself:
chmod +x ./Merframe_amd64.AppImage.deb and .rpm packages are provided for Debian, Ubuntu, Fedora and their relatives.
On Arch, install the .pkg.tar.zst with pacman -U, or build it from source with makepkg in packaging/arch/.
The in-game overlays need X11 or XWayland. Proton runs the game under XWayland, so Wayland desktops (including Hyprland) work. For more information, read Overlays.
The app offers you a self-installing update when one is available. You may disable this under Settings -> Prices and Data, or during any update offer. The About page has a button to check for updates manually at any time.
The Arch package does not update itself. You'll have to install the next .pkg.tar.zst with pacman -U again.
| Platform | Directory |
|---|---|
| Linux | ~/.local/share/Merframe/ |
| Windows | %APPDATA%\Merframe\ |
This folder has the SQLite database (merframe.sqlite), the last inventory as inventory.json.gz, the WFCD data and image cache, the settings (merframe.json), the warframe.market token (market_token), and Merframe's own log merframe.log. Deleting the directory resets Merframe. Please attach the Merframe log to bug reports.