Remove "Hidden Blocks" and Make Them Visible to the Public.

lapisi

hidden blocks were never intended to remain in Scratch in the first place, they were hacked in, the ST does not plan on making updates to support something they never intended to happen in the first place

ideapad-320

dhfbei8987 wrote:
…
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.
…

you dont need powershell. Hove you heard of show file extensions in file explorer?

thunderbolt48942

Patricson wrote:

(#86)

change pen size by (#388ba8)
01010101011101010101010101010110110100110

Blockspamming is prohibited. If you do this again you will get blocked.

Jackson49_test

Bump

rareusers

Only the ones that work though.

JustWaitA_Sec

Support, but only for the blocks that work. I don't think it would be that difficult, they already have functions, it's not like they're adding new features, they're just making it easier for us use features already there. Maybe rename a few, to make their purpose more obvious.

7salad3salad

Most of the blocks dont even work

scratchcat348854

scroll up () ::motion
scroll right () ::motion
align scene [bottom left v] ::motion
(scroll x ::motion)
(scroll y ::motion)
hide all sprites ::looks
set stretch to () % ::looks
change stretch by () ::looks
when this sprite touches [mouse pointer v] ::events hat
([mouse pointer v] ::events)
for each [variable v] in (10){
} ::control
while <>{
} ::control
(counter ::control)
increment counter ::control
clear counter ::control
all at once{
} ::control
<loud? ::sensing>
(user id ::sensing)

scratchcat348854

([random position v] ::motion)
([mouse-pointer v] ::motion)
([backdrop1 v] ::looks)
([costume1 v] ::looks)
([Meow v] ::sound)
([message1 v] ::events)
([myself v] ::control)
([mouse-pointer v] ::sensing)
([space v] ::sensing)
([space v] ::sensing)
([edge v] ::sensing)

RED-001-alt

Do you mean we should have all the useful “hidden blocks” implemented into Scratch? Most of them are more complicated, and beginners wouldn't know how to use them.

scratchgodo

If I seen the OP correctly:

What if some made a

forever if  <>{
}:: cap :: control

block that is rejected and it got added to the editor because of this suggestion being added then it will make coding harder.

30ISChanneI

scratchgodo wrote:
If I seen the OP correctly:

What if some made a
forever if  <>{
}:: cap :: control
block that is rejected and it got added to the editor because of this suggestion being added then it will make coding harder.

REJECTED.

30ISChanneI

lapisi wrote:
hidden blocks were never intended to remain in Scratch in the first place, they were hacked in, the ST does not plan on making updates to support something they never intended to happen in the first place

No, they aren't. Or, atleast the for loop, while loop, all at once, when sprite touches, and other things.

lapisi

30ISChanneI wrote:
(#103)
lapisi wrote:
hidden blocks were never intended to remain in Scratch in the first place, they were hacked in, the ST does not plan on making updates to support something they never intended to happen in the first place
No, they aren't. Or, atleast the for loop, while loop, all at once, when sprite touches, and other things.

they aren't what?

Legend_SCR_Official

DualPikachu wrote:
(#40)
There's also these other hidden blocks too:

Do you want these back too? I can't think of a use for them.

A use for them could be

switch costume to [backdrop1]

which if it doesn't exist in the costumes tab, it would set the costume to where that is in the backdrop.

glomeromycota

I would support some, because others don't work anymore

thugatwoary

The

for each [i v] in (10){
...
} :: control

hidden block has no workaround.

set [i v] to (1)
repeat (10)
change [i v] by (1)
...

looks like a workaround, but these two scripts have different results:

for each [i v] in (10){
change [i v] by (1)
} :: control // i = 11

set [i v] to (1)
repeat (10)  // i = 21
change [i v] by (1)
change [i v] by (1)

Maximouse

thugatwoary wrote:
The
for each [i v] in (10){
...
} :: control
hidden block has no workaround.
set [i v] to (1)
repeat (10)
change [i v] by (1)
...
looks like a workaround, but these two scripts have different results:
for each [i v] in (10){
change [i v] by (1)
} :: control // i = 11

set [i v] to (1)
repeat (10)  // i = 21
change [i v] by (1)
change [i v] by (1)

The workaround does have the expected result in every practical use case.

Username229999

for each [variable v] in (10) {

}::control

you can replicate it using

set [i v] to [1]
repeat (10)
change [i v] by (1)
end

Last edited by Username229999 (Aug. 14, 2022 06:23:53)

OPagel

dhfbei8987 wrote:
Naleksuh wrote:
-snip-
…and reconverting everything back to an sb3 through PowerShell.

Reconverting the zip files to sb3 is not required.

Discuss Scratch