Included capx if you want to mess with it
I implemented savedata in my Zelda SDK using the native save/load, with naming slots, separate saves, etc. An issue, as a cavet of the native save/load: It creates a snapshot of "slotx" so using a variable to ensure a save slot exists before-hand is moot.
My research indicates my best option is using dictionary+webstorage and storing 3 dictionary keys each for data. Is this the right away to go about it? I have researched webstorage and dictionary a little but I only have a small hunch of how to. My hunch is better with saving said keys but not on how to actually reload them.