Attract‑Mode Plus v3.2.2 Adds Multi‑Platform Binaries, Feature Enhancements

Attract‑Mode Plus v3.2.2 rolled out in mid‑February 2026 with release artifacts and binaries added to GitHub for Windows, Linux (x86, x86‑64, ARM, Raspberry Pi), and Mac OS X, giving users prebuilt options instead of forcing local compilation. The project is maintained by oomek and contributors and is presented under the GNU General Public License, version 3 or later; the README directs users to the Releases page to download updates and notes that "A notification will appear at startup whenever an update is available."

The repository describes Attract‑Mode Plus as a feature‑enhanced fork of Attract‑Mode and positions the frontend as "a graphical frontend for launching command‑line emulators. It offers robust list filtering capabilities, and employs a versatile scripting language to showcase an extensive range of image, video, and audio formats." The README also warns that "Attract‑Mode Plus is a blank canvas that requires external assets to operate effectively" and explicitly calls out that "Snaps" are essential while "Videos greatly enhance the frontend experience."

Practical setup examples in the Quickstart target Windows installations with literal paths such as C:\attract-mode-plus, C:\mame, C:\mame\roms, C:\mame\snap, C:\mame\video, C:\mame\wheel, C:\mame\marquee and a repeated example C:\mame\folders; the sample executable path is C:\attract-mode-plus\attractplus.exe and example artwork is shown as C:\attract-mode-plus\menu-art\snap\mame.png. Control mappings are explicit: Select - Up/Down, Accept/Back - Return/Escape, Configure - Tab, Fullscreen/Window - F11, and those tokens appear verbatim in the repository text as Up/Down, Return/Escape, Tab, and F11.

Configuration and runtime behavior are spelled out in the README. Rom clones are grouped into sub‑menus and "Use the `Back` control to exit the clone sub‑menu." The Files section explains that "Configuration files can be edited while Attract‑Mode Plus is running" but instructs users to "Close the menu to avoid changes being overwritten by the frontend. Preserve the file's formatting to ensure it remains readable." The README provides the explicit reload mechanism: "Use the `Reload Config` control to reload all configuration files." For updates the documentation is similarly prescriptive: "Extract the new version over your existing files - your configuration will remain intact."

The repository page also exposes developer and support navigation items that matter when tracking the new build artifacts: Releases, Manual, Discord, Coding Reference, Compiling, and WIP appear alongside visible UI elements such as a Logo, Latest commit, History, and Repository files navigation. The supplied material for v3.2.2 contains no detailed changelog entries; an original report begins a sentence "The patchset focu" but that line is truncated in the available notes, and no further commit‑level details were provided. Expect the project's Releases page and commit history to hold the specific build filenames and commit authors if you need verification, while the README's upgrade instruction - extract the new version over your existing files - provides an immediate, low‑risk path to try the new multi‑platform binaries.