Yo, change the last script I suggested to this:
You can delete the first block if you want. It is just a custom block I made which contains 3D movement blocks inside of it.
Yo, change the last script I suggested to this:
You can delete the first block if you want. It is just a custom block I made which contains 3D movement blocks inside of it.
This project is stale for a while, so I'm reviving it.
I have modified the clock script for the original (non-clone) sprite, which in turn tells the stage to tell the time. Havng multiple clones replicate the exact same bubble at once only creates a lot of lag.
Last block of the script hatted by when I start as a clone is now this:
forever {
run ({move () steps::rgb(0,14,230)
if on edge, bounce} @>) with inputs ((1) + (([abs V] of (x position::rgb(0,14,230))) / (10)) @<:>) @<:>
}This is now the last block of the first script:
Are we allowed to remove blocks other people have made, or is it purely additive?
I say yes, but this is about adding.
Make sure you keep the block count increasing by adding more blocks at a rate higher than removing.
I thought about reviving this again.
I guess it's time to slowly morph this into another operating system because interest plummeted really swiftly...
when gf clicked +ask (list [Apps] (list [Clock] @<>) @<>) and wait +if <answer is [Clock]::sensing>::control cap
At least to me it's looking fit for another library block.