I’ll also say it scared the hell out of me when I first activated it as I was up late and everything was real quite. 
1 Like
Aikibujin said... I'll also say it scared the hell out of me when I first activated it as I was up late and everything was real quite. :PLol. Thx btw.
For anyone interested, here's the link: https://greasyfork.org/en/scripts/15703-wanikani-super-burn-happy-script
1 Like
Thanks Mempo (and Aikibujin, too). I’ll install it now.
Lol, just burned a ton of radicals. Non stop confetti. Very cool.
This is gonna scare the crap out of me when it finally goes off.
Edit: Not sure if anyone will see this, but there is a reference to ConfettiRibbon.bounds in the resize function. I keep getting undefined errors, so I have commented that line out.
OM!
TOTAL. MUST. HAVE. Downloading as soon as I am back to my main computer… which is like… 10 minutes. I haven’t burned anything yet. I think I still have a few months to go… you get your first burns around 6 months or something, right?
YAY! YAY! happy dance & thanks to Mempo for the link.
As always, thanks to the OP for creating this wicked script. :thumbs up:
Yeah I’m also getting (Linux chrome 51.0.2704.103 m):
VM119:166 Uncaught ReferenceError: ConfettiRibbon is not definedI haven’t look at the script, but might be the cause of all my confetti to cluster on the left hand side! (which isn’t very super happy)
Is there anyone who can look through the script and update it/ fix the formatting? I am getting the “one sad confetti in the top left corner”. I’m using Chrome browser. I don’t know enough to fix anything but I can see that the script has tagged many spots as needing some additional formatting.
I do enjoy using this script since it makes sure I know when I’ve burned something, I tend to not notice otherwise.
VikiO said...Is there anyone who can look through the script and update it/ fix the formatting? I am getting the "one sad confetti in the top left corner". I'm using Chrome browser. I don't know enough to fix anything but I can see that the script has tagged many spots as needing some additional formatting.Try this: https://www.idigtech.com/scripts/wksbh.js
I do enjoy using this script since it makes sure I know when I've burned something, I tend to not notice otherwise.
I did a quick test on my free WK test account, and it worked fine.
If it works for you, I'll post a permanent link on greasyfork.org.
I didn't do much.... just cleaned up the TamperMonkey warnings, and changed how the script starts up.
Thanks so much for spending time on this. I copied your script, pasted it in instead of the Burn script that was there and hit the save button (in tampermonkey, looks like a floppy disk) If that was all I needed to do, then unfortunately it didn’t fix my problem. See the pink rectangle on the far left upper corner under the home icon. That’s the confetti I got for remembering “money collection”
Am I running too many scripts?
VikiO said... Thanks so much for spending time on this. I copied your script, pasted it in instead of the Burn script that was there and hit the save button (in tampermonkey, looks like a floppy disk) If that was all I needed to do, then unfortunately it didn't fix my problem.As long as you refreshed the review page after updating the script, you did everything right.See the pink rectangle on the far left upper corner under the home icon. That's the confetti I got for remembering "money collection"
I'm still not able to replicate the issue. I'm on Chrome in Window10, and also test on Chome in Ubuntu Linux. What OS are you using?
However, now that I actually looked at how the code works, rather than just eliminating the TamperMonkey warnings, I did find one error.
So, I updated the code [link], and added a little bit of debug code to see what the browser thinks is going on.
After updating the script, reopen the review page, press F12 to open the developer tools, and click on the Console tab. It should tell you what version of the script is running (which should be 1.2.1), and some info about the window size that the code thinks it should be using. I don't know if the error I found was causing the issue (I kind of doubt it), but maybe the debug info will help narrow down what's going on.
Am I running too many scripts?All of those scripts should work fine together.
1 Like
Fantastic animation man, great stuff!
Do you mind if we integrate this on Kaniwani?
My burns there could do with a little love too.
1 Like
Subversity said... Fantastic animation man, great stuff!I don't think the OP/author is still around. His/her last post was Jan23,2015.
Do you mind if we integrate this on Kaniwani?
My burns there could do with a little love too.
When I burned flag all the confetti decided to form a clique and fluttered down in unison. ; - ; I’ll try to record it if it happens again, since I have a lot of burns to get through.
//Edit: Don’t mind the colors, I don’t get why Byzanz inverts them.
//Edit 2: I just installed Mempo’s script and it works perfectly. 
Yay, happy burn!
//Edit 3: The error is reproduced when I remove levels using Reorder Ultimate.
Oh man is anyone still using this? I’ve been asleep a long time but I just burnt my first item after restarting this year and I was not covered in confetti 
. I fixed up the script and it’s working for me now – but I did not see the corner confetti problem.
https://toemat.com/wanikani/wanikani.sbhs.user.js
Happy 2020 burns, friends!
3 Likes
I’m still using it! Just headed over here because nothing was happening after I burned an item, it was sad, I was sad :c
But good to see it’s already fixed :))
I’m using it too 
However it did not work today for me (Firefox 84.0 (64-bit), ubuntu 18.04) - I think I updated it in Tampermonkey (it says updated 26 hours ago). I clicked your link and reinstalled it, hopefully the next time I burn something I will be covered in confetti again
Me too! Worked perfectly prior to me updating Firefox yesterday. Was very sad not to have the confetti and horn. I have a burn coming up tomorrow so fingers crossed after the re-install! 
Thanks @toemat
I’m still sad, still no confetti or horns to congratulate me on a burn. Running Firefox 84.0.2 (64-bit) on Mac Air. Has to be something to do with the Firefox update. I’ve done a few WK log outs, browser restarts, machine restarts (for other things) and uninstall/reinstall the script a few times - all to no avail. I’m not coding literate at all, but sample screenshot of my install shows a few little spots marked with scary things 
Thanks to anyone who has time to look at it.
Thanks to OP and the others in the thread who have kept it alive.
Ah okay I’ve been using Greasemonkey on Firefox. It looks like there are some differences with Tampermonkey. I updated the script and it seems to work for both now. Give it a shot and let me know!
2 Likes