Games and runtimes
Many games built for Windows can run without it, because their engine also exists for macOS or an open-source reimplementation can read the same data. MacLauncher collects those runtimes, picks the right one when you import a game, and manages their versions for you.
Every game in MacLauncher has a game type, such as Ren’Py, Unity or PlayStation 5, and each game type has one or more runtimes that can play it. Choosing a runtime explains the two terms. The pages in this section group related game types and describe what runs them. In the repository, the game type reference has a page for every game type with its exact formats, versions, settings, tools and runtimes.
The game types
Section titled “The game types”| Page | Game types |
|---|---|
| Desktop engines | RPG Maker (MV and MZ, XP/VX/VX Ace, 2000/2003), WOLF RPG Editor, Ren’Py, Godot, GameMaker, Unity, LÖVE, XNA/FNA, Java, Flash, and the web game types: Construct, Tyrano, GameMaker HTML5 and Web |
| Visual novels | KiriKiri, Siglus / RealLive, NScripter, AliceSoft, MAGES., Nitroplus, Minori, FAVORITE / FVP, AI5WIN, VNDS, BGI / Ethornell, CatSystem2 |
| Windows games through WINE | Windows Game, plus the Windows executables of other game types, played with Sikarugir (WINE) or CrossOver |
| Mobile and consoles | Android, iOS / iPadOS, PlayStation 5, Nintendo Switch |
| Mac apps, retro and more | macOS Game (including 32-bit apps), DOS, ScummVM, Infinity Engine, Half-Life (Xash3D FWGS), MUGEN / Ikemen GO, HashLink, Haxe native build, Video |
How a game finds its runtime
Section titled “How a game finds its runtime”MacLauncher identifies a game by reading its files on import: a Game.ini with RPG Maker scripts, a Ren’Py game/ folder, a Godot .pck, a GameMaker data.win, an .apk manifest or a PS5 param.json. From those it works out the game type and, where it matters, the engine version, which often decides whether a game runs at all. Godot 4.5 and 4.6 projects, for instance, usually aren’t interchangeable, and Unity games want the exact player version they were built with.
The game’s inspector then shows the runtime MacLauncher picked, along with the alternatives, and pressing Play downloads anything missing and starts the game.
Native first
Section titled “Native first”Wherever there’s a native runtime, MacLauncher prefers it. Speed and battery life are part of the reason, since no translation layer sits between the game and your Mac. A native runtime also behaves like a Mac app: window management, fullscreen, mouse and audio work the way macOS expects, and those are the areas where WINE can be erratic. A game whose own Mac .app fails to open because of signing or packaging problems can still run on a native runtime, which plays the same game data.
When there is no native runtime, Sikarugir and CrossOver are always available as a fallback, and you can switch at any time. Choosing a runtime talks through the trade-offs.
Runtimes come from catalogs
Section titled “Runtimes come from catalogs”MacLauncher itself stays small, because engines and tools are downloaded on demand from two kinds of catalog: the upstream projects’ own releases, and MacLauncher Builds, a companion project with ready-to-run macOS builds of engines that need adapting or have no official Mac release. Either way, you pick versions in the Runtimes window.
Runtimes built for MacLauncher
Section titled “Runtimes built for MacLauncher”Most runtimes are existing open-source projects that MacLauncher manages. A few exist only in MacLauncher:
- MacLauncher Android, a game-focused Android runtime that also handles ARM64 VR/XR titles.
- A macOS port of OpenGMK, the only native way to play classic GameMaker 8 games on a Mac.
- macOS ports of AnyPS5, ONScripter-EN, AI5-SDL2, KAG3 and ReMinori.
- Offline Steam API support, for games that expect Steam to be running before they’ll start.