minekraftkid wrote:

I'm not sure if this is still relevant, but I 100% support. It's been beautifully implemented in turbowarp, and I'd love to see it as part of the native scratch experience.

mumu245 wrote:

IDK if this has been suggested, but localStorage could be used instead of cookies. 2560 digits (the cloud variable limit) is very little for a savegame.

Also, there should be an option to clear these local variables.

Zro716 wrote:

(#3)

Superdoggy wrote:

As long as you do it right, cloud variables are a very effective method of saved games.

right, but with several users writing to the cloud at once, it can sometimes cause collisions and mishaps. like in my internetz game, I frequently get complaints about data not being saved correctly, and when I investigate it comes down to two or more users saving data at the same time. so a cloud list is not a foolproof option for per-player saved data.

cookie variables sound like a very good idea, but there needs to be some kind of restriction to prevent unlimited storage of data to a browser's cache.

superbuddy2 wrote:

Zro716 wrote:

(#3)

Superdoggy wrote:

As long as you do it right, cloud variables are a very effective method of saved games.

right, but with several users writing to the cloud at once, it can sometimes cause collisions and mishaps. like in my internetz game, I frequently get complaints about data not being saved correctly, and when I investigate it comes down to two or more users saving data at the same time. so a cloud list is not a foolproof option for per-player saved data.

cookie variables sound like a very good idea, but there needs to be some kind of restriction to prevent unlimited storage of data to a browser's cache.

Cookies could be used as spyware, like if a seller knew that you were interested in buying something, it'd up the price. If they knew you were playing this game, game devs might be able to increase the price of their game.

Lists already save data to the computer's hard drive, so you could use that instead.

superbuddy2 wrote:

Zro716 wrote:

(#3)

Superdoggy wrote:

As long as you do it right, cloud variables are a very effective method of saved games.

right, but with several users writing to the cloud at once, it can sometimes cause collisions and mishaps. like in my internetz game, I frequently get complaints about data not being saved correctly, and when I investigate it comes down to two or more users saving data at the same time. so a cloud list is not a foolproof option for per-player saved data.

cookie variables sound like a very good idea, but there needs to be some kind of restriction to prevent unlimited storage of data to a browser's cache.

Cookies could be used as spyware, like if a seller knew that you were interested in buying something, it'd up the price. If they knew you were playing this game, game devs might be able to increase the price of their game.

Lists already save data to the computer's hard drive, so you could use that instead.

54387a wrote:

(#433)

superbuddy2 wrote:

Zro716 wrote:

(#3)

Superdoggy wrote:

As long as you do it right, cloud variables are a very effective method of saved games.

right, but with several users writing to the cloud at once, it can sometimes cause collisions and mishaps. like in my internetz game, I frequently get complaints about data not being saved correctly, and when I investigate it comes down to two or more users saving data at the same time. so a cloud list is not a foolproof option for per-player saved data.

cookie variables sound like a very good idea, but there needs to be some kind of restriction to prevent unlimited storage of data to a browser's cache.

Cookies could be used as spyware, like if a seller knew that you were interested in buying something, it'd up the price. If they knew you were playing this game, game devs might be able to increase the price of their game.

Lists already save data to the computer's hard drive, so you could use that instead.

But what if you want it automatically inside the project while also not requiring the user to input it in manually? Also, it's only for the project. By the way, lists don't save automatically.

Edit: Ninja'd

when flag clicked
forever
replace (1) of [list name v] with (variable name)
end

when flag clicked
set [variable name v] to (list name :: list)

superbuddy2 wrote:

54387a wrote:

(#433)

superbuddy2 wrote:

Zro716 wrote:

(#3)

Superdoggy wrote:

As long as you do it right, cloud variables are a very effective method of saved games.

right, but with several users writing to the cloud at once, it can sometimes cause collisions and mishaps. like in my internetz game, I frequently get complaints about data not being saved correctly, and when I investigate it comes down to two or more users saving data at the same time. so a cloud list is not a foolproof option for per-player saved data.

cookie variables sound like a very good idea, but there needs to be some kind of restriction to prevent unlimited storage of data to a browser's cache.

Cookies could be used as spyware, like if a seller knew that you were interested in buying something, it'd up the price. If they knew you were playing this game, game devs might be able to increase the price of their game.

Lists already save data to the computer's hard drive, so you could use that instead.

But what if you want it automatically inside the project while also not requiring the user to input it in manually? Also, it's only for the project. By the way, lists don't save automatically.

Edit: Ninja'd

All you need is this:

when flag clicked
forever
replace (1) of [list name v] with (variable name)
end

when flag clicked
set [variable name v] to (list name :: list)

josueart wrote:

(#434)
~5 MB

54387a wrote:

(#432)

superbuddy2 wrote:

54387a wrote:

(#433)

superbuddy2 wrote:

Zro716 wrote:

(#3)

Superdoggy wrote:

As long as you do it right, cloud variables are a very effective method of saved games.

right, but with several users writing to the cloud at once, it can sometimes cause collisions and mishaps. like in my internetz game, I frequently get complaints about data not being saved correctly, and when I investigate it comes down to two or more users saving data at the same time. so a cloud list is not a foolproof option for per-player saved data.

cookie variables sound like a very good idea, but there needs to be some kind of restriction to prevent unlimited storage of data to a browser's cache.

Cookies could be used as spyware, like if a seller knew that you were interested in buying something, it'd up the price. If they knew you were playing this game, game devs might be able to increase the price of their game.

Lists already save data to the computer's hard drive, so you could use that instead.

But what if you want it automatically inside the project while also not requiring the user to input it in manually? Also, it's only for the project. By the way, lists don't save automatically.

Edit: Ninja'd

All you need is this:

when flag clicked
forever
replace (1) of [list name v] with (variable name)
end

when flag clicked
set [variable name v] to (list name :: list)

But you would need this suggestion implemented for that to work because a reload would immediately clear this without this suggestion implemented.

superbuddy2 wrote:

54387a wrote:

(#432)

superbuddy2 wrote:

54387a wrote:

(#433)

superbuddy2 wrote:

Zro716 wrote:

(#3)

Superdoggy wrote:

As long as you do it right, cloud variables are a very effective method of saved games.

right, but with several users writing to the cloud at once, it can sometimes cause collisions and mishaps. like in my internetz game, I frequently get complaints about data not being saved correctly, and when I investigate it comes down to two or more users saving data at the same time. so a cloud list is not a foolproof option for per-player saved data.

cookie variables sound like a very good idea, but there needs to be some kind of restriction to prevent unlimited storage of data to a browser's cache.

Cookies could be used as spyware, like if a seller knew that you were interested in buying something, it'd up the price. If they knew you were playing this game, game devs might be able to increase the price of their game.

Lists already save data to the computer's hard drive, so you could use that instead.

But what if you want it automatically inside the project while also not requiring the user to input it in manually? Also, it's only for the project. By the way, lists don't save automatically.

Edit: Ninja'd

All you need is this:

when flag clicked
forever
replace (1) of [list name v] with (variable name)
end

when flag clicked
set [variable name v] to (list name :: list)

But you would need this suggestion implemented for that to work because a reload would immediately clear this without this suggestion implemented.

It's local and account specific, so if you logged onto a different account on the same device, or logged into the same account on a different device, the data would not be there, but if you reloaded or exited and re-entered the webpage on the same device and you are logged into the same account, the data would remain.

54387a wrote:

(#438)

superbuddy2 wrote:

54387a wrote:

(#432)

superbuddy2 wrote:

54387a wrote:

(#433)

superbuddy2 wrote:

Zro716 wrote:

(#3)

Superdoggy wrote:

As long as you do it right, cloud variables are a very effective method of saved games.

right, but with several users writing to the cloud at once, it can sometimes cause collisions and mishaps. like in my internetz game, I frequently get complaints about data not being saved correctly, and when I investigate it comes down to two or more users saving data at the same time. so a cloud list is not a foolproof option for per-player saved data.

cookie variables sound like a very good idea, but there needs to be some kind of restriction to prevent unlimited storage of data to a browser's cache.

Cookies could be used as spyware, like if a seller knew that you were interested in buying something, it'd up the price. If they knew you were playing this game, game devs might be able to increase the price of their game.

Lists already save data to the computer's hard drive, so you could use that instead.

But what if you want it automatically inside the project while also not requiring the user to input it in manually? Also, it's only for the project. By the way, lists don't save automatically.

Edit: Ninja'd

All you need is this:

when flag clicked
forever
replace (1) of [list name v] with (variable name)
end

when flag clicked
set [variable name v] to (list name :: list)

But you would need this suggestion implemented for that to work because a reload would immediately clear this without this suggestion implemented.

It's local and account specific, so if you logged onto a different account on the same device, or logged into the same account on a different device, the data would not be there, but if you reloaded or exited and re-entered the webpage on the same device and you are logged into the same account, the data would remain.

That's a totally different suggestion that doesn't make sense and isn't implemented.

OP wrote:

I have a better idea, rather than storing cached vars as cookies (which makes people complain about spam), “cached” vars should actually be stored with each Scratch user's account info on the Scratch server.

mumu245 wrote:

IDK if this has been suggested, but localStorage could be used instead of cookies. 2560 digits (the cloud variable limit) is very little for a savegame.

Also, there should be an option to clear these local variables.

superbuddy2 wrote:

54387a wrote:

(#438)

superbuddy2 wrote:

54387a wrote:

(#432)

superbuddy2 wrote:

54387a wrote:

(#433)

superbuddy2 wrote:

Zro716 wrote:

(#3)

Superdoggy wrote:

As long as you do it right, cloud variables are a very effective method of saved games.

right, but with several users writing to the cloud at once, it can sometimes cause collisions and mishaps. like in my internetz game, I frequently get complaints about data not being saved correctly, and when I investigate it comes down to two or more users saving data at the same time. so a cloud list is not a foolproof option for per-player saved data.

cookie variables sound like a very good idea, but there needs to be some kind of restriction to prevent unlimited storage of data to a browser's cache.

Cookies could be used as spyware, like if a seller knew that you were interested in buying something, it'd up the price. If they knew you were playing this game, game devs might be able to increase the price of their game.

Lists already save data to the computer's hard drive, so you could use that instead.

But what if you want it automatically inside the project while also not requiring the user to input it in manually? Also, it's only for the project. By the way, lists don't save automatically.

Edit: Ninja'd

All you need is this:

when flag clicked
forever
replace (1) of [list name v] with (variable name)
end

when flag clicked
set [variable name v] to (list name :: list)

But you would need this suggestion implemented for that to work because a reload would immediately clear this without this suggestion implemented.

It's local and account specific, so if you logged onto a different account on the same device, or logged into the same account on a different device, the data would not be there, but if you reloaded or exited and re-entered the webpage on the same device and you are logged into the same account, the data would remain.

That's a totally different suggestion that doesn't make sense and isn't implemented.

No, that's how list saving works.

54387a wrote:

superbuddy2 wrote:

54387a wrote:

(#438)

superbuddy2 wrote:

54387a wrote:

(#432)

superbuddy2 wrote:

54387a wrote:

(#433)

superbuddy2 wrote:

Zro716 wrote:

(#3)

Superdoggy wrote:

As long as you do it right, cloud variables are a very effective method of saved games.

right, but with several users writing to the cloud at once, it can sometimes cause collisions and mishaps. like in my internetz game, I frequently get complaints about data not being saved correctly, and when I investigate it comes down to two or more users saving data at the same time. so a cloud list is not a foolproof option for per-player saved data.

cookie variables sound like a very good idea, but there needs to be some kind of restriction to prevent unlimited storage of data to a browser's cache.

Cookies could be used as spyware, like if a seller knew that you were interested in buying something, it'd up the price. If they knew you were playing this game, game devs might be able to increase the price of their game.

Lists already save data to the computer's hard drive, so you could use that instead.

But what if you want it automatically inside the project while also not requiring the user to input it in manually? Also, it's only for the project. By the way, lists don't save automatically.

Edit: Ninja'd

All you need is this:

when flag clicked
forever
replace (1) of [list name v] with (variable name)
end

when flag clicked
set [variable name v] to (list name :: list)

But you would need this suggestion implemented for that to work because a reload would immediately clear this without this suggestion implemented.

It's local and account specific, so if you logged onto a different account on the same device, or logged into the same account on a different device, the data would not be there, but if you reloaded or exited and re-entered the webpage on the same device and you are logged into the same account, the data would remain.

That's a totally different suggestion that doesn't make sense and isn't implemented.

No, that's how list saving works.

Foolproof list saving doesn't exist currently.