I have a couple theories -

• Maybe altering the truth table? Can that be done?
  

• Messing with the JSON so the input is the same as the output…
  

• Nothing else…
  

The purpose of this is to allow a Cloud Var to accept characters besides 1234567890 and 1 {.}.

set [☁hack v] to [<<> and < >> ]

Gives you…

<(☁hack) = [false ]>

And it saves!

UPDATE: (I know it's early) I don't think the JSON is going to cut it.

Thats because True or False are considered values by most programming language

You can update your posts with the EDIT button.

So….
There's a fundamental problem with this.
Scratch is setting the cloud var to This is very different than Scratch converts the value to a string when you visit the cloudmonitor page.

That makes sense.

So

True

Isn't what's actually in the var, it's the value true.

I think.

flutehamster wrote:

That makes sense.

So

True

Isn't what's actually in the var, it's the value true.

I think.

Exactly!

I think

Should I close this?

No, wait a day.
Maybe somebody can prove us wrong

░░░░░░░░░░░░▄▄░░░░░░░░░
░░░░░░░░░░░█░░█░░░░░░░░
░░░░░░░░░░░█░░█░░░░░░░░
░░░░░░░░░░█░░░█░░░░░░░░
░░░░░░░░░█░░░░█░░░░░░░░
███████▄▄█░░░░░██████▄░
▓▓▓▓▓▓█░░░░░░░░░░░░░░█░
▓▓▓▓▓▓█░░░░░░░░░░░░░░█░
▓▓▓▓▓▓█░░░░░░░░░░░░░░█░
▓▓▓▓▓▓█░░░░░░░░░░░░░░█░
▓▓▓▓▓▓█░░░░░░░░░░░░░░█░
▓▓▓▓▓▓█████░░░░░░░░░█░░
██████▀░░░░▀▀██████▀░░░

It's not possible to change the output of a reporter/boolean to set a cloud var to anything other than numbers.
It's not hacked, those are boolean values and not actually strings, which ARE permitted in cloud variables (actually 0=false and 1=true, so they are still numbers). You can use hexadecimal instead of decimal. To use hexadecimal just prefix all your numbers with 0x and they will be treated as integers (you can store them in cloud vars, and you can multiply, divide, add and anything else although if you use maths it will return the corresponding decimal number).
So no…

Ah, I tried.