In a game, say there are, for example, secret codes you have to crack or usernames/password storage. The See Inside ruins it all. If you could have, for example a checkbox that disables or enables See Inside, then so many more things could be possible.

Why would you want to create and share secret and private information on Scratch? Oh, anyone can access anything, no matter what privacy thingies you set.

No support. Scratch is meant to be an open source code for everyone to learn and build upon. The stickies also reject this suggestion.

Stickies wrote:

Several people want to be able to lock their projects so that they are read-only, and other people can't see the code to copy their scripts, sounds, or artwork. However, the motto of Scratch is “Imagine - Program - Share”. By putting a project on the site, you give anyone who sees it the right to see your code, all data in it, and potentially copy it. Part of the whole goal of Scratch is remixing. If you do not wish to allow this, then you are welcome to publish the project on your own site (once the downloadable Scratch 2.0 comes out).

DownsGameClub wrote:

Why would you want to create and share secret and private information on Scratch? Oh, anyone can access anything, no matter what privacy thingies you set.

No support. Scratch is meant to be an open source code for everyone to learn and build upon. The stickies also reject this suggestion.

Stickies wrote:

Several people want to be able to lock their projects so that they are read-only, and other people can't see the code to copy their scripts, sounds, or artwork. However, the motto of Scratch is “Imagine - Program - Share”. By putting a project on the site, you give anyone who sees it the right to see your code, all data in it, and potentially copy it. Part of the whole goal of Scratch is remixing. If you do not wish to allow this, then you are welcome to publish the project on your own site (once the downloadable Scratch 2.0 comes out).

I disagree. If there is a code you have to crack in the game, or something, people could just walk right inside, sift through the scripts, find out the correct answer, and type it in.

How will people be able to remix a project with see inside disabled? And what if someone wanted to see how something worked in a project? This would limit learning

hm… didn't think 'bout that… how about on the outside of it they add a remix button?

Defiently no support

Da sticky wrote:

Disabling “See inside”, restricting sharing, etc.
Several people want to be able to lock their projects so that they are read-only, and other people can't see the code to copy their scripts, sounds, or artwork. However, the motto of Scratch is “Imagine - Program - Share”. By putting a project on the site, you give anyone who sees it the right to see your code, all data in it, and potentially copy it. Part of the whole goal of Scratch is remixing. If you do not wish to allow this, then you are welcome to publish the project on your own site (once the downloadable Scratch 2.0 comes out).

Restricting sharing (i.e. sharing a project so only some people can see it) is also not going to be implemented.

Paddle2See wrote:

We depend very heavily on our community to help us keep an eye on things and make sure that the Community Guidelines are being followed. Reducing the number of people that can see a project increases the likelihood that inappropriate content could be shared without being reported. That's a risk that we are not willing to take. Keeping everything out in the open is the best way we have found to help keep Scratch friendly and safe.
(source)

Also, Scratch is meant for learning. If the project had its code hidden, then how would people learn from it? If you're worried about cheating, it doesn't matter.

Rejected by sticky so No Support

Nightseeker1 wrote:

hm… didn't think 'bout that… how about on the outside of it they add a remix button?

Then they could remix see the code and delete the remix.

This suggestion is rejected:

jvvg wrote:

3. Disabling “See inside”, restricting sharing, etc.
Several people want to be able to lock their projects so that they are read-only, and other people can't see the code to copy their scripts, sounds, or artwork. However, the motto of Scratch is "Imagine - Program - Share". By putting a project on the site, you give anyone who sees it the right to see your code, all data in it, and potentially copy it. Part of the whole goal of Scratch is remixing. If you do not wish to allow this, then you are welcome to publish the project on your own site (once the downloadable Scratch 2.0 comes out).

Restricting sharing (i.e. sharing a project so only some people can see it) is also not going to be implemented.

Paddle2See wrote:

We depend very heavily on our community to help us keep an eye on things and make sure that the Community Guidelines are being followed. Reducing the number of people that can see a project increases the likelihood that inappropriate content could be shared without being reported. That's a risk that we are not willing to take. Keeping everything out in the open is the best way we have found to help keep Scratch friendly and safe.
(source)

In the case of wanting to keep a “password” secret, you aren't storing the “password” securely at all. You should always hash passwords.

Stickies say no support.

Sigton

People are already helping you, but I'd also like to mention that this is in the FAQ page:

What if I don’t want others to remix my projects?
By publishing your project on the Scratch website, you agree to license it under a Creative Commons Share Alike license. If you don’t want others to view and remix your creations, don’t share them on the Scratch website.

EDIT: Added link to FAQ page.

No support for the reasons above. PLEASE read the stickies!

No support. The website is licensed under a Creative Commons license. Locking See Inside would get the license taken away and would destroy the purpose of Scratch.

Also, just use a hash script if you want to hide a password.

As pointed out by many others, this feature suggestion is not something we are going to put into Scratch because it would interfere with people learning about Scratch. Scratch is designed to be tinkered with and remixed - we want to make sure that it remains that way for every project on Scratch.

There are ways to still have surprises in games though. As @Jonathon50 points out in a post above, you could use a hashing technique to compare a password that a project user gives you to the hashed version of the correct password. You can draw images using the pen and a table of geometry points to show an image that doesn't appear when you look at the sprite costumes. It takes some imagination and work - but it is possible