Scratch

benjamin2 · 2010-04-03 05:09:14

Sometimes you may have a secret password for a game which must be entered to play it. Maybe it could be found from another game.

The idea is, you must script the password, and people may download your project and see the password, or any other secrets in the project. Maybe you could do it so that if you want, you can have an option so that if people download your project, you can enter a password for a script, sprite, or background, so that in order to view the script,sprite, or background, a password of the maker's choice must be entered.

Example:

Maybe on a level 3 project of a game, when you beat it, you got a password. This could be anything: let's example it as (paper).

On the level 4 project, you will be asked to enter a password to play. It could ask for the password with the ask block, then if you entered 'paper', the level would play. People could download and see that the password to play is paper, without beating level 3.

So you could put a password on the script, a random one like 'computer', then downloaders would have to enter that password to see the script, but only the person who made the game would know the password to view the script. Then they could also password protect any background or sprite that shows the password. This would protect the solution of the game.

benjamin2
_________

Last edited by benjamin2 (2010-04-03 05:55:34)

LWB · 2010-04-03 05:33:29

i think yum should be a password

benjamin2 · 2010-04-03 05:55:01

LWB wrote:
i think yum should be a password

The point is not about what the password is. The point is the idea! If this gets added as a feature in 1.5 or whatever the next version is, then yum could be a password if you wanted it to be.

Phi_Lho · 2010-04-03 06:18:20

I understand the motivation, which is quite legit, but such protection would go against the goal of sharing everything in the site, of open source spirit.

Now, it might be interesting to have a password protection on a given list: one can view/edit it only when providing the right password.
So you can reuse/remix the project: just delete the protected list, and make your own.

Mmm, but if so, people can still run whatever level they want, which ruins the purpose of the request... Unless the level data is stored in a protected list too. :-)

benjamin2 · 2010-04-03 07:22:56

Phi_Lho wrote:
I understand the motivation, which is quite legit, but such protection would go against the goal of sharing everything in the site, of open source spirit.

Now, it might be interesting to have a password protection on a given list: one can view/edit it only when providing the right password.
So you can reuse/remix the project: just delete the protected list, and make your own.

Mmm, but if so, people can still run whatever level they want, which ruins the purpose of the request... Unless the level data is stored in a protected list too. :-)

Okay... store the level data in a protected list.

benjamin2 · 2010-04-03 07:23:58

benjamin2 wrote:
Phi_Lho wrote:
I understand the motivation, which is quite legit, but such protection would go against the goal of sharing everything in the site, of open source spirit.

Now, it might be interesting to have a password protection on a given list: one can view/edit it only when providing the right password.
So you can reuse/remix the project: just delete the protected list, and make your own.

Mmm, but if so, people can still run whatever level they want, which ruins the purpose of the request... Unless the level data is stored in a protected list too. :-)
Okay... store the level data in a protected list.

You can't delete the protected list without the protected list's password.

Kingdaro · 2010-04-03 17:19:22

Ask a question.
Check question.
Simple.

technoguyx · 2010-04-03 23:16:56

Kingdaro wrote:
Ask a question.
Check question.
Simple.

And use the hidden sprite trick. But still you can avoid the trick by importing the project...

Yes, Scratch projects are supposed to be editable by anyone. If you don't want people to take it, upload it somewhere else.

qwertypower · 2010-04-04 10:10:45

benjamin2 wrote:
Sometimes you may have a secret password for a game which must be entered to play it. Maybe it could be found from another game.

The idea is, you must script the password, and people may download your project and see the password, or any other secrets in the project. Maybe you could do it so that if you want, you can have an option so that if people download your project, you can enter a password for a script, sprite, or background, so that in order to view the script,sprite, or background, a password of the maker's choice must be entered.

Example:

Maybe on a level 3 project of a game, when you beat it, you got a password. This could be anything: let's example it as (paper).

On the level 4 project, you will be asked to enter a password to play. It could ask for the password with the ask block, then if you entered 'paper', the level would play. People could download and see that the password to play is paper, without beating level 3.

So you could put a password on the script, a random one like 'computer', then downloaders would have to enter that password to see the script, but only the person who made the game would know the password to view the script. Then they could also password protect any background or sprite that shows the password. This would protect the solution of the game.

benjamin2
_________

I know what your talking about but what if the person can't finish the game and they want to see the scripts so they are able to use them in developing their own projects.
Bottomline is that passwords would take away the scratch policy of sharing projects freely.