If you didn't make any changes you can't share the remix.

savaka wrote:

If you didn't make any changes you can't share the remix.

That seems like it'd be hard to enforce. You could literally take one variable, rename it, and the project would still function the same, and pass the blocker.

terminator68 wrote:

savaka wrote:

If you didn't make any changes you can't share the remix.

That seems like it'd be hard to enforce. You could literally take one variable, rename it, and the project would still function the same, and pass the blocker.

That is true, but I will support anyways.

Define “any changes”.

mathfreak231 wrote:

Define “any changes”.

You didn't do anything on the project but push “remix”.
At least that's my definition
Well, or you didn't do anything worth an autosave in Scratch's opinion.

Which is basically not doing anything but pushing “remix”.

Renaming a variable shouldn't count.
Support.

No support. People will find a way to bypass this as if nothing was ever different.

Sorry, you can just throw in some random scripts and the hit remix and then remove the random scripts… =/

Yeah, it's good in theory, but there's a million ways to get around it.
And even if there's a “crackdown” (which will never happen because Scratch is open), people will always invent new ways.

Guys. Be reasonable.

If someone doesn't make any changes to a project, clearly they need to make changes.
If they have to change one thing and for it to be allowed to be posted, that still decreases the amount of copies by half and can motivate remixers to actually change things. This suggestion has way more upsides than downsides.

SUPPORT

At least it does something against “illegitimate remixing”. Support.

Additionally, it should ignore changes to sprite and costume names, sounds, and variables.

ProdigyZeta7 wrote:

At least it does something against “illegitimate remixing”. Support.

Additionally, it should ignore changes to sprite and costume names, sounds, and variables.

Yup!

savaka wrote:

If you didn't make any changes you can't share the remix.

Support but the Scratchteam shoudln't tell the community so when the copiers copy the will be alerted and the copy deleted.

I at least think there needs to be a certain degree of difference in the .json file from the original…

Support! I've often noticed that comments that should have been directed to me and loves and faves end up on remixes of my best projects. The remixes are essentially exact, so the remixer is “stealing” my project, especially since 90% of all my remixers give no credit whatsoever. I work hard to make my projects, and the remixer gets some of my hard-earned credit by doing essentially NOTHING. Of course, there is nothing wrong with legit remixes, with full credit, and I actually like to see those.

I agree.

But the blocker should block every remix except if the remix includes one or more of these criteria:

- Adds one or more blocks in a script, excluding blocks in the “Control” tab.
- Adds one more script with at least one block from the “Events” tab.

sti_scratch wrote:

I agree.

But the blocker should block every remix except if the remix includes one or more of these criteria:

- Adds one or more blocks in a script, excluding blocks in the “Control” tab.
- Adds one more script with at least one block from the “Events” tab.

the way you get around this without really affecting anything is:

when green flag clicked
if <> then 
else

end

fulfills both criteria

pretty much whatever you do to prevent exact copies, people are always going to get around it somehow

the best solution is just to report them.

I feel like this is a duplicate, but I can't find the original topic..

savaka wrote:

If you didn't make any changes you can't share the remix.

terminator68 wrote:

savaka wrote:

If you didn't make any changes you can't share the remix.

That seems like it'd be hard to enforce. You could literally take one variable, rename it, and the project would still function the same, and pass the blocker.

I agree with both of these. It’s a good idea, but I don’t really see how they could do that. Plus, eventually, someone would figure out how to do it again.

Banning minor remixes are rejected. Also, anyone can get around this blocker. There's no way to detect if a user has made NO CHANGE.

sti_scratch wrote:

I agree.

But the blocker should block every remix except if the remix includes one or more of these criteria:

- Adds one or more blocks in a script, excluding blocks in the “Control” tab.
- Adds one more script with at least one block from the “Events” tab.

Well, yeah, but what if somebody added another script, remixed the project, and removed it?

No support, this would be way too easy to work around. Support for the concept, though, but it would be really hard to implement a foolproof copy-preventing system.