Pages: 1
THE DO'S
1. To save your changes, shift-click the loop in the "r" of the Scratch logo and select "save image for end user." This is important.
2. Always create a function for a command block, it won't automatically do it for you!
3. It is highly recommended that you know what you are doing before hacking Scratch.
4. If you mess up, it's okay. You can always re-install Scratch!
5. It is possible to make Scratch hack-resistant. This is highly recommended if you plan to make your own version of Scratch.
THE DON'T'S
6. NEVER close out of Scratch while your image is saving. This will break it.
7. Do not save the image if you were messing around and it doesn't work now.
8. While you are hacking Scratch, if you used the memory bug, sooner or later delete the sprite that caused the bug. Do not leave it open.
9. Don't make Scratch hack-resistant until you're POSITIVE that you do not want to add more blocks or anything.
10. Don't panic if you do something wrong. Just close out of Scratch without saving.
That's all for now! I hope you enjoyed this tutorial!
Offline
How do you make it hack-resistant?
Offline
I'll show you. Okay, open it up the way you normally do. Now open the browser. Select Scratch-UI-Panes, ScratchFrameMorph, MenuButtonActions.
Completely delete the "developers menu."
Hit alt + s.
Then, click on the gray and select save. Then close out...and it's hack-resistant! They can't access the developers menu! But they can use that bug...how do I get rid of the bug...
Offline
somelia wrote:
THE DO'S
1. To save your changes, shift-click the loop in the "r" of the Scratch logo and select "save image for end user." This is important.
2. Always create a function for a command block, it won't automatically do it for you!
3. It is highly recommended that you know what you are doing before hacking Scratch.
4. If you mess up, it's okay. You can always re-install Scratch!
5. It is possible to make Scratch hack-resistant. This is highly recommended if you plan to make your own version of Scratch.THE DON'T'S
6. NEVER close out of Scratch while your image is saving. This will break it.
7. Do not save the image if you were messing around and it doesn't work now.
8. While you are hacking Scratch, if you used the memory bug, sooner or later delete the sprite that caused the bug. Do not leave it open.
9. Don't make Scratch hack-resistant until you're POSITIVE that you do not want to add more blocks or anything.
10. Don't panic if you do something wrong. Just close out of Scratch without saving.That's all for now! I hope you enjoyed this tutorial!
This is really good, maybe good enough to be stickied...
Offline
markyparky56 wrote:
somelia wrote:
THE DO'S
1. To save your changes, shift-click the loop in the "r" of the Scratch logo and select "save image for end user." This is important.
2. Always create a function for a command block, it won't automatically do it for you!
3. It is highly recommended that you know what you are doing before hacking Scratch.
4. If you mess up, it's okay. You can always re-install Scratch!
5. It is possible to make Scratch hack-resistant. This is highly recommended if you plan to make your own version of Scratch.THE DON'T'S
6. NEVER close out of Scratch while your image is saving. This will break it.
7. Do not save the image if you were messing around and it doesn't work now.
8. While you are hacking Scratch, if you used the memory bug, sooner or later delete the sprite that caused the bug. Do not leave it open.
9. Don't make Scratch hack-resistant until you're POSITIVE that you do not want to add more blocks or anything.
10. Don't panic if you do something wrong. Just close out of Scratch without saving.That's all for now! I hope you enjoyed this tutorial!
This is really good, maybe good enough to be stickied...
I'm glad you think so!
Offline
somelia, please read my post on the Panther topic. I re-thought your request.
Offline
SeptimusHeap wrote:
somelia, please read my post on the Panther topic. I re-thought your request.
I will!
Offline
Jakey22 wrote:
How do you make it hack-resistant?
ubuntu is awesome.
Offline
To be honest... I don't get the point of hacking Scratch... projects written in hacked Scratch won't run on vanilla Scratch will they?
If Scratch won't do what you want, then maybe Scratch is the wrong platform for your project?
Offline
Pages: 1