>>>> Click here to check it out! <<<<


::::::::::::::UPDATES:::::::::::::::

3/28/13

* Confirmed that cloud variables are stable.

* Released 2.0 final version to the community.


3/27/13

* Fixed data translation. Local variable got mixed up after a certain length.


3/26/13

* Had to fix the duplicate handler because it needed exceptions for usernames longer than 9 characters. Silly, but pesky mistake! Took forever to fix.

* Added hotfix for glitching cloud variables




Feedback much appreciated!

- Z <3

Will anyone ever learn.

-facepalm-, just delete this topic

Jeez, bunch of rudes didn't even leave me a chance to update! The irony of your ignorance is that the project actually works. You are free to apologize whenever. Thanks.

oh, well, that's not cloud lists. It's just cloud variables as far as I can tell.

bullelk12 wrote:

oh, well, that's not cloud lists. It's just cloud variables as far as I can tell.

Scratch Community is and should be a friendly community, and 80% of us are and his project has cloud variables which are used to make a list and so it indirectly works and a cloud list, so its good, Instead of teasing him, u should just think how u could use this idea for ur good

Aditya007 wrote:

bullelk12 wrote:

oh, well, that's not cloud lists. It's just cloud variables as far as I can tell.

Scratch Community is and should be a friendly community, and 80% of us are and his project has cloud variables which are used to make a list and so it indirectly works and a cloud list, so its good, Instead of teasing him, u should just think how u could use this idea for ur good

Agreed this method is very usefull, but i do not think it should be labeled as a cloud list.

that was my point, it's not a cloud list, it's a work-around which is great but it's a stretch to call it a cloud list in my opinion.

I made a real cloud list (not that it actually functions as a cloud list), and you do that by hacking. But yours isn't hacked like that I don't think.

I've already done this before, but it was before the time when they said encoders were allowed. THEN, they allowed them again, but by that time, I'd already turned the list into a chatroom for myself, and I wouldn't be able to share it, so now everyone else is taking credit for it.

ImagineIt wrote:

I've already done this before, but it was before the time when they said encoders were allowed. THEN, they allowed them again, but by that time, I'd already turned the list into a chatroom for myself, and I wouldn't be able to share it, so now everyone else is taking credit for it.

It just sucks because I can make the cloud list literally completely functional, but there's and EPIC glitch that scratch team has yet to fix. I don't know how to explain it but basically; cloud variables “expire” after prolonged use. What I mean by that is, when I first make the project (I've made two, so I know it's not my coding) it runs PERFECTLY. Case sensing, number sensing, underscores, dashes. Completely fine. But after about 20 minutes of adding data to the variables, they stop adding them properly, and some of the data gets deleted and the code slips up because of it. If that wasn't happening, I feel like my project would be very appreciated and admired….

that sucks

It seems to be that since the variables extend so long from storing users' names in number form, they reach the floating point and “break” beyond repair.

whoa, that's rare, but apparently possible.

Zparx wrote:

ImagineIt wrote:

I've already done this before, but it was before the time when they said encoders were allowed. THEN, they allowed them again, but by that time, I'd already turned the list into a chatroom for myself, and I wouldn't be able to share it, so now everyone else is taking credit for it.

It just sucks because I can make the cloud list literally completely functional, but there's and EPIC glitch that scratch team has yet to fix. I don't know how to explain it but basically; cloud variables “expire” after prolonged use. What I mean by that is, when I first make the project (I've made two, so I know it's not my coding) it runs PERFECTLY. Case sensing, number sensing, underscores, dashes. Completely fine. But after about 20 minutes of adding data to the variables, they stop adding them properly, and some of the data gets deleted and the code slips up because of it. If that wasn't happening, I feel like my project would be very appreciated and admired….

This sounds like a pretty serious glitch…perhaps you can narrow it down to a simpler case that still shows the problem?

ImagineIt wrote:

I've already done this before, but it was before the time when they said encoders were allowed. THEN, they allowed them again, but by that time, I'd already turned the list into a chatroom for myself, and I wouldn't be able to share it, so now everyone else is taking credit for it.

which technically is also stealing credit fro me because you sued me encoder right

(i meant used, not sued i purposely left it though because i thought it was funny)

bump

bumpdate

bumpdate!