I don't want to be greedy, but I'm uneasy about knowing that people can just take my projects and tinker with them. Is there any way to not allow other people to download my script? Thanks in advance.
Offline
Hey ChuxXxliciousness, all projects uploaded to the Scratch website are released under a Creative Commons license which allows for Scratchers to download projects off the Scratch website and remix them. Sorry, but there is currently no way to block downloads of your projects from the Scratch website.
If it makes you feel at ease, any of your projects that have been remixed by other Scratchers and then put on the Scratch website will automatically cite credit to you as the original project owner.

Offline
cheddargirl the creation thing is not so accurate its always b8r to write a guard code like this game's starting version was done by : - and if someone removz the script the game dosent works
Hide this script under ur bggst script and then u will get credits for sure . use pen to show the text.
Offline
fanofcena wrote:
cheddargirl the creation thing is not so accurate its always b8r to write a guard code like this game's starting version was done by : - and if someone removz the script the game dosent works
![]()
Hide this script under ur bggst script and then u will get credits for sure . use pen to show the text.![]()
I don't understand. A project's code [the blocks] can be manipulated, but every Scratch project usually has a tracker which allows for credit to the original project owner. For example, my project Balloon Pop was remixed many times over by other Scratchers, but even if they manipulated the images or code (such as this one by stevinmarvin), credit is still given to me on the project pages of the remixes.

