Yep, there’s an option for “Prioritization” in the settings (general settings, not for individual preset)
It is not, because whenever you alter the queue WK forgets all half complete items. If you find a way to do it I’d be happy to hear it. Previously the queue was managed in jStorage, so I wouldn’t say having it in the DOM is easier
When did all the private variables in the controllers become public? Was there discussion about it, or did someone simply notice?
I don’t know when exactly, but I noticed it when updating my type declarations for WaniKani after checking out the files changed in the updated import map.
Oh, I’m sorry, I misunderstood the point you were making. I’ll definitely take a look at the controllers next!
If there hasn’t been any specific mention of intent to make the private variables public, I’d be cautious about trying to use them yet. They could be temporarily public for WK’s debugging purposes, but I really have no idea. Maybe I’ll ask, though.
I made this change last week in order to give me a bit more headroom when it comes to browser support. I may go back to using private variables once we have done some more browser testing and working out which browsers and versions will be supported.
I would like to reiterate @rfindley’s words of warning. I will change JS function names (if I think there is a more appropriate name, if I refactor code, or if I go back to using private variables) as and when I see fit and without warning or notification. Please do heed @rfindley’s warning as I consider all implementation details private and don’t expect anyone using a script to be manipulating the JS prototypes. Obviously you are free to do what ever you want as it is your computer and your own environment, This is just my big warning sign / PSA… the implementation will change over time.
Any chance you can advise on how to change within JS/implement the feature to reset/alter the streak count? After some conflict with the new double check script, I was being awarded 2 “points” to my streak for every correct answer as opposed to 1.
It would be great if this could be avoided. Adapting scripts to refactored WK code is not a big problem in my opinion, but having some functionality completely inaccessible to scripts leads script authors to only two options: either discontinue the script, or try to overcome the hurdle with extremely brittle hacky solutions (the third option would be to reimplement the entire review functionality using only the public API, which can then be extended by new features – but I think this is beyond the scope of most script authors who just want to tweak a small aspect of WaniKani according to their preferences).
As an example, having the variables containing the quiz queue not private anymore allows scripts to change the queue order without resetting all half-answered subjects. One of my scripts allows users to push the current subject to the end of the queue (if they cannot remember the answer immediately and want to be asked again later). If pushing back the subject also results in the loss of information about all half-answered subjects, the script becomes unusable.
@Kumirei I noticed a bug in Queue Manipulator that caused settings like questionOrder
or completeSubjectsInOrder
to not be forwarded correctly if the wkQueue
was replaced by a newer version. I think if you update to the newest version, the back-to-back and question order problems should be fixed.
I should be able to find a resolution for that. Previously I was able to detect when you undid an answer, and I should be able to do that again
Thank you, I will update immediately
THANK YOU!! This script and its predecessors always was a necessity for me, you are a savior!
I have never used this script before, I started using it after the update. So far I love it, but I wanted to share something interesting that happened today.
I’ve got the settings as “Speed Demon”, you know to get the critical reviews first. It normally takes less than a second to reorder things, but sometimes I entirely forgot this and just start typing right away when a session starts. It normally means that I get caught by surprise when it reorders but today i was going to guru some radicals, so i forgot to let the script reorder for me and just typed a kanji lecture i was being asked, I got it right, but because of the settings it changed to the radicals right away and suddenly it was showing me that what I got right was a radical. I closed the session to confirm and indeed. I never typed the meaning of the radical, but somehow getting the kanji lecture right just before it changed counted as if I got the radical correct.
I’m not complaining, just think it’s funny
That’s… interesting. Must have something to do with when the WK events are fired. Not sure if there’s much we can do about that I am going to need to get more familiar with how reviews and lessons work now; I haven’t had a lot of time since they made the change
The streak counter should now work with Double-Check. It will only count an answer towards your streak once it’s finally submitted (meaning you won’t see it count down when you undo or count up before you undo)
You’re amazing, as always.
I can only think that in the same way I got that radical right I could get it wrong. But either way with how the review sessions work now if you simply don’t hit that second enter to “send” the answer and just exit and restart the session it doesn’t register it (or so I’ve noticed)
A bit tricky but it sorts out itself.
Have a nice one!
The streak counter should now work with Double-Check. It will only count an answer towards your streak once it’s finally submitted (meaning you won’t see it count down when you undo or count up before you undo)
I think I am still experiencing an issue.
I use the new Double Check script (3.0.14) and Reorder Omega (1.3.32) and if I get something wrong, the % goes down, and if I hit ESC to try again the % does not go back up when I hit ESC and instead stays at say, 75% instead of jumping back to 100%.
I have tried reordering the scripts in TamperMonkey just because it’s about all I know to try and it didn’t change anything.
I can live with it since I am so close to finally being done w/ WK but would also like more accurate % if I can have them.
Thanks!
Thanks for reporting that. I’ll (hopefully) take a look this weekend
Hey bro,
have you found any lead for the re-implementation of back-to-back?