TopCode wrote:

support, as always there is a workaround, but who wants to have to make everything a workaround

I don't think this can be worked around.. can it?

Doesn't seem to be rejected, support. It could use less cloud variables for save codes (if cloud variables are used for save codes, idk I haven't used one yet)

NotDucki_ wrote:

Doesn't seem to be rejected, support. It could use less cloud variables for save codes (if cloud variables are used for save codes, idk I haven't used one yet)

Using a cloud-based save data system is a really bad idea when you're working with a limit at all. Just give the user their save data and tell them to save it in a text document. Here's what I said about it in a different thread:

A save code system lets users save multiple games at once and take them wherever they want, which is much more convenient than being restricted to a single save per account.

I think the character limit should be 5040 characters long as that number has a lot of factors and thus you could evenly divide it between all the integers from 1 to 10 and:
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 14, 15, 16, 18, 20, 21, 24, 28, 30, 35, 36, 40, 42, 45, 48, 56, 60, 63, 70, 72, 80, 84, 90, 105, 112, 120, 126, 140, 144, 168, 180, 210, 240, 252, 280, 315, 336, 360, 420, 504, 560, 630, 720, 840, 1008, 1260, 1680, 2520, 5040 cloud variables. If that is too much, we could always do 2520, which is less than 2560, but is divisible by 1 through 10 as well.

On a side note, what would happen if I had a number of cloud variables that doesn't even divide 2560 or any other number? For instance, what if I wanted 13 cloud variables, but… 2560/13 = 196.9230769 = 196 R12, so 12 cloud variables could be 197 digits and the 13th would be 196. Which one would be the shorter one? Or would the 12 extra digits be discarded?

fdreerf wrote:

On a side note, what would happen if I had a number of cloud variables that doesn't even divide 2560 or any other number? For instance, what if I wanted 13 cloud variables, but… 2560/13 = 196.9230769 = 196 R12, so 12 cloud variables could be 197 digits and the 13th would be 196. Which one would be the shorter one? Or would the 12 extra digits be discarded?

I thought the cloud variable limit was 10

NotDucki_ wrote:

fdreerf wrote:

On a side note, what would happen if I had a number of cloud variables that doesn't even divide 2560 or any other number? For instance, what if I wanted 13 cloud variables, but… 2560/13 = 196.9230769 = 196 R12, so 12 cloud variables could be 197 digits and the 13th would be 196. Which one would be the shorter one? Or would the 12 extra digits be discarded?

I thought the cloud variable limit was 10

Correct you are! You get a gold star for your valiant observation!

That question is for when this suggestion gets implemented, so you could have more than 10 cloud variables.

Good idea, but the limit must be ten clould varubles and i feel i could use this

PGBFLITE6373 wrote:

Good idea, but the limit must be ten clould varubles and i feel i could use this

Why must the limit be 10 cloud variables? The whole point of this suggestion is to use more variables without increasing the space Scratch needs.

fdreerf wrote:

PGBFLITE6373 wrote:

Good idea, but the limit must be ten clould varubles and i feel i could use this

Why must the limit be 10 cloud variables? The whole point of this suggestion is to use more variables without increasing the space Scratch needs.

so you don't crash scratch, its got to keep track 40 cloud varubles per prodject and 800 prodject no thats to much

PGBFLITE6373 wrote:

fdreerf wrote:

Why must the limit be 10 cloud variables? The whole point of this suggestion is to use more variables without increasing the space Scratch needs.

so you don't crash scratch, its got to keep track 40 cloud varubles per prodject and 800 prodject no thats to much

That's not how things work.

bump

bump

2nd page bump (again)

and a bump

bump

bump

bump

bump bumpity bump bump bah-dump

You can implement your own cloud storage engine to split the 2560 digits between different variables however you want. For example, here is mine: https://scratch-mit-edu.ezproxyberklee.flo.org/projects/485326740/ . (I didn't optimize it fully so it is a bit slow)

I think the 10 cloud variable is fine, you can workaround it through putting multiple values into one variable and using this block

(letter (2) of (☁ variable))

and the site is already laggy enough, no support