I wanted to make a password system or something very similar to that but I think users will find out the password/code/key by looking in the scripts easily so anyway to make the password/key/code system impossible to find passwords for my game in the scripts so no one can play if they're really a tester?

you could do something like adding any significant amount of codes on different sprites (you could even hide the code under other code) in a string that you would remember

when I receive [broadcast]
ask [digbrist] and wait
if <(answer) = [whatever]> then
broadcast [broadcast 2]
end

and then eventually do what you need to do

was this helpful

Not really possible but why do you want to do this? They can't change your project so what does it matter if they run it?

Unfortunately this is not possible, I guess you can put loads of random blocks on top of it but it might violate community guidelines (Embrace remix culture.)

TonGames wrote:

I wanted to make a password system or something very similar to that but I think users will find out the password/code/key by looking in the scripts easily so anyway to make the password/key/code system impossible to find passwords for my game in the scripts so no one can play if they're really a tester?

You can hide blocks under each other (only a pixel will be peeking out so it will be hard to see)

You could cover it with lots of other code that is disconnected from any real way to run, or name everything, including variables something odd. You could also design a numerical or letter code for everything you write so no one can understand it.

You could encode the answer and compare it with the encoded password. Use difficult, random strings when encoding, and name the variables to make it look like the encoded password variable is the real password variable.

Hello
I think this could help you.
Code:

when green flag clicked
ask [Pin] and wait
if (pin) then
broadcast [start]
end
when green flag clicked
set [Pin] to (join (pick random (1) to (10)) [(username)])

But if you want to work for you only you can do this:

when green flag clicked
if <(username) = [TonGames]> then 
broadcast [START]

else
broadcast [ PRIVATE]
end

You can give testers turbowarp link of the project, so they can test unshared project.

There is no way to protect project from hackers unless you make your scripts so hard to read they can't find the right script.

TonGames wrote:

I wanted to make a password system or something very similar to that but I think users will find out the password/code/key by looking in the scripts easily so anyway to make the password/key/code system impossible to find passwords for my game in the scripts so no one can play if they're really a tester?

you could just use a save code which is unique to every user and has their data on it.

Adam-Basha wrote:

Hello
I think this could help you.
-snip-

But how would anyone know the pin if its just randomized? Like OP said, they want a password so only testers can play the game.

you can just click the “set variable to ()” block with the password, then delete that block and no one will know

you can even disguise the variable name so that it wouldnt seem like the password

Conduit7 wrote:

you can just click the “set variable to ()” block with the password, then delete that block and no one will know

you can even disguise the variable name so that it wouldnt seem like the password

Not really going to make much difference - you just identify the code that rejects the wrong password and you can see what it is being checked against.