EDIT: Duplicate of https://scratch.mit.edu/discuss/topic/87548/ - but with some differences, try reading?
————————————————————————————————————————————————————–
I don't know if this was suggested, but I'm gonna leave this here in case.

I really wanted the local storage variable. Seeing a lot of potential it can get, it's really useful for many conditions and shouldn't be dissed out by no reason at all. The workaround is, having to construct a script to save variables and ask for the scratcher to save the code somewhere to reuse it later on. It takes a lot of time and it's not worth it at all.

However, with local storage variable, it only takes less than second to save, and gives the creator of project no hassle. Even better than the workaround that I just mentioned.

Here's a comparison:

If the ‘var’ variable has an cloud icon next to it, it means the variable will be saved to cloud (Scratchers can only access)

Now this is my suggestion, an ‘var’ variable with a floppy disk next to it, means that the variable will be saved locally (Everyone can access)

And here's something to know:
- Scratchers can only place the local var block. New Scratchers cannot use this to prevent abuse.
- Everyone, even those using phosphorus player can access the local storage variable, can toggle the setting on and off for local saving too.
- Local saving is default to off. It can be turn on manually on the player settings.
- Unlike Cloud, the Local's limit is 2 times.
- The project can detect if the player's local saving is on or off.
The following can be changed, depending on what you'd like it to be.

The benefit from this? Of course:
This is a bigger step to making Scratch a little bit more advanced.
- As example, if the project is all about voting, the local storage variable can disallow the player to vote again with ‘✎ voted?’ set to 1. Safe and sound.
- With griffpatch's 2D Minecraft, he can allow anyone to save their worlds by a local storage variable. Useful.
- A LOT MORE POSSIBILITIES

This might be happening with the Scratch 3.0. I hope, at least.

Would love anyone to support the suggestion. Thanks

Support for variables that are stored per user (not per device), but that's a duplicate.

stickfiregames wrote:

Support for variables that are stored per user (not per device), but that's a duplicate.

Thanks for letting me know.