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. After, they need to be reconverted to be shown.

I would like these to be visible regardless. We need these blocks without having to do some more dirty work.

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.

Cons:
- ends the fun of finding hidden blocks.

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.

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.

100% support. There is a project here that has lots of these hidden blocks. All thats left is to add functionality to some and polish them. Some of the blocks like the for loop and while loop would be useful, while others, like the custom blocks with description and function, would help new scratchers easily know what the block does. Support.

I think I've seen a thread for this before?

Anyway, the majority of the hidden blocks do nothing and are only there for compatibility reasons, with a few oddballs which do nothing and aren't there for compatibility reasons (no idea why those ones exist). That's why I specified “the functional hidden blocks” in my similar suggestion. I prefer that one just because I have a feeling that they would've already added these blocks to the main palette if they actually wanted to.

There are known as hacked blocks, Semi-Support.

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.”

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.

hidden blocks? what are they hiding from us?

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.

haileylgbt wrote:

hidden blocks? what are they hiding from us?

They are known as hacked blocks, some of them are removed.

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.

No; the “hacked blocks” are, to my knowledge, officially known as “hidden blocks”. At the very least, that's what the Scratch Wiki calls them.

Bump

Where in the block pallet do you propose these blocks to go? If they are just mixed in with everything else, it will be really confusing to people when they try to use blocks that don't actually do anything.

Support, this enforces something in the Terms of Use:

4.2 The Scratch Team encourages everyone to foster creativity by freely sharing code, art, music, and other works.

But my question is, will all the false shadow properties just be set to true?

Basic88 wrote:

Support, this enforces something in the Terms of Use:

TOS wrote:

4.2 The Scratch Team encourages everyone to foster creativity by freely sharing code, art, music, and other works.

But my question is, will all the false shadow properties just be set to true?

I think so.

imfh wrote:

Where in the block pallet do you propose these blocks to go? If they are just mixed in with everything else, it will be really confusing to people when they try to use blocks that don't actually do anything.

The hidden blocks already have assigned categories. I'm assuming that the OP doesn't want the useless hidden blocks like ([sound name v]) to be added to the main palette.

the2000 wrote:

imfh wrote:

Where in the block pallet do you propose these blocks to go? If they are just mixed in with everything else, it will be really confusing to people when they try to use blocks that don't actually do anything.

The hidden blocks already have assigned categories. I'm assuming that the OP doesn't want the useless hidden blocks like ([sound name v]) to be added to the main palette.

You read my mind.

I've never done Json editing, and I don't intend to, so this would be nice.

the2000 wrote:

I think I've seen a thread for this before?

There are threads for adding the while block which you could use to discuss adding unused blocks in general, and there's a topic for adding a for loop, but I couldn't find a suggestion entirely based on “adding unused blocks”, despite me having a feeling there is.

the2000 wrote:

I'm assuming that the OP doesn't want the useless hidden blocks like ([sound name v]) to be added to the main palette.

It isn't completely useless (the “start sound” block actually has it as an input) but it wouldn't make sense to add it to the palette.

I support putting the hidden blocks in the palette as some are useful, and scratchers can know about them.