Project copying is the worst enemy of Scratchers who make original content. Many famous scratchers and new scratchers alike, due to project copying, have been putting the following words/words similiar to it on their projects:

“Do not remix! It is a premium game/os/thingy, as you can see on (username).com! Pay me $$ on (username).com for remixing!!1!!”
(exaggerated for comedic effect)

So, what do we do about it? The answer is surprisingly just a click of the revert changes button away.

Make it so:

Scratch can track your changes for remixes. When you click “see inside”, you will not be able to press remix until you change something. And no, moving the blocks around does not count. Adding, removing and rearranging them does. It would track the code in the text code counterpart. Then, it will allow you to press remix.

When you press on the “remix” button for the first time, it explains to you remixing and copying. The message is in bold, and it cannot be skipped. It requires you to wait 10secs to skip it. Next time you use “remix”, you will get the option to skip the message.

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

DotDash wrote:

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

I see.

jh1234l wrote:

DotDash wrote:

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

I see.

But project copying is usually from new scratchers who don't know what remixing is. They press see inside, remix, and then share without changing anything.

One thing I hate is when people only change one or two things, like putting their own logo on the project, and publish it. It would be impossible to prevent that, and I think it would be just as bad as not changing anything.

kenblu24 wrote:

One thing I hate is when people only change one or two things, like putting their own logo on the project, and publish it. It would be impossible to prevent that, and I think it would be just as bad as not changing anything.

Putting their own logo in a remix without changing something else is still a copy.

same as AE studios…

Probably wouldn't work as the program wouldn't be able to tell between adding a miniscule pixel and changing all the costumes all together- simply put there would be way to many ways to bypass this program. It's a good idea but probably wouldn't work too practically…

Support. But if someone would delete a block then remix and put the block back like @DotDash said. A fix for that could make scratch check to see if the project is the same as the project remixed and then make the project private if it is the same as the project that was remixed.

Correct me if I'm wrong but isn't the whole idea of the Scratch community to share and learn from each other? I thought that was the idea behind sharing your projects.

ButlerBoy wrote:

Correct me if I'm wrong but isn't the whole idea of the Scratch community to share and learn from each other? I thought that was the idea behind sharing your projects.

I'm sorry, but what can someone learn by remixing a project without changing anything?

Remixing ≠ Copying.

ButlerBoy wrote:

Correct me if I'm wrong but isn't the whole idea of the Scratch community to share and learn from each other? I thought that was the idea behind sharing your projects.

You made a bread. You gave it to someone to eat. They can do 2 things. Eat it… or claim that they baked it themselves. (I forgot the scratcher's name who made this example…. but I give the credit to whoever made this example).

That is just like Scratch. You make a project, and then you share it. People can play with it or claim it as their own. Claiming ownership of a project is called Plagiarism and a remix that is a copy of another project can be reported and deleted.

http://mv.ezproxy.com.ezproxyberklee.flo.org/issues/1039

joshuaho wrote:

…People can play with it or claim it as their own.

Or both.

mathfreak231 wrote:

joshuaho wrote:

…People can play with it or claim it as their own.

Or both.

Yep…. agreed.

I totally agree with you on this but if you read the scratch community guidelines it says that putting your project on the public means letting people potentially remix it and copy it. Correct me if Im wrong

It's pretty much a contract I guess, as long as your project is public, it can be copied.

tacky365 wrote:

I totally agree with you on this but if you read the scratch community guidelines it says that putting your project on the public means letting people potentially remix it and copy it. Correct me if Im wrong

People are allowed to remix projects, but NOT copy it.

A remix is a modified version of a project, and is allowed.

A copy is a project that is a duplicate of another project without changes. Copying someone else's project without changing anything is not allowed (except if you are in a collab).

Sincerely, it's not so much of a problem, people tend to be able to tell the differrance between the original and a blatant copy. Just remember to check the remix tree!