when dash [turned on v]::hat events
when dash [turned off v]::hat events
when dash shaken::hat events
broadcast [message1 v] to dot::events
flash color [purple v]::looks
drive (10) steps::motion
turn in direction [north v]::motion
turn in direction [south v]::motion
turn in direction [east v]::motion
turn in direction [west v]::motion
play sound [meow v] for [3] seconds::sound
play recording::sound
record voice for [5] secs::sensing
turn off dash::cap control
<camera [on v]?::sensing>
<camera [off v]?::sensing>
<dot touching [sprite1 v]?::sensing>
<dash [on v]?::sensing>
<dash [off v]?::sensing>
sense person::sensing
go to [person v]::sensing

Geometry_Dash3 wrote:

how to make hat blocks

hat block :: hat events

hat block :: hat events

when green flag clicked
move (999999999999999) steps

jax_rose wrote:

You could make it very slow when this code used:

when green flag clicked
move (999999999999999) steps

-gge wrote:

jax_rose wrote:

You could make it very slow when this code used:

when green flag clicked
move (999999999999999) steps

that's not slow

wait (or whatever you want to put in here) secs
move (insert variable here) steps

frances2005 wrote:

While looking on amazon, i saw a dash robot. it is used with an IPAD and you can control it to make sounds, change colors, drive etc. we already have a picoboard, the lego wedo 1.0, and the lego wedo 2.0. what if for scratch 3.0, projects could connect to the dash robot?
there would be blocks that would work like this:

when dash is turned on:: sensing hat
drive [10 v]  steps :: operators stack
flash the color [purple v] ::variables stack
turn [10 v] to the north and [10 v] to the south ::pen stack
play sound [laughing v] for [2 v] secs :: motion stack
record viewers voice for [5] secs ::sensing stack
play back recording ::operators stack
turn off dash ::looks cap

when dash is turned on :: events hat
drive (10)  steps :: motion
flash the color [#ffff00] :: looks
turn (10) to the north and (10) to the south :: motion
play sound [laughing v] for (2) secs :: sound
record viewers voice for (5) secs :: sensing
play back recording :: sound
turn off dash :: control cap

Pianostar4 wrote:

While I like the idea, most people don’t have dots or dashes

dhuls wrote:

Pianostar4 wrote:

While I like the idea, most people don’t have dots or dashes

You can say the exact same thing about all of the hardware extensions, so should we remove those too?

37_Scratch wrote:

frances2005 wrote:

While looking on amazon, i saw a dash robot. it is used with an IPAD and you can control it to make sounds, change colors, drive etc. we already have a picoboard, the lego wedo 1.0, and the lego wedo 2.0. what if for scratch 3.0, projects could connect to the dash robot?
there would be blocks that would work like this:

when dash is turned on:: sensing hat
drive [10 v]  steps :: operators stack
flash the color [purple v] ::variables stack
turn [10 v] to the north and [10 v] to the south ::pen stack
play sound [laughing v] for [2 v] secs :: motion stack
record viewers voice for [5] secs ::sensing stack
play back recording ::operators stack
turn off dash ::looks cap

How about this?:

when dash is turned on:: sensing hat
drive [10]  steps :: operators stack
flash the color [purple v] ::variables stack
turn [10] to the north and [10] to the south ::pen stack
play sound [laughing v] for [2] secs :: motion stack
record viewers voice for [5] secs ::sensing stack
play back recording ::operators stack
turn off dash ::looks cap

when dash is turned on:: extension hat
drive (10)  steps :: extension stack
flash the color [#ff0000] ::extension stack
turn (10) to the north and (10) to the south ::extension stack
play sound (laughing v) for (2) secs :: extension stack
record viewers voice for (5) secs ::extension stack
play back recording ::extension stack
set dash speed to (15)
turn off dash ::extension stack

set dash speed to ((1)/(0))
drive ((1)/(0)) steps::extension stack

Geometry_Dash3 wrote:

Blocks:

when dash [turned on v]::hat pen
when dash [turned off v]::hat pen
when dash shaken::hat pen
broadcast [message1 v] to dot::pen
flash [color v] [purple v]::pen
drive (10) steps::pen
turn in direction [north v]::pen
turn in direction [south v]::pen
turn in direction [east v]::pen
turn in direction [west v]::pen
play sound [meow v] for [3] seconds::pen
play recording::pen
record voice for [5] secs::pen
turn off dash::pen
<camera [on v]?::pen>
<camera [off v]?::pen>
<dot touching [color v]?::pen>
<dash [on v]?::pen>
<dash [off v]?::pen>
say [] for [] seconds::pen
sense person::pen
go to [person v]::pen

frances2005 wrote:

Can't believe people still are liking my year old idea. Thanks for the support.

navigator.bluetooth

frances2005 wrote:

While looking on amazon, i saw a dash robot. it is used with an IPAD and you can control it to make sounds, change colors, drive etc. we already have a picoboard, the lego wedo 1.0, and the lego wedo 2.0. what if for scratch 3.0, projects could connect to the dash robot?
there would be blocks that would work like this:

when dash is turned on:: sensing hat
drive [10 v]  steps :: operators stack
flash the color [purple v] ::variables stack
turn [10 v] to the north and [10 v] to the south ::pen stack
play sound [laughing v] for [2 v] secs :: motion stack
record viewers voice for [5] secs ::sensing stack
play back recording ::operators stack
turn off dash ::looks cap

-frostyiceprincess- wrote:

aweisgerber17 wrote:

fun

?? Please be relevant or constructive when replying.

Pianostar4 wrote:

dhuls wrote:

Pianostar4 wrote:

While I like the idea, most people don’t have dots or dashes

You can say the exact same thing about all of the hardware extensions, so should we remove those too?

Well… true, but dots and dashes do seem like lesser used things. Plus, all of our hardware extensions are Lego, which are a bit more appealing to kids because you get to put them together, whereas the dots and dashes are ordered in a store, ready to use.

(days since 2000)

medians wrote:

I have no idea what a dash dot is