save [score v] for user::variables

load [score v] for user::variables

this would make save load for some games like RD WAY easier, it would just be the click of a button!
e.g code

when this sprite clicked::cat
save [score v] for user::variables

when this sprite clicked :: cat
load [score v] for user::variables

 

This is similar to cloud variables and cloud lists, both of which are rejected.
I also think this would be confusing for new Scratchers. If all they see is a ‘save variable’ with nothing else, they might be confused on how to edit it, etc.

Abrig67 wrote:

This is similar to cloud variables and cloud lists, both of which are rejected.
I also think this would be confusing for new Scratchers. If all they see is a ‘save variable’ with nothing else, they might be confused on how to edit it, etc.

similar but not the same, it would save the variable for the individual user not everyone

Support!

Handling save codes is a hassle, this would give Scratchers a huge tool!


Although this might crowd the Variables section, and it might confuse New Scratchers, so it should exist as an Extension. (Like the Pen Extension)

dizzyboy42 wrote:

save [score v]::variables

load [score v]::variables

this would make save load for some games like RD WAY easier, it would just be the click of a button!
e.g code

when this sprite clicked::cat
save [score v]::variables

when this sprite clicked :: cat
load [score v]::variables

 

I feel this is not realistic AT ALL. Think about even any semi-popular game: they have thousands of people that play! The Scratch servers would have to handle an extravagant amount of data, causing lag.

Furthermore, some trolls might find a way to save a massive number of variables with lots of characters in them, potentially crashing Scratch.

MrSpace-fish wrote:

Support!

Handling save codes is a hassle, this would give Scratchers a huge tool!


Although this might crowd the Variables section, and it might confuse New Scratchers, so it should exist as an Extension. (Like the Pen Extension)

I agree! should I change it tho

idog9 wrote:

dizzyboy42 wrote:

save [score v]::variables

load [score v]::variables

this would make save load for some games like RD WAY easier, it would just be the click of a button!
e.g code

when this sprite clicked::cat
save [score v]::variables

when this sprite clicked :: cat
load [score v]::variables

 

I feel this is not realistic AT ALL. Think about even any semi-popular game: they have thousands of people that play! The Scratch servers would have to handle an extravagant amount of data, causing lag.

Furthermore, some trolls might find a way to save a massive number of variables with lots of characters in them, potentially crashing Scratch.

I agree with this. Definitely would take too much server data. There are over millions of users and just a few thousand is enough to need servers full of storage to hold that data which costs money that Scratch doesn't have. Plus this would probably end up with how cloud variables are now: Inconsistent and always down.

I support, this could add the opportunity to add save slots in games

Abrig67 wrote:

This is similar to cloud variables and cloud lists, both of which are rejected.
–snip–

Those were rejected because they could be used to make online chat projects - explain how you'd make a chat project with a variable that only saves for the user running the project.

Abrig67 wrote:

–snippity snip snip–
I also think this would be confusing for new Scratchers. If all they see is a ‘save variable’ with nothing else, they might be confused on how to edit it, etc.

I agree, but I have a solution: make the player variables work like cloud variables:

∆ Player variable ::variables reporter

∆ set [Player variable v] to [] ::variables

etc.

idog9 wrote:

dizzyboy42 wrote:

–snip–

I feel this is not realistic AT ALL. Think about even any semi-popular game: they have thousands of people that play! The Scratch servers would have to handle an extravagant amount of data, causing lag.

Furthermore, some trolls might find a way to save a massive number of variables with lots of characters in them, potentially crashing Scratch.

About the troll part:

• You can always add a character/number of variables limit
  
• I had the idea of a adding a menu in account settings where you can manually remove any player variables
  

edit1: does the emoji on the variables show up?
Edit2: just pretend that the triangle is a user icon

this is a duplicate please close this topic and contribute to the discussion on the linked topic

jmb1293634 wrote:

this is a duplicate please close this topic and contribute to the discussion on the linked topic

No it isn't, that suggestion is talking about saving in the browser's cookies, this suggestion is about saving to the user's profile.
I have actually seem suggestions remain open for reasons this small before

BUMP

b

u

m

p

FreshTheCat wrote:

b

u

m

p

thanks (:

B u m p

Buts

set [var v] to (load variable [var] from project with ID () ::variables)

CodeComet6161 wrote:

Dupe

closing due to dupe