@Sinyaven Confusion Guesser is one of my favorite scripts, but has been broken by the recent WaniKani update. Is there an update in the works?
I wanted to update it yesterday, but it took me until 2am to update Item Info Injector (which is used by several other scripts), so I postponed my work on ConfusionGuesser. I will try to release an update for ConfusionGuesser today, but I donāt know how long it will take.
Thanks so much. I donāt even mind if it takes a couple days or whatever, just wanted to make sure it was still something you keep up to date, because it is an amazing script that I have come to rely on a lot. Instead of just being told āno, thatās wrongā, I can find out that I was thinking of the wrong kanji, or that the reading I put is a valid one but not the right one for this word, or whatever and really helps correct gaps in my learning.
I really appreciate you writing this script. ![]()
As an new wanikani user, I just wanted to drop by and say an well ment thanks for working on the update!
Much appreciated.
@Corodon @danyramdas I have released version 1.16 of ConfusionGuesser. Itās not that well tested yet, but it should hopefully work again. The settings menu was provided by Open Framework which is not updated yet, so the settings menu is inaccessible for now until the release of the next Open Framework version.
Works great! Thanks for fixing it so quickly, ConfusionGuesser really enhances my WK experience.
One question though, thereās no gear icon at the top of the screen anymore, how do I check whether I have IDS mode enabled?
The gear icon is the settings menu that I was talking about ![]()
The settings should be unaffected, so if you already had it enabled it should still be. But if you really want to check, you can open the browser console during reviews, paste the following code:
wkof.settings.confusionguesser.useIds
and see if it returns true. If it does, then IDS mode is still enabled.
This is one of my favourite scripts, thanks so much for fixing it so quickly.
Canāt wait for my next reviews to come up now that this works again.
Hmmm, Iāve updated the script but somehow I canāt get it to work anymore ![]()
Can you go through the steps listed in this guide and report back with the details?
Okay, I just checked the list and tried it again with all other users scripts disabled (except for WaniKani Open Framework) - this resulted in no change while doing my reviews, nothing comes up when I get an answer incorrect.
My other scripts work well, but this one unfortunately does not. Iām on Safari, macOS Ventura 13.3. Hereās what I see in Tampermonkey:
And hereās what is running while doing my scripts:
Hereās what I see in the console though:
I tried switching off my VPN, but it made no difference either.
I use Double Check, and one bug I have encountered recently (which I donāt know if it was there before or after the Wanikani changes) is where it tells me what I could be confusing it with, despite me not going onto the next answer.
If this is not a bug, I apologize.
The script is working now, hurrah! ![]()
Iām glad to hear that it is working for you now! I would love to say that this was thanks to my valiant effort in fixing the bugs, but that would be a lie ā I did not have the time to look into the reported problems yet.
But I have to say that I like it when bugs are fixing themselves. ![]()
I think I need this explained a bit more. The guesses should appear when an answer was marked wrong. What do you mean with āgoing onto the next answerā? And if this is a conflict with Double Check, can you tell me your Double Check settings so that I can try to reproduce it?
Sorry, I wrote that while I was pretty tired. Let me try to explain this better.
The āpipelineā for answering a given question goes sort of like this (w/o any extensions):
Question ā Answer ā Next Question
With double check, it is:
Question ā Answer ā Decide Whether To Go Back To The Question (Step 1) ā Next Question
Since you said this, what I said isnāt a bug but a feature. I guess what Iām asking for now is more compatibility with double check by adding an additional setting to only show the guesses when you go onto the next question.
Apologies for the confusion, and I hope this clear things up!
I consider ConfusionGuesser mostly feature complete and donāt really intend to continue adding new features, unless I see the feature as a huge benefit. In this case, I donāt see why it would be useful to have the guesses appear after already proceeding to the next question. If the problem is that ConfusionGuesser sometimes gives away the answer whereas you would like to challenge yourself to find the right answer at least on the second try, then you can change the āWhen answer incorrectā setting to āMinimized ā show arrowā. That causes the guesses to be initially hidden, and you can look at them by clicking the arrow or pressing the hotkey.
my laptop broke last month and all of my userscripts had to be found from the api list and this makes dealing with really visually similiar kanji workable in my brain. So I wanted to stop by and say thanks for this script ![]()
This helped me to understand what your script is doing, thanks! I noticed that although a lot of times the ā+ā sign appears (top right), there are times that it doesnāt appear. What does the ā+ā mean and what happens if I were to click it?
I am worried that if I did click it something might change that I donāt want.
The + button just expands/collapses the list of guesses.
The script compiles a list of guesses and assigns a rating to them for how likely it is that you confused them with the question. The guesses with the highest rating are shown first, but sometimes the actual source of your confusion is not the top rated guess. Then it can be useful to expand the list and look through the other guesses.
Thanks! I didnāt want to click it and have something happen that I couldnāt undo and thank you so much for creating this script. It definitely helps to see where my confusion occurred.


