[Unsupported] Leech training script

I’m using the standard wanakana script for this. Do you not have to double press n when doing the normal reviews?

Thanks for the feedback @xyzbuster. My plans for the script are (and this is already probably too long a list for me):

  • Move the leech review preparation logic to my website - so that it can cache all of the user’s synonyms, and leech review queues work across browsers (e.g. home and work computers)
  • Add in a mnemonics review at the start
  • Repeat each item at least 3 times, and only remove if from the list of leeches if it’s passed all three times
  • Add in confusion elements too (and they have to all pass for the leech to get removed).

My early thoughts on the last one are mostly around adding in extra items around readings mistakes:

  • switch type subject <-> vocab for a different reading (内 nai <-> 内
  • switch similar kanji for a different reading (休 kyuu <-> 体 tai)
  • switch hiragana/kanji for a different reading of the kanji (天国 tengoku
    <-> zenkoku 全国, 正す tadasu <-> 正直 shyoujiki)
1 Like

For Wanikani, whenever n comes either before a letter it can’t possibly be connected to or at the end of a word, WaniKani automatically changes it to ん. For example

  1. The n in something like いちもんじ (一文字) automatically turns into ん whenever I hit the subsequent j for じ. This is because there exists no kana in which nj would be used, so it automatically understands it as a ん then a j.
  2. In something like せんうん (戦雲) (not a WaniKani word but was all I could come up with) if I don’t double tap the ん it becomes せぬん instead of せんうん.
  3. And, if the n comes at the end of a word like in さくせん (作戦), then it automatically converts the last n into ん.

As for your suggestions, I personally think it would be better if we were able to have an options to have a mnemonics review at the start. It would allow things to progress much more quickly in my opinion. Also, I’m not sure what you means by confusion elements, but if you are talking about tagging words so that they will only be removed whenever the user says they could, I think that would be a good idea. Still, I would like to be able to add words from WaniKani if I find them to be leaches and the system doesn’t catch it. While the system might be good and catch all my leaches, I feel giving the option would be more calming for the user.

1 Like

gimme gimme gimme :star_struck:

1 Like

I just noticed something I don’t think has been mentioned yet. When the leech trainer asks for a reading on the kanji, it accepts both the readings WaniKani wants and the ones WaniKani doesn’t want.

So, if I were to be asked for the reading of 投 and I typed in とう (the onyomi) instead of な (the kunyomi), it accepts it. Even though WaniKani itself would not accept とう as say it wants the other reading. Something worth noting.

1 Like

This is a great script and saves me a lot of time transferring all of my leeches to HouHou to review- which was the plan. However, would it be possible to incorporate both the readings and the meanings- instead of just what you are the worst on. The way I see it, more practice is always better :smiley:


Cool script.

1 Like

Thank you!! I was wanting something exactly like this and then here it is!

1 Like

Another item worth noting (Sorry that it seems like I’m piling on the criticism, I really do like this script a lot and simply want it to reach it’s full potential).
Whenever I signed out of WaniKani on my computer, the leach script number reset. Essentially, instead of saying I reviewed all my leeches, it reset to just saying I must review all my leaches. I think you were saying something about putting it on a separate site so that you could review on different platforms and I think that will fix it. Just something to keep in mind in case.

This is awesome.

It probably shouldn’t count a word as wrong if you press enter without typing anything?

Just wanted to say, a big thank you! That’s gonna be very useful/humbling…

I fixed a bunch of issues. Thanks your patience!

  • Prevent double enter.
  • Fix circle styling (and make it dark-theme-friendly).
  • Only accept the primary kanji reading.
  • Accept “n” as “ん”.

Think I’ve already gotten a good bit better on my leeches thanks to this script. TY.

1 Like

Nice script, I will definitely use it. Thanks a lot! However I have some questions.
When I provide wrong answer it goes back a couple of items and asks me again things I provieded correct answers for. Should it work like this?
Also: I provided か as an annswer for 下 kanji (https://www.wanikani.com/kanji/下). It’s a primary answer for this kanji. Correct answer was showed as げ (which is the second). Seems like a bug.

Are you sure about this? I kept putting in しnfor the kanji 振 (しん) and it kept rejecting it. Normally WaniKani changes the n at the end to ん, but the script didn’t do that for me. Could be user error, but the circle styling was fixed so I’m a bit confused.

Also, while the primary kanji reading is fixed, I think it might be better if it shook around instead of counting it wrong if you put in the wrong reading. Just, something to keep in mind for future reference. Thanks for the update!

1 Like

The script is not working for me. How do I get it to work?

Depending on browser that you’re using you’ll have to download some extension to allow scripts to run. In chrome I use “Tampermonkey”. Here you can check every browser: https://greasyfork.org/en. After you install this extension Install button (for scripts) should work.

… I have the extension installed. It’s not working …
Plenty of other extensions are working normally.

I have 4 leeches I can see using the WaniKani Tools website.

Leech Training script is installed but the circle shows no number, not even a zero and when clicked, nothing happens.

1 Like

You might want to try downloading “Dashboard Userscript: Leech, Apprentice, and Guru detail (aka SRS level progress)” which you can download here:

It’s made by the same guy and basically works off of that in some ways. Might need that script before you can work this one.

That, or maybe something is wrong with your particular browser? Firefox recently changed somethings which might cause a problem with previously downloaded scripts.

Sorry it’s not working for you Izana. Can you open up the Console window and look for a error displayed in red and share a screenshot of it? It’s accessible in Chrome via the menu View > Developer JavaScript Console.

Wrong reading bug (version 0.2.0):



…Also, it didn’t accept a user synonym for me just now on a different item, so that might have some issues left still as well.