With 2.0, do projects with clones still count as 1s1s? This may have been asked before, but I couldn't find it.

Even if you implement cloning capabilities, if you have only one sprite and one script in the project, it should still be considered 1s1s.

EDIT: Whoops. I forgot that 1s1s meant one script, one sprite for a second. Anything with clones is probably not gonna be 1s1s, then.

I think that

when I start as a clone

would count as the start of a second script. However, you could potentially work around this by having the script start with

when this sprite clicked

and then clicking on any clones to get them up and running.

–Danlo

Ahhh… Well… 1s1s projects are in my opinion ONLY 1 sprite with ONLY 1 script (meaning ONLY one hat block in use)

Which is why custom blocks don't count as 1s1s projects.

Of course, there really is no official definition, so believe whatever you want.

I think that the “when I start as a clone” wouldn't count because it doesn't affect the main sprite, and only runs at runtime on it's respective clone.

I count

 
when I start as a clone

as a second script, but I do not count procedures, as long as they are not being used instead of broadcasting.

My definition of 1s1s is the following:
1s1s: 1 Sprite with 1 running script. That means:
- A project which uses only one “when green flag clicked” etc. block can use custom blocks and “broadcast … and wait” blocks - because it is still one script, but splitted.
- All scripts have to be in 1 sprite.
- If you clone a sprite, “When I start as a clone” and “When I receive …” blocks mustn't be used.
- No scripts are running simultaneously.

1s1s1c

1 sprite
1 sprite script
1 clone script

…could be one way to think of it.

TimothyLawyer wrote:

1s1s1c

1 sprite
1 sprite script
1 clone script

…could be one way to think of it.

But 1s1s1c is 1 sprite, 1 script, 1 costume.