Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
But if you choose such a big Vendor Lock In (= Mac) you kind of have to expect this. Especially because even Apple themselves dropped Intel based Macs in 2023...
I guess the player count of people playing this game on Macs is already pretty low. The number of those who do it on Intel based Macs might be even far smaller / tiny. I wouldn't be surprised when you are 1 of total 10 people (or similar) playing this game on a Intel based Mac...
While the work required to make that all possible is in no relation to the gain. Primarily because Apple makes it as bad as possible for developer to support their platform...
So yeah what Kaworu said is the only things you might be able to do. But if you want to blame someone, blame Apple that they make it that bad, that they switch their architecture every few years and yourself that you still choose to use a Mac without Upgrading to their new Stuff...
Btw. this short is very well describing the Mac situation (and now imagine even splitting it further into 2 different architectures where one isn't even supported by Apple anymore): https://youtube.com/shorts/qRQX9fgrI4s?si=9JO7fi3bZLkLAU_C
Also this is whole process is very time consuming (=costly) and had to be done twice to do it for both platforms (Intel and non intel).
I also do not understand why the Mac approval process for mod.io mods is connected to that of consoles. They have to be approved for both to be approved, when these things should be separated. It's just because Mac and console patches arrived at the same time, but there is no reason to connect the approval process of Mac. 90% of mods will work on Macs; the only ones that didn't in the past were usually based on script extender, or used DLLs like Native Mod Loader, but pretty much all the mod.io mods don't use either, because they need to work on consoles.
TLDR: there is no reason Mac users should wait on mod approval for testing to see if they work on console, which seems to be a glacial process. Almost always, the RECENT ones that work on Windows (and Linux) will work on Macs.
Slowing down the approval process forces a lot of Mac users who want to use mods to get them outside the built in mod manager, and update them that way. I can do this, but I imagine it's frustrating for a lot of others.
Could you still get a refund?
1) You can go to the game settings in Steam and choose Beta participation, that would give you access to the HF24 version.
Pros: about 10GB of download instead of the whole game, easy
Cons: Isn't compatible with the saves from the latest playable version (HF25), has a few extra bugs
2) Download the latest playable version from depot
Pros: you get the latest playable version
Cons: you have to download the whole freaking game, and not via the standard Steam download tools, oh no, you have to use the damn console download that doesn't even have a verbose option and doesn't always restart if your internet connection flickers. Then you have to jump through hoops to get this thing to work and to protect it from being overwritten by Steam's autoupdate system.
If you do decide to download HF25:
Go to your Steam app's console tab. If you don't see it, go to any browser and enter steam://nav/console and let it be redirected to the Steam app. Now you do have the console.
In the console enter "download_depot 1086940 1419660 7401447368017585881" (without the quotation marks). It should give you a line about starting download and then kinda do nothing. Do Not Touch Anything. As I mentioned, that thing doesn't even have a verbose option, so unless it outright tells you the download has failed, assume it's still downloading. When it finishes, it gives you a line that the download has finished. Keep in mind that you're downloading the whole game, so it can take a while. Also, it doesn't put the download in its standard Download folder, it puts it in:
~/Library/Application Support/Steam/Steam.AppBundle/Steam/Contents/MacOS/steamapps/content/app_1086940/depot_1419660/
When the download has finished and you've had time to curse all of the gods of the Forgotten Realms, the easiest way to proceed is:
In the Steam app set updating to "Only when the game runs" then quit the app, and check that it isn't running before you open the game.
Take the app bundle you've just downloaded and move (or copy if you have enough space) it to the game's standard folder ~/Library/Application Support/Steam/steamapps/common/Baldurs Gate 3/ You can keep the other version, just rename the app bundle (either or both of them). The reason for that is, that damn thing has the path hardcoded somewhere in the runnable. If you run it from any other location (either by double-clicking the app bundle or by running the runnable within the bundle), that damn thing redirects the call to "~/Library/Application Support/Steam/steamapps/common/Baldurs Gate 3/Baldur's Gate 3.app" (so it runs the "official" version it expects to find there, and if it doesn't find it, it throws an error and quits the process), but if you run it from within the expected folder, it doesn't check the name of the bundle itself, it just runs.
Re-install whichever mods you've been using, if any.
Double-click the app bundle.
I don't think the devs have anything to do with it, unfortunately. Apple dropped support, there isn't much Larian can do about it.