The issue is that auto-save is enabled, and SugarCube maintains all the save slots and your current "save" as a single compressed JSON string, so every time you make a change to the save state (perform an action or click a link), SugarCube has to replace the whole string by serializing your current session, attaching the other slots' data to that string, and then it has to compress the entire thing.thank you, i will give this option one last try before deciding to give this up for good
really exciting game with so many different archs to explore but this tedious nuisance can ruin anything no matter how good the game might be
If opening the save dialog takes a second (or more), your session data is too large!
To reduce the performance impact of late game/bloated/large saves, restrict yourself to one or two save slots OR use Save to File/Load from File (preferred as you can have as many saves as you want) and CLEAR the other slots
Not optimal, I know, but this avoids the performance hit in most cases AND if you use only one or two save slots, it reduces the chance of running out of web storage space (and corrupting the saves) or running into crashes because SugarCube ran out of space.
To the devs out there using SugarCube: keep your session state as small as possible (sanitize your variables!), restrict history rollback (not 50 undo slots!), set the number of save slots to a reasonable number AND think about the implications of enabling "auto-save".