shd02 wrote:

There are also remixes that the “CloneAlert” system would not detect as clones. I think these changes should not allow the project to be remixed:

• adding a repeated block that has no effect such as this:
  

  when green flag clicked
  show
  show

  adding a block that would not change anything (An example is adding a “show” block when the sprite is already shown and the sprite has no “hide” blocks anywhere.")
  
  
• adding or removing a variable or list that has no uses and is not displayed (no reporter blocks of that variable or list)
  
  
• moving a script or adding blocks that are not connected to hat blocks
  
  
• changing the stage or costumes by adding parts that cannot be seen such as adding a shape within another shape of the same color, or grouping and ungrouping the stage and costumes
  
  
• adding a backdrop or costume that is never used
  
  
• adding empty “if”, “if else”, or repeat () blocks or adding “if” or “if else” blocks with booleans that always return false, or adding “repeat” or “repeat until” blocks with booleans that always return true.
  
  
• adding a c-block that has no effect to any blocks inside(An example is a repeat (1) block).
  
  
• adding custom block definitions that do not have any uses of the actual custom block or adding broadcasts with no uses of the “when I receive” block
  
  
• adding hat blocks with no blocks under the hat block
  
  
• using a block with inputs that produce no effect such as “move 0 steps”.

Austinato wrote:

That does make me want to suggest something; instead of directly punishing the user, just tell them:

Oh noes! You were caught by the CloneAlert filter!

______________

The CloneAlert filter prevents users from directly remixing a project without changing anything (or something, at a bare minimum.) Adding, removing, or even significantly modifying content in the remixed project won't cause this to pop up again!
______________

Thank you for reading, and Scratch on!

Minecratch_project wrote:

If i put unnesessary sprites on the project, like ‘'When green flag pressed’' block, but without contents, how will detect a copy?

Sigton wrote:

I don't think banning copies is the right way to encourage creativity

Sigton

Scratcher1002 wrote:

Semi-support, on one hand you have copies and blatant plagiarism, on the other you have the questions of, “How would this work?” and, “Is this possible?”

NanoRook wrote:

Sigton wrote:

I don't think banning copies is the right way to encourage creativity

Sigton

So I guess plagiarism is okay?

cheddargirl wrote:

Scratcher1002 wrote:

Semi-support, on one hand you have copies and blatant plagiarism, on the other you have the questions of, “How would this work?” and, “Is this possible?”

The last two are the most important part when offering a suggestion. We need people to also offer ways on how to accomplish it.

We're all for the suggestion on preventing a remix, but none so far have offered a viable way on how to develop such a system.

LP_Play wrote:

We should create a system that hides the remix button until someone modifies the project

And if someone gets around the remix button it hides the share button until it detects at least a recolour.

It would allow sharing if it detects at least two more or less full scripts, or a new or deleted sprite, or an added, deleted or fully recolored costume

And if someone some way gets around it…

when green flag clicked
show

iamunknown2 wrote:

LP_Play wrote:

We should create a system that hides the remix button until someone modifies the project

It would be easy to workaround.

Lythium wrote:

I add this script:

when green flag clicked
show

It's a complete script. I can now bypass all your restrictions and share this copy.

LP_Play wrote:

cheddargirl wrote:

Scratcher1002 wrote:

Semi-support, on one hand you have copies and blatant plagiarism, on the other you have the questions of, “How would this work?” and, “Is this possible?”

The last two are the most important part when offering a suggestion. We need people to also offer ways on how to accomplish it.

We're all for the suggestion on preventing a remix, but none so far have offered a viable way on how to develop such a system.

We should create a system that hides the remix button until someone modifies the project, and if someone gets around the remix button it hides the share button until it detects at least a recolour. It would allow sharing if it detects at least two more or less full scripts, or a new or deleted sprite, or an added, deleted or fully recolored costume. And if someone some way gets around it…


There's always this.