Your games. Your Linux arcade. Less setup. More PLAY. Explore how working setups become repeatable game packages.
Responsibility map, not a complete API call graph. Software preparation and game installation require approval.
Explore the parts of a package, then change a sample payload to see why fixed versions and exact bytes matter. These examples are teaching aids, not runnable installer files.
Momentum stores library data and play history locally. Downloads still make external requests. “No external tracking” does not mean “no network traffic.”
Package scripts execute as your user, without a sandbox. Hashes establish exact identity, not safety. Trust the publisher before approving execution.
This static export contains no analytics code and does not set cookies or use browser storage. Its hosting service may have its own logging, authentication or cookies; those are outside this app. Links contact their destination only when followed.
Ordinary 1920×1080 fullscreen now matches the canonical laptop launcher. A bundled clean calibration seed initializes only absent isolated NVRAM.
Marvel Infinity War and Ultimate Double Dragon 3 share the same exact extracted native OpenBOR 6391 runtime. Package preparation needs no FUSE or engine launch.
The current installer does not bundle the mod. Reuse verified files/cache or approve the pinned publisher download separately.
Copies media into ~/Games/virtua-cop-2 and leaves the previous game folder and separate settings/saves intact.
Pinned MAME 0.289 with fullscreen, mouse aiming, BGFX default and an absent-only free-play seed. Supply your own timecrs2.zip.
Static checks, synthetic lifecycle tests, real runtime acquisition, owner-reported gameplay and full campaign completion are different claims. Exact compatibility evidence enables installation. Each player still confirms their own setup.
Brutal Doom 64 0.3.0 has synthetic installation/managed-engine checks but no reported graphical gameplay or save/relaunch acceptance. A published package is not universal certification.
The package store is one way into the library. Other Linux games can use shortcut import or a manual command. These cards describe current catalog records, not live downloads.
Duke Nukem 3D, Aliens: Eradication, Ashes 2063 and QBJ3 have historical packages/adapters, but are absent from this pinned ten-entry catalog. Withdrawal does not uninstall an existing game.
Compatibility is exact and package-specific. An unsupported build is untested, not necessarily broken. Change the scenario to see the permitted path.
Managed Flatpak slots identify app ID, architecture, branch and exact commit. Each managed game receives a separate profile and a hash-bound launch helper. Existing personal profiles are not imported. Different slots may duplicate dependencies.
software/flatpak/<app-id>/<arch>/<branch>/<commit>/ state/<package-id>/<profile-id>/
Preparation can leave a verified engine behind if later game setup fails. Closing the UI does not kill an active Flatpak transaction. No automatic slot cleanup, engine switch or existing-game migration.
Current manifests, code, catalog and dated evidence take precedence over stale summary prose. These documentation differences remain in the repositories; this review does not edit them.
Launcher and authoring source remain private. Public catalog and game pages are readable without a GitHub account. Revision identifiers below pin the source used for this review. Private repositories require separate access; public hosting of this guide does not grant it.
Review scope: current source, release history, package manifests and evidence records. Release ZIP bytes were not downloaded/rehashed and games were not installed or launched during this documentation update.