deck26 wrote:

If this was a while ago it may have been before Scratch limited cloud variables to 256 digits - at one time you could store 10240 digits per variable. This change happened before Scratch 3 - latter day Scratch 2 only allowed 128 digits per variable.

codeman1044 wrote:

I've seen a lot of cloud issues come up since 3.0 dropped, and the most common solution I've seen is to delete your cloud variables then rewrite it the same way. It's really annoying to do, but I think it's with the way that the cloud variables changed in 3.0, and their old code is obsolete.

when green flag clicked
wait (1) secs // Allow time for the variables to load
set [1 v] to (☁ 1)
wait (0.1) secs // Could probably use smaller/no delay
set [2 v] to (☁ 2)
wait (0.1) secs
set [3 v] to (☁ 3)
wait (0.1) secs
set [4 v] to (☁ 4)

define list to variables
...
set [update cloud v] to [1] // Replaces setting the cloud vars

when green flag clicked
forever
wait until <(update cloud) = [1]>
set [update cloud v] to [0]
set [☁ 1 v] to (1::variables)
wait (0.1) secs // Could probably use a smaller delay
set [☁ 2 v] to (2::variables)
wait (0.1) secs
set [☁ 2 v] to (2::variables)
wait (0.1) secs
set [☁ 4 v] to (4::variables)
wait (0.1) secs // Might not need this one
end

imfh wrote:

I can see in the cloud log that it is changing two of the cloud variables, but it doesn't seem to read the changes when I reload the page. Additionally it seems that only variable 1 and 4 are being set. You might be reading/setting the variables too quickly, maybe add a delay? Scratch sometimes disconnects from the cloud server for acting too fast. You could try something like this to limit how fast they are read and changed:

when green flag clicked
repeat until <(☁ new scratcher)=[1]>
wait (1) secs // Large delay to prevent the server from disconnecting with the repeated loop
set [1 v] to (☁ 1)
wait (0.1) secs
set [2 v] to (☁ 2)
wait (0.1) secs
set [3 v] to (☁ 3)
wait (0.1) secs
set [4 v] to (☁ 4)
end
...