Discuss Scratch
- Discussion Forums
- » Bugs and Glitches
- » Blocks that target the sprite they're in incorrectly report the default option
- Whitepatchwastaken
-
Scratcher
100+ posts
Blocks that target the sprite they're in incorrectly report the default option
My browser / operating system: ChromeOS 14541.0.0, Chrome 138.0.0.0, No Flash version detected
There's a certain quirk I use often where you can get blocks like
I have an example project here: https://scratch.mit.edu/projects/1308134235/
There's a certain quirk I use often where you can get blocks like
go to (Sprite1 v)to target the sprite it's inside of by going to another sprite, setting it to target the sprite you want, and dragging/backpacking it into the main sprite. In the latest update, this functionality still works fine but it resets the dropdown visually to whatever the default is.
I have an example project here: https://scratch.mit.edu/projects/1308134235/
- redspacecat
-
Scratcher
1000+ posts
Blocks that target the sprite they're in incorrectly report the default option
My browser / operating system: Windows NT 10.0, Firefox 149.0, No Flash versions detected
Can replicate
Can replicate
- medians
-
Scratcher
1000+ posts
Blocks that target the sprite they're in incorrectly report the default option
Oh wait, I feel like this also kinda breaks projects too if it isn't just visual bc if the touching block targets itself, usually it will work with clones.
Edit: ok luckily it's just visual I think
Edit: ok luckily it's just visual I think
Last edited by medians (April 16, 2026 19:18:44)
- Whitepatchwastaken
-
Scratcher
100+ posts
Blocks that target the sprite they're in incorrectly report the default option
Oh wait, I feel like this also kinda breaks projects too if it isn't just visual bc if the touching block targets itself, usually it will work with clones.Little bit offtopic, but I felt so smart when I figured out they worked with clones. All the weird wacky workarounds I workshopped, gone in an instant!
Edit: ok luckily it's just visual I think
As far as I can tell, it's all visual. In my example project the self-targeting blocks still work fine.
- Turbo_yeeter
-
Scratcher
500+ posts
Blocks that target the sprite they're in incorrectly report the default option
My browser / operating system: ChromeOS 14541.0.0, Chrome 138.0.0.0, No Flash version detectedWhy yes, my browser / operating system is ChromeOS 14541.0.0, Chrome 146.0.0.0, No Flash version detected, why'd you ask?
There's a certain quirk I use often where you can get blocks likego to (Sprite1 v)to target the sprite it's inside of by going to another sprite, setting it to target the sprite you want, and dragging/backpacking it into the main sprite. In the latest update, this functionality still works fine but it resets the dropdown visually to whatever the default is.
I have an example project here: https://scratch.mit.edu/projects/1308134235/
I COMPLETELY misunderstood the assignment.
Anywho, can replicate. I also have a fun little tidbit/workaround if it bothers you like it bothers me.
You can also just slide a join block into the input and have it work just fine, like this:go to (join [Sprite1] []) // The join block outputs Sprite1 without any whitespace characters.My hypothesis is that this works because the dropdown to select sprites and messages can work with a string input, and the join block just so happens to output a string.
Yes this also means you can do this…broadcast (join [shalala] (num))…or this…broadcast (join [shalala] (num)) and wait…and attempt to broadcast events that do not exist. (does nothing as far as i have checked) (also means that you can broadcast events like shalala1, shalala2, e.t.c without dragging out a new broadcast block every time!)
Last edited by Turbo_yeeter (April 16, 2026 20:35:18)
- redspacecat
-
Scratcher
1000+ posts
Blocks that target the sprite they're in incorrectly report the default option
This has been fixed 

- Discussion Forums
- » Bugs and Glitches
-
» Blocks that target the sprite they're in incorrectly report the default option