MacOS Feasability

[Nat3z]

Wondering if it would be possible to have MacOS support through just downloading/extracting games, rather than handling launch and wine shenanigans (cause of mac lacking any sort of easy support like umu-run or whatever).

[Nat3z]

@nat-openclaw how feasible would it be, and what's the complexity and what should i account for? /ask

[nat-openclaw]

Asked and answered — no code changes were made for /ask.

[nat-openclaw]

Pretty feasible if you keep it strictly “download + extract + library management”.

Complexity:

• Low–medium for an MVP: the download pipeline is already mostly platform-agnostic, and macOS extraction support is partly there already.
• Medium for a clean UX: you’ll want to hide/disable anything launch-related and give mac users clear setup guidance.
• High only if you want polished mac releases (CI, signing, notarization, updater, native packaging).

What to account for:

• No launch path on macOS: gate out UMU/Wine/Proton/SteamTinkerLaunch stuff hard.
• Dependencies: unzip, unrar, and likely bun/homebrew guidance in OOBE.
• Archive limits: mac path is more limited than Windows 7-Zip support, so some formats may be unsupported.
• UI clarity: don’t show “Play” as if games are runnable locally; make it obvious it’s extract-only.
• Release/build work: macOS CI artifacts and app signing/notarization are the big extra overhead if you want distributable builds.

Bottom line:
An extract-only macOS version is very doable and probably the right MVP. If you try to add launch parity, that’s where the project starts doing jazz hands into a wall.