http://scratch.mit.edu/projects/11650770/

Ok, for some reason, if you get the timing of the warp the same time an asteroid hits the bottom of the screen (I think this is when is happens) it spams the game with clones until the browser freezes. Why is this happening?? I had a bug free game and this stupid bug ruins it

birchyboii wrote:

http://scratch.mit.edu/projects/11650770/

Ok, for some reason, if you get the timing of the warp the same time an asteroid hits the bottom of the screen (I think this is when is happens) it spams the game with clones until the browser freezes. Why is this happening?? I had a bug free game and this stupid bug ruins it

How do you get the warp? I keep dying
I really need to recreate the bug before attempting a fix

go through the purple orb

My guess would be that you haven't taken into consideration that all clones receive broadcasts, not just the original sprite. So, if you have a sprite with a receive broadcast script that creates another clone, the number of clones will double (rather than just adding one more, as you may have intended).

A quick look at your asteroid scripts suggests this may well be what's happening…

Hope that helps!

how'd you suppose I get around this?

It is a very uncommon glitch but It would be nice to fix it

You could make it so it only creates another clone if it itself isn't a clone (the original sprite).

Create a local variable in the asteroid sprite (call it IAmAClone? or something) and after ‘when gf clicked’, add in “set IAmAClone? to 0”. (0 will be the equivalent of no and 1 = yes).

Then after “when i start as a clone”, add “set IAmAClone? to 1”.

Finally, wrap a “if IAmAClone? = 0” around the cloning script.

Hope this helps!

thanks, that may solve the issue! I'll implement it into the code as soon as I can

Yeah, that's the one - a local variable to say if you're a clone or not.

It's not that uncommon to find glitches caused by this - I've seen it several times in posts here (which is why it was the first thing I thought to suggest) - I mean, until you actually stop to think about it, and test it to see what happens with clones and broadcasts, it's not obvious that you need to guard against it…