ThatExplosivePigeon wrote:

DualPikachu wrote:

And if anyone's wondering what they are

Some of those hidden blocks such as all at once do not work anymore, actually if you've used snap, there is a block called warp, which acts like all at once. The loops such as for and while do work still, but im not so sure about the counter block.

dhfbei8987 wrote:

haileylgbt wrote:

hidden blocks? what are they hiding from us?

Deeper explanation:
These so-called hidden blocks are available as long as you convert the project to a ZIP, then pasting/copying code in the JSON file. This is only accessible through GitHub. It's a complicated process to even obtain these.

dhfbei8987 wrote:

Naleksuh wrote:

There appears to be some confusion about what the suggestion is.

I believe what OP means by “hidden blocks” is a trick that allows you to turn any script invisible. It will still work and be called when the hat block is called, but you won't be able to see the script when you click see inside, or edit or delete it.

OP is suggesting making this no longer possible. I'm not really sure why the ability to do this was added, but it seems to never be used by projects created within the editor and only used by directly editing the project's JSON.

Edit: It appears I myself have been mistaken, as one of the pros here is “Gives a wider variety of visible blocks.”

Ok, you at least understand the concept. Hidden blocks, also known as “Hacked Blocks”, are only obtainable through Github, where Scratch's main developing sources is from.

These can simply be obtained by copying and pasting the source code for these blocks, converting the Sb3 to a ZIP, pasting the code to the JSON file, and reconverting everything back to an sb3 through PowerShell.

DualPikachu wrote:

There's also these other hidden blocks too:
(image hidden beacuse this hosting is now blacklisted)
Do you want these back too? I can't think of a use for them.

ThatExplosivePigeon wrote:

polish them

                           ::#ffffff 
                           ::Polska Górom 

ThatExplosivePigeon wrote:

im not so sure about the counter block.

scroll up (10)::motion

scroll right (10)::motion

align scene [bottom-left v]::motion
(x scroll::motion
(y scroll::motion
hide all sprites::looks

set stretch to (100)%::looks

change stretch by (10)::looks
when this sprite touches[mouse-pointer v]::events hat
([mouse-pointer v]::events
for each [i v] in (10){
                           }@loopArrow::control

while <>{
}@loopArrow::control
(counter::control
increment counter::control

clear counter::control

all at once{
}::control
<loud?::sensing
(user id::sensing
([ v]::#fff)//list index random
([ v]::#fffffe)//list index all
play drum (1) for (0.25) beats

set instrument to (1) 

set pen color to (50)

change pen color by (20)

change pen shade by (20)

set pen shade to (50)

([on v]::extension//micro:bit pin state
play note (60) for (0.25) seconds::wedo2.0//WeDo 2.0
(example block::extension
block with image @turnRight inline::extension

dhfbei8987 wrote:

Pros:
- Gives a wider variety of visible blocks.
- Helps those on mobile that can't use hidden blocks
- Makes no “easter eggs” for everyone to have to scout everywhere.

dhfbei8987 wrote:

Q&A:
Why?
Most younglings cannot code those JSON files. Plus, some don't even have/know how to operate the Powershell to convert everything to an SB3 and back. It would also be a long process to do all of that just for some hidden blocks.

dhfbei8987 wrote:

How would this benefit Scratchers?
Scratchers have access to a wider variety of blocks, as stated earlier, and in addition, no extra time would have to be taken just to obtain the hidden blocks.

set pen shade to ()

play sound [ v] until done :: hat

Mark12042016 wrote:

this a HIDDEN BLOCK

play sound [ v] until done :: hat

while <> {

} :: control

loud? :: sensing boolean