You probably know this, but sometimes, people will download a project, modify it (or not), and then re-share it. By doing this, they have bypassed the remix system, so therefore, if won't show who they remixed the project from. After poking around, I discovered that all of the specs of the projects (variable names, variable values, custom blocks, scripts, etc.), are stored in a Json file, which is in the zip archive that you get after downloading a project. I don't know very much about this, but wouldn't it be possible to store the remix tree in the Json file? That way, even if you downloaded the project and then re-shared it, it would still show who it was remixed from.

1000% support.

mathfreak231 wrote:

1000% support.

Thanks. Did you really invent the phrase?

Support.

Fiat500Abarth wrote:

mathfreak231 wrote:

1000% support.

Thanks. Did you really invent the phrase?

AFAICT. Didn't see anybody use it before me.

Just add loads and loads and loads of local variables to your sprites and make them depend on them. When the project is re-uploaded, the local variables become global and (depending on how you used them) make the project completely useless. (I've suggested a fix for this bug but it didn't get much attention. I guess now it'll come in handy! )

Zparx wrote:

Just add loads and loads and loads of local variables to your sprites and make them depend on them. When the project is re-uploaded, the local variables become global and (depending on how you used them) make the project completely useless. (I've suggested a fix for this bug but it didn't get much attention. I guess now it'll come in handy! )

Good idea.

Support.

I 1,000,000% support.

Thanks to everyone who supports!

Support.
I thought of it before but I was just like “Oh well time to do some more math work ;-;”

Support!!

Definitely support.

Support! Support! Bravo! Bravo!!! Then only a few will know how to work around it.

Support.

The only problem I can see with this is that someone could modify the remix tree to look like the project was original - or for example, make it look like the project was a remix of a project from their test account, and that could easily turn very messy, because it would look like a completely original project.

However, I do agree something should be done, so support.

AonymousGuy wrote:

The only problem I can see with this is that someone could modify the remix tree to look like the project was original - or for example, make it look like the project was a remix of a project from their test account, and that could easily turn very messy, because it would look like a completely original project.

However, I do agree something should be done, so support.

Yes, but I'm asuming that the people doing this wouldn't know enough programming to know how to get into the file. Even if some people did, this would eliminate probably 90% of the remixing problems.

Fiat500Abarth wrote:

AonymousGuy wrote:

The only problem I can see with this is that someone could modify the remix tree to look like the project was original - or for example, make it look like the project was a remix of a project from their test account, and that could easily turn very messy, because it would look like a completely original project.

However, I do agree something should be done, so support.

Yes, but I'm asuming that the people doing this wouldn't know enough programming to know how to get into the file. Even if some people did, this would eliminate probably 90% of the remixing problems.

Yes, and I realized that someone can already do this by download and re-uploading a project, then remixing it. So there really shouldn't be problems.

Support.

Support!

<(((Minecraft) + (Doctor Who)) + (Punk Rock Music)) = [Awesome! ]>