Make there be specific blocks for multiplayer, and not something that we have to waste an hour or two by just putting in complex threads and scripts.

If you want to put multiplayer in a project, you will have to code it yourself. Not everything will be given to you on a silver platter. All of coding is practically based on not having things given to you on a single platter.
Take a look at this very website, for example. If you happen to be using Chrome, you can right click on any part of this website and click the “Inspect element” button.
That's a lot of text, right?
Exactly. All of that text was coded by MIT students, specifically the Scratch team, and you can bet that they didn't just type in "<website src='https://scratch.mit.edu'>" (an imaginary piece of magical HTML code that would summon the entire Scratch website into being if it worked). The same goes for you, too, Sidd. Coding leads to challenge. Challenge leads to trial and error. Trial and error leads to learning. Learning leads to becoming a great game developer or whatever coding-based profession you would like to be when you grow up.
If you do not understand that coding being difficult leads to you becoming smarter, you do not understand coding. One might say you would not understand learning in general.
How, for example, do you think that the first caveman learned how to create fire? How do you think the Mayan civilization developed a system of math? How do you think civilization developed machinery and government and everything else you take for granted nowadays?
The answer is trial and error. It certainly was difficult for that caveman to find out striking flint against steel would start a fire. You could bet that when he found out you strike two shiny objects together to create warmth, he was amazed. He had learned something, and that method of learning would prove to be the best method of learning throughout history. The young George Washington learned not to lie to his father with trial and error. Genghis Khan learned not to do anything in anger with trial and error. Them, and countless others throughout history have learned infinitely wise pearls of wisdom throughout using trial and error. So, if trial and error proved to be such an indispensable method of learning to them, it may as well prove that indispensable to you.

I rest my case.

Semi-Support. While like @therealpsy said, you can't create by not working and putting little effort. If you ever get stuck on a multiplayer script, you can get help in the Help with Scripts forum.

Please don't use the George Washington Cherry Tree story. It drives me nuts, and its fake.

No support. Programming isn't meant to be easy. It's more satisfying to code something yourself and have it work than to do something like this:

Also, isn't @therealpsy's speech the same from one of those other multiplayer topics? :P

therealpsy wrote:

If you want to put multiplayer in a project, you will have to code it yourself. Not everything will be given to you on a silver platter. All of coding is practically based on not having things given to you on a single platter.
Take a look at this very website, for example. If you happen to be using Chrome, you can right click on any part of this website and click the “Inspect element” button.
That's a lot of text, right?
Exactly. All of that text was coded by MIT students, specifically the Scratch team, and you can bet that they didn't just type in "<website src='https://scratch.mit.edu'>" (an imaginary piece of magical HTML code that would summon the entire Scratch website into being if it worked). The same goes for you, too, Sidd. Coding leads to challenge. Challenge leads to trial and error. Trial and error leads to learning. Learning leads to becoming a great game developer or whatever coding-based profession you would like to be when you grow up.
If you do not understand that coding being difficult leads to you becoming smarter, you do not understand coding. One might say you would not understand learning in general.
How, for example, do you think that the first caveman learned how to create fire? How do you think the Mayan civilization developed a system of math? How do you think civilization developed machinery and government and everything else you take for granted nowadays?
The answer is trial and error. It certainly was difficult for that caveman to find out striking flint against steel would start a fire. You could bet that when he found out you strike two shiny objects together to create warmth, he was amazed. He had learned something, and that method of learning would prove to be the best method of learning throughout history. The young George Washington learned not to lie to his father with trial and error. Genghis Khan learned not to do anything in anger with trial and error. Them, and countless others throughout history have learned infinitely wise pearls of wisdom throughout using trial and error. So, if trial and error proved to be such an indispensable method of learning to them, it may as well prove that indispensable to you.

I rest my case.

Cool! But don't you agree that there should be at least little bit of blocks, very vague?

That's the fun of coding! It's called challenge and learning, which is pretty much the point of the website.

Taking your suggestion literately, multiplayer can be easily done by assigning each player a different set of controls and make each avatar a different sprite.

SiddKidd wrote:

therealpsy wrote:

If you want to put multiplayer in a project, you will have to code it yourself. Not everything will be given to you on a silver platter. All of coding is practically based on not having things given to you on a single platter.
Take a look at this very website, for example. If you happen to be using Chrome, you can right click on any part of this website and click the “Inspect element” button.
That's a lot of text, right?
Exactly. All of that text was coded by MIT students, specifically the Scratch team, and you can bet that they didn't just type in "<website src='https://scratch.mit.edu'>" (an imaginary piece of magical HTML code that would summon the entire Scratch website into being if it worked). The same goes for you, too, Sidd. Coding leads to challenge. Challenge leads to trial and error. Trial and error leads to learning. Learning leads to becoming a great game developer or whatever coding-based profession you would like to be when you grow up.
If you do not understand that coding being difficult leads to you becoming smarter, you do not understand coding. One might say you would not understand learning in general.
How, for example, do you think that the first caveman learned how to create fire? How do you think the Mayan civilization developed a system of math? How do you think civilization developed machinery and government and everything else you take for granted nowadays?
The answer is trial and error. It certainly was difficult for that caveman to find out striking flint against steel would start a fire. You could bet that when he found out you strike two shiny objects together to create warmth, he was amazed. He had learned something, and that method of learning would prove to be the best method of learning throughout history. Genghis Khan learned not to do anything in anger with trial and error. Them, and countless others throughout history have learned infinitely wise pearls of wisdom throughout using trial and error. So, if trial and error proved to be such an indispensable method of learning to them, it may as well prove that indispensable to you.

