hello
there

that os
    
end

SilverEye wrote:

You mean like custom blocks for C blocks, hat blocks, reporters, etc.? Support.

-Cherri- wrote:

I don't get what you're saying, could you be a bit clearer? ^^;;
augh 60 sec rule whyy

custom c block :: cstart custom
:: cend
custom hat block :: hat custom

custom cap block :: cap custom

1. Custom C blocks: Sorry but this block would need an extra block to run the content inside
   
2. Custom Hat blocks: What would they listen to? How would you choose what do they listen to? Would they work like “if”?
   
3. Custom Cap blocks: These are unnecessary. What the cap does is stop any extra blocks after it, often used when no blocks after it will ever run and to make new Scratchers not ask why aren't the blocks after it executing. Not much new Scratchers use custom blocks anyways.
   

this :: custom cstart

^^^ ::custom cend

this :: custom hat
and this :: custom cap

gamebeater187 wrote:

means

this :: custom cstart

^^^ ::custom cend

this :: custom hat
and this :: custom cap

when @stop clicked :: custom hat

define (custom boolean) //this is for a boolean
report <> ::custom //both should be connected with no way of disconnecting
//Example:
define (high score detected) /
report <(your score) > (high score)> ::custom 

if (high score detected ::custom) then
...
end

I wrote:

Support for custom reporters and booleans, and block inputs for stack blocks to make custom C-blocks, which I explained here. Also support for “return” blocks for the reporters and booleans.

Dy155 wrote:

Why not change the stack blocks to C blocks, Hat blocks, or Cap blocks? I don't like putting in regular stack blocks!

hello::custom hat
there::custom cstart

that os::custom cap
    
end