Still broken. Whats going on?

e

apparently all you gotta do is just rename the variable..

Mano21x wrote:

Still broken. Whats going on?

please don't necropost lol (posting on forums with 1+ month inactivity)

The same problem

When i reload my page my cloud variable is 0.

My New Game does that too
Here Is The Link https://scratch.mit.edu/projects/992467877/

im still having this problem in 2024

people were having this problem 3 years ago

I am having this problem now! Was just discussing this at another forum: https://scratch.mit.edu/discuss/topic/751588/?page=1#post-7896339

I don't think that this is a bug anymore, as the issue still exists. (I think it's intentional, maybe to save up some space). When joining a new game, the variable will be set to whatever it was when it was last saved. While this means you can no longer have a highscore counter, it also creates issues for online games as well. For these, make sure that when new players join, they wait the maximum amount of time between cloud var updates so that they don't override them with their “reseted” variables.

MrKingofScratch is correct. I checked the last high score feature on one of my games. It was more than 12 days ago. Therefore, this is the new cloud variable feature now. No more saving of history.

So what do i do then

Tml321 wrote:

So what do i do then

it should all work now, if it doesn't rename the variable a bunch, but it works now

???

still no work

Im currently trying to make an auto save feature for my RNG game, but to no avail it doesn't save for some strange reason idk why

BabyBallHead wrote:

when green flag clicked I made a "World Record" Variable and sometimes when I beat it, it wouldn't save ;(

forever
if <(foo) < (☁ score)> then
set (☁ score) to (foo)
end
end

Same with me

its still broken, im trying to make a world wide clicker game but its not saving….

when this sprite clicked

change [ ☁️score v] by (1)

when page reset

set [ ☁️score v] to [0]

this is fixed i think. delete and remake your variables and it should be fixed as of now

Mano21x wrote:

(#39)
this is fixed i think. delete and remake your variables and it should be fixed as of now

For anyone else reading: try renaming them a few times before deleting them!

Last time I tried that, all my cloud variables started working properly again.