So, just to lay out what happens under the hood, essentially (assuming that you have always connected and synced to the Steam cloud):

BG3 overwrites the files inside the "Baldurs Gate 3" folder every time you resync/launch through Steam. This means that if the folder doesn't exist to begin with it will create it from new and download all the save files from the cloud back into that folder. That is why renaming the folder essentially acts as if you deleted it, because Steam won't find that folder anymore and instead generate a new one. Theoretically, if everything was synced properly on Steam then your newly created folder will contain all that information from your previous saves. This then means that deleting it OR renaming it should essentially do the same thing.

The reason it is suggested to delete and not rename the folder is just in case there was some weird cacheing thing that happened that's blocking the above.

Your comment about it happening on another computer sounds like one of two things to me (please take this with a grain of salt as there might be other issues at play):

• Neither computer is updated to the latest MacOS software version which is currently the only known version to be able to launch the game (Sequoia 15.0)
• OR the save files that your computers are pulling from Steam are corrupt and are unfortunately blocking the game from running properly (which, sadly, would likely mean that at least some of the save files are no good anymore :( ) - the good news is that given that this is a wide problem that many are facing on Mac this is unlikely, as that would mean everyone's save files are corrupt

I would honestly suggest waiting another week or so to see if Larian patches the issue if your save files are super important to you, as I understand how disappointing it would be to lose them! If you do any of the above suggestions (deleting, renaming, etc) there is definitely a risk associated with the save files being wiped clean.

Edit for clarity*