Cloud variables consume a lot of server space, so remove them.
How will multiplayer work instead? I propose 2 new block ideas and 2 new data types:
/ Multiplayer Variables /

set [variable name v] to [eurhoshirhiei] for (username) :: variables
change [variable name v] by [11] for (username) :: variables

Cloud variables would work the same, but with a lot more restrictions and they would be renamed to “global cloud variables”,
and the multiplayer blocks i made above would be using a new type of variable called a “user cloud variable”, which has the value set differently for each user, but the value set when created in the editor is the default.
And I guess there would be a new tab for viewing and modifying each user’s variable like a sheet?

Not every project with cloud variable…is a multiplayer game. No support.

48kxzh0tzz_____ wrote:

Not every project with cloud variable…is a multiplayer game. No support.

You are not required to create a user cloud variable though? I am not proposing to completely remove normal cloud ones, just saying they should be renamed to global cloud variables to avoid confusion from the user one. This new suggestion makes it easier for multiplayer ones

yes-i-am-lanky wrote:

I am not proposing to completely remove normal cloud ones, just saying they should be renamed to global cloud variables to avoid confusion from the user one.

That's not what your first two sentences say???

yes-i-am-lanky wrote:

Remove cloud variables / Cloud variables consume a lot of server space, so remove them.

Za-Chary wrote:

yes-i-am-lanky wrote:

I am not proposing to completely remove normal cloud ones, just saying they should be renamed to global cloud variables to avoid confusion from the user one.

That's not what your first two sentences say???

yes-i-am-lanky wrote:

Remove cloud variables / Cloud variables consume a lot of server space, so remove them.

I am proposing for the original cloud variables to be removed, and that they are replaced with a more limited, but simpler version, and not to completely absolutely remove them.

no support. these seem more complicated than the original, and tbh the original cloud variables work fine.
if the scratch team were worried about server space usage because of cloud variables they probably would have done something already.

No support
I use cloud data all the time, and not everything I make is a multiplayer game.
Cloud variables work just fine so no support.

No support
It’s more work and it seems more confusing then the cloud variables we already have.and all the projects that use them will be broken.

Prince_Wolf1 wrote:

No support
It’s more work and it seems more confusing then the cloud variables we already have.and all the projects that use them will be broken.

they will be replaced with the global ones ??

yes-i-am-lanky wrote:

Za-Chary wrote:

yes-i-am-lanky wrote:

I am not proposing to completely remove normal cloud ones, just saying they should be renamed to global cloud variables to avoid confusion from the user one.

That's not what your first two sentences say???

yes-i-am-lanky wrote:

Remove cloud variables / Cloud variables consume a lot of server space, so remove them.

I am proposing for the original cloud variables to be removed, and that they are replaced with a more limited, but simpler version, and not to completely absolutely remove them.

pretty sure they are limited enough and wouldn't this suggestion break all existing cloud projects?

I don't agree either, it takes a lot of resources to change something on Scratch, and there's just a small group of people with little budget, so every penny spent has to count, and when they change something so crucial, it might confuse people or brake old projects, so I don't think they are gonna do something about this so soon.

yes-i-am-lanky wrote:

Prince_Wolf1 wrote:

No support
It’s more work and it seems more confusing then the cloud variables we already have.and all the projects that use them will be broken.

they will be replaced with the global ones ??

They would have too be changed I think.they can’t automatically do it

yes-i-am-lanky wrote:

48kxzh0tzz_____ wrote:

Not every project with cloud variable…is a multiplayer game. No support.

You are not required to create a user cloud variable though? I am not proposing to completely remove normal cloud ones, just saying they should be renamed to global cloud variables to avoid confusion from the user one. This new suggestion makes it easier for multiplayer ones

global is a COMPLETELY different word
if you're a programmer…
a variable (or even a function) will have different scopes: local and global. a local scope is where the variable is only accessible to one portion of code and code in the same block (or further down the tree)
a global variable is a variable that can be accessed by the entire process, regardless of what file is attempting to call the variable.
they are NOT anything close to cloud variables
so renaming cloud variables to global variables is inherently confusing and misleading

Banana

banana439monkey wrote:

