Copied from : https://forums.faforever.com/viewtopic.php?f=2&t=16947#p169818
I got SupCom and FAF running on a mac and figured I should post about what I had to do, so anyone else who tries this has ideas.
I basically started by following this guide: https://wiki.faforever.com/index.php?ti ... hon_client
except I changed things whenever I had to.
I installed Steam with PlayOnMac, which is basically just a wrapper around Wine. Once I had Steam I installed FA in there. At first Steam wouldn't download anything, I had to change it to use different download servers for some reason, using some weird advice I saw on Reddit or something. I don't remember exactly what I had to do here but it was annoying.
I used the original FAF client because I know more about Python than Java, sorry Downlord.
I had to do dumb stuff to get faf-uid working because there isn't a compiled Mac (BSD) client. Specifically, I downloaded the linux faf-uid, then I installed this program called "noah" with homebrew. It is basically Wine for Linux -> BSD. Then I renamed faf-uid to real-faf-uid, and in the place of faf-uid put this script:
#!/bin/bash
noah $(dirname "$0")/real-faf-uid "$@"
I don't know if this actually works well or not, so don't blame me if you get autobanned
For the FA directory, I used the directory from the WIne client. PlayOnMac installs everything in "$HOME/Library/PlayOnMac/wineprefix/Steam/drive_c" so look there.
Finally it was really hard to debug why launching FA was working or not working. As such I just gave up and used this as the "exe" in the [wine] section of FA Lobby.ini:
[wine]
exe=/Users/nrook/code/faf-client/dumb_wine_shim
Of course dumb_wine_shim is something I wrote myself. It is another dumb script, here is its contents:
export WINEPREFIX=/Users/nrook/Library/PlayOnMac/wineprefix/steam
/Users/nrook/Library/PlayOnMac/wine/darwin-x86/3.17/bin/wine "$@" >/Users/nrook/FAForever/logs/winestdout 2>/Users/nrook/FAForever/logs/winestderr
Since it pipes the output of wine, it is way easier trying to figure out why FA decided not to boot than going through forever.log or gamesession.log.
So that is how I got FAF running. Hopefully this is slightly helpful to anyone trying this. It is not supported and will probably break randomly but oh well. I haven't actually played a multi game with it because my network is currently bad, but vs AI worked, and connecting in lobby worked, so it will probably work.
So yeah As you can see in the old thread I'd gotten an auto-install script working that was gonna work for every single existing operating system, even windows (this script doesn't work anymore because I haven't updated since it's really lost it's point: most of the things that were needed are no longer needed, it much easier today).
That guy's guide will serve you much better.
I may not be able to answer your mac questions but if it pertains to proton and steam ect I'm pretty sure I'll be able to help out.
Also I personally know jack shit about the python client, I use the downlord Java one (that's the one that's supported and who's support isn't going away anytime soon) I'm pretty sure you can get that one running natively too. I'll ask around to see if they can get a Mac native build going.
That being said. All of this was from the post-"Big Sur" era. Building either FAF clients for Mac's new architecture is probably a tall ask, let alone emulating Forged Alliance.
I dunno how that will pan out, this post is mainly intended for pre-"Big Sur" macs.
A general-use piece of wisdom for your life: don't buy apple.
TLDR : I don't own a mac, I'm no mac expert, this method worked before on a non big-sur mac it should still work on a non big-sur mac today for you. I'll start digging for more info and support.
Git issue is here : https://github.com/FAForever/downlords-faf-client/issues/1854
You want mac support with a full mac build? be the hero you want to see in the world and offer your testing help in that github issue!
and then use my code to fix them as long as they are easy fixes that is gonna work
