This is a script-based capture-the-flag game. In order to play, you will have to actually go into the scripts and alter them to extract the original value that was encrypted. Since you need to modify scripts to play, coming back to this project and entering the answer you found on your own is a good way to go about this. The leaderboard "rankings" are based on who finished the challenges first; there is no point system. The leader-board is cloud-based, so the usernames you see are the actual Scratchers that completed each challenge. All of the scripts you will need to modify are in the "The Encryptor Sphere" sprite. They are under a yellow comment band in custom blocks named by each level. Have fun and good luck! For level 3, there are a couple of answers that will work for the decrypted value, just by nature of the decryption algorithm. Due to Scratch cloud server rules, if you are not signed in, you can't be added to the leaderboard for others to see; the "Guest User" is just temporary. WARNING: as project creator, I have the right to reset the leaderboard if need be. If there is any data loss to the leaderboard, users who have been erased will be re-added from the "Cloud Data" tab. In the event of any resets or script changes, I will post the date of them here: Resets: NONE Changes: NONE Manual Leaderboard Changes: - 2019 May 9: manual update of a username. For some reason, the value in the Cloud Data tab didn't match the value in the project. Please notify me if the problem persists. I'll start a version log if I end up making script changes...
NOTE: All scripts are original and made by me. Please, if you use them, give credit! It took some time and effort to make this, so I would appreciate it if you would do so. Thanks! This game came about as a sort of proof-of-concept. Since you can actually see the scripts in Scratch, how would you design a project to be password-protected? You would have to find some way of avoiding plain-text passwords throughout the scripts. If you used a one-way function to produce a hash like real computer encryption, the encryption and decryption keys would be exposed, making the password easy to derive. So, what if you use just a decryption algorithm and have the answer stored as a hash or cipher? Well, if you only use a decryption algorithm, then the algorithm cannot be a one-way function; the answer can still be derived from the scripts, though not directly. This means that the user would have to crack it themselves, which would definitely increase the difficulty of finding the original password than just having it in plain-text. That’s when I figured that this might make an interesting game for the Scratch community. ---- Credit: ---- - Intro music: https://freesound.org/people/frankum/sounds/324881/ - Sounds: http://soundbible.com/suggest.php?q=message&x=0&y=0 - Icon: https://cdn.iconscout.com/icon/premium/png-256-thumb/corrupt-file-2-652742.png - Sphere: https://carmelourso.files.wordpress.com/2010/06/esfera.png - Buttons: https://d2gg9evh47fn9z.cloudfront.net/800px_COLOURBOX3088866.jpg - Case Sensitivity Approach: https://en.scratch-wiki.info/wiki/Case_Sensing ---- Made in Scratch 2.0
