im making a fnaf game and it uses multiple tabs so i would be cool to do somthing like this:

when green flag clicked
broadcast to [secondarygame] [animatronic in vent]

when green flag clicked
when I receive [animatronic in vent] from [maingame]
show

WE NEED THIS! what about like a “shop” for points you used in other projects.
waiiiit I just thought of something! the first “egg hunt” easter event could exist

I support this idea so much!

bump (even if it's archived), this is a good idea.

Also, why is this archived?

MagicCoder330 wrote:

bump (even if it's archived), this is a good idea.

Also, why is this archived?

what do you say on an archived post?

this isn’t some why did the chicken cross the road joke, i just have never encountered an archived post

bump

bumpity bump bump

‌

Bump due to duplicate.

MillionOfficial wrote:

+99999999999999

This suggestion is archived. This shows why it was archived (note that what @flutehamster is saying was from before it was closed):

flutehamster wrote:

I feel like Paddle2See actually has a point. Sure, you can use it for, a multi stage game, but why not combine them? They are, after all, one project. I asked my little brother, and he thought it was too complicated. For emerging Scratchers, doesn't it make sense for one project to be self contained?

Don't get me wrong - I do see how the potential upsides. If you make the second half based on popularity, it would be nice to transfer their “User Stats” to the second project. Or maybe, if you have something that goes pass the storage limit, you may want that, or multiple servers… but all of this is hard.

Paddle2See wrote:

Seems like it adds a fair amount of complexity.

In the end, you have to consider Scratch's target audience - Should new programmers be exposed to such complexity?

In conclusion, I have to make another point. Reading past posts, I feel like the question has changed from “Why should we have it?” to “Why shouldn't we?”, which, in my opinion, is not the correct way to frame a suggestion. Example: Why shouldn't we have a Veloceraptor head run across the screen every page load on the forums?



PS: Does your suggestion help the target audience have a smoother experience? Example: the steps block.

TheCreatorOfUnTV wrote:

MillionOfficial wrote:

+99999999999999

This suggestion is archived. This shows why it was archived (note that what @flutehamster is saying was from before it was closed):

The original poster said that you can still post though, despite it being archived.

flutehamster wrote:

I feel like Paddle2See actually has a point. Sure, you can use it for, a multi stage game, but why not combine them? They are, after all, one project. I asked my little brother, and he thought it was too complicated. For emerging Scratchers, doesn't it make sense for one project to be self contained?

Don't get me wrong - I do see how the potential upsides. If you make the second half based on popularity, it would be nice to transfer their “User Stats” to the second project. Or maybe, if you have something that goes pass the storage limit, you may want that, or multiple servers… but all of this is hard.

Paddle2See wrote:

Seems like it adds a fair amount of complexity.

In the end, you have to consider Scratch's target audience - Should new programmers be exposed to such complexity?

In conclusion, I have to make another point. Reading past posts, I feel like the question has changed from “Why should we have it?” to “Why shouldn't we?”, which, in my opinion, is not the correct way to frame a suggestion. Example: Why shouldn't we have a Veloceraptor head run across the screen every page load on the forums?



PS: Does your suggestion help the target audience have a smoother experience? Example: the steps block.

Inter-project cloud variables open up new possibilities for Scratch. They allow for cloud variables in older versions of a project to sync with newer ones. There are nearly infinite uses for this feature, and it allows for incredibly complex projects to become reality. “Low floor and wide walls” are two principles that Scratch goes by, and this suggestion falls into both. There are no perfect workarounds, either.
Imagine this scenario: you have two versions of a cloud multiplayer game. You know that not enough people will play the old version for it to be fun anymore, but you know that some folks still want to play the old version instead. If you combined the projects, it would cause long loading times, and fewer people would be willing to use your project. There’s a third party cloud variable synchronizer available, but it is unreliable and has frequent outages. In this case, inter-project cloud variables are the only viable option. What if you simply had a cloud scoreboard instead? Would it say to the user after they beat their personal best score, “You beat your highscore! Now enter your score into the new version’s scoreboard!” It couldn’t really just do that, because people would type in something that’s 10 above the world high score. Sure, hackers will always just use See Inside and modify the code to allow them to enter something outrageously high, but then you at least have to go out of your way to lie about your score.
There are other new possibilities, too. People could come up with authenticators that save account stats across their projects. They could have one project that scans a profile picture texture and passes it onto a variety of other projects that use it, instead of having to re-enter the texture data each time. Unfortunately, this could be used to automate user blocking systems, but that was going to happen manually anyway, if it happens at all. Almost every other programming language can communicate with other websites- why can’t Scratch? I know that we have to keep projects contained within the website, but they shouldn’t have to be contained within the project page.
Scratch’s slogan is “Imagine, Program, Share” but they also go by another saying: low floor and wide walls. Wide walls means that you can do almost anything on Scratch. While it’s often used to convey the idea that you can make all different kinds of projects, it also means that you can do all kinds of things within your project. Inter-project cloud variables are one of those things that widen those walls. Low floor means that even people with no prior coding experience can still understand and use the platform. First of all, true beginners probably don’t even have a Scratch account, and those who do are New Scratchers. Neither can create cloud variables. Even those who do reach Scratcher status before learning more advanced features would probably steer clear of cloud variables in general until they needed them, in which case they would probably seek a tutorial. Also, new users have just as hard a time understanding custom block inputs and ordinary cloud variables as they would this. Why not add a feature that creates new possibilities when you’ve already added these other features that have the same problem?
I’ve already covered the imperfect workaround with copying data from one project to another, but what about other ones? There are, of course, third-party services that do the job, but these can be unreliable. There was once a shop (mentioned in the OP) that did this, and it has since shut down. Combining the projects can cause them to become over the 5MB JSON size limit, especially if you have several versions that you’re keeping completely separate from each other except for the cloud variable(s). The project owner can manually sync the projects, but you can’t expect the user to just keep doing this indefinitely at a high rate of speed (one sync per minute, say) and even that doesn’t work for cloud multiplayer games, which require live (or as fast as the server can handle) updates.
A quick note for everyone saying that it adds too much complexity- if you're trying to say that new users won't understand this, you're using the wrong word. This, if implemented properly, is actually fairly simple. Confusion would be a better word choice because it can be hard to wrap your head around the idea of a project being able to set a variable that can be read from another project. I understand not being able to understand something- when I first started, I had a hard time understanding lists. There are little features of Scratch that allow for highly inventive projects, like trigonometry blocks and run without screen refresh in custom blocks. Some features have workarounds, but others, like this, don't. I can understand not wanting to implement a suggestion that just speeds up the process doing something complex, like exponents, but this has no other way of doing it within Scratch.
There is no reliable or practical workaround for this, there’s no good reason (as far as I can tell) to not implement this, and it unlocks numerous possibilities that Scratchers could only dream of before. I am putting my full support behind this suggestion because it would benefit the Scratch website tremendously.

Bump and support.
This would be super cool.
The amount of creative uses this could have is crazy.

Bump, read what I posted above.

HighlaneGamingStudio wrote:

I literally wrote an entire essay in support of this and nobody else except lfg30700 has responded.

Bump, does anyone else care about this? C'mon, people!

HighlaneGamingStudio wrote:

I literally wrote an entire essay in support of this and nobody else except lfg30700 has responded.

5 bumps and still no responses. How?

If I bump this all the way to the next page, I'm posting a revised version of my essay there.

This is going to get bumped to the next page, isn't it?