define true
if <[thing] = (true)> then
activate true::sensing
broadcast [true v]
end

(true)
when I receive [true v]
say [Correct!] for (2) secs
change [points v] by (1)

define false
if <[thing] = (false)> then
activate false::sensing
broadcast [false v]
end

(false)
when I receive [false v]
say [Incorrect...] for (2) secs
change [points v] by (-1)

if <thing> then
...
end

medians wrote:

If these are meant to be boolean blocks, you can use any condition that is either always true or always false.

Eason_9 wrote:

Why do we need it anyway? We could just do:

if <thing> then
...
end

when green flag clicked
if <<touching color [#FF0000] ?> and <true>> then
restart::control
end

AllenderaGames wrote:

Hey y'all! Can you or someone can make an workaround of this blocks?

set [variable v] to [true]

set [variable v] to [false]

<not <>>//returns true
<<> and <>>//returns false

<not <>> // reports true
<not <not <>>> // reports false

gdfsgdfsgdfg wrote:

<not <>> // reports true
<not <not <>>> // reports false

<not <not <>>>

<<> and <>>

AllenderaGames wrote:

medians wrote:

If these are meant to be boolean blocks, you can use any condition that is either always true or always false.

you don't understand these blocks are for more like quizzes like when a answer is correct or false

cookieclickerer33 wrote:

is this like report or something??

AllenderaGames wrote:

cookieclickerer33 wrote:

is this like report or something??

I didn't understanded you with: ‘' is this like report or something??’' because I only understand if your'e talking about the shape of the block, if that's the case it's reporter not report if you mispelled

cookieclickerer33 wrote:

AllenderaGames wrote:

cookieclickerer33 wrote:

is this like report or something??

I didn't understanded you with: ‘' is this like report or something??’' because I only understand if your'e talking about the shape of the block, if that's the case it's reporter not report if you mispelled

Report as in a report function

when backdrop switches to [question time v]
ask [What's 6x6?] and wait
if <<(answer) = [36]> or <(answer) = (true::sensing)>> then 

  
say [good! you earned an point!] for (2) secs
change [score v] by (1)
else
say [Uh Oh! that's wrong!] for (2) secs
change [score v] by (-1)
end

AllenderaGames wrote:

medians wrote:

If these are meant to be boolean blocks, you can use any condition that is either always true or always false.

you don't understand these blocks are for more like quizzes like when a answer is correct or false

-Expo wrote:

AllenderaGames wrote:

medians wrote:

If these are meant to be boolean blocks, you can use any condition that is either always true or always false.

you don't understand these blocks are for more like quizzes like when a answer is correct or false

then you can easily use variables for that. The computer itself does not know whose cousin's uncle's niece's nephew's sister's brother's baby bro's God father died in 1842 (Joking)

AllenderaGames wrote:

AllenderaGames wrote:

Hey y'all! Can you or someone can make an workaround of this blocks?

forget it I searched the posible workarounds but I searched on the wiki and some Scratchers wanted it as an operator block, anyways here are the workarounds I found:
In variables:

set [variable v] to [true]

set [variable v] to [false]

In operators:

<not <>>//returns true
<<> and <>>//returns false

but I still want a workaround that can be made with sensing blocks ( only voluntary)
and in this post I will interpret that add these blocks in sensing not in operators
and finally I think that these blocks could get added on future versions like 4.0 or the next update but still being 3.0. I don't mind if it's added in operators but I prefer that these blocks are added in sensing

<[1] = [1]>
<[1] = [0]>

Andygun11 wrote:

AllenderaGames wrote:

AllenderaGames wrote:

Hey y'all! Can you or someone can make an workaround of this blocks?

forget it I searched the posible workarounds but I searched on the wiki and some Scratchers wanted it as an operator block, anyways here are the workarounds I found:
In variables:

set [variable v] to [true]

set [variable v] to [false]

In operators:

<not <>>//returns true
<<> and <>>//returns false

but I still want a workaround that can be made with sensing blocks ( only voluntary)
and in this post I will interpret that add these blocks in sensing not in operators
and finally I think that these blocks could get added on future versions like 4.0 or the next update but still being 3.0. I don't mind if it's added in operators but I prefer that these blocks are added in sensing

personally i use:

<[1] = [1]>
<[1] = [0]>

AllenderaGames wrote:

AllenderaGames wrote:

medians wrote:

If these are meant to be boolean blocks, you can use any condition that is either always true or always false.

you don't understand these blocks are for more like quizzes like when a answer is correct or false

and plus in this discussion I interpret that these blocks are reporters (sorry if I sounded rude)