(#13)
~snip~

a variable (or even a function) will have different scopes: local and global. a local scope is where the variable is only accessible to one portion of code and code in the same block (or further down the tree)
a global variable is a variable that can be accessed by the entire process, regardless of what file is attempting to call the variable.

A local cloud variable would only be accessible to one user, and a global cloud variable would be accessible to the entirety of Scratchers.

I think they have similar semantic meaning

No Support
This would be too confusing for new scratchers

WallydogChoppychop wrote:

No Support
This would be too confusing for new scratchers

It is not available to new scratchers…

banana439monkey wrote:

yes-i-am-lanky wrote:

48kxzh0tzz_____ wrote:

Not every project with cloud variable…is a multiplayer game. No support.

You are not required to create a user cloud variable though? I am not proposing to completely remove normal cloud ones, just saying they should be renamed to global cloud variables to avoid confusion from the user one. This new suggestion makes it easier for multiplayer ones

global is a COMPLETELY different word
if you're a programmer…
a variable (or even a function) will have different scopes: local and global. a local scope is where the variable is only accessible to one portion of code and code in the same block (or further down the tree)
a global variable is a variable that can be accessed by the entire process, regardless of what file is attempting to call the variable.
they are NOT anything close to cloud variables
so renaming cloud variables to global variables is inherently confusing and misleading

Banana

I am a programmer too thanks

ticoeteco23gb wrote:

I don't agree either, it takes a lot of resources to change something on Scratch, and there's just a small group of people with little budget, so every penny spent has to count, and when they change something so crucial, it might confuse people or brake old projects, so I don't think they are gonna do something about this so soon.

“Oh I dOnT agReE cuZ tHe ScRaTcH T-“ Then if it takes billions of dollars to change a few blocks then why not remove the entire suggestions forum altogether? I mean, they can’t be bothered to consider one suggestion huh?

yes-i-am-lanky wrote:

“Oh I dOnT agReE cuZ tHe ScRaTcH T-“ Then if it takes billions of dollars to change a few blocks then why not remove the entire suggestions forum altogether? I mean, they can’t be bothered to consider one suggestion huh?

they spend money and time developing suggestions that are actually plausible.
This suggestion is basically removing cloud variables, re-adding them back in, and then renaming everything into confusing terms which make no sense whatsoever. It's completely unnecessary, it contradicts itself, and it's confusing. You're taking a problem and then making it even worse(this method doesn't solve the problem that “cloud variables take too much space, let's remove them.” since not only are you literally adding them back in, you're making them even more complicated).
Think about it. The current system works fine. It is simple(r) and while it takes up space, the servers can handle it. This version is complicated, doesn't make sense, probably won't work fine, and takes up more space than the normal cloud variables. If you ask me, the current cloud variables would be a solution to this suggestion, not the other way around.
I would also like to point out that removing the suggestions forum would cost more than adding this in.

yes-i-am-lanky wrote:

Za-Chary wrote:

yes-i-am-lanky wrote:

I am not proposing to completely remove normal cloud ones, just saying they should be renamed to global cloud variables to avoid confusion from the user one.

That's not what your first two sentences say???

yes-i-am-lanky wrote:

Remove cloud variables / Cloud variables consume a lot of server space, so remove them.

I am proposing for the original cloud variables to be removed, and that they are replaced with a more limited, but simpler version, and not to completely absolutely remove them.

Then it's not removing them, it's just changing them. “Removing” means “removing”, so if you use it to mean “changing”, chances are thousands of people are going to completely misinterpret it.

ajskateboarder wrote:

banana439monkey wrote:

(#13)
~snip~

a variable (or even a function) will have different scopes: local and global. a local scope is where the variable is only accessible to one portion of code and code in the same block (or further down the tree)
a global variable is a variable that can be accessed by the entire process, regardless of what file is attempting to call the variable.

A local cloud variable would only be accessible to one user, and a global cloud variable would be accessible to the entirety of Scratchers.

I think they have similar semantic meaning

no not at all
a global variable is comparable to a variable accessible to ALL sprites, not all users. a cloud variable would refer to a variable that is externally stored on a central server, which is what scratch does. the global variable is ONLY accessible WITHIN ALL THROUGHOUT the entire process, not the entire world

Banana

yes-i-am-lanky wrote:

I am a programmer too thanks

then you'd know that changing the name to “global variables” would be an inherently bad idea and would be confusing to the literal entire world
programmers would assume that a “global variable” refers to one that can be accessed by the entire project and new users would not understand that “global” refers to “cloud”, where cloud is an absolutely universal buzzword such that the entire world knows what it means at this point. even current users would be confused given that the name of something that has stayed the same for nearly a decade has suddenly changed for no good/apparent reason

also new scratchers/users in this context does not necessarily refer to the status of a user and instead refers to their familiarity with scratch. for example, someone with full scratcher status can still be “new” to using scratch (or just new to scratch hence), especially if they're unfamiliar with it or/and have only used it for two or so weeks. they could well still be considered to be new.

Banana