My browser / operating system: Windows NT 10.0, Chrome 75.0.3770.142, No Flash version detected

So today I was having some fun with custom blocks when I decided to see what will happen if I named a custom block “%”.
and it was crazy. all of the blocks were piled onto each other in one place! and when I tried “%b”, and clicked the Boolean input, I got a weird-looking block. So I looked on the scratch wiki for answers, and I got one on the “variables” page.

So Scratch Team…

how did you miss this glitch?
(P.S. I advise you to play around with this glitch, like naming a custom block “%b”, clicking the Boolean input, and clicking the text box thing.)

chrdagos wrote:

My browser / operating system: Windows NT 10.0, Chrome 75.0.3770.142, No Flash version detected

So today I was having some fun with custom blocks when I decided to see what will happen if I named a custom block “%”.
and it was crazy. all of the blocks were piled onto each other in one place! and when I tried “%b”, and clicked the Boolean input, I got a weird-looking block. So I looked on the scratch wiki for answers, and I got one on the “variables” page.

So Scratch Team…

how did you miss this glitch?
(P.S. I advise you to play around with this glitch, like naming a custom block “%b”, clicking the Boolean input, and clicking the text box thing.)

It's problematic because it's possible to use on a finished project for anti-remix purposes.

DipLeChip wrote:

chrdagos wrote:

My browser / operating system: Windows NT 10.0, Chrome 75.0.3770.142, No Flash version detected

So today I was having some fun with custom blocks when I decided to see what will happen if I named a custom block “%”.
and it was crazy. all of the blocks were piled onto each other in one place! and when I tried “%b”, and clicked the Boolean input, I got a weird-looking block. So I looked on the scratch wiki for answers, and I got one on the “variables” page.

So Scratch Team…

how did you miss this glitch?
(P.S. I advise you to play around with this glitch, like naming a custom block “%b”, clicking the Boolean input, and clicking the text box thing.)

It's problematic because it's possible to use on a finished project for anti-remix purposes.

using a glitch to keep people from remixing is so messed up.
So, If a member of the scratch team is reading this, PLEASE fix this bug!

bump.

b-b-b-bump

Here's a crazy one. Try %c and press boolean. The block is now empty. Exit out. WHAT JUST HAPPENED?

i have a fix for this glitch:
you can name the custom block ‘\%’
then the backslash will “escape” and you have a % in the custom block

EDIT: in scratch 2.0, when you do the same bug, this happens:

(i made this screenshot myself, but using ScratchX)

Nothing happens if you put it in the label.

PkmnQ wrote:

Nothing happens if you put it in the label.

that was in 2.0 (also scratchx now). so i think it has to do something with that

bump.

bump

Yikes, it does a lot of funky things with all the blocks in the project and then eventually causes a crash.

Dablux wrote:

Yikes, it does a lot of funky things with all the blocks in the project and then eventually causes a crash.

Crash?
What did you do?

Dablux wrote:

Yikes, it does a lot of funky things with all the blocks in the project and then eventually causes a crash.

Oof. but why hasn't a scratch team member taken notice of this glitch, because of what @DipLeChip said:

DipLeChip wrote:

It's problematic because it's possible to use on a finished project for anti-remix purposes.

and that is a big and bad thing. And I say:

save remixes!
Fix this glitch!
PLEASE!

Did you notice that Paddle2See edited your post?

PkmnQ wrote:

Dablux wrote:

Yikes, it does a lot of funky things with all the blocks in the project and then eventually causes a crash.

Crash?
What did you do?

It didn't cause a full site crash, but the area where you put all your blocks was replaced with a generic scratch error message. All I did was what was said above, and I think I tried to get one of the broken custom blocks into a standard ‘when flag clicked’ script.

I found the crash glitch that you were talking about.
Step 1: Create a normal block.
Step 2: Right click the define block, and click edit.
Step 3: Rename it to %c. This is where the magic happens.
Step 4: Press ok. Nothing happens, no surprise, we've seen that before, press cancel.
Step 5: Right click the define block again, and click edit again.

To freeze the editor,
Step 1: Create a normal block.
Step 2: Drag in the block.
Step 3: Right click either the define block or the custom block, then click edit.
Step 4: Rename to %c.
Step 5: Press ok, then cancel.
Step 6: Click on the blank block.

Some additional odd things:

• If the definition of a block contains itself, you need to rename the block multiple times to get all blocks glitchy. The define block has the lowest “priority”.
  
• If you do something that moves the block (like dragging a define block, dragging an if block that contains it, or placing blocks before it) it gets displaced.
  
• If you add a block onto the bottom of a glitched block (that includes putting a reporter/boolean in another slot), it gets cut in half.
  
• Blocks that got cut in half stay that way, and cannot be displaced.
  
• You cannot move glitched blocks using hat blocks, as trying to do so freezes the editor.
  
• If you put a reporter/boolean in a custom block, then glitch it, the boolean stays of course, but when you cut it in half, the boolean gets removed.
  

None of this makes sense.

DipLeChip wrote:

It's problematic because it's possible to use on a finished project for anti-remix purposes.

I don't think it can, but I don't know if half-blocks are savable, so…

Edit: They turn into normal blocks.