Add something to the list, then reload the page - the data will still be there! (if your internet is decent) The data stored by this system is synced across different projects (don't believe that? go to a remix of this project to see it yourself: https://scratch.mit.edu/projects/966154404/ ) No cloud variables used! The data is saved locally* and can be accessed from all devices in your network. It will be auto-cleared after a while (can range from a few minutes to days / weeks) (Scratch team, I hope you're okay with me using the translate extension like this - if not, I won't do it again.) -- PRACTICAL USES -- Before using this storage system in your project, please read the warnings below! ⚡ Detecting if the Scratcher who uses your project has recently opened it before ⚡ Auto progress-saving features in games (so in case the user accidentely closes the tab, the progress won't be lost) ⚡ Sharing data (like highscores or user input) locally* across different Scratch projects ⚡ Storing data locally for a short amount of time Before using this storage system in your project, please read the warnings below! Keep in mind that this is NOT A PERMANENT storage and doesn't work consistently for all users. -- WARNINGS -- TL;DR: I do not recommend actually using this because it's so inconsistent. It's just an experimental beta. ⚠️ The system is pretty inconsistent. If you switch tabs during encoding / decoding process, all saved data will be erased. ⚠️ This is not a permanent storage, it will be reset every now and then (can range from a few minutes to days / months depending on the device) ⚠️ For all of the use cases listed above, a cloud backend (with a Python library like scratchattach) is the faster and more stable option - however it requires knowledge in text-based coding languages. ⚠️ This system can NOT be used for cloud games / cloud highscores because the data isn't stored online - it's stored on your device and only visible to you. If you're looking for a cloud engine, check this: https://scratch.mit.edu/projects/440516876/ ⚠️ Encoding and decoding is both slow. The more often the saved data is encoded / decoded, the longer encoding / decoding will take. ⚠️ Only works on Scratch. Doesn't work on TurboWarp at all. ⚠️ During the encoding process, around 30 clones are created, so beware of the clone limit (300). -- HOW DOES THIS WORK? -- TL;DR: It's based on Scratch's translate extension and the fact translations requested before are cached server-side for the network that requested them. Full explanation coming soon lol -- CREDITS -- Credit to by TimeTravel2022 and by Retr0id for inspiration and for inspiration They used a quite similar concept, however my implementation of it is significantly faster and also more reliable. These people wrote that caching is happening locally - this doesn't seem to be the case, at least for me. The data stored by this system is synced across all devices that are in my network no matter what browser I use, therefore I believe the caching is happening server-side (I believe the Scratch API caches the response it sent to a specific network and will provide the same response again if the same network sends the same request again). -- APPENDIX -- *The caching of Scratch's translate API that allows this project to work does not actually seem to happen locally (read the paragraph above for more information).
ty for the views but I don't get the hearts and faves should go do that on Tim's project! Also while your here mind as well go check out SSS5 and Gundam Clicker on my profile.
