|This article or section documents something not included in the current version of Scratch (3.0). It is only useful from a historical perspective.|
- On Tuesday, February 22, 2011, an announcement was made about the new player. It asked for feedback and bug reports. Within an hour, there were more than 20 replies, many of them giving much praise to the new player.
- On Thursday, October 18, 2012, an announcement was made about the flash player becoming the default, even for non-registered users.
- On Saturday, May 9, 2013, the Flash Player exited its beta stage, and became the official, only player available on the Scratch website.
- On Wednesday, January 2, 2019, the Flash Player was terminated due to the release of Scratch 3.0.
There were several noticeable changes from the Java player. Some of these included:
- Scratch 2.0 styling
- An enlarged screen mode that adjusted to one's web browser's size
- Text in variables and lists were vector text
- Variables and lists were displayed differently
- The "ask" box showed a cursor
- A new Flash loading bar
- Shift-clicking the Green Flag would switch the project to Turbo Mode; shift-clicking the flag again will put the project back into regular mode. Turbo mode can be helpful for performing complicated computations rapidly
- Supported some blocks that would appear in Scratch 2.0
- Scratch projects could be opened from local files by shift-clicking the version number
- This article is about the version in Scratch 2.0. For the feature in Scratch 1.4, see Presentation Mode.
There was a full screen option in the Flash Player. If the browser is put into full screen mode, then Scratch is put into full screen. Full screen is very similar to presentation mode, except presentation mode doubled the stage's vertical and horizontal resolution, and full screen mode scales and fits to one's browser's displaying size.
When the button is clicked, it goes into full screen, which almost fits the computer's resolution, through displaying tools; and when the button is clicked, the resolution adjusts back to normal size.
Bitmap graphics may look pixelated in full screen mode.
If the Flash Player runs something which causes too much lag, the Adobe Flash Player will crash. The user can reload the Flash Player by reloading the page. On certain browsers, there's an option to send a crash report. However, this isn't necessary.
In Internet Explorer, when the Flash Player crashes, it leads to a white screen with a circle containing an exclamation mark. On Firefox, it shows a sad plugin, as seen on the image on the right. On Google Chrome, it crashes to a black screen with a dead puzzle piece.
- HTML5 Player
- Java Player
- Experimental Viewer
- Scratch 2.0
- Forum topic: Beta Flash player
- Forum topic: Report bugs in the Flash-Based Scratch Player beta here!