Photoguy77 wrote:

I definetly support this! It'd make scratch so much nicer to use.

while <touching [sprite1 v]?> {
move (10) steps} :: control

JavierR100 wrote:

for those can't make the “while <>” block, here is:

while <touching [sprite1 v]?> {
move (10) steps}

bumpjammy wrote:

test

define hat block when flag clicked :: custom hat 

when flag clicked

Sheep_maker wrote:

For custom C-blocks:
I was thinking, instead of making custom C-blocks a completely different thing, we could add a “scripts” input, which makes a C-block in the custom block.

define custom C-block {script}
hide
script::custom-arg
show

custom C-block::cstart custom
wait (1) secs
end

The first script is the definition block. As you can see, the script argument can be used as a regular block and does nothing when used outside of the definition. The second script has the custom loop; the C-block is the script input, and the wait block is the argument. Running that script would hide, wait a second, then show.
With this, you can have multiple script inputs.

For custom hats:
Instead of hat blocks, we can have custom booleans and this block:

when <>::events hat //or "when <> is true" "if <> then do" etc. but I think you get what I mean

which acts the same way the workaround does in this project. That way in order to make a custom hat block, all you need is a custom boolean and the ‘when <>’ block:

when <custom boolean::custom>::events hat

when<boolean>becomes true::events hat

when [timer v] > ((timer)-<boolean>)

define while <boolean> (block ::stack)
repeat until <not <boolean>>
block ::custom-arg
end

while <something ::custom-arg> {
. . .} ::custom

Falcon1234567 wrote:

custom c defines should look like this:

define while <boolean> (block ::stack)
repeat until <not <boolean>>
block ::custom-arg
end

And… hey presto!

while <something ::custom-arg> {
. . .} ::custom

<something :: custom-arg>

<boolean :: custom-arg>

HOWING wrote:

dhdguysg wrote:

-snipped by The4thPixel-

Support? I'm not 100% sure.
Also, you could use this:

...

Instead of the grey block “Code below hat”.

dhdguysg wrote:

HOWING wrote:

dhdguysg wrote:

Hello again!
As you saw my last post about pen blocks maybe, I was getting good support, I hope those blocks will come to life, Anyways, Lets get to the subject
I have been looking threw obsolete blocks, Some dont have workarounds and they are c blocks or something,
Heres an example of a custom c block define and everything

Scratch C block definers+c block examples

define c block while <stuff :: custom-arg> :: custom hat
Scratch Code [repeat until <not <stuff :: custom-arg>>] //Experimental block for custom code. there's an easier way to make c blocks in the next explanation
//So it asks you to insert scratchblocks code that you'd do in a post inside the experimental block saying: scratch code

when gf clicked
while <mouse down?> :: cstart custom
say [HoodelHoe!]
end :: cend custom

That was pretty easy right??
Here's the easier way to set behavior the same way i did up there..

define c block while <stuff :: custom-arg> :: custom hat
repeat until <not <stuff :: custom-arg>> :: cstart control
end :: cend control
when gf clicked
while <mouse down?> :: cstart custom
say [Easier way!]
end :: cend custom

Well that was easy, Now to show you hat blocks, This is also easy
The red flag is a sprite ingame

define hat block When red flag clicked :: custom hat //This code is inside the red flag
if <<mouse down?> and <touching [mouse pointer v]?>>
Code below hat :: grey //This is not in the actual code, it will just run anything below if this statement is true..
end

