Why is there a clone limit in the first place? Why not set it to 2147483647 or something?

Because lag

You can still make 301 though. Im not sure why you would need more clones than that.

customhacker wrote:

You can still make 301 though. I'm not sure why you would need more clones than that.

Hacking or using the main sprite?

1a3c5e7g9i wrote:

customhacker wrote:

You can still make 301 though. I'm not sure why you would need more clones than that.

Hacking or using the main sprite?

No, you can make 301 clones because of a bug in the scratch code that lets you make one more clone once you get to 300.

LAG is a word.

As mentioned by others, the limit is there to fight lag. I don't support as the limit's likely higher than you would ever need, and plus you can just duplicate the original sprite with the cloning scripts inside it.

Its because of Lag even if i make like 20 clones my cpu starts to lag.

Once upon a time, In a game called roblox, where you are free to copy a block as much as you want


my computer bluescreened multiple times


THAT is why we arent allowed to have infinate clones

miniepicness wrote:

Once upon a time, In a game called roblox, where you are free to copy a block as much as you want


my computer bluescreened multiple times


THAT is why we arent allowed to have infinate clones

Eh, it kind of depends on your device specs. I have an Intel i3 core and I can put a few thousand blocks down without lag.

The4thPixel wrote:

miniepicness wrote:

Once upon a time, In a game called roblox, where you are free to copy a block as much as you want


my computer bluescreened multiple times


THAT is why we arent allowed to have infinate clones

Eh, it kind of depends on your device specs. I have an Intel i3 core and I can put a few thousand blocks down without lag.

itll bluescreen any kind, just go on some admin house games and nuke yourself 50 times
… along with 12 other people 50 times

No support, we don't want random computers crashing just because of lag.

-stache- wrote:

Because lag

JonathanSchaffer wrote:

LAG is a word.

gems89 wrote:

Its because of Lag even if i make like 20 clones my cpu starts to lag.

PrincessPanda_test_ wrote:

No support, we don't want random computers crashing just because of lag.

^^^

Have you ever seen a project with 300 clones? It lags quite a bit. If we were to increase the limit to even 1000, I'm pretty sure the vast majority of computers, even good ones, would be unable to render that many clones without trouble. My computer is pretty beefy (it handled a forum post composed mostly of tons and tons of scratchblocks, which apparently nearly crashed other peoples' computers), and even it can't handle many clones.
I'm sorry, but you've got no support from me on this one.

It's because lot's of people running Scratch have slow computers. Also, edit your post: The limit is 301, not 300.

WolfCat67 wrote:

Have you ever seen a project with 300 clones? It lags quite a bit. If we were to increase the limit to even 1000, I'm pretty sure the vast majority of computers, even good ones, would be unable to render that many clones without trouble. My computer is pretty beefy (it handled a forum post composed mostly of tons and tons of scratchblocks, which apparently nearly crashed other peoples' computers), and even it can't handle many clones.
I'm sorry, but you've got no support from me on this one.

Not if you have a fast computer.

Just to clarify about clones and lag…

Having lots of clones does not cause lag.

Continually telling lots of clones to do intensive things (such as switch costume, resize, rotate, graphic effects) does cause lag.

Also, creating a clone is fairly intensive, but particularly so if the sprite it is cloned from has resize/rotate/effects applied (since that means these things have to be applied to the clone's costume, too, when it is created). So continually creating numerous clones can also cause lag (but how many you can get away with creating at each frame will depend on what needs to be applied to the costume, how large that costume is, and how good your computer is – but I would recommend keeping it down to only a handful at once).

If you avoid continually telling clones to change their looks, and you avoid continually creating many clones (instead of deleting & recreating them, create as many as you'll need at the start, and reuse them when needed), then even a slow computer can easily handle all 301 clones.


The problem, then, is that Scratch makes it so easy to ‘abuse’ lots of clones, scripting them in a naive way (without realising!) such that it causes a lot of lag.

TheLogFather wrote:

Just to clarify about clones and lag…

Having lots of clones does not cause lag.

Continually telling lots of clones to do intensive things (such as switch costume, resize, rotate, graphic effects) does cause lag.

Also, creating a clone is fairly intensive, but particularly so if the sprite it is cloned from has resize/rotate/effects applied (since that means these things have to be applied to the clone's costume, too, when it is created). So continually creating numerous clones can also cause lag (but how many you can get away with creating at each frame will depend on what needs to be applied to the costume, how large that costume is, and how good your computer is – but I would recommend keeping it down to only a handful at once).

If you avoid continually telling clones to change their looks, and you avoid continually creating many clones (instead of deleting & recreating them, create as many as you'll need at the start, and reuse them when needed), then even a slow computer can easily handle all 301 clones.


The problem, then, is that Scratch makes it so easy to ‘abuse’ lots of clones, scripting them in a naive way (without realising!) such that it causes a lot of lag.

I understand now, but why would they want a higher clone limit if they wouldnt be using 12849213599 clones
using 12849213599 clones
RIP MY COMPUTER IF THAT HAPPENS

miniepicness wrote:

I understand now, but why would they want a higher clone limit if they wouldnt be using 12849213599 clones
using 12849213599 clones
RIP MY COMPUTER IF THAT HAPPENS

You can ‘use’ clones without continually having them do intensive things.

For example, just moving 301 clones around the screen is no problem.

If you only change the costume/size/direction/effects for the clones every so often, then it's also no problem.


But it's so easy in Scratch to make the mistake of telling clones (or any sprite, for that matter) to do anything & everything all the time (even when not necessary, because it's already set to the costume/size/direction/effect you wanted), so there's a clone limit to avoid that causing too much trouble.