You don't need to re-load the game after saving it, because what you saved is what the player currently sees in the browser. From the programming point of view - you can save the same save file unlimited times in NG API, and it will result in the file overwriting itself with new data, without changing the file ID. You don't need to load it any time other than in the very beginning, when the player presses the button.
You also do not need to delete save files - I have no idea why would you need to delete. NG API should not delete files either. Every player always has only one save file for him.
kkots
I'm going to review the updates for all mentioned aspects. In a day.
A few questions I can already ask:
How did you fix the Newgrounds API saving? What was the error? How did you enable auto-saving despite the error that you mentioned? Are those errors caused by the Newgrounds API or by your coding?
Maxiecole
I think the reason people sometimes loaded an old savefile was because Newgrounds took too long to delete the save, and the way "I coded it", the file gets loaded when the save is finished and doesn't care whether the previous save is deleted or not.
I made it so it didn't load after you saved. It magically works fine now, in contrast to what occurred before. I have no idea why. But since I don't need to load the game during gameplay, I can enable auto saving.