Glad I just saw this. Know its hard work maintaining the scripts. Hope you add back shuffle incorrect because I loved how that feature worked.
Of course, as a programmer, I understand that this seems like a pain in the butt now with the changes made to the API and I am way to lazy myself to try to contribute to the github and spend hours trying to figure out a clean way to reimplement it. Also, I suck at Javascript. I’m a C++ person mainly.
The issue isn’t workload, but that the devs made private properties temporarily public to help debugging, and I don’t want to rely on those properties staying public. As far as I am aware there is no way to implement the shuffle incorrect mode without relying on those variables (or reimplementing large parts of the front end)
Understood. That sucks. Hopefully based on dev feedback, the API can be improved. Honestly, I am sadden by some of the changes going on. But, I am sure the kinks will be worked out over time.
I found an issue while doing some testing with Double-Check and Reorder Omega, and then disabled Double-Check and the problem remained.
Settings:
Actions:
[1] Filter: ItemType==Vocabulary
Back To Back Behavior: Repeat Until Correct
Prioritize: Reading
Refresh the screen until WK brings up a Radical or Kanji first. Instead of Reorder successfully filtering out all but the Vocab, it just changes the background color to Purple (vocab) and leaves the item (radical or kanji) the same.
Example:
As you can see, it has a purple background, but it’s still asking for “Radical Name”, and indeed the radical name is the answer that it expects and accepts.
After further troubleshooting, I found that it happens regardless of “Back To Back Behavior” setting, and actually seems tied to “Prioritize: Reading”. (And probably the vocab-only filter)
I haven’t dug any further into it yet. I’ll follow up if I find anything else.
Edit: Managed to make it work how I want it to by just removing ‘voc’ from the order. I guess it was putting all the kana vocab items at the very end and since I haven’t got my reviews down to 0 for a few days I was never getting to them
Kana vocab are treated as normal vocab in Omega. However, removing “voc” should still place vocab after radicals and kanji, is that not what you are experiencing?
With ‘voc’ in the order, it was separating regular vocab from kana vocab and putting all the kana vocab at the very end. I guessed it was working similar to the ‘filter’ action where it differentiates between the two types of vocab.
Somehow it currently breaks LesssonQuiz and Review on init, so refresh with delay. Perhaps add a loading screen, instead of letting it refresh visibly?
It becomes unbearable, so I have to add Review (https://www.wanikani.com/subjects/review*) to user exclude for now. I will perhaps test with Lesson later, but it’s SPA, so both https://www.wanikani.com/subjects/*/lesson* and https://www.wanikani.com/subjects/lesson/quiz*. I am using native reorder for both Review and Lesson.
I want to keep Omega for customizable Extra Study, however.
Ooh, this means I can filter out Kana Vocabs? Thank you so much for this!
Edit: A thought came to my mind. I’m still new with using this Userscript and I wonder if filtering Kana Vocabs this way would still make me able to Level Up? Especially after WK will continue adding more Kana Vocabs over time.
For Lesson, after the first native LessonQuiz is loaded, it goes back the the first Lesson batch for the second time. After than second time, it stops repeating itself.
For Review, after it is loaded, the first item changes, sometimes with my half-typing state and input box is emptied. So sometimes resulting in empty green.
During a session there should be a cog in the top left which will take you to script settings. Elsewhere you can access the settings through the regular WK menu under “Settings”