Offline
cheddargirl wrote:
fanofcena wrote:
cheddargirl the creation thing is not so accurate its always b8r to write a guard code like this game's starting version was done by : - and if someone removz the script the game dosent works
![]()
Hide this script under ur bggst script and then u will get credits for sure . use pen to show the text.![]()
I don't understand. A project's code [the blocks] can be manipulated, but every Scratch project usually has a tracker which allows for credit to the original project owner. For example, my project Balloon Pop was remixed many times over by other Scratchers, but even if they manipulated the images or code (such as this one by stevinmarvin), credit is still given to me on the project pages of the remixes.
True. But if you edit a .sb file in HexEdit, you can change the original creator.
Offline
gershmer wrote:
cheddargirl wrote:
fanofcena wrote:
cheddargirl the creation thing is not so accurate its always b8r to write a guard code like this game's starting version was done by : - and if someone removz the script the game dosent works
![]()
Hide this script under ur bggst script and then u will get credits for sure . use pen to show the text.![]()
I don't understand. A project's code [the blocks] can be manipulated, but every Scratch project usually has a tracker which allows for credit to the original project owner. For example, my project Balloon Pop was remixed many times over by other Scratchers, but even if they manipulated the images or code (such as this one by stevinmarvin), credit is still given to me on the project pages of the remixes.
True. But if you edit a .sb file in HexEdit, you can change the original creator.
Really? Can you show me how? I want to release a project that was remixed from a non existent person.
Offline
juststickman wrote:
gershmer wrote:
cheddargirl wrote:
I don't understand. A project's code [the blocks] can be manipulated, but every Scratch project usually has a tracker which allows for credit to the original project owner. For example, my project Balloon Pop was remixed many times over by other Scratchers, but even if they manipulated the images or code (such as this one by stevinmarvin), credit is still given to me on the project pages of the remixes.
True. But if you edit a .sb file in HexEdit, you can change the original creator.
Really? Can you show me how? I want to release a project that was remixed from a non existent person.
I'm pretty sure that he learned this from my post on binary editing sb files - see it for yourself here: http://scratch.mit.edu/forums/viewtopic.php?id=29182
Or read the version I copied from there:
billyedward wrote:
You will need a binary editor.
The one which I prefer is Hexedit, however there are loads of others out there.
First, you'll need to open the scratch file.
You will see two main panes: One filled with numbers, and the letters A-F. The other will look like what you saw in notepad. The second one is of most interest to us, at the moment.
To begin: The first 10 letters are the file header.
This is the source of those dreaded 'bad header' errors.
It tells scratch what program made the file. This allows scratch to tell quickly and harmlessly whether it can open that particular file.
1.0-1.2.1 projects will have ScratchV01.
1.3+ projects will have ScratchV02.
BYOB, lists & files, etc. projects have their own.
Using your binary editor, you can change the header.
If you have a project that was made in, say, 1.3, but you want to open it in 1.2, then changing it from ScratchV02 to ScratchV01 will tell scratch that the file is compatible.
One problem: it isn't.
There are many other things you'll have to do in order to make it compatible, but those are unfortunately beyond the scope of this explanation.
Scrolling down, you will see the save history.
This includes the date, time, etc of each save.
In the hex panel (1-9,A-F) you will see that each entry is separated by the byte sequence 09-09-0D.
You can make scratch think that it has been saved more than it has, only once, etc. by carefully adding, editing, or removing entries here, making sure that you stick with this format.
Also, you can get rid of the 'based on ####'s project' message on remixed projects this way, however due to the ethics of this, I'd highly discourage it.
The last thing you can easily do is to edit costume, sprite, variable, list, and sound names. You can also change the project notes, and some things entered into blocks.
Just scroll down until you find some text you recognise, and edit away!
***NOTE: Whatever you do, do not change the length of any string you edit. Just replace characters. I would recommend that you put it into overtype mode, to make this easier.***
One useful thing you can do with the above is:
Make a graphic effect block, with brightness in it.
In the binary editor, change 'brightness' to 'saturation.'
Open it in scratch: The block now says saturation!
But the really cool part is that it works.
Just set the saturation effect to a negative value, and watch what happens.
Also, if you use a scratchconnections application, then you may find it annoying how you can only get the special sensor values when connected... well, not anymore!
Here, just change one of slider, light, etc to your own, of the same length.
Whew!
That's a lot to take in.
Oh well, hope you can use it at some point!
But, please do not use this to prevent scratch from giving credit to someone else, or to do anything else that violates the TOS.
Last edited by billyedward (2010-03-07 20:12:05)
Offline
billyedward wrote:
juststickman wrote:
gershmer wrote:
True. But if you edit a .sb file in HexEdit, you can change the original creator.Really? Can you show me how? I want to release a project that was remixed from a non existent person.
I'm pretty sure that he learned this from my post on binary editing sb files - see it for yourself here: http://scratch.mit.edu/forums/viewtopic.php?id=29182
Or read the version I copied from there:billyedward wrote:
You will need a binary editor.
The one which I prefer is Hexedit, however there are loads of others out there.
First, you'll need to open the scratch file.
You will see two main panes: One filled with numbers, and the letters A-F. The other will look like what you saw in notepad. The second one is of most interest to us, at the moment.
To begin: The first 10 letters are the file header.
This is the source of those dreaded 'bad header' errors.
It tells scratch what program made the file. This allows scratch to tell quickly and harmlessly whether it can open that particular file.
1.0-1.2.1 projects will have ScratchV01.
1.3+ projects will have ScratchV02.
BYOB, lists & files, etc. projects have their own.
Using your binary editor, you can change the header.
If you have a project that was made in, say, 1.3, but you want to open it in 1.2, then changing it from ScratchV02 to ScratchV01 will tell scratch that the file is compatible.
One problem: it isn't.
There are many other things you'll have to do in order to make it compatible, but those are unfortunately beyond the scope of this explanation.
Scrolling down, you will see the save history.
This includes the date, time, etc of each save.
In the hex panel (1-9,A-F) you will see that each entry is separated by the byte sequence 09-09-0D.
You can make scratch think that it has been saved more than it has, only once, etc. by carefully adding, editing, or removing entries here, making sure that you stick with this format.
Also, you can get rid of the 'based on ####'s project' message on remixed projects this way, however due to the ethics of this, I'd highly discourage it.
The last thing you can easily do is to edit costume, sprite, variable, list, and sound names. You can also change the project notes, and some things entered into blocks.
Just scroll down until you find some text you recognise, and edit away!
***NOTE: Whatever you do, do not change the length of any string you edit. Just replace characters. I would recommend that you put it into overtype mode, to make this easier.***
One useful thing you can do with the above is:
Make a graphic effect block, with brightness in it.
In the binary editor, change 'brightness' to 'saturation.'
Open it in scratch: The block now says saturation!
But the really cool part is that it works.
Just set the saturation effect to a negative value, and watch what happens.
Also, if you use a scratchconnections application, then you may find it annoying how you can only get the special sensor values when connected... well, not anymore!
Here, just change one of slider, light, etc to your own, of the same length.
Whew!
That's a lot to take in.
Oh well, hope you can use it at some point!But, please do not use this to prevent scratch from giving credit to someone else, or to do anything else that violates the TOS.
Yeah. I learned it from you.
Offline