Scratch

One of the newer things you have been seeing are games, which only use one sprite, which uses just 1 script, which is most likely long, so it can fit the entire game of code. There have been multiple games of this style, made by scratchers including The-Whiz and RHY3756547. Here I am, to explain the pros (reasons to) and cons (reasons not to) of making these kinds of games.

Pros

- Smaller file size - One thing noticable, is that if you look at RHY3756547's game, LINE, which many have you have probably played, if you download it, its only about 239KB (memory), which is fairly low, compared to most advanced games. And the truth is, most of that is just from graphics. So how do you explain the miniscule (tiny tiny) file size? The reason for this, is because there is only one script.

- Less Lag (when playing) - Another reference to the game, LINE. Normally, there are many sprites with many scripts, so together, and due to all of those sprites and scripts computing all of the blocks and what to do, it can't update the screen as fast. In the 1-sprite 1-script situation, there is just one sprite to respond to, so it updates the screen when it can, which is usually fast. Some more evidence for this theory, is that when I was making my Super Smash Bros. Ball, I noticed even in presentation mode, that during the countdown (where there was no animations except for the countdown animation), it was quick to speed, but when the 'GO!' started, the last of the animation went slower because the screen had a lot more action going on.

Cons

- Very advanced - Because you have only one sprite, and not even a stage, there are many downfalls in scripting that you can't normally get through, so you have to use the complicated way to do what you want to do, or find a substitute or another solution. For example, in one of my 1-sprite 1-script projects, it requires to use the distance to mouse pointer block. So if this was not a 1-sprite 1-script project, there would be one sprite that was hidden at one location, and constantly set a variable to the distance from it to the mouse pointer, using that one simple block in the sensing category. But in this case, the sprite has other things to do, so it has to do it using the long written out way, so it acts 'as if the sprite was there'. Though the fact is, most poeople won't know the long written out formula. This obviously isn't the best example, but the first sentence in this paragraph says it all really.

- More lag (when scripting) - By this, I mean when you type in a number into a text box, there is a couple seconds of lag, before it highlights the previous number so you can type in the number you want to switch it to. Also  when your moving a script around the scripts section of the Scratch, it lags, so if you want to insert a group of blocks into the script, you have to guess at first of where it will go, and you hold the mouse longer, while the screen updates, so the script doesn't go where you don't want it to. Why does it do this? Because as scripts get longer, it generally becomes more and more laggier like this. Because the script will be long, as it is just 1 script for the entire game, it will quickly lag up.

I hope this helps. If there are any other major points, then just tell me!