Hello - it's been a while, but I have returned from the void with a juicy update!

• Created documentation of the entire package, along with code snippets and examples.
  • View the documentation here!
• A brand new demo, because apparently the new demo which was supposed to be clearer... was not clearer. I guess I suck at making demos!
• Added reset() and reset_all() functions to the SSave class which resets a value (or all) back to it's default.
• Added erase() function to the SSave class, which deletes the file from disk if it exists.
• Added ssave_erase() function for use with SSaveManager which deletes the file from disk if it exists.
• Added get_default() function to the SSave class, which retrieves the default value.
  
• Fixed all feather warnings and suggestions.
• Added a new config value: SSAVE_ERROR_ON_SET_INVALID_TYPE. By default, this is enabled.
  • For example, if you have a string value and try to write an array to it, you'll get an error instead of the old printed message.
• Added get_all() function to SSaveManager,  and  ssave_get_all() is now a wrapper of it.
  • Previously, you could only get all when using the automated SSAVE_USE_MANAGER functions, now it's directly usable within the class.
• When loading a file, set_protection() is now automatically called with whatever was stored in the header.
• Fixed an oversight where custom errors could cause the game to crash when saving/loading.
  • Thank you @tthrelfo for reporting this!
• Fixed an oversight where enum values (specifically int32/int64 values) were not being considered when validating SSAVE_TYPE.REAL values.
  • Thank you @rbarbosa95 for reporting this!
• Fixed an oversight where set_file_prefix() did not return itself for chaining.
• Updated some existing JSDoc, added in missing documentation, and fixed some value types being input incorrectly.
• Updated various comments and error messages for improved clarity.

P.S. - Thank you all for using SSave!! I'm really happy a lot of people have been enjoying it, and to see games be released using it. It's been a little while since the last update, but I'm hoping to tie up some loose ends and get as many issues squashed as I can. The most important of all those was definitely the lack of documentation; it's a nice weight off my shoulders to get this update out there. See you in the next!