This is a demo of case-sensitive cloud lists. Click flag to add your username! You must read inside comments if you want to use to understand usage. IMPORTANT: If you stop the project while the list is saving, or if multiple people are updating the list at once, it will cause issues. First one: https://scratch.mit.edu/projects/424026136/ Case checker: https://scratch.mit.edu/projects/424079136/ See inside for a comment tutorial. Feel free to use with credit. UPDATE 10/25/2020: This has a bug. It is sometimes adding 809090 into cloud variables for some reason, which decodes to {<< in the cloud list. I am sorry, I do not know why this is happening, it might just be because of the glitchy properties of cloud variables.
Features: .This has all the tricks and customization options possible, I doubt there is anything that can do something this can't. (This was written a year ago, and I found out this can be made faster and less likely to be corrupted, but this does work good enough. Let me know if you want me to make this better and I will.) .Full comment tutorial inside, you must read if you want to use. .It uses 10 combined cloud variables to make the maximum length 10 times higher, 2,560 characters. .It is case-sensitive. .You can add blanks to the cloud list. .It is easy to use. .It can store numbers. .It has an adaptive encoder, so you can change the characters it is able to store. .You do not need to sacrifice a character to put in between list items. Stats: ____________________________________________ 100% by me Made in about 3 1/2 hours. (I had experience from my first attempt.) 480 blocks, including username cloud list and reset controls, etc. Notes: ____________________________________________ .Infinite cloud lists are impossible, because you can only use up to 10 cloud variables, and each one can only hold a maximum of 256 characters. I used all the possible tricks to make this save as many characters as possible. .Cloud variables can only hold numbers, which greatly reduces the maximum length, but there is no workaround other than encoding into numbers, which takes up at least twice as much space :(