When red flag clicked :: custom hat
say [I'm clicked!] for (2) secs

I hope you will support this! Ask me anything but before you ask look if i answered the question already!

Support? I'm not 100% sure.
Also, you could use this:

...

Instead of the grey block “Code below hat”.

Oh okay,
And yes you can be sure to support this thing, We'll need this for alot

GoldenPickaxe2 wrote:

-snip-

dhdguysg wrote:

Hello again!
As you saw my last post about pen blocks maybe, I was getting good support, I hope those blocks will come to life, Anyways, Lets get to the subject
I have been looking through a lot of the posts in this thread, Seeing all of the support, I decided to update this post (my english was so bad for it I can't even.)
So here it is!

Custom C blocks
(because custom hat blocks would probably be useless)
So C blocks are really useful, but a lot of people hate having to just re-create their conditional (c-block) functions as it makes code messier.
I've decided to create a post for this feature.
I hope ST reads this.
So I've been working out a way that it works.

define cblock etc
code here

Pretty simple? But how exactly do you create them?
Alright, so you create your new custom block, it has a define. and you put code inside the define, But how does it map out how the c-block will work?
Here's an example.

define repeat*2 (int32)
repeat (int32)
    // in here it'd assume ok this is a c block so we'll use this as part of the c block
end
repeat (int32)
   // same for here
end

So if you've seen what I'm going for (It uses c-blocks and other blocks that'd work with conditionals as the conditional) then you might want to go ahead and support!
Now, about my other thing (custom hats) This feature isn't as great, but it is basically just a custom event being pulled, So for example if I have a 3 click event on an object, I can create a custom hat for that.
It'd use event combining and I don't know how exactly it would look in scratchblocks, that's beyond the BB plugin's feature.
Thanks for supporting in advance!

cs405849 wrote:

dhdguysg wrote:

Hello again!
As you saw my last post about pen blocks maybe, I was getting good support, I hope those blocks will come to life, Anyways, Lets get to the subject
I have been looking through a lot of the posts in this thread, Seeing all of the support, I decided to update this post (my english was so bad for it I can't even.)
So here it is!

Custom C blocks
(because custom hat blocks would probably be useless)
So C blocks are really useful, but a lot of people hate having to just re-create their conditional (c-block) functions as it makes code messier.
I've decided to create a post for this feature.
I hope ST reads this.
So I've been working out a way that it works.

define cblock etc
code here

Pretty simple? But how exactly do you create them?
Alright, so you create your new custom block, it has a define. and you put code inside the define, But how does it map out how the c-block will work?
Here's an example.

define repeat*2 (int32)
repeat (int32)
    // in here it'd assume ok this is a c block so we'll use this as part of the c block
end
repeat (int32)
   // same for here
end

So if you've seen what I'm going for (It uses c-blocks and other blocks that'd work with conditionals as the conditional) then you might want to go ahead and support!
Now, about my other thing (custom hats) This feature isn't as great, but it is basically just a custom event being pulled, So for example if I have a 3 click event on an object, I can create a custom hat for that.
It'd use event combining and I don't know how exactly it would look in scratchblocks, that's beyond the BB plugin's feature.
Thanks for supporting in advance!

I tried that, and it didn't work!

define when<boolean ?>(script λ::custom stack)::hat
if<boolean::custom-arg>then
script::custom
define while<boolean λ>(script λ::stack)::stack
repeat until<not<boolean::custom-arg>>
script::custom-arg

when<(slider)\>[50]>::custom
while<(slider)\>[50]::operators>{
turn cw(15)degrees
}::custom

define C hat to predicate hat::boolean
C hat{
return<true::operators>::custom-arg cap
}::custom
return<false::operators>::custom-arg cap

define predicate hat to C hat(script::stack)
if<predicate hat::custom>::control
script::custom-arg
end

define custom hat :: custom hat

define custom cap :: custom cap

define custom c {script inside}

define <custom boolean only> :: custom boolean

define (custom number or text only) :: custom reporter

AdrianaMan8 wrote:

define custom c {script inside}

define <custom boolean only>

define (custom number or text only)

NitroCipher wrote:

AdrianaMan8 wrote:

define custom c {script inside}

define <custom boolean only>

define (custom number or text only)

Please do not necropost. This topic hasn't been active since January.

repeat (1) seconds {
move (10) steps} :: custom

define repeat (n) seconds (script :: stack)
...

when stop sign clicked :: hat :: custom

custom block::custom hat

custom block::custom cap

if <> then {} else if <> {} else {}::custom

custom block::custom hat
if <> then {} else if <> {} else {}::custom
custom block::custom cap