set[☁ cloud variable v]to[0]

change[☁ cloud variable v]by(1)
(☁ cloud variable)

space_elephant wrote:

How do I simulate a cloud var watcher?
I know how to do blocks but not watchers.

Garamol56 wrote:

What do you mean by watcher? Like something that detects when they change?

(12::variables)
(☁ score(12::variables)::grey)
☁ score(12::variables)::grey hat
------+-----------------::grey cap

(☁ score)
set[☁ score v]to[0]

change[☁ score v]by(1)

Jonathan50 wrote:

It should appear on the stage once you make a cloud variable. You can toggle it with the checkbpxcheckbox next to the variable in the palette.

space_elephant wrote:

I mean like another program, not scratch, using a cloud var watcher.

space_elephant wrote:

Jonathan50 wrote:

It should appear on the stage once you make a cloud variable. You can toggle it with the checkbpxcheckbox next to the variable in the palette.

I mean like another program, not scratch, using a cloud var watcher.

Jonathan50 wrote:

space_elephant wrote:

I mean like another program, not scratch, using a cloud var watcher.

Oh, okay, sorry. Then you will have to write code to draw the watcher, using whatever graphics library you use (if that's what you want.)

Wettining wrote:

Do you mean something like the ScratchAPI that will get your cloud variables from an external client?

space_elephant wrote:

I don't care about the drawing it. I mean the API.

wss://clouddata.scratch.mit.edu

• method (string) - the action that this object represents
  
• project_id (string) - the numeric ID (as seen in the URL bar) of the project in question. Note that this value is a string.
  

• user (string) - your username
  

• name (string) - the name of the cloud variable, including the cloud symbol
  
• value (string) - the value of the cloud variable - always a string
  

1. Client connects to clouddata.scratch.mit.edu
   
2. Client sends handshake
   

   {
     "user": "exampleuser",
     "project_id": "1234567",
     "method": "handshake"
   }
   

3. Server tells client what the current value of the cloud variable is
   

   {
     "project_id": "1234567",
     "method": "set",
     "name": "☁ counter",
     "value": "12"
   }
   

4. Client tells server about a change to the cloud variable
   

   {
     "user": "exampleuser",
     "project_id": "1234567",
     "method": "set",
     "name": "☁ counter",
     "value": "13"
   }
   

jokebookservice1 wrote:

Scratch uses WebSockets (RFC6455) for it's Cloud Data API. You want to open a connection to

wss://clouddata.scratch.mit.edu

For security, you'll need to send an Origin: header of scratch.mit.edu, and be logged in (i.e., have your Cookie: header set)

Basic Structure
All data is sent backwards and forwards as JSON objects. Here are the properties that all such objects will have

• method (string) - the action that this object represents
  
• project_id (string) - the numeric ID (as seen in the URL bar) of the project in question. Note that this value is a string.
  

In addition, client-to-server objects must have an additional property that server-to-client messages don't need.

• user (string) - your username
  

Setting data
On top of the basic structure, you also need to send the following to set a cloud variable to a specific value. The “method” property should be set to “set”.

• name (string) - the name of the cloud variable, including the cloud symbol
  
• value (string) - the value of the cloud variable - always a string
  

Getting data
The server will send you the same data as in Setting data if the value of a cloud variable changes (and you weren't the person who set it). It'll still be the “set” method, but note that the “user” parameter will not be given to you (that's only given on client-to-server data)

Example
Here's a generic example of what a connection might look like:

1. Client connects to clouddata.scratch.mit.edu
   
2. Client sends handshake
   

   {
     "user": "exampleuser",
     "project_id": "1234567",
     "method": "handshake"
   }
   

3. Server tells client what the current value of the cloud variable is
   

   {
     "project_id": "1234567",
     "method": "set",
     "name": "☁ counter",
     "value": "12"
   }
   

4. Client tells server about a change to the cloud variable
   

   {
     "user": "exampleuser",
     "project_id": "1234567",
     "method": "set",
     "name": "☁ counter",
     "value": "13"
   }
   

But how does the slider work?

And how do I know who changed it?

jokebookservice1 wrote:

space-elephant wrote:

And how do I know who changed it?

Good question! As far as people have discovered, the only way is to parse the HTML of the cloud logs. (The URL of these logs can be found by clicking a link below the relevant project)

space_elephant wrote:

How do I simulate a cloud var watcher?
EDIT: many have been confused about what I mean so:
I can do

set[☁ cloud variable v]to[0]

change[☁ cloud variable v]by(1)
(☁ cloud variable)

and I can also do

the only thing that I need help for is


Also the I can do that last one without the slider.

Raytracing wrote:

space_elephant wrote:

How do I simulate a cloud var watcher?
EDIT: many have been confused about what I mean so:
I can do

set[☁ cloud variable v]to[0]

change[☁ cloud variable v]by(1)
(☁ cloud variable)

and I can also do

the only thing that I need help for is


Also the I can do that last one without the slider.

Check out my userstats project (it takes your info and uploads it to the cloud)
Then I made a python script to check what has been uploaded. so now I have a log of everyone >
Also my python script doesn't use and API's it only uses the tools provided in 3.0 . I could give you the script if you want

space_elephant wrote:

jokebookservice1 wrote:

space-elephant wrote:

And how do I know who changed it?

Good question! As far as people have discovered, the only way is to parse the HTML of the cloud logs. (The URL of these logs can be found by clicking a link below the relevant project)

Looking at this, the HTML does not help at all. the correct file is at https://clouddata.scratch.mit.edu/logs?projectid=279457375&limit=1&offset=0 and is JSON, not HTML.

space_elephant wrote:

Unable to find either by hyperlinks on this page. Can you make one here?