How do you turn off the “See Inside” button, basically disallowing people to see your project s scripts and etc..
I want to make a game but players may just see inside and cheat so for that reason, i want to do that.
Also, if you can tell me how to make your project unremixable, I'd appreciate that.

If possible, this is not allowed. It's not even allowed to describe methods of how to make a project unremixable. This is part of the “Embrace remix culture” part of the Scratch Community Guidelines.

If you want to share your project on the Scratch website, you will have to do so with the understanding that anybody is allowed to see inside it and remix it.

Za-Chary wrote:

If possible, this is not allowed. It's not even allowed to describe methods of how to make a project unremixable. This is part of the “Embrace remix culture” part of the Scratch Community Guidelines.

If you want to share your project on the Scratch website, you will have to do so with the understanding that anybody is allowed to see inside it and remix it.

True. Well, about the remixing factor i agree. But, i mean for seeing inside your projects, for example to keep your projects safe and an anti-cheat, is it fine?
And.. can it even be possible? And how..?

GamerMYM wrote:

Za-Chary wrote:

If possible, this is not allowed. It's not even allowed to describe methods of how to make a project unremixable. This is part of the “Embrace remix culture” part of the Scratch Community Guidelines.

If you want to share your project on the Scratch website, you will have to do so with the understanding that anybody is allowed to see inside it and remix it.

True. Well, about the remixing factor i agree. But, i mean for seeing inside your projects, for example to keep your projects safe and an anti-cheat, is it fine?
And.. can it even be possible? And how..?

It's not allowed. I believe there are ways to crash the project if someone sees inside, though.

han614698 wrote:

