click the green flag use arrows to move through the tutorial, it is short I say "use at your own risk" because Scratch hacks tend to get patched over the years and projects using them then break. Also as pointed out by @papipupepappa using Scratch's editor on a hacked svg may overwrite your hack text and erase it
I had a couple of old projects with costumes that quit working and turned into a box with a question mark. After posting in the forums I found other people's projects with the same issue, some of which were old popular projects by Scratchers who don't log in anymore. So yeah, ruined forever. This lead to an offsite discussion with a Scratch developer which in turn lead to them discovering that a recent Scratch update had caused the problem. I use Inkscape for most of my svg editing and part of our discussion involved differences in header data written to .svg files by Scratch versus Inkscape. Over the years the main trick to making Inkscape svgs compatible with Scratch was to ungroup all objects (if necessary) and with all of them select perform Path / Object to Path. I'd accidentally set an svg's opacity lower than 100% in Inkscape, saved in, then opened it in Scratch and sure enough it maintained the transparency setting. So I started comparing svgs saved from Scratch to those from Inkscape using Wordpad and after trial and error figured out the transparency hack. I'm pretty sure there are more .svg parameters Scratch has us locked out of but recognizes and responds to besides this one.