I rest my case.

Cool! But don't you agree that there should be at least little bit of blocks, very vague?

Nitrus Oxide. Why don't you just learn to program and start simple?!?

What would be the fun in Scratch if you could do this

No support. Scratch doesn't work like that. If you want a multiplayer game, code it yourself. They are hard, but possible. It would take the whole point out of Scratch if all you did was:

SiddKidd wrote:

Cool! But don't you agree that there should be at least little bit of blocks, very vague?

I don't think so. Scratch isn't a put-four-blocks-and-then-done program. Try to program multiplayer yourself. It's a lot more satisfying to see your code work

therealpsy wrote:

If you want to put multiplayer in a project, you will have to code it yourself. Not everything will be given to you on a silver platter. All of coding is practically based on not having things given to you on a single platter.
Take a look at this very website, for example. If you happen to be using Chrome, you can right click on any part of this website and click the “Inspect element” button.
That's a lot of text, right?
Exactly. All of that text was coded by MIT students, specifically the Scratch team, and you can bet that they didn't just type in "<website src='https://scratch.mit.edu'>" (an imaginary piece of magical HTML code that would summon the entire Scratch website into being if it worked). The same goes for you, too, Sidd. Coding leads to challenge. Challenge leads to trial and error. Trial and error leads to learning. Learning leads to becoming a great game developer or whatever coding-based profession you would like to be when you grow up.
If you do not understand that coding being difficult leads to you becoming smarter, you do not understand coding. One might say you would not understand learning in general.
How, for example, do you think that the first caveman learned how to create fire? How do you think the Mayan civilization developed a system of math? How do you think civilization developed machinery and government and everything else you take for granted nowadays?
The answer is trial and error. It certainly was difficult for that caveman to find out striking flint against steel would start a fire. You could bet that when he found out you strike two shiny objects together to create warmth, he was amazed. He had learned something, and that method of learning would prove to be the best method of learning throughout history. The young George Washington learned not to lie to his father with trial and error. Genghis Khan learned not to do anything in anger with trial and error. Them, and countless others throughout history have learned infinitely wise pearls of wisdom throughout using trial and error. So, if trial and error proved to be such an indispensable method of learning to them, it may as well prove that indispensable to you.

I rest my case.

The Scratch Team aren't MIT students.

OH MY GOSH I'VE SEEN THIS SUGGESTION EVERYWHERE

Anyways, coding isn't supposed to be simple. You can't do:

and boom, you're done.

And also, Scratch isn't always about multiplayer. The scratch blocks that exist are there for a reason. They can be used to make anything. All this:

is gonna do is make multiplayer games.

Therefore, no support.

alexphan wrote:

No support. Programming isn't meant to be easy. It's more satisfying to code something yourself and have it work than to do something like this:

Also, isn't @therealpsy's speech the same from one of those other multiplayer topics? :P

Guilty as charged.

therealpsy wrote:

alexphan wrote:

Guilty as charged.

Nice necropost bro

I do think we need more cloud support to make cloud stuff easier, like cloud strings, cloud lists, faster cloud data delivery times between computers, and perhaps other cloud tools, like cloud broadcasts or something. But I do agree with everyone else, too- we can't make multiplayer games too easy.

I like how whenever someone says “We should improve cloud/multiplayer!” everyone immediately assumes they mean add blocks like this:

The fact is that the cloud is incredibly broken right now. It is very very difficult to make a cloud project that works robustly, especially one that is also fast enough to actually be used for realtime gameplay.

Of course, part of the problem is just the inherent lag in cloud variable updates. Still, there is a lot that could really help. For example, if it was possible to allocate space per user and have them write to that, then cloud games would be infinitely easier - there would be no need to keep track of who was connected, who was saving data, who was updating data, etc…

In fact, if cloud included two things: per-user storage space and a block that told whether a particular user was connected, cloud games would be really easy to make and much much more reliable and better in general.

SiddKidd wrote:

and not something that we have to waste an hour or two by just putting in complex threads and scripts.

Waste an hour? Listen, if you really want to make a multiplayer game, then put in some effort. It's not wasting time if you're working really hard on something you want to be proud of. And in the end, wouldn't you feel better and more proud of yourself if you accomplished something really hard, and not something simple that everyone else can do? I think you would. But if you're not willing to put in that effort, you might as well not do it at all. It's not wasting time, it's called hard work.

I could go on and on, but no support.

There are too many ways to make multiplayer. No Support. Also, you need to learn to code. Scratch shouldn't be like this:

I know your not suggesting anything like that, but there are plenty of sourses out there. It's not that hard.

Oh, and if making multiplayer is wasting an hour, then why do you want the ST to waste an hour making it when they have moderation to deal with too?

Sorry if I sounded harsh, I just kinda got carried away. (<—not at you.)

Okay I get that you guys like to be smart and give out examples of multiplayer, but it's getting very annoying. So stop spamming stuff I've seen for years.

I think it's best to leave the multiplayer suggestion to those who can actually code/understand multiplayer, because they know the hardship and will attest to specific cases that merit the need for some built-in mulitplayer.

I find it ironic that you suggested “Make there be specific blocks for multiplayer” but you haven't given one specific block for the idea. It's very downtrodden to make an empty suggestion where the content of the idea rests with someone other than the author. The least you can do to not repeat history again is to specify blocks for multiplayer. Explain what you want each block to do, why it is necessary for multiplayer, and maybe then you might find someone agreeing with you.

If you need help for ideas, consider studying my multiplayer project.

At least a