(#4)
It's not allowed. I believe there are ways to crash the project if someone sees inside, though.

Though that is also against ToU.

3.5 You agree not to use Scratch in any way intended to disrupt the service, gain unauthorized access to the service, or interfere with any other user's ability to use the service. Prohibited activities include, but are not limited to:

1. Posting content deliberately designed to crash the Scratch website or editor;
(…)

There's not really anything wrong with cheating and there are valid reasons for some players to cheat or break the game, like if a level is too hard, it's just that the intended way to play can also be a valuable and rewarding experience that you don't want your players to lose. You can always encourage the player to accomplish everything legitimately, though.

-PinPoint- wrote:

(In a code comment in Ice Mage)

WARNING: if you've come inside the project to try and skip a level, DON'T DO IT! It will be a lot more rewarding if you solve each level properly - you will get a lot of satisfaction from managing to solve a difficult level.

By the way, it's not unheard of for modern games to offer assist modes and options to reduce the difficulty, even to game-breaking extents, in case someone out there just can't enjoy the game as it was meant to be played.

The most you could do if you really wanted to protect your game's secrets is obfuscating things like answers to questions or puzzles in such a way where you can do some math to “encode” user input, which is actually how modern websites password-protect accounts without knowing the actual passwords themselves.

If you're concerned about players cheating in multiplayer, don't worry - Scratch Cloud variables disconnect when the user sees inside.

D-ScratchNinja wrote:

There's not really anything wrong with cheating and there are valid reasons for some players to cheat or break the game, like if a level is too hard, it's just that the intended way to play can also be a valuable and rewarding experience that you don't want your players to lose. You can always encourage the player to accomplish everything legitimately, though.

-PinPoint- wrote:

(In a code comment in Ice Mage)

WARNING: if you've come inside the project to try and skip a level, DON'T DO IT! It will be a lot more rewarding if you solve each level properly - you will get a lot of satisfaction from managing to solve a difficult level.

By the way, it's not unheard of for modern games to offer assist modes and options to reduce the difficulty, even to game-breaking extents, in case someone out there just can't enjoy the game as it was meant to be played.

The most you could do if you really wanted to protect your game's secrets is obfuscating things like answers to questions or puzzles in such a way where you can do some math to “encode” user input, which is actually how modern websites password-protect accounts without knowing the actual passwords themselves.

If you're concerned about players cheating in multiplayer, don't worry - Scratch Cloud variables disconnect when the user sees inside.

I totally agree with this. However, in my case, i mean, like, for example, a player has a ferrari. And there is a special save code for that. The ferrari is obviously exclusive. Despite of my warnings, i know that of course there will be people who break the rule and leak the code in the comments, which will destroy the car's value and literally everyone can access it. Or for example, the same way, if there is a person on for example level 995, but he wishes to pause, and gets a save code for lvl 995. But then he leaks it in the comments and everyone can access level 995 then, making the game like.. exploited..

Actually, disabling see inside isn't possible, because it's rejected:

The Official List of Rejected Suggestions wrote:

4.1 Disable “See Inside” or restrict sharing

Some users want an option to prevent Scratchers from looking inside their project and using their artwork, scripts, or sounds. However, the core ideas of Scratch are "Imagine, Program, Share." By sharing a project on the Scratch website, you are allowing others to see the code and potentially remix or reuse the data inside, as long as they give credit. That being said, please use the Report button on any project that uses content from another Scratcher without giving credit to them. If you do not want other users to see inside your project, then do not share your project on the Scratch website.

GamerMYM wrote:

I totally agree with this. However, in my case, i mean, like, for example, a player has a ferrari. And there is a special save code for that. The ferrari is obviously exclusive. Despite of my warnings, i know that of course there will be people who break the rule and leak the code in the comments, which will destroy the car's value and literally everyone can access it. Or for example, the same way, if there is a person on for example level 995, but he wishes to pause, and gets a save code for lvl 995. But then he leaks it in the comments and everyone can access level 995 then, making the game like.. exploited..

Such is the fun of Scratch. As I get older, I find myself getting impatient with games that feature unlockable content, because if I can't unlock it within several tries, then I get bored and move on to a different project. That's why most of my games these days feature little to no unlockable content — players can just play most of the full game right from the start. I'm probably not the only one who thinks this way, but surely I may be in the minority of people who think this way. Just wanted to give you a different perspective on this.

For those who are not impatient and appreciate a challenge, they will play your game the intended way without trying to skip ahead through someone else's save code. If you want to stop this sort of thing from happening anyway, one way may be to encourage others to post their save codes on their own personal devices; nothing is stopping you from deleting all the comments which have save codes in them.

i have a very bigfear for if someone clicks see inside, goes to my scripts where i have my game's developer controls and activates them, it clears the lists and deletes the main level meaning that if anyone after plays the game (which is unlikley i get like 5 views per update) they wont be able to play the main level because all its lists have gotten edited in some way/cleared

sterple100 wrote:

i have a very bigfear for if someone clicks see inside, goes to my scripts where i have my game's developer controls and activates them, it clears the lists and deletes the main level meaning that if anyone after plays the game (which is unlikley i get like 5 views per update) they wont be able to play the main level because all its lists have gotten edited in some way/cleared

Which will in no way affect the original copy of the game unless that person is the person who made it. When you click “See inside” and edit something, the game is sandboxed and can't affect the original or other users. As a result, there is nothing to fear from anyone who hits “See inside” and destroys things, because it only affects them and only them until they reload the page.

GamerMYM wrote:

Za-Chary wrote:

If possible, this is not allowed. It's not even allowed to describe methods of how to make a project unremixable. This is part of the “Embrace remix culture” part of the Scratch Community Guidelines.

If you want to share your project on the Scratch website, you will have to do so with the understanding that anybody is allowed to see inside it and remix it.

True. Well, about the remixing factor i agree. But, i mean for seeing inside your projects, for example to keep your projects safe and an anti-cheat, is it fine?
And.. can it even be possible? And how..?

Why would you want an anti cheat?

sterple100 wrote:

i have a very bigfear for if someone clicks see inside, goes to my scripts where i have my game's developer controls and activates them, it clears the lists and deletes the main level meaning that if anyone after plays the game (which is unlikley i get like 5 views per update) they wont be able to play the main level because all its lists have gotten edited in some way/cleared

That’s not how it works. The lists dont save across everybody who plays your project.

GamerMYM wrote:

How do you turn off the “See Inside” button, basically disallowing people to see your project s scripts and etc..
I want to make a game but players may just see inside and cheat so for that reason, i want to do that.
Also, if you can tell me how to make your project unremixable, I'd appreciate that.

It is 100% possible. When I was new to Scratch 3 years ago I saw a project with it. I didn't think to report it.

However, even if you do find the code to do it, don't do it.

If you see a project with it, silently report and be on your way.

It is against the TOS to implement this.

If the reason you're asking is because you're afraid that someone is going to directly copy your project, you may, again, silently report (leave a comment if you want telling them that it's your project in a POLITE manner) and be on your way.