Cloud Variables used to only accept numbers or hexadecimal. Now, with the launch of Scratch 3, they will accept text but it will not be saved to the server, and instead they will act like regular variables. This is not as dangerous of a bug as it may first seem, because the variable will not be saved to the server, but definitely misleading and confusing behavior. You can see this at https://scratch.mit.edu/projects/276752971. Try entering a number and reloading the page versus entering a string and reloading the page. Both update the variable, but the number persists after a reload.

My browser / operating system: MacOS Macintosh X 10.14.2, Chrome 71.0.3578.98, No Flash version detected

Uh… Maybe the scratch team updated the cloud variables to support all characters?

jamer8 wrote:

Uh… Maybe the scratch team updated the cloud variables to support all characters?

They didn't. When you create a Cloud Variable, it still warns you that you can only put numbers in cloud variables, and, as my tests showed, the cloud variables aren't saved to the server.

ok then

well that sucks

If you want to store text on cloud variables you have to convert the text into numbers (a=1 b=2 c=3) and then convert it back. (1=a 2b 3=c)

Coolaction wrote:

If you want to store text on cloud variables you have to convert the text into numbers (a=1 b=2 c=3) and then convert it back. (1=a 2b 3=c)

While that could be useful, note that there's more than 10 letters in the alphabet so you'd have to figure out some way to handle k onwards.
I'd also suggest not posting on a bug/glitch report if there hasn't been a response on it for over a month unless it's something that is beneficial to the question of the topic. This sort of action is considered by the forum community to be a Necropost.

CatsUnited wrote:

Coolaction wrote:

If you want to store text on cloud variables you have to convert the text into numbers (a=1 b=2 c=3) and then convert it back. (1=a 2b 3=c)

While that could be useful, note that there's more than 10 letters in the alphabet so you'd have to figure out some way to handle k onwards.
I'd also suggest not posting on a bug/glitch report if there hasn't been a response on it for over a month unless it's something that is beneficial to the question of the topic. This sort of action is considered by the forum community to be a Necropost.

*facepalm* Why would you need multiple cloud variables to have each letter their own?

when green flag clicked
forever
go to x: (qumquat x :: sensing) y: (qumquat y :: sensing)
if <touching [evil qumquat v] ?> then
stop [evil qumquat v]
end
end