Sure, I may have used a few (extension [ V] $verticalEllipsis-1$addInput-1) blocks, but it's worth the trade-off. (Spoiler alert: it's not a very unique block)
Let me know if the RGBA from [#911a44] :: reporter pen blocks gives out cursed results (script pic-ing sometimes corrupts blocks)
unfortunately you are right - @helicoptur (who is not active on the forums) made this a while ago:
Possible improvements:
1: instead of all the catch error shenanigans, just use
guh???
Making a radial gradient is difficult, even though that could be done as a trick by putting stroke-only circles on top of each other... But how would I know when to stop?
repeats do tend to be a bit slow and laggy depending on the size of the gradient, but I don't think map ({report [insert actions here]} input names: ((item)) ((index)) @delInput@addInput) over (numbers from (1) to (w)) would generally work better.um i dont think thats a word (anyway, what is the confusion about?)
you can probably use pi to calculate the approximate amount of circles to make
um thats not what I meant, but i will try to show you when I make the modified block
The confusion is that I didn't see another gradient-making block. 
P.S.: I remade a simple Python code snippet that I created a long time ago, was going to use my block in a project 
no i mean an another gradient block when i was posting
like when i was doing research to not dupli-post
Maybe because it was from this topic, which doesn't say anything about the gradient block in the title.
It's also from 2021, which snap has changed quite a lot since then. I think it's good that you created your own gradient block, since now you can take advantage of the new snap features that weren't available back then.
The only recent and new things I see in my code is script vars and extension [ V] <t> blocks, though I do kind of agree with the concept of your thinking.
i dont think thats new
those are a snap! 7.0 feature but just recently got renamed.
also, isnt it extension [ V] []@delInput@addInput not extension [ V] <t>?
Well, it's extension [ V] [] @delInput @verticalEllipsis @addInput
Mixed it up with the prim block.
ah ok. but remember the primitive block has the boolean before the text.
I took a shoot at making my own, and this is what I came up with,
The only problem I ran into was the 
maxing out at the stage size.
So I made a work around
I compared yours and mine, and they have similar outcomes.
try to guess who's is who's.
The left one has a invisible transparent border on the left and bottom side. So I declare the left one as yours because stretching can generate goofies like that. Mine doesn't use stretching.
EDIT: wait, both of em have the border. then i declare...
IT AS A TRICK QUESTION, BOTH
Quoting isn't helpful here. 
It only shows Costume(12) and Costume(11) respectively so it's a mystery for now.
imagine @origamicircuits remembering which costume is from which block 
