Well i think that locking downloads is extreme i feel that a hide block option is needed. You click a button and then it asks: What password will you hide with?
You then enter in the password like this
[Popsicle]
Please re-enter password:
[Popsicle]
Then if you download and know the password:
Please enter the hide block password
[Popsicle]
blocks are unhidden
Offline
This would go against Scratch's open-source policy - Scratch projects are supposed to be free for people to examine and remix.
Offline
yes but: If you have a project as a quiz you will want to hide an answer block. Therefore you can actually only hide a block at a time. This will mean people will get bored of hiding every single block and just hide the necessary ones to hide. This in turn makes it a better solution than locking downlaods
Offline
ssss wrote:
yes but: If you have a project as a quiz you will want to hide an answer block. Therefore you can actually only hide a block at a time. This will mean people will get bored of hiding every single block and just hide the necessary ones to hide. This in turn makes it a better solution than locking downlaods
The problem with this is that scratch is designed for people to use scripts that are already made to make other games. If someone wanted to make a quiz using your scripts, and some blocks were hidden, then they wouldn't be able to and that would defeat the whole point of scratch.
Besides, does it matter that much if people cheat on a quiz?
Offline