CST1229 wrote:

also, what blocks will this have?

while <> {

} :: control

(counter :: control)
increment counter :: control
clear counter :: control
<loud? :: sensing>
for each [foo v] in (10) {

} :: control
when this sprite touches (mouse-pointer v) :: hat events

(operating system :: sensing)
(browser :: sensing)
(user agent :: sensing)
(get data [] from JSON [] :: operators)
(convert [list v] to JSON :: list)
<is on [edge v]? :: sensing>
[whisper v] [] :: looks stack
[whisper v] [] for () secs :: looks
[sign v] of () :: operators // "reports 1 if it is positive, 0 if it is zero and -1 if it is negative" ~ BanMeOS
(is () a [positive v] ::operators)
(is () a [negative v] ::operators)
(is () a [decimal v] ::operators)
(is () a [string v] ::operators)
(is () a [zero v] ::operators)
(is () a [negative integer v] ::operators)
(is () a [integer v] ::operators)
(is () a [whole v] ::operators)
(is () a [natural v] ::operators)
(()^() :: operators)
bounce :: motion

(- () :: operators) // reverse the number (multiply by -1)
(get data from url [] :: extension)
(convert [CSV v] data [] to costume :: looks)
(convert [SVG/XML v] data [] to costume :: looks)
(convert [Base64 v] data [] to costume :: looks)
<() xor () :: operators>
(days since year () :: sensing)

kccuber wrote:

(user agent :: sensing)

kccuber wrote:

CST1229 wrote:

also, what blocks will this have?

Hmm. I want to get stage scrolling working.
Probably the scroll blocks, and I'll also add the removed ones that still exist like:

while <> {

} :: control

(counter :: control)
increment counter :: control
clear counter :: control
<loud? :: sensing>
for each [foo v] in (10) {

} :: control
when this sprite touches (mouse-pointer v) :: hat events

u7p wrote:

Can you clone the scratch-gui and scratch-vm on github?

if on [edge v], bounce::motion

dhuls wrote:

u7p wrote:

Can you clone the scratch-gui and scratch-vm on github?

they don't have a github account.

How about

if on [edge v], bounce::motion

Tadpole971 wrote:

ideas:

if on [edge v], bounce :: motion
(numbers from (1) to (10) :: operators //from snap but its in the operators category

Maximouse wrote:

kccuber wrote:

(user agent :: sensing)

I like most of the blocks, but I don't think this one is very useful – parsing it would be difficult.

OS and Version, Browser and Version

Windows NT 10.0, Firefox 92.0

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0

kccuber wrote:

Maximouse wrote:

kccuber wrote:

(user agent :: sensing)

I like most of the blocks, but I don't think this one is very useful – parsing it would be difficult.

oops. i feel like it should report something like this:

OS and Version, Browser and Version

So

Windows NT 10.0, Firefox 92.0

Much more readable than

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0

right? Even though it's not exactly a “user agent”

(join (operating system :: sensing) (join [, ] (browser :: sensing))

Naleksuh wrote:

There's also no guarantee a user agent would contain that information at all, you can set your user agent to be any string of text you want.

(join (join [Hello] [there]) [world])

(join [Hello] [There] [World] :: operators)

u7p wrote:

I've had this idea of making a scratch mod that has a bunch of advanced blocks like a for loop (like the in snap that stores the index as a script variable) and when you save the project to your computer it replaces the blocks with their workarounds (so a variable named “i” and a repeat until loop would be created for the for loop I mentioned earlier).

u7p wrote:

I've had this idea of making a scratch mod that has a bunch of advanced blocks like a for loop (like the in snap that stores the index as a script variable) and when you save the project to your computer it replaces the blocks with their workarounds (so a variable named “i” and a repeat until loop would be created for the for loop I mentioned earlier).

CST1229 wrote:

u7p wrote:

I've had this idea of making a scratch mod that has a bunch of advanced blocks like a for loop (like the in snap that stores the index as a script variable) and when you save the project to your computer it replaces the blocks with their workarounds (so a variable named “i” and a repeat until loop would be created for the for loop I mentioned earlier).

The for loop is actually already in vanilla Scratch, as a hacked block!

Tadpole971 wrote:

Windowscreator7 wrote:

Tadpole971 wrote:

dhuls wrote:

Ideas:

(web browser::sensing) // Reports as Chrome 93, Firefox 91, Safari 14, etc.
(operating system::sensing) // Reports as Windows 11, macOS 12, Android 12, iOS 15, etc.

has flash player? :: sensing boolean
flash player version :: sensing reporter

flash player has ended

i know

kccuber wrote:

BanMeOS wrote:

kccuber the name made it confusing. should of been if touching edge

Oh, so like this?

<if on edge? :: sensing>

or

<touching (edge v) ?>

(sorry for the messed up looking dropdown on this last one, 3.0 blocks use a rounded drop down)

point towards [random position v]

point towards x: () y: () ::motion

point towards [sprite v]

point towards [random sprite v]

point towards [random sprite v]

glide () secs to [sprite v] ::motion

glide () secs to [random sprite v] ::motion

go to [sprite v]

go to [random sprite v]

go to [center v]

point towards [center v]

glide () secs to [center v] ::motion

clear speech bubbles in [sprite v] ::looks

clear speech bubbles in [other sprites v] ::looks

clear speech bubbles in [all sprites v] ::looks

clear speech bubbles in [this sprite v] ::looks

[say v] () for () secs in [sprite v] ::looks

[say v] () for () secs in [all sprites v] ::looks

[say v] () for () secs in [other sprites v] ::looks

[say v] () for () secs in [this sprite v] ::looks

[previous v] costume ::looks

[random v] costume::looks

[next v] costume::looks

([ v] effect ::looks)

([pitch v] ::sound)

([volume v] ::sound)

([pan left/right v] ::sound)

when this sprite clicked () times in () seconds ::events hat

when <> is [true v] ::events hat

when <> is [false v] ::events hat

(number of clones ::control)
(counter ::control)

([foo v] ::variables)

([list v] ::list)

custom block ::#4C0099 hat

selfexplanatory wrote:

more ideas:
-snip-

when <> is [true v] ::events hat

when <> is [false v] ::events hat

if you have questions you can ask below

<not <>>

kccuber wrote:

selfexplanatory wrote:

more ideas:
-snip-

when <> is [true v] ::events hat

when <> is [false v] ::events hat

if you have questions you can ask below

the false one is the most useless block ever, aside from say nothing, because you can just use a

<not <>>

selfexplanatory wrote:

kccuber wrote:

selfexplanatory wrote:

more ideas:
-snip-

when <> is [true v] ::events hat

when <> is [false v] ::events hat

if you have questions you can ask below

the false one is the most useless block ever, aside from say nothing, because you can just use a

<not <>>

yes you can though i think just a dropdown would be a bit faster (yes its 2 blocks though still)
say nothing would require putting the say () block with no input in all of the sprites with the text bubbles

when <>::control hat
when <not <>>::control hat