[Creating a new thread for this so that I don’t hijack @striker’s thread any more than I have done already.]
The purpose of this user script is to allow users to lock a set number of reviews so that they don’t appear in their review sessions. This is to allow people to reduce the review queue size down to something they can manage at any particular time.
Whether you’ve been whisked away back into real life or you’ve toked too much from the lesson pipe, it’s no fun at all coming back to a review queue that you just can’t manage!
As a user, all you specify is how many reviews are to be locked.
The method is actually very simple: The script maintains a list of all the active reviews you have and sorts them in order of when they entered your review queue. The script then locks the earliest reviews in the queue. You might think this is the wrong way around but I’ll try and make my case here.
Consider a review queue with 1000 items and you’ve been away from WK for some time. Oh dear.
If you’ve got the time and energy for, say, 100 reviews a day, then you’ve got a problem. Every time you get a review wrong, there’s only a 10% or so chance that it will appear when it’s next up for review. This amounts to a lot of wasted effort if you try and clear the queue this way because you won’t see an Apprentice item again until way after it actually appears again and SRS is unlikely to work well.
If the earliest 900 reviews are locked then, no matter how you perform, the remaining 100 reviews will always be for the same subjects (radicals / kanji / vocabulary) since they will always re-enter the review queue at later point compared to the locked reviews. This allows you to get comfortable with those subjects to the point where you’re scoring well before you choose to expand further into the locked reviews.
I’m almost on top of my queue with only 325 reviews locked.
Great, but what if real life rears its ugly head again and you’ve got less time again?
You simply lock more items until your review queue is manageable again. Let’s say we go down to 50 subjects this time. The set of active subjects is now a subset of the 100 subjects you were already working on just before and so you don’t have to start any of them from cold.
Once real life is less of a problem again, just go back to the previous setting and you’ll pick those from where you left off. If we go back to 100 subjects now then those will be the 50 most recent subjects and also the other 50 subjects you were working on when you had first set it to 100.
Hopefully you’ll agree with me that you only need to set the level to how much you can handle at any particular time and it will keep the wasted effort to the minimum.
Why not remember the actual list of locked subjects internally?
Using this sorting method, you only need to maintain a single number (the number of locked items) between devices if you frequently use multiple devices with WK. Also, if you regularly clear your browser data then you only need to supply the locked item count afterwards (and your API key) and everything is back to where it was.
What if I don’t like the script and uninstall it?
Nothing bad will happen. Your full review queue will appear again.
It’s bloody brilliant!
Early release - expect gremlins! Help by reporting said gremlins!
|0.0.2||Fixed incompatibility with the Similar Kanji script.|
|0.0.3||Fixed silly bug where it would lock items than requested.|
|0.0.4||Fix for items that have been removed from WaniKani.|
- Go to https://www.wanikani.com/review
- Enter your API V2 key
- Click “Set API key”
- Set the number of items you want to lock
- Click “Save options”
- Start your reviews
You shouldn’t have to click the “Reload cache” button.
When you want to change the number of items to lock, redo the above from step 3.
- Firefox - works for me™
- Chrome - works for me™
- Edge - works but there seems to be weird caching issues with WK API V2