caftingdead261 wrote:

you can use scratch attach

BigNate469 wrote:

(#4)
Nothing in the OP's question actually requires the Scratch API, and thus does not require scratchattach.
Just create a program with one list (if in Scratch)/array (if anywhere else) that has a list of usernames that have a rank. Then, have another with their rank (if in Scratch), or (if anywhere else) create an object/dictionary inside each array item that holds the user's name and rank.
Note: you will have to update rank manually, because Scratch* doesn't provide a way to do this, because you can't rank people from inside Scratch (outside of the three levels of New Scratcher, Scratcher, and Scratch Team, which are applied already anyways)

*using anything the ST has built into Scratch, anyways.

BigNate469 wrote:

caftingdead261 wrote:

you can use scratch attach

Nothing in the OP's question actually requires the Scratch API, and thus does not require scratchattach.
[…]

Ghxstify2009 wrote:

(#7)
Cloud variables sadly don't accept letters, so it's kinda difficult to create that.

Ghxstify2009 wrote:

What do you mean by cloud list? I know Scratch doesn't yet have a ‘cloud’ list feature available, but there may be a way to create one.. could you provide a link to a tutorial/project/etc.?

Ghxstify2009 wrote:

(#9)
What do you mean by cloud list? I know Scratch doesn't yet have a ‘cloud’ list feature available, but there may be a way to create one.. could you provide a link to a tutorial/project/etc.?

LIZARD_OFFICIAL wrote:

(#12)
EasyDB is great for that!

Stegie1234 wrote:

(#6)

BigNate469 wrote:

caftingdead261 wrote:

you can use scratch attach

Nothing in the OP's question actually requires the Scratch API, and thus does not require scratchattach.
[…]

Cloud variables cannot store enough data and updating local variables or lists manually would be impractical. This would mean using an external database to store the map, and would require scratchattach or a similar API to transfer data between the database and the Scratch project.

ninjaMAR wrote:

Stegie1234 wrote:

(#6)

BigNate469 wrote:

caftingdead261 wrote:

you can use scratch attach

Nothing in the OP's question actually requires the Scratch API, and thus does not require scratchattach.
[…]

Cloud variables cannot store enough data and updating local variables or lists manually would be impractical. This would mean using an external database to store the map, and would require scratchattach or a similar API to transfer data between the database and the Scratch project.

You can store 2560 characters in cloud variables (10 cloud variables * 256 characters)

davidtheplatform wrote:

Cloud vars can only hold digits, not letters so you get 2560 digits. This works out to about a kilobyte of data. If we assume 2x compression on usernames*, an average of 8 characters per username, and 2 bytes of extra data per entry, we can store ~166 total entries.
If you just want a leaderboard this will work, but if you want actual cloud saving you'd need to use a server to handle things.

p.s. The theoretical throughput of cloud variables is 10kb/sec, but I've found that only around half that is possible

ninjaMAR wrote:

davidtheplatform wrote:

Cloud vars can only hold digits, not letters so you get 2560 digits. This works out to about a kilobyte of data. If we assume 2x compression on usernames*, an average of 8 characters per username, and 2 bytes of extra data per entry, we can store ~166 total entries.
If you just want a leaderboard this will work, but if you want actual cloud saving you'd need to use a server to handle things.

p.s. The theoretical throughput of cloud variables is 10kb/sec, but I've found that only around half that is possible

what do you mean by 2x compression? (typo?) my understanding is that you need 2 digits per character of the alphabet, meaning that a username needs 2x space

davidtheplatform wrote:

(#17)
There's roughly 65 characters you can use in a username, so if we encode them properly we only need 1.8 digits per character. Some letters are more/less common, ie. “Q” is probably used less than “e”. We can use huffman coding (or something similar) to get a little bit more compression. Normal english text can be compressed by about 8x for reference.

Various other methods could be used, like truncating usernames to 5 characters, but then you'd have to deal with collisions.

ninjaMAR wrote:

(#11)
https://scratch.mit.edu/projects/495545839/

ninjaMAR wrote:

davidtheplatform wrote:

(#17)
There's roughly 65 characters you can use in a username, so if we encode them properly we only need 1.8 digits per character. Some letters are more/less common, ie. “Q” is probably used less than “e”. We can use huffman coding (or something similar) to get a little bit more compression. Normal english text can be compressed by about 8x for reference.

Various other methods could be used, like truncating usernames to 5 characters, but then you'd have to deal with collisions.

Interesting! Do you have a Proof-Of-Concept?.

base:     14.8 digits per username
packing:  13.4
huffman:  11.2
best:     11.1

ninjaMAR wrote:

davidtheplatform wrote:

(#17)
There's roughly 65 characters you can use in a username, so if we encode them properly we only need 1.8 digits per character. Some letters are more/less common, ie. “Q” is probably used less than “e”. We can use huffman coding (or something similar) to get a little bit more compression. Normal english text can be compressed by about 8x for reference.

Various other methods could be used, like truncating usernames to 5 characters, but then you'd have to deal with collisions.

Interesting! Do you have a Proof-Of-Concept?

ninjaMAR wrote:

(#11)
https://scratch.mit.edu/projects/495545839/

I updated the project to include an API that you can use. Directions are in the editor.