Discuss Scratch

MrLazyboi22
Scratcher
4 posts

Suggestion

When you create a project that has cloud highscore in it , people can press ‘see inside’ and change the code code for it and basically breaking the game . So why don't you add an option to stop that by making (remix on / off) and (see inside on / off) pls it helps stop people breaking your games
MrLazyboi22
Scratcher
4 posts

Suggestion

MrLazyboi22 wrote:

When you create a project that has cloud highscore in it , people can press ‘see inside’ and change the code code for it and basically breaking the game . So why don't you add an option to stop that by making (remix on / off) and (see inside on / off) pls it helps stop people breaking your games
Xolay
Scratcher
1000+ posts

Suggestion

This suggestion is rejected:

Za-Chary wrote:

3.2 Disable remixing or censor minor remixes
One of the most important ideas of Scratch is the share aspect. Scratch is a website not only for displaying your work, but also for sharing it with others, and by posting your project on the Scratch website you agree to allow others to remix your work. You are not allowed to write “Do not remix this project” in the Notes and Credits of your project; you may get alerted for this, because it discourages remixing. This suggestion extends to the ability to require permission to remix a project, as you have already given permission to others to use your creations by sharing a project on Scratch; for more information, see this post.

Last edited by Xolay (Sept. 8, 2021 18:28:41)


I'm a 8 year old boy
[0.0](ᵔ ᵕ ᵔ::stack)('_'::stack variables)(o,o::stack control)(d_b::stack operators)(²-²::stack motion)(1_1::stack looks)(°-°::stack sound)::stack #000000//these are my kumquat protectors

if <(username) = [add signature] > then
set [big brain v]to [True]
end
WHAT??? HOW ARE YOU SEEING THIS?
<<true(::grey) ::#00FF00>::operators>
<<(::grey) false::#ff0000>::operators>
I love courtney from total dramarama
My goal:
5000 posts (::control) (::control) (::#000000) (::#000000) (::#000000) ::#00008B

Credits: Google

move (1) step::motion

hello, light mode user
hello, dark mode user

this hat is looking at u
() () ::custom hat

POV: you are a ST member about to report
See the POV of being a Scratch Team member.

atchscray isyay ayay igh-levelhay ock-basedblay isualvay ogrammingpray anguagelay andyay ebsiteway argetedtay imarilypray atyay ildrenchay 8–16 asyay anyay educationalyay ooltay orfay ogrammingpray.

PLZ buy me a Wedo 2.0

hellohellohellohello

I BELIEVE IN VS TOTAL DRAMARAMA SUPREMACY

you are not being valid offtopic there

hahaha superhero block go brrrr::#FFFFFF cap

made with uploads.scratch.mit.edu
AwezomeXD
Scratcher
100+ posts

Suggestion

Technically already implemented? You can't disable remixing but if you go into a project via See Inside it automatically disables the cloud functionality of cloud variables (which means people can't cheat)

Hooplah
dhuls
Scratcher
1000+ posts

Suggestion

This is not only rejected, but also, thanks to the non-revocable CC-BY-SA 2.0 license all Scratch projects use, may be illegal.

Anyway, using see inside on a project you don't own disables cloud variables until you reload.
Ciyob86
Scratcher
500+ posts

Suggestion

When you see inside of a project cloud data is disabled so this is already implemented.
ScolderCreations
Scratcher
1000+ posts

Suggestion

No support, this isn't legal.

Quantum-Cat
Scratcher
1000+ posts

Suggestion

You don't actually change anything about the original project, only the creator can. Cloud variables are also automatically disabled when you press see-inside. As for disabling see-inside and remixing, that is rejected:

TOLORS wrote:

3.2 Disable remixing or censor minor remixes

One of the most important ideas of Scratch is the share aspect. Scratch is a website not only for displaying your work, but also for sharing it with others, and by posting your project on the Scratch website you agree to allow others to remix your work. You are not allowed to write “Do not remix this project” in the Notes and Credits of your project; you may get alerted for this, because it discourages remixing. This suggestion extends to the ability to require permission to remix a project, as you have already given permission to others to use your creations by sharing a project on Scratch; for more information, see this post.

A remix of a project is allowed on Scratch, even if the remix only contains minor changes (this includes recolors). However, when you remix a project, you should put in the Notes and Credits what you changed. If you see a project that contains no noticeable changes, please use the Report button on it so the Scratch Team can take a look at it. This suggestion extends to “extremely minor remixes,” such as a remix of a game that gives you 2 points per second instead of 1. As long as the user explains what they changed about the project and gives proper credit, this is okay.

TOLORS 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.

Restricting sharing so that only certain users can view the project is also not going to be implemented. It is important for projects to be publicly shared for everyone to see so people can report them if they are inappropriate. Only allowing certain users to view projects could increase the chances of inappropriate projects being shared on the website. “Unlisted projects,” similar to a YouTube feature, will also not be implemented for the same reason. It could also be used for private messaging; for more information, see #7.1 on this list.

Next time, before making a suggestion, read these topics:

Notice: Everything below the solid grey line (↑↑) above is my signature and appears on every post I make. Here, it is okay for you to advertise
your projects and other creations. To create your own, scroll to the bottom of the Discussion Home page and select “change your signature”.

I aplogise if I seem a bit too serious on the forums, but I am always open to feedback on my profile.
Past PPTBF Curator || Forum Helper (TFH) || Some Python, HTML and C

————————————————————————————

————————————————————————————
Quantum-Cat

Powered by DjangoBB