Beta build. It reaches the people who turned on "Get beta builds" in Settings, and everyone else once it is promoted.
A graphics mode for one game, and a way to find it (#66, #67). The mode used to be a setting of the whole environment, so a game that ran badly on it could only be fixed by changing every other game too. Each game page now has "Mode for this game" under Advanced, and after a session that went badly, "Had problems" offers the next mode for that game with one click, then the report. Two reports this week were old DirectX 9 games stuck on Wine's own Direct3D, the slowest path for them.
Engines and environments on any APFS folder or drive (#24, #68). Settings, Environments, Change… moves everything to the folder you pick, checks the copy file by file before removing anything, and relaunches. Drives formatted as exFAT are refused up front: Wine cannot build an environment on them. If the drive is not connected at launch, Highball says so instead of starting over on the internal disk. From the terminal: highball config home.
Engine updates that change no Wine apply themselves. When a new engine is the same Wine build with a component added, the way r2 added the D3DMetal timestamp shim, Highball applies it at launch when nothing is running. A different Wine still waits for your click.
Shortcuts carry the game's own icon. Make a shortcut… now reads the icon out of the game's program instead of cropping the store cover.
The Sims Legacy Collection draws with Vulkan directly (#44), so its page now says the graphics mode does not apply rather than offering one.
Five Nights at Freddy's is verified: a full night at 60 fps on DXVK.