I found that there are no tools for testing your ping with the cloud that actually work.
So why don't we make a ‘ping’ block for Scratchers (Since it goes with the cloud stuffs) to test the ping to the cloud?

I imagine it like this:

☁ ping :: sensing reporter

This block would return the current ping with the cloud in milliseconds (ms).

I know what you're thinking. Why? What's useful about this block? It's too confusing for new Scratchers.

1. Because, it is a capability fundamentally nonworkaroundable that many multiplayer game-makers could really use.
2. You can use it for all sorts of things. You can use it to test if someone's able to recieve messages fast enough to keep up with your game, if they're lagging, or if they are connected to cloud after they load the page.
3. New Scratchers couldn't access this, and so we don't need to worry about them; New Scratchers can't do anything with the cloud, so why let them have this?

Q & A
Q: What is ping? (CandyLanguageGirl)
A: Ping is the time it takes for a computer to send a message to a server and receive a response.

-Brax

Reserved in case Q and A gets too big, or I decide to add a supporter/nosupporter list

*Awkwardly coughs* Ermm, what is a ping? That should probably be explained in the OP so cloud-challenged scratchers like myself have some idea of what you're talking about.

Candylanguagegirl wrote:

*Awkwardly coughs* Ermm, what is a ping? That should probably be explained in the OP so cloud-challenged scratchers like myself have some idea of what you're talking about.

Ping is the time it takes for a user to send a message to a server and receive a response.

Candylanguagegirl wrote:

*Awkwardly coughs* Ermm, what is a ping? That should probably be explained in the OP so cloud-challenged scratchers like myself have some idea of what you're talking about.

In first post now.

bump

bump

bump

I think this would be useful! But I think it should be called “ping time” since it would report the time it took for it to ping the cloud, not just do a ping.

P-Code wrote:

I think this would be useful! But I think it should be called “ping time” since it would report the time it took for it to ping the cloud, not just do a ping.

Yes but the time it takes to ping a server in most cases is referred to as ‘ping’. Any gamers ask: “What's your ping?” not “What's your ping time?”. Time's redundant because the computer already measures the time between the sending of the message and the receiving of it. Besides; there's always that info bar at the right to explain a block. If they don't quite know what it is, they can use that.

I would like a bit of justification here. How will this help projects?

DownsGameClub wrote:

I would like a bit of justification here. How will this help projects?

It allows many things. See first post.

braxbroscratcher wrote:

DownsGameClub wrote:

I would like a bit of justification here. How will this help projects?

It allows many things. See first post.

(*neck* Why do I not read posts?)

I like this idea. The idea is specific enough to carry out a function as needed, but also lets users customize it to their benefit.

bump

(time since last cloud update)::sensing

Something like this, maybe, so it's less confusing? I'd love it!

(I don't know what's going on with my Scratchblocking)

JoeyTheChicken wrote:

(time since last cloud update)::sensing

Something like this, maybe, so it's less confusing? I'd love it!

(I don't know what's going on with my Scratchblocking)

That's kinda wordy… Ping is actually a very good term as it's literally like a ping. It sends a message and waits for it to bounce back. Also, this is unavailable to New Scratchers so yea

braxbroscratcher wrote:

JoeyTheChicken wrote:

(time since last cloud update)::sensing

Something like this, maybe, so it's less confusing? I'd love it!

(I don't know what's going on with my Scratchblocking)

That's kinda wordy… Ping is actually a very good term as it's literally like a ping. It sends a message and waits for it to bounce back. Also, this is unavailable to New Scratchers so yea

Yeah, I know it's wordy ;D But maybe if we can find a way to shorten it without losing too much meaning. I get what you mean by ping, but “ping” is kinda an esoteric term. I mean, most people who are using Scratch (Even after they're New Scratchers) won't quite get it as well as if we spell it out right in the name

JoeyTheChicken wrote:

braxbroscratcher wrote:

JoeyTheChicken wrote:

(time since last cloud update)::sensing

Something like this, maybe, so it's less confusing? I'd love it!

(I don't know what's going on with my Scratchblocking)

That's kinda wordy… Ping is actually a very good term as it's literally like a ping. It sends a message and waits for it to bounce back. Also, this is unavailable to New Scratchers so yea

Yeah, I know it's wordy ;D But maybe if we can find a way to shorten it without losing too much meaning. I get what you mean by ping, but “ping” is kinda an esoteric term. I mean, most people who are using Scratch (Even after they're New Scratchers) won't quite get it as well as if we spell it out right in the name

yes but there are still terms like that: e.g. variable, boolean, reporter.

If you really want to understand something, you gotta look it up.

Doesn't mean we can't make things a little easier on people! That's what Scratch is all about, ya know? I mean, think about your example, booleans. You don't actually have to know the name of a boolean to use it. I mean, I'm not even confident I remember what it is and I'm pretty proficient! (It's the point-ended condition-checker, right?) Scratch makes them easy to remember by their shape. Making everything easy to understand is important to the Team!

Yes, but still; you can't baby everyone and shield them from the technical terms.