hainguyents13/mechvibes v3.2.1 on GitHub

Windows: upgrading through winget removes Mechvibes 2. winget installs silently, so the installer skipped its "Remove version 2?" question and left both apps running, and every key played twice. The winget package now asks the installer to remove Mechvibes 2 by itself. Your Mechvibes 2 settings and sound packs are kept, as with the question. Updating from inside the app works as before.

Windows: Mechvibes-<version>-Setup-x64.exe, the installer and the only asset the in-app updater uses.
Linux (Debian/Ubuntu): .deb. Install with sudo dpkg -i. It does not add you to the input group; run sudo usermod -a -G input $USER and log out/in, or key events won't be seen.
Linux (any distro): .AppImage is portable, with no install step. Run chmod +x on it first, then launch it. The input group requirement is the same as the .deb and nothing sets it up for you: sudo usermod -a -G input $USER, then log out and back in, or key events won't be seen.
macOS (Apple Silicon): .dmg. Open it and drag Mechvibes to Applications. Ad-hoc signed but not notarized, so Gatekeeper blocks a normal double-click: right-click the app → Open → confirm, once. See README-macos.txt.

What's Changed

fix(installer): remove Mechvibes 2 on a silent install that asks for it by @hainguyents13 in #144

Full Changelog: v3.2.0...v3.2.1