Had you tried to blacklist Spark Pixels it would end up being dismissed as an invalid post. Like I said, my viz does not break cubes because it does work fine for all users who flashed it throughout its many iterations (over a year and a half). I've put tenths of hours of testing before each public release (hundreds of hours throughout its lifetime).
I've noticed ever since your viz was blacklisted, you tried to imply many times that the problems caused by your code would somehow be related to Spark Pixels (as in "if it goes bad in my code it is also bad in Spark Pixels"), however that couldn't be farther apart from the truth.
I shall point out that your code was blacklisted because it displayed many bugs as reported by different users and confirmed by our lab and myself. So again, I stress that you properly test and debug your own viz before implying that your code was "unfairly blacklisted" or go on a crusade against someone's viz (which had been through hundreds of hours of testing before public release).
I guess you also forgot the main reason why I stripped some of the modes off my code. I shall remind you to re-read through this thread then.
The reason why Spark Pixels has become so popular among users is mainly because I try to be extra careful with the code I write; by putting as much testing and debugging time into it as I possibly can, I try to ensure every user out there will have a pleasant experience straight away. I am aware that by releasing my code publicly I'm embracing a huge responsibility. By being reckless and releasing code publicly before proper testing, is why you end up blacklisted.
If you want to use some or all of other people's code to create something of your own, I suggest you focus on displaying more concern in understanding the original code (what it does and why it does what it does).