<[Broadcast v]?>

when gf clicked
set [YeetRecieved? v] to [0]
broadcast [yeet v]
when I receive [yeet v]
set [YeetRecieved? v] to [1]

<(YeetRecieved?) = (1)>

<[Broadcast v]?>

set pen color to hex input []::pen

define set pen color to hex input [hex]
set pen color to (join [0x] (hex))

MathlyCat wrote:

dvargasews wrote:

alexphan wrote:

MathlyCat wrote:

alexphan wrote:

MathlyCat wrote:

You should fix the Leap Year workaround

I put it into a custom block:

define (year) is a leap year?
set [leap year v] to [false]
if <((year) mod (4)) = [0]> then 
  if <((year) mod (100)) = [0]> then
    if <((year) mod (400)) = [0]> then
      set [leap year v] to [true]
    else
      set [leap year v] to [false]
    end
  else
    set [leap year v] to [true]
  end
else
  stop [this script v]
end

…or as a boolean:

<<((year) mod (4)) = [0]> or <<((year) mod (100)) = [0]> and <((year) mod (400)) = [0]>>>

Wait why does the custom block have two ‘true’?

…whoops, fixed it!
Leap years are every 4 years canr you jist do year mod 4
I'm just dumb like that

I think that

define (year) is a leap year?
if <((year) mod (4)) = [0]> then 
  if <((year) mod (100)) = [0]> then
    if <((year) mod (400)) = [0]> then
      set [leap year v] to [true]
    else
      set [leap year v] to [false]
    end
  else
    set [leap year v] to [true]
  end
else
  set [leap year v] to [false]
end
stop [this script v]

would be better.
For Boolean, I think that the correct version is

<<((year) mod (4)) = [0]> and <<not <((year) mod (100)) = [0]>> or <((year) mod (400)) = [0]>>>

but maybe someone else could check it?

This is totally wrong…

Leap Years are every 4 years, and so they work by mod 400, but for that to work you also need to mod 4 and 100.

You overcomplicate the custom block which was best as alexphan had it, and the reporter is wrong…

if on top edge, bounce

BD10355 wrote:

Could you make a workaround that senses if the sprite touches a specific side of the screen? Thx. It might look like this.

if on top edge, bounce

if <(y position) > [180]> then
    if on edge, bounce
end

Shaymin524 wrote:

BD10355 wrote:

Could you make a workaround that senses if the sprite touches a specific side of the screen? Thx. It might look like this.

if on top edge, bounce

Use

if <(y position) > [180]> then
    if on edge, bounce
end

change y position and 180 for whichever side you need.

say [You r de best Shaymin524!]

BD10355 wrote:

Shaymin524 wrote:

BD10355 wrote:

Could you make a workaround that senses if the sprite touches a specific side of the screen? Thx. It might look like this.

if on top edge, bounce

Use

if <(y position) > [180]> then
    if on edge, bounce
end

change y position and 180 for whichever side you need.

Thank you!

say [You r de best Shaymin524!]