Eng:One Sprite One Script Project

A One Sprite One Script Project, or 1s1s project, is a project that runs on only one sprite and one script. There are limitations, but most can be worked around.

Methods
Below are some of the many methods used to avoid extra scripts or sprites:
 * Multiple sprite movement The sprite will place itself at a certain set of coordinates, stamp itself, and move away, doing this at another place in an another costume to give the illusion of many sprites.
 * Swift "Auto-Lines" To draw a quick line between two points use this script:

when gf clicked clear pen up go to x: (0) y: (0)//starting position pen down go to x: (100) y: (100)//end position pen up


 * Single Frame This method is used to speed up scripts.

History
The idea of a 1s1s project is not new, but it was noticed by the Scratch Team that 1s1s projects were becoming a big trend. Although many 1s1s projects have been made before, some say that RHY3756547's LINE was the first major 1 Sprite 1 Script project this project most likely triggered the fad. Following this project, many people made their own 1s1s projects, from games to simulations. There was also a Scratch Design Studio with 1s1s projects.

Since the release of Scratch 2.0, 1s1s projects were in quick decline and the trend faded away. Although 1s1s projects are still being created, they no longer reach popularity.

Difficulties

 * The Wait Secs block will slow the entire script - one solution is to have the sprite change a variable repeatedly until it has reached a certain value. This can be an advantage or disadvantage, depending on the situation  it will be measured by the amount of frames, not the amount of time. Another solution to this is to reset the timer, and have the sprite repeat its normal functions until the timer is greater than or equal to the wanted time. The best solution is to make the script Single Frame.

Ambiguity
There are some features of Scratch that make it harder to determine if a project is 1 sprite 1 script:
 * Clones. Although clones are the same sprite, there are almost always two hat blocks - one to generate the clones and one to execute the scripts for the clones. There are, however, ways to make it only one script, such as using a When Pressed block.
 * Custom blocks. The custom block hat block counts as a separate script according to the Scratch editor, but they are necessary to run certain functions without screen refresh, which allows for pen drawn projects to be very easily made, because the screen can be rendered without a lot of lag in-player (even if there is lag in-editor).

Zero Sprite One Script (0s1s)
Some users, finding One Sprite One Script Projects too easy to make, have moved on to creating a project that runs on simply one script on the Stage no sprites included.

Some tricks for programming in this way are as follows:
 * Multiple object movementThe stage is frozen; it cannot place itself at different locations and stamp. Some backgrounds form an animation, resembling the wanted effect - but can be somewhat glitchy.
 * Mouse detectionThe stage can switch to a new background by looking at a mouse's coordinates. Using these, it can check to see if the mouse is in a certain region on the screen.

One Sprite One Script One Costume (1s1s1c)
Other users, finding One Sprite One Script projects too easy and Zero Sprite One Script projects too hard, settle for One Sprite One Script One Costume projects. With only one costume but one sprite, there are limitations to what the project can stamp, so these projects use the pen to draw objects. This is slow and time-consuming to program, so these projects are also difficult to make.

An example can be found here. Notice how the cars are drawn by a long script consisting mainly of Motion Blocks.