Discuss Scratch
- Discussion Forums
- » Suggestions
- » A way to prevent remixes with no change
- hjklr54679
-
100+ posts
A way to prevent remixes with no change
This has been a HUGE issue. People are remixing projects with no change at all, and no credit given. I think I have a solution to fix this. First, the most obvious one to filter out nearly 3 quarters of all remixes there are, would be to not allow it to just have the original project name and “remix” at the end. Another way to fix this issue would be to compare the remix with the original project and make sure there is at least 1 difference, and not just a comment in the project to get around that fix. Also, to make sure the original poster of the project gets credit, make the remix automatically have the original project creator's username in it. These are just a few suggestions to fix what I think is a major issue with remixes in Scratch.
- GyroscopeBill
-
500+ posts
A way to prevent remixes with no change
Support. It seems like a great idea: I hate how people try to take credit for things that aren't their own. Although one thing I would like to say, what about when people take the entire scripting of a project, put it in their backpack, and use it as their own project? That is another problem which is worse, because there is no way of telling that the scripts come from another user.
Last edited by GyroscopeBill (May 27, 2014 14:52:27)
- hjklr54679
-
100+ posts
A way to prevent remixes with no change
I know that, but it is much less frequent than this and is not as big of an issue because if it is a popular project, most people could tell it isn't theirs. I'm sure the Scratch team could find a way to fix that.
- lol90
-
500+ posts
A way to prevent remixes with no change
Support. It seems like a great idea: I hate how people try to take credit for things that aren't their own. Although one thing I would like to say, what about when people take the entire scripting of a project, put it in their backpack, and use it as their own project? That is another problem which is worse, because there is no way of telling that the scripts come from another user.
This problem can easily be fixed. Make it so that the backpack can only hold things from your own projects that are saved along with this change.
- GyroscopeBill
-
500+ posts
A way to prevent remixes with no change
But what if I took a couple of scripts from a project I liked, then used them as a small part of my own project, giving credit to be the creator of the scripts? That is one of the main uses for the backpack, and if it could only be used for scripts from your projects, the backpack would become less useful.Support. It seems like a great idea: I hate how people try to take credit for things that aren't their own. Although one thing I would like to say, what about when people take the entire scripting of a project, put it in their backpack, and use it as their own project? That is another problem which is worse, because there is no way of telling that the scripts come from another user.
This problem can easily be fixed. Make it so that the backpack can only hold things from your own projects that are saved along with this change.
- sit95
-
21 posts
A way to prevent remixes with no change
Yeah, I agree. I normally don't bother looking at the remixes because the are likely to have no change.
- DaveTheGamer80
-
91 posts
A way to prevent remixes with no change
I agree too. I have always hated how people can do this, but all of the people commenting on this forum thread are absolutely brilliant and even give suggestions for Scratch staff on how this could be made possible.
Perhaps there is a way to stop people from doing this using some clever scripting….
Perhaps something about a turbo mode detector?
Hmm….
And perhaps say in notes/credits,
“Use turbo mode?”
That way, when the notes/credits are deleted after a remix, no one uses turbo mode.
Hmm….
Hehehe….
Mwahaha!
Perhaps there is a way to stop people from doing this using some clever scripting….
Perhaps something about a turbo mode detector?
Hmm….
when green flag clicked
set [Timer] to [0]
wait (0.1) secs
if <[0.08] < [Timer]> then
stop [all]
end
And perhaps say in notes/credits,
“Use turbo mode?”
That way, when the notes/credits are deleted after a remix, no one uses turbo mode.
Hmm….
Hehehe….
Mwahaha!
- MattBen789
-
7 posts
A way to prevent remixes with no change
Support! Because, how would it feel to have slaved away on a project, when someone just copies it and it gets all the attention you deserve that the “remix” doesn't deserve? In fact, doing that even goes against the Scratch rules.
The purpose of remixing is to help users learn, not be famous. Okay, I'm done ranting.
We consider even a minor change to be a valid remix, as long as credit is given to the original project creator and others who made significant contributions to the remix.When a Scratcher makes a copy of someone else’s project and modifies it to add their own ideas (for example, by changing scripts or costumes), the resulting project is called a “remix.” Every project shared to the Scratch website can be remixed.
The purpose of remixing is to help users learn, not be famous. Okay, I'm done ranting.
- mathfreak231
-
1000+ posts
A way to prevent remixes with no change
This would be impossible. There are infinitely many ways to get around such a “copy-filter”, with the functioning word being “infinite”.
- Julianthewiki
-
100+ posts
A way to prevent remixes with no change
I just actually don't mind whether the remixers give credit to me or not; as long as they don't plagiarize.
And, no support for the first one. This would know that it is a remix, and it prevents plagiarizing, right from the project name.
And, no support for the first one. This would know that it is a remix, and it prevents plagiarizing, right from the project name.
- Chainmanner
-
100+ posts
A way to prevent remixes with no change
Whether I support or not doesn't matter. Anybody can just change the name of a variable and then remix it, big whoop. If somebody bugs you out by directly copying your project, you just gotta deal with them yourself.
- Kal_Kal_Kal
-
100+ posts
A way to prevent remixes with no change
Yes! This happend to my project Broken tiles! This has been a HUGE issue. People are remixing projects with no change at all, and no credit given. I think I have a solution to fix this. First, the most obvious one to filter out nearly 3 quarters of all remixes there are, would be to not allow it to just have the original project name and “remix” at the end. Another way to fix this issue would be to compare the remix with the original project and make sure there is at least 1 difference, and not just a comment in the project to get around that fix. Also, to make sure the original poster of the project gets credit, make the remix automatically have the original project creator's username in it. These are just a few suggestions to fix what I think is a major issue with remixes in Scratch.
- Dylan5797
-
1000+ posts
A way to prevent remixes with no change
I agree too. I have always hated how people can do this, but all of the people commenting on this forum thread are absolutely brilliant and even give suggestions for Scratch staff on how this could be made possible.
Perhaps there is a way to stop people from doing this using some clever scripting….
Perhaps something about a turbo mode detector?
Hmm….when green flag clicked
reset timer
wait (0.1) secs
if <[0.08] <(timer)> then
stop [all v]
end
And perhaps say in notes/credits,
“Use turbo mode?”
That way, when the notes/credits are deleted after a remix, no one uses turbo mode.
Hmm….
Hehehe….
Mwahaha!
This will only work if they mindlessly backpack this script without checking it over
Last edited by Dylan5797 (Nov. 27, 2014 15:47:56)
- Superdoggy
-
1000+ posts
A way to prevent remixes with no change
Well if your projects don't use the timer you can use this: http://scratch.mit.edu.ezproxyberklee.flo.org/projects/17832425/ 
Currently the Scratch Team has some ugly boxes around all the sprites because they didn't want some sprites to be invisible. So instead replace the empty Remix Protection costume with a number or coin or start button or something to disguise it in your project.

