Some Scratchers like me want to have saving enabled on their games, however the current way they do it (right click a list, export is for saving, right click a list, import for loading) is way too clunky. I think that a “User Cloud Variable” should be available. These are the same as cloud variables, but unique to each user. Also, these should support text, but it doesn't have to.

User Cloud Variables Pros and Cons

PROS:
-Easy in-game data saving for each user, which is behind the scenes.
-Following on the above pro, when using a list players could change the list's data
in order to cheat the game, using this cloud variable stop them from changing the
data on the Scratch servers unless they remix.
-Good for personal high-scores in games and personal levels
-Easier to make online multiplayer games.

CONS:
-Could be exploited to make chat-rooms

That's the only real con I can think of haha!



My final conclusion is that personal cloud variables can help a lot in games, and could make Scratch games more complex, and have more content.

I think the limit per project for these variables should be about 2.

Thank you for reading, let the ST know!

First, this should be in the Suggestions forum.
Second, this (I think) is a duplicate.

I found some more cons:

1. This would easily lead to private messaging, which is rejected.
   
2. The Scratch Team don't have that server space.
   
3. How would people access the changelog? If, say, the creator wanted to see what users did with their cloud data, how would they check fhat?
   
4. Following up on that, what about very busy projects or projects with lots of views?
   

Sorry, if I sounded aggressive.

openPoll wrote:

First, this should be in the Suggestions forum.
Second, this (I think) is a duplicate.

I found some more cons:

1. This would easily lead to private messaging, which is rejected.
   
2. The Scratch Team don't have that server space.
   
3. How would people access the changelog? If, say, the creator wanted to see what users did with their cloud data, how would they check fhat?
   
4. Following up on that, what about very busy projects or projects with lots of views?
   

Sorry, if I sounded aggressive.

I came up with this idea while working on a game, so it's not a duplicate as far as I know.

The private messaging thing could be an issue, maybe a very low character limit so not much can be stored anyway? Like maybe 20 characters maximum, which is more than enough for a few numbers.

F in the chat for server space. I really don't know what to say for this one.

There could be a page available only to the creator that allows them to see logs on what users have set the cloud data to, a bit like the logs for normal cloud variables.

Actually, scrap the whole idea, make something just like this, but it's stored on the user's computer (with permission, of course.) But at the same time, something like this can be edited, destroying the whole point of this.

I know I am late to this conversation and you already said “scrap the whole idea”, but I would like to contribute some math:
Taken from https://scratch.mit.edu/statistics/data/daily/

There are 43,198,442 projects, and 44,710,594 users on scratch.
That comes out at 1.93142800169E+15 (1,931,428,001,690,000 or 1.93quadrillion) unique variables that would have to be stored.
That number wouldn't be 100% accurate if its only accessible by Scratcher's.

Storing data on the users computer/device is a lot easier to do.
JavaScript LocalStorage/SessionStorage/Cookies would do the trick.

Local Storage has already been suggested.

CW_school wrote:

I know I am late to this conversation and you already said “scrap the whole idea”, but I would like to contribute some math:
Taken from https://scratch.mit.edu/statistics/data/daily/

There are 43,198,442 projects, and 44,710,594 users on scratch.
That comes out at 1.93142800169E+15 (1,931,428,001,690,000 or 1.93quadrillion) unique variables that would have to be stored.
That number wouldn't be 100% accurate if its only accessible by Scratcher's.

Storing data on the users computer/device is a lot easier to do.
JavaScript LocalStorage/SessionStorage/Cookies would do the trick.

Local Storage has already been suggested.

If I'm going to be honest, I forgot this thread was even here.

Yeah, Local Storage would be nice. I'll probably delete this thread soon.