So… here’s what we know:
Every time the team changes a lua file that records world-state data (that’s most lua files) there is a chance that we introduce a bug that causes that file to, in some circumstances, not save its world state properly. If you save while the lua file is in a buggy state, the save game that is created will be corrupted and will not load properly. Furthermore, going back to an older, working save, and then trying to save THAT game will fail, because one corrupted save file in the folder prevents all subsequent saves from working properly. This problem can be worked around by deleting the corrupted save from the folder. To do this, you have to identify which save is corrupted. If you can’t figure out which file is corrupted, then the fastest thing to do is move all your files into another folder and start over from scratch (adding back good saves that you really like).
If your save folder is completely empty, and you still cannot generate a save, then there’s a chance that this is a slightly different bug, and in that case, Team Radiant would like to know more. Exactly what happens when you try to save? Does the UI stall? Does the game crash? Does the save game just not appear in the folder? When does it happen/how many things have you done in the game until that point?
We have not tested the game in OSX in any way/shape/form, so we might be in new territory here.
Update: If you have a save file from Alpha6 latest that does not load, attach it to this thread and we’ll do our best to take a look. Note: the entire dev team is working on the build on Steam Latest, so any saves from any build that doesn’t have the blueprint splash screen has code that is probably not relevant anymore.