Scratch

joefarebrother wrote:

kayybee wrote:

joefarebrother wrote:

It's what happened when I tested it before making this topic.

You're a tester? Oh. Never saw you on the forum.
But it's always been the way I described, so I don't know if you we're doing something differently. Look at my project the billion button. Look inside it and you'll see that each digit has its own variable. Or my particle test. The most recent one with gravity. The gravity wouldn't work if they all had the same variable...

I'm not a tester, I've just read this. At some point before I made this topic I did a test and local variables worked as sprite-specific, not clone-specific.

But I tested it and it did what I described so...

joefarebrother wrote:

kayybee wrote:

joefarebrother wrote:

I'm not a tester, I've just read this. At some point before I made this topic I did a test and local variables worked as sprite-specific, not clone-specific.

But I tested it and it did what I described so...

OK, I'm just saying that the last time I tested it, they worked as sprite-specific. It must have changed since I tested it. I'll edit the OP.

I don't think they changed it because it also worked last week and before when I created my project the billion button and CPU made pico...

KrIsMa wrote:

Stage local variables although I don't think it would be helpful.

How many times have you made a project where there are tons of variables that are only needed in a few scripts? You probably make them local variables of the sprite, to avoid cluttering the pallet of globals. Now what if you had to do that with the stage?

Script variables block would be more useful, because you could save the results of a long calculation in a variable. How many times have you had to do this?

stuff
set [result v] to (long, complex calculation)
use (result) in the script, possibly more than once
more stuff
set [other result v] to (something else)
...

This will clutter up the variable pallet.

With your idea, you would have to do this:

stuff
broadcast [use the result v]  (long, complex calculation)
when i receive [use the result v] (result)
use the result
more stuff
broadcast [use the next result v] (another calculation)
when i receive [use the next result v] (result)
...

This clutters up the broadcast menu!
With a script variables block, you could do

script variables (result1) (result2)
as first example, but the pallet isn't cluttered!