Currently, in scratch only one object (the cloud variable) can be used to transfer data between clients. However it is incredibly limited.

• cloud variables cannot store strings, only numbers
  
• cloud list do not exist, only variables
  
• cloud variables cannot transmit between projects or users
  

This is why I think that cloud data needs to be improved.


1. Cloud Lists
Cloud strings and lists have not been implemented because if you can put any string in a cloud variable, then you can put a bad word in the cloud.
Same for lists, you can put a bad word as an item in a list.
But what if you could have lists who could only have number as items?


2. Bridge and Ship Vars
Cloud variables cannot transmit between projects or users. I think this should be fixed, and I have at least an idea about how to implement it.

Bridge Vars
Currently the scratch variable system looks like this:

(anyone can change and read the values above themselves)
We should add a new variable type that is placed in the user boxes, like this:


Ship Vars
Ship vars are created like bridge vars and have the same effects when created. However, other users may ask for access to read or write to ship vars. You do this by clicking a button on their profile and submitting a request.They may allow you to read, write or use (read and write) the specified ship variable. You may not give a ship variable to a user who has not asked.

You make bridge and ship vars with a modified make variable dialog:

Scratchers also get a different data palette:

when you load you get


Bridge variables go below the bridge var button and ship vars under the ship var button.
There will not be bridge or ship lists.

Please state your opinions for this suggestion.

Awesome idea!

A48c wrote:

Awesome idea!

Please be constructive. Just saying it's awesome isn't constructive. Why do you think it's awesome?
—————–
Anyway, to the OP- Support! I never knew how complex variables were, but this would help improve their functionality.

KJRYoshi07 wrote:

Anyway, to the OP- Support! I never knew how complex variables were, but this would help improve their functionality.

The example assumes shows two users. They each have two shared projects. Each project has one sprite.
There are two running clients on each project. The sprite has one clone.

This is not usual.

KJRYoshi07 wrote:

A48c wrote:

Awesome idea!

Please be constructive. Just saying it's awesome isn't constructive. Why do you think it's awesome?
—————–
Anyway, to the OP- Support! I never knew how complex variables were, but this would help improve their functionality.

Please be constructive instead of harassing users who don't succumb to the scratch suggestion forum echo chamber.

badatprogrammingibe wrote:

KJRYoshi07 wrote:

A48c wrote:

Awesome idea!

Please be constructive. Just saying it's awesome isn't constructive. Why do you think it's awesome?
—————–
Anyway, to the OP- Support! I never knew how complex variables were, but this would help improve their functionality.

Please be constructive instead of harassing users who don't succumb to the scratch suggestion forum echo chamber.

@KJRYoshi07 is right though… this is bad

While this seems like a really good idea at first, wouldn't this allow for cross-project currency?

Cyborus wrote:

While this seems like a really good idea at first, wouldn't this allow for cross-project currency?

Whats wrong with that?

Inkulumo wrote:

Cyborus wrote:

While this seems like a really good idea at first, wouldn't this allow for cross-project currency?

Whats wrong with that?

When someone did make it using their own server (I think @MCanimator3D? I can't quite remember) they took it down.

Cyborus wrote:

Inkulumo wrote:

Cyborus wrote:

While this seems like a really good idea at first, wouldn't this allow for cross-project currency?

Whats wrong with that?

When someone did make it using their own server (I think @MCanimator3D? I can't quite remember) they took it down.

Wouldn't cross-project currency be useful?

Inkulumo wrote:

Cyborus wrote:

Inkulumo wrote:

Cyborus wrote:

While this seems like a really good idea at first, wouldn't this allow for cross-project currency?

Whats wrong with that?

When someone did make it using their own server (I think @MCanimator3D? I can't quite remember) they took it down.

Wouldn't cross-project currency be useful?

If moderated properly, which the scratch team couldn't really do unless the they made one themselves, which they've said they won't do.

Cyborus wrote:

Inkulumo wrote:

Cyborus wrote:

While this seems like a really good idea at first, wouldn't this allow for cross-project currency?

Whats wrong with that?

When someone did make it using their own server (I think @MCanimator3D? I can't quite remember) they took it down.

Cross-project currency isn't bad just because scratch team once banned a cross-project currency server.

Cyborus wrote:

Inkulumo wrote:

Cyborus wrote:

While this seems like a really good idea at first, wouldn't this allow for cross-project currency?

Whats wrong with that?

When someone did make it using their own server (I think @MCanimator3D? I can't quite remember) they took it down.

Because external servers manipulating cloud data is not allowed, nothing to do with cross project currency.

bybb wrote:

Cyborus wrote:

Inkulumo wrote:

Cyborus wrote:

While this seems like a really good idea at first, wouldn't this allow for cross-project currency?

Whats wrong with that?

When someone did make it using their own server (I think @MCanimator3D? I can't quite remember) they took it down.

Because external servers manipulating cloud data is not allowed, nothing to do with cross project currency.

That isn't the only reason though. IIRC they said they didn't want people making projects you had to pay to access, microtransactions, etc.

Well, if you could make somthing like a thing where you have to view 1 project or get to a level befor starting another, it would be useful. But it would be a very complicated feature. Still… I support

Bridge vars are a duplicate.