Support, since this always happened in 1.4 there was no reason to remove it.

You mean like a note on top not bothering the code? Cuz JSON probably wouldn't be able to handle an entire new code with the remix tree. It wouldn't work. Also, now that I think about it, LOTS of information would need to be stored to put the remix tree inside the project. It might work, but probably won't, sadly. I'm 50/50. Maybe some other type of idea like that?

mariobros406 wrote:

You mean like a note on top not bothering the code? Cuz JSON probably wouldn't be able to handle an entire new code with the remix tree. It wouldn't work. Also, now that I think about it, LOTS of information would need to be stored to put the remix tree inside the project. It might work, but probably won't, sadly. I'm 50/50. Maybe some other type of idea like that?

I just mean a note at the top that had the remix tree encoded in. I can't imagine it would take up a super lot of space because it would just need to have the pictures, links, and a “map” of the tree.

Support!

Support!

Absolute 1000000000000% support, there was someone who did this to a project I spent ages making, and said it make it themselves!

Storing the entire tree won't be necessary. The JSON only needs to store the i.d. of the project that it was downloaded from. Then, when the new project is uploaded, the upload system goes and inserts the new project into the old project's remix tree.

However, please note that within ten seconds I managed to come up with two ways to bypass this system that don't involve going into the JSON file and editing the data that anyone who went as far as to download and reupload the project would almost certainly be able to think of and go through the relatively simple effort of doing.

lalala3 wrote:

Storing the entire tree won't be necessary. The JSON only needs to store the i.d. of the project that it was downloaded from. Then, when the new project is uploaded, the upload system goes and inserts the new project into the old project's remix tree.

However, please note that within ten seconds I managed to come up with two ways to bypass this system that don't involve going into the JSON file and editing the data that anyone who went as far as to download and reupload the project would almost certainly be able to think of and go through the relatively simple effort of doing.

I can't think of any. If it's hard coded inside the project, the only way to change it is by changing said hard code.

Is the “import project” feature an option in the 2.0 offline editor, as in, importing all the scripts and assets of one project into another? You could do this in 1.4 and steal projects easily, if it's still available in 2.0 you could probably do the same thing.

Iditaroid wrote:

Is the “import project” feature an option in the 2.0 offline editor, as in, importing all the scripts and assets of one project into another? You could do this in 1.4 and steal projects easily, if it's still available in 2.0 you could probably do the same thing.

Bingo. Also, backpacking all of the sprites (as well as the backgrounds, sounds, and scripts attached to the Stage). Essentially, the principle behind both methods is to create a new project (which will, of course, not have the relevant data coded into it) and insert all of the sprites/scripts/etc. Basically, if a project is a box of items and the remix data is writing on the box, the logical bypass is to take a new unmarked box and dump the contents of the old box inside.

lalala3 wrote:

Iditaroid wrote:

Is the “import project” feature an option in the 2.0 offline editor, as in, importing all the scripts and assets of one project into another? You could do this in 1.4 and steal projects easily, if it's still available in 2.0 you could probably do the same thing.

Bingo. Also, backpacking all of the sprites (as well as the backgrounds, sounds, and scripts attached to the Stage). Essentially, the principle behind both methods is to create a new project (which will, of course, not have the relevant data coded into it) and insert all of the sprites/scripts/etc. Basically, if a project is a box of items and the remix data is writing on the box, the logical bypass is to take a new unmarked box and dump the contents of the old box inside.

Yes, but that's basically impossible to stop anyways.

And there could be a link to the original project stored inside of sprite files, etc…

Support!

lalala3 wrote:

Iditaroid wrote:

Is the “import project” feature an option in the 2.0 offline editor, as in, importing all the scripts and assets of one project into another? You could do this in 1.4 and steal projects easily, if it's still available in 2.0 you could probably do the same thing.

Bingo. Also, backpacking all of the sprites (as well as the backgrounds, sounds, and scripts attached to the Stage). Essentially, the principle behind both methods is to create a new project (which will, of course, not have the relevant data coded into it) and insert all of the sprites/scripts/etc. Basically, if a project is a box of items and the remix data is writing on the box, the logical bypass is to take a new unmarked box and dump the contents of the old box inside.

Yes, but implementing this feature couldn't hurt, because it would just make it so that the downloading loophole wouldn't work, even if the others still did. And also, the most common projects to be copied have lots of sprites and scripts so that would be a pain.

Fiat500Abarth wrote:

lalala3 wrote:

Iditaroid wrote:

Is the “import project” feature an option in the 2.0 offline editor, as in, importing all the scripts and assets of one project into another? You could do this in 1.4 and steal projects easily, if it's still available in 2.0 you could probably do the same thing.

Bingo. Also, backpacking all of the sprites (as well as the backgrounds, sounds, and scripts attached to the Stage). Essentially, the principle behind both methods is to create a new project (which will, of course, not have the relevant data coded into it) and insert all of the sprites/scripts/etc. Basically, if a project is a box of items and the remix data is writing on the box, the logical bypass is to take a new unmarked box and dump the contents of the old box inside.

Yes, but implementing this feature couldn't hurt, because it would just make it so that the downloading loophole wouldn't work, even if the others still did. And also, the most common projects to be copied have lots of sprites and scripts so that would be a pain.

That's why I said I support it. Also, lots of sprites/scripts isn't a problem if you just use importing

support!

Absolute support. Who would want to bypass the “copyright” system on Scratch?

It would just have to look something like this (I don't know JavaScript, so I don't know how the formatting would look):
“Remixed From”: “Project”
Then, when the project was uploaded, the translator that translates the json into scripts and sprites would just find the project, add this into the project's remix tree, and then add this projects remix tree. It might need some kind of way to identify the original project, though, because there are multiple projects that share the same name.

+1quadrillion

So much support, I could cry.

I love that you went through the files, we need people like that on scratch.

Fiat500Abarth wrote:

It would just have to look something like this (I don't know JavaScript, so I don't know how the formatting would look):
“Remixed From”: “Project”
Then, when the project was uploaded, the translator that translates the json into scripts and sprites would just find the project, add this into the project's remix tree, and then add this projects remix tree. It might need some kind of way to identify the original project, though, because there are multiple projects that share the same name.

Then the “Project” thing could hold the number corresponding to the project instead of its name.