My browser / operating system: Windows NT 10.0, Chrome 107.0.0.0, No Flash version detected
I have found even more OP things. In the wrong hands this could be harmful. I know many project glitches that can potentially be harmful.
• Using the hacked user ID block, setting a variable to this will prevent saving and remixing.
• The user ID block can instantly crash Scratch by having it be placed into a list that's currently showing.
• The user ID block can temporarily freeze all Scratch blocks, by switching costume to it.
• Naming a variable , or any other control character, will make all or sprite-specific blocks invisible.
• Naming a list does the same.
• Having all costume names in a sprite contain a control character will cause the block palette to cut off at “Looks.”
• Having all backdrop names contain a control character will break the palette for the whole project.
• If the name of all broadcasts contains a control character, the whole project will be irreversibly invisible, unless you remove the sprite. The backdrop is extra dangerous
• Any control character glitches will cause “Clean up Blocks” and “Delete 0 Blocks” to be greyed out.
These are the potentially dangerous glitches I found.

If you name a sound a control character, the palette gets cut off at sound.

If you try to name a block a control character (I've only heard of it with %) then click on a section of the block palette, all the blocks will render in the exact same spot until you click out of the sprite or backdrop scripts.

WindowsMeRules2000 wrote:

If you name a sound a control character, the palette gets cut off at sound.

I forgot to mention that one lol

I don't think you should tell people how to make/use dangerous exploits in public, try using contact us.
Also, where do I get this hacked user ID block?

fuiregbus wrote:

I don't think you should tell people how to make/use dangerous exploits in public, try using contact us.
Also, where do I get this hacked user ID block?

Backpack it from a hacked blocks project. Or hack the JSON. Also you're right. Though invisible code isn't a new issue.

Bump!