Faster speed 
Radicals are easy so I do them as soon as I level up even though I have vocab
Ah!
So you mean you donāt always want to do vocab from the prior level first?
Wouldnāt you still be more interested in the number of prior level vocab though?
I still donāt understand why you prefer current level counts over prior level counts (in addition to total).
At this point, youāve already done all the unlocked level 32 kanji and radicals. You have 60 total items in your queue.
If I understand correctly, you want to finish those 30 L31 items before your reviews guru the L32 kanji required to level up.
I still donāt quite understand why the L32 count is more interesting to you at this point than the L31 count.
1 Like
Yes, thatās true. Itās a stylistic choice. Prior is a negative catch-all term (there could be a new addition to level 1 in there) whereas current level is a single level.
Iām usually on mobile which presents me with the current level numbers so Iām always doing the math. 
I see. Current is always one level, but prior might be multiple.
But, if I understand correctly, if we are presented with prior counts, weāre done (neither of us would bother doing the simple subtraction to come up with the current count).
If presented with current, we both need to do the math to come up with prior. Not hard, just seems silly since weāre both after prior.
(To completely kick this dead horse to the ground! Mea culpa.)
This thread is about this script. I requested adding prior-level counts, and hacked a version for my own use that satisfied my needs. You then asked about the status of the feature and whether it will be added.
@seanblue reasonably asked if there was sufficient demand: whether to leave it as is, or publish a version that let you choose whether to see total+current, total+prior, or just total.
You and I both want total+prior. Iām just pointing out that nobody is asking for total+current, and I fail to see a use-case for it.
(Sorry PM habits: any new features come with a cost. Itās important to understand exactly whatās requested and the use-case. Deciding not to implement is reasonable. Implementing the requested feature is reasonable. Implementing a slightly different feature is rarely reasonable.)
1 Like
I guess I donāt care which way OP picks any more. I hope to see it published but whether they pick prior, current, or both doesnāt matter to me.
1 Like
Think of yourself as one out of a thousand customers and me as the PM in this case. Usually a PM has some vision for a product and requests contrary to that vision often wonāt get implemented. Honestly, I think your request is a little odd and the chances of me releasing a version of the script with only the option to show prior level numbers in parentheses is precisely zero. I understand where youāre coming from, but to me current level is more relevant than prior, which is why Iād emphasize that (if anything) in the popup. Besides, at this point Iāve already implemented a version where itās configurable, so thereās really no point in debating which data should be shown since both options would be available. Now I have to decide whether releasing this version will cause more harm than good (e.g. by confusing people with this new information and it not being obvious that itās configurable). Iām not really sure how to determine that though since people rarely visit these script threads.
2 Likes
Personally, I think it would be very clear to show the current level, if thatās the format you choose. Every WK user knows what a current level item is!
You could always ask for second opinions on the 49th POLL thread to help decide. Perhaps some of them use this script already anyways!
2 Likes
Iāll let it die after this. I promise. 
Isnāt that last bit the debate, though?
Iām satisfied with my own version of the script, and would also use the proposed version configured to show prior. I wonāt use the existing version. Just one user, but itās feedback.
I was just pointing out that two of us at least care about finishing prior level items before current level and would like to know that count, whether displayed directly or by doing the mental math with the current level count.
Itās certainly your call whether or not to implement (as Iāve stated).
I pushed up the change to show current level counts in parentheses by default. This can be changed back to the old behavior or changed to show prior level counts in parentheses instead by changing the variable levelSetting to None or PriorLevels instead of the default value of CurrentLevel.
6 Likes
very nice addition to my collection of scripts, thank you!
(set to show prior levels in parentheses, btw) ^^
2 Likes
Have just installed the script with level setting options on prior levels too!
Iām a noob when it comes to scripts and have never edited a script since I started installing them very recently. This way my very first! 
Thank you for such a useful, straightforward script! Will definitely help me keep track of those vocab from prior levels that I still need to do.
2 Likes
It seems like the kana only vocab do not get counted in the vocabulary part of this script. Any plans to update the script to support them?
Iāll take a look. If itās easy Iāll update it.
I updated the script to show kana vocab on a separate line. Let me know if you still have any issues.
2 Likes
works for me ^^
1 Like
Hello, just noticed that on the /level/*, /radical(/*), /kanji(/*), and /vocabulary(/*) pages, the script does not seem to work (no popover for the Lessons button in the header). Checking the console shows an error saying that $ is not a function. window.jQuery is still defined on those pages so Iām not sure whatās causing it to bug out on those pages specifically. Not the biggest of deals since it still works on the one page I need it to, the dashboard, but I thought Iād bring it to attention.
1 Like
Youāre probably aware since I saw you post over in the Todayās Lessons & Lesson Picker thread, but the updates to the main page broke this. Looks like the selectors need to be updated as well as the popover template styling.
I believe div.todays-lessons__button will work for the dashboard item selector and .navigation .navigation-shortcuts div.lesson-and-review-count will work for the lesson menu item selector.
1 Like
Seems to work if the lessonMenuDashboardItemSelector is set to '.navigation .navigation-shortcuts .lesson-and-review-count__item' (needs to be the item as div.lesson-and-review-count is the div containing both the lesson count and review count). If lessonDashboardItemSelector is set to 'div.todays-lessons__button' as you suggest that also works.
But yeah the popover styling is broken. Probably whatever css Wanikani still had baked in for the popover class has been removed.
Edit: also, slightly annoyingly, because Wanikani is using flex and container queries, when you hover over the start button the popup gets inserted and messes up the styling of the advanced button.
1 Like
I guess it depends on where you want the popup inserted. I had picked the div over the anchor so that the popup is appended after (but outside of) the div.lesson-and-review-count div so the popup does not inherit the styling of it and instead is contained by the parent turbo-frame.
With my suggested '.navigation .navigation-shortcuts .lesson-and-review-count':
With your suggested '.navigation .navigation-shortcuts .lesson-and-review-count__item':
1 Like