It does seem to be somewhat related to double check, though. Just tested by resurrecting an old item, and only when that script is active the problem appears.
while at the same time you can know for sure if you WERE correct
That’s true too
It may be a update of WK that affects the script, after all, though.
Edit: Removed last sentence, it was incorrect after all. There is a different issue with the old script.
I just had this same thing happening to me. I was confused as to why I didn’t get the wrong answer screen either!
The issue with DoubleCheck appears to be caused by WaniKani enabling an experimental feature called the shared answer checker without any prior warning or explanation of what it is. It’s kind of frustrating that in the past few days, they have made so many changes to the site that have broken things (for both script users and people who don’t use them) without testing them on the preview site first and giving script authors a chance to update their scripts. I’ll try to see if I can find a fix.
Edit: A fix for the issue of stuff being marked right when it should be is here.
Can confirm happened with double check, wrong answers insta accepted as right. (reading only). Turned it off and session was just fine. Tried off and on again and got this bug (?) with URL, never seen that before! (pic)
Yo, would explain why everything was running fine in the morning for me then. The double-check script hasn’t been updated since yesterday.
Things are running fine with the double-check script off (at least on my side, but at that point I didn’t have many items to check against), that’s the only workaround for now I guess.
I thought I was going crazy or my keyboard was hitting enter twice for some reason. Glad I’m not the only one!
Okay tested a little bit more (yes failed gurus for the sake of people) and the issue IS with double check. Can’t reproduce insta accept bug without it.
A fix for the issue of stuff being marked right when it should be is here.
Was the double-check script causing the n problem too? Or is that still an issue?
The n being correct at the end of a word is intended behavior, per here.
Speed demon tip: You don’t have to type the double n to make ん at the end of a word when answering the reading of a kanji or vocabulary word. We’ll auto-convert the final n to ん for you. BUT it’s much better if you get used to typing it correctly right from the start. Your Japanese teacher or boss won’t be as lenient as us.
Personally I am very glad for it, as getting used to typing the double n took me a while, and it’s easy to miss a double key tap at the end and not visually check it, when going fast lol.
I can reproduce the n problem even with all scripts disabled, so it is still an issue.
Thanks for checking on this. We’ll look into this bug!
The script has been officially updated to a working version now!
Go here to update: [Userscript]: Double-Check (Version 2.x)
Thank you so much! I’m glad we got this figured out.
Me too, I can’t live without it!
Upon changing the title (Added Solved) I found I hadn’t even written items right! (iems =P ) just goes to show I NEED this script XD
I also like Auto Commit. If it doesn’t go through I can look it over, was that what I meant to type? (note: it, like so many others, can be abused. Don’t change to “the other reading then” )
I’m brand new to scripting. I installed some; mostly there’s one so I can filter my lesson list and learn the radicals and some of the kanji first (very useful), but also I typo all the time, and I hate getting punished for that, so this Double Check is invaluable. I have to admit I sometimes use it even when I clearly got the answer wrong, but I think I still learn from my mistakes even if they’re not counted as mistakes.