Currently the Scratch Team has some ugly boxes around all the sprites because they didn't want some sprites to be invisible. So instead replace the empty Remix Protection costume with a number or coin or start button or something to disguise it in your project.
- seanbobe
-
500+ posts
A way to prevent remixes with no change
R.I.P. all of the music in my games.Support. It seems like a great idea: I hate how people try to take credit for things that aren't their own. Although one thing I would like to say, what about when people take the entire scripting of a project, put it in their backpack, and use it as their own project? That is another problem which is worse, because there is no way of telling that the scripts come from another user.
This problem can easily be fixed. Make it so that the backpack can only hold things from your own projects that are saved along with this change.
support the original idea
- Prinseskat
-
1000+ posts
A way to prevent remixes with no change
I support. Copyright is important.
- gregory9
-
100+ posts
A way to prevent remixes with no change
Support, but people can just download the project and upload it as their own.
- Xelophelt
-
500+ posts
A way to prevent remixes with no change
HUGE support.
*Almost* Every remix of Explosion the Racer 1 is literally a copy of my own game. This would prevent puny attempts at fame (such as making copies of a featured game).
I am glad someone is thinking on the same page with me.
*Almost* Every remix of Explosion the Racer 1 is literally a copy of my own game. This would prevent puny attempts at fame (such as making copies of a featured game).
I am glad someone is thinking on the same page with me.
- Discussion Forums
- » Suggestions
-
» A way to prevent remixes with no change