Hi, what do you think of the idea of us being able to export our projects to .exe, so we can have playable pc games? And as an addition to that, Scratch could make new script blocks: Saving. Something like“ ”Save the Game“ would make the game save the progress. So we could make either Saving with a button like: ”when the sprite clicked —-> Save the game“ or make the game always save: ”When the green flag clicked —-> always —-> Save the game —-> Wait 0.01 seconds" It could be really helpful since I published my game on gamejolt and people can't save their game. Have a nice day.

Please only put 1 suggestion per topic, otherwise they will drown each other out.
Note that exporting Scratch to EXE is rejected:

Za-Chary* wrote:

2.5 Official Scratch to EXE converter
On Scratch, an important goal is to have anyone be able to look at the code for any project. This philosophy is not only important for learning code and remixing, but is also important for moderation purposes; for more information, see #3.2 and #4.1 on this list. Converting to EXE (or any other black box executables) will prevent users from looking at the code, and hence goes against this philosophy. Third-party converters do exist, and you are allowed to use those, but the Scratch Team will not make an official converter.

As a replacement, use this method.
Please read the pinned topics before posting.

Converting to EXE is rejected (and I got ninja'd):

The Official List Of Rejected Suggestions wrote:

2.5 Official Scratch to EXE converter
On Scratch, an important goal is to have anyone be able to look at the code for any project. This philosophy is not only important for learning code and remixing, but is also important for moderation purposes; for more information, see #3.2 and #4.1 on this list. Converting to EXE (or any other black box executables) will prevent users from looking at the code, and hence goes against this philosophy. Third-party converters do exist, and you are allowed to use those, but the Scratch Team will not make an official converter.

And saving is a dupe.
(Also, if you're publishing using either the HTMLifier or the TurboWarp Packager, there's an option to save cloud variables to local storage (which is ususally on by default).)