deck26 wrote:

Please give more detail. Total of what?

change [total v] by (1)

deck26 wrote:

So when you get a new point you increase the total by 1

change [total v] by (1)

change [total v] by (currentchange)

deck26 wrote:

So you use a variable

change [total v] by (currentchange)

deck26 wrote:

If you're trying to use cloud variables you need to allow 0.1 seconds between updates, even to different variables. So updating a cloud variable in a forever loop without any delay is always going to be problem. Same goes for setting two cloud variables in consecutive blocks. So just looking at Sprite1 shows problems.

Why does Sprite1 check the backdrop in multiple green flag scripts? They all seem to be setting the costume to the named costume that corresponds to the backdrop number so these aren't actually doing anything.

So is Sprite1 the right sprite to be looking at or is it another one? Giving your sprites meaningful names would be a lot better than just keeping the default SpriteN names.

So please spend time identifying the sprite and script involved and explain how to see the issue and the symptoms. If it is the cloud variables I referred to you need to address those though.

letmethinkforaminute wrote:

deck26 wrote:

If you're trying to use cloud variables you need to allow 0.1 seconds between updates, even to different variables. So updating a cloud variable in a forever loop without any delay is always going to be problem. Same goes for setting two cloud variables in consecutive blocks. So just looking at Sprite1 shows problems.

Why does Sprite1 check the backdrop in multiple green flag scripts? They all seem to be setting the costume to the named costume that corresponds to the backdrop number so these aren't actually doing anything.

So is Sprite1 the right sprite to be looking at or is it another one? Giving your sprites meaningful names would be a lot better than just keeping the default SpriteN names.

So please spend time identifying the sprite and script involved and explain how to see the issue and the symptoms. If it is the cloud variables I referred to you need to address those though.

It is the cloud save variables and the green flag scripts is for the backdrop

deck26 wrote:

letmethinkforaminute wrote:

deck26 wrote:

If you're trying to use cloud variables you need to allow 0.1 seconds between updates, even to different variables. So updating a cloud variable in a forever loop without any delay is always going to be problem. Same goes for setting two cloud variables in consecutive blocks. So just looking at Sprite1 shows problems.

Why does Sprite1 check the backdrop in multiple green flag scripts? They all seem to be setting the costume to the named costume that corresponds to the backdrop number so these aren't actually doing anything.

So is Sprite1 the right sprite to be looking at or is it another one? Giving your sprites meaningful names would be a lot better than just keeping the default SpriteN names.

So please spend time identifying the sprite and script involved and explain how to see the issue and the symptoms. If it is the cloud variables I referred to you need to address those though.

It is the cloud save variables and the green flag scripts is for the backdrop

But those scripts just switch the backdrop to the current backdrop - so they do nothing. It's like saying if you're outside go outside and if you're inside go inside. What do you think the scripts are doing?

So you need to modify your scripts to not try to write to the cloud without allowing for that delay. If you don't believe that's the problem try changing to non-cloud variables and you should see it works - or if not you're at least dealing with a simpler problem.

letmethinkforaminute wrote:

I finally made it work, there’s a slight delay but it works

letmethinkforaminute wrote:

deck26 wrote:

The backdrops scripts were for so people couldn’t cheat by pressing the flag and switching back to backdrop 1 but it didn’t work

No, it wouldn't. The built in variables are just different ways of accessing the information about the current backdrop and are always in sync.

You'd need to have a separate variable keeping track of backdrop number or name and use that to control the backdrop but it shouldn't be necessary and if someone is going to cheat they can cheat that system anyway.

deck26 wrote:

letmethinkforaminute wrote:

deck26 wrote:

The backdrops scripts were for so people couldn’t cheat by pressing the flag and switching back to backdrop 1 but it didn’t work

No, it wouldn't. The built in variables are just different ways of accessing the information about the current backdrop and are always in sync.

You'd need to have a separate variable keeping track of backdrop number or name and use that to control the backdrop but it shouldn't be necessary and if someone is going to cheat they can cheat that system anyway.

Oh ok