Remix prevention
https://scratch.mit.edu/projects/72581962/

I would rather have it so you have an ability to turn of remixing for your project, and it would just prevent the ability for remixers to share the remixed project. I believe this would be fair

support if i havent

Axel-Innovations wrote:

I would rather have it so you have an ability to turn of remixing for your project, and it would just prevent the ability for remixers to share the remixed project. I believe this would be fair

That's been rejected in the sticky.

i usually make the changes after i press the remix button (so there saved into my stuff) so no support

DotDash wrote:

But people could just delete a block , remix, and put the block back

^^

I often remix a project for something in it, such as a sprite, or an idea. That way I can look for it easily. Maybe you can't share until something has been changed, instead of changing something before remixing.

Semi-support. As per above, there are many faults with this system. If all can be worked out, then you have my full support

Yes, I know this is a bump on an old topic, but it is not a necropost because it is still useful.

Off of what you're all saying, I think I know of a way to fix this once and for all:

Say you create a simple platformer (BOUNCE for an example). Create an introduction and descriptive project (TRAILER) that explains the project. THEN have others get a download link from the page separately, in which you make them sign a creative commons limitation agreement. If they sign it, download the file, and put it on Scratch with very little - no changes made to it, then you can present the document and prove you are the original creator, and you may even be able to legally force them to remove it from the website.

Semi-support for this, it can't be perfectly implemented.

nitrodext wrote:

Off of what you're all saying, I think I know of a way to fix this once and for all:

Say you create a simple platformer (BOUNCE for an example). Create an introduction and descriptive project (TRAILER) that explains the project. THEN have others get a download link from the page separately, in which you make them sign a creative commons limitation agreement. If they sign it, download the file, and put it on Scratch with very little - no changes made to it, then you can present the document and prove you are the original creator, and you may even be able to legally force them to remove it from the website.

That's a bit too complex for most Scratchers and there's no need to push it to legal limits.

Here Go To This Project To Stop Copying!
https://scratch.mit.edu/projects/138440886/#player
Enjoy!

Scraatchoo2 wrote:

Here Go To This Project To Stop Copying!
https://scratch.mit.edu/projects/138440886/#player
Enjoy!

That project is not shared. Please, remember to contribute with shared projects, not unshared ones.

Support! I once got reported for “copying” when it wasn't a copy!

Just check inside, compare the code, if it's pretty much the same, report.

Absolutely no support. I don't want that stupid pop-up every time I remix a project only because some idiot can't follow the rules.

Make it so that when you remix it, at least some of the code has to be changed from the original project before scratch allows you you to share the remixed project.

Lord_of_Fish wrote:

Make it so that when you remix it, at least some of the code has to be changed from the original project before scratch allows you you to share the remixed project.

Code or assets. The ST already said that recolors are valid remixes, so they should be allowed.

Support!

R4356th wrote:

Support!

Please be constructive and say why you support.

Support! Somebody (not naming and shaming ) copied my game Life which I spent hours working on and did not give any credit, and then it got on trending. Maybe instead of this just a permanant note in the notes and credits of who contributed to it? For example: "Parts of this project are from a project by {username and link} called {project name and link}. Please not that it is against the community guidelines to copy one's work or use it without credit. The data about where the assets, etc. came from would be inside the project.json file stored in the .sb3 file.