why don't the scratch team make the maximum clones limit infinite

Birdlegs

I like clone management

It's a fun brain exercise

TheHockeyist

My computer can handle 301+ clones. My guess is maybe 1000 before things go weirdo.

I support more clones, though, but with a warning that it might crash your computer if someone implements one of the many “put 1000+ clones on your screen” scripts.

AwesomeLolLol

CosmicHamster wrote:

when green flag clicked
forever
    
create clone of [myself v]
end

when I start as a clone
forever
    
create clone of [myself v]
end

Now what?

Look what happens:

when I start as a clone
create lots of lag

AwesomeLolLol

AwesomeLolLol wrote:

CosmicHamster wrote:

when green flag clicked
forever
    
create clone of [myself v]
end

when I start as a clone
forever
    
create clone of [myself v]
end

Now what?

Look what happens:

when I start as a clone
create lots of lag

when green flag clicked
say [by that I mean a LOT of lag...] for (Infinity) secs

when green flag clicked
forever
set [Infinity v] to ((Infinity) * (Infinity))
end

Last edited by AwesomeLolLol (May 12, 2015 23:34:58)

DaSpudLord

AwesomeLolLol wrote:

CosmicHamster wrote:

when green flag clicked
forever
    
create clone of [myself v]
end

when I start as a clone
forever
    
create clone of [myself v]
end

Now what?

Look what happens:

when I start as a clone
create lots of lag

when green flag clicked
say [by that I mean a LOT of lag...] for (Infinity) secs

when green flag clicked
forever
set [Infinity v] to ((Infinity) * (Infinity))
end

Please don't necropost.

DogQueenGirl

Prinseskat wrote:
Because something will crash after the first few hundred clones.

The_Scratch_Squad

DaSpudLord wrote:

AwesomeLolLol wrote:

CosmicHamster wrote:

when green flag clicked
forever
    
create clone of [myself v]
end

when I start as a clone
forever
    
create clone of [myself v]
end

Now what?

Look what happens:

when I start as a clone
create lots of lag

when green flag clicked
say [by that I mean a LOT of lag...] for (Infinity) secs

when green flag clicked
forever
set [Infinity v] to ((Infinity) * (Infinity))
end

Please don't necropost.

Um… That was posted about 2 weeks ago… And that isn't necropsying…

AGGGH! THIS IS WHY I HATE AUTO CORRECTIONS AT TIMES! IT THINKS THE WORD IS NECROPSYING WHEN IT IT NECROPOSTING!!!!

Last edited by The_Scratch_Squad (May 14, 2015 01:34:57)

greentexas

Prinseskat wrote:
Because something will crash after the first few hundred clones.

The exact number is 302.

rollercoasterfan

Some computers will be fine, but others won't be. Any computer that is over 5 years old and doesn't have great specs will be dead. The current limit is still too much for some computers, so I don't think raising the limit will benefit anybody.

Lag and crashed computers anybody?

DaSpudLord

The_Scratch_Squad wrote:
DaSpudLord wrote:
AwesomeLolLol wrote:
...
Please don't necropost.
Um… That was posted about 2 weeks ago… And that isn't necropsying…

AGGGH! THIS IS WHY I HATE AUTO CORRECTIONS AT TIMES! IT THINKS THE WORD IS NECROPSYING WHEN IT IT NECROPOSTING!!!!

Well, this was a dead topic, it had basically no supporters, so… yeah, I'd say it's necroposting.

Evil_Kumquat

CosmicHamster wrote:

when green flag clicked
forever
    
create clone of [myself v]
end

when I start as a clone
forever
    
create clone of [myself v]
end

Now what?

No Support.

PieCraftTV

I support! I made a couple “Glitch Creator” projects with tansparent sprites following your mouse then doing whatever. They constantly clone to keep the glitch pattern going, but it only lasts a few seconds. I agree with this idea completely.

greentexas

My computer makes up to 302 clones.

modrapetka

I think, is it really neccessary? Anyway, while 300 clones don´t necessarily crash the computer, it can lag seriously and you don´t want this.
And yeah, this was said already, I´m just thinking the same.

EduKumagai2003

.

Last edited by EduKumagai2003 (May 29, 2019 17:03:10)

TheLogFather

Having the maximum number of clones (301) does not cause lag, nor does it cause a crash.

Having lots of clones continually doing things at the same time causes lag.
Having clones continually creating more clones (e.g. by not realising that clones also receive broadcasts, so all of them end up cloning, rather than just the original sprite doing the cloning) can cause enough lag to make your browser effectively unusable (so it's as if it crashes).

I'd be very surprised if just having 300 clones, which are not all created at once (i.e. a short delay between each), and which are all doing nothing, can cause a crash - if anyone does have such a machine, let me know!

But you really don't need clones to cause either of the above…

You can cause lag simply by forever doing lots of pen drawing within a non-refresh custom block.
You can cause a *real* Flash crash (not just unresponsive browser) within 3-4 seconds with a simple two-block script, if you know how.

Last edited by TheLogFather (May 28, 2015 22:46:54)

Discuss Scratch