Yo! We all know cloud variables have been super finicky lately. A big reason they keep going down is that many projects “spam” the server with too much data, which makes the whole system lag or crash for everyone.

I’ve been working on a way to make multiplayer games “Server-Friendly.” If we all use these tricks, our games will run smoother and the cloud might actually stay up!

1. The “Only if Changed” Rule
Most people put the set ☁ cloud variable block inside a forever loop. Don't do this! This tells the server your position 30 times a second, even if you aren't moving.

The Fix: Use an if block to check if your X or Y is different from the last time you sent it. If you’re standing still, your project should stay quiet.

if <not <(cloud var) = (local var)>> then
set [cloud var v] to (local var)
wait (0.1) seconds
end

2. Take a Breather (The 0.2s Rule)

Scratch can’t handle a hundred people all talking at once.

The Fix: Put a wait 0.2 seconds block after you update your cloud variable. It sounds slow, but if you use “Lerp” (smooth movement code), nobody will even notice the delay.


3. “Squish” Your Numbers (Encoding)

Instead of using 10 different variables for 10 players, squish everything into one long string.

The Fix: Make every number the same length (like always using 3 digits). For example, instead of sending 12, send 012.

Why? It’s way easier for the server to handle one big “package” of info than ten tiny ones hitting it at different times.

set [buffer v] to (join (x position) (join (y position) (direction)))
if <not <(cloud var) = (buffer)>> then
set [cloud var v] to (buffer)
wait (0.1) seconds
end

4. Use “Fast Blocks” (Run Without Refresh)

When your game reads that long string of numbers to find the other players, it can make your FPS drop.

The Fix: Put your decoding code into a Custom Block and check the “Run without screen refresh” box. This makes the math happen instantly so your game stays at a smooth 30 FPS.


5. Clear Out “Ghosts”

If a player closes their tab, their character stays in the cloud forever unless you fix it.

The Fix: Give every player a “timer.” If they haven't updated their data in 5 seconds, delete their clone! This keeps the game clean for new people joining.
If we all try to be “Server-Friendly,” we can have awesome multiplayer games without breaking Scratch for everyone else.


Check out my project here to see the code in action: https://scratch.mit.edu/projects/1305126896

Bumping for more people to see!

This will also help your lag if you have any!

Bump. Teaching more people about cloud variables.

Please spread the word!

Bumping this for the afternoon crowd! I've also figured out a way to handle infinite players using just one cloud variable while keeping the string at exactly 16 characters. Check the guide for the ‘squishing’ logic!

this is cool! cloud is barely up, so this is very good!

DarkMB wrote:

this is cool! cloud is barely up, so this is very good!

Have you got a multiplayer game? If so, make the changes so cloud might actually stay up!

Also, if you want the multiplayer engine, go here. https://scratch.mit.edu/projects/1050309304 This is a tutorial(not mine) and only uses 107 blocks! Other players can see each other. Using the tricks mentioned in this forum, you can make that tutorial's code even more server friendly!

Wow, so many people are learning! If you have any questions, you can always ask!

If we all code like this, cloud variables will stay up forever!

I'm creating a 3D multiplayer game. I need help with some of the mechanics. Here is the forum post. https://scratch.mit.edu/discuss/topic/880522/?page=1#post-9134015

yo I'm making a instant load no need to use your cheesy fingers and i thought it wasn't working but it's just scratch servers ty

Thank you everyone for the help with cloud variables!