I’ve updated to 3.0.33, but the total time is still broken.
Thanks! This should be fixed now in v3.0.34
Thanks for the update! The single review display looks better now:
Yes everything works fine for me now, thanks for the updates!
I use the first review to determine when your session started, so unfortunately it’s not possible to time a single review (and the time for 2 reviews is actually just the time for the second review)
What’s up with the difference in the amount of burned items? Does it count removed and/or resurrected items?
For the reviews I look at all registered reviews, which I believe include both removed and resurrected items.
I also explicitly request removed items from the API for the lessons, too
Oooh, nice nice. Would it be possible to make the removed items appear in the list of items? (preferably grouped together at the bottom of the list or in their own distinct color)
Might be related - I see that neither 今日は nor 乱交 appear on wkstats. No idea whether that is intentional or caused by limitations of API stuff.
They don’t already?
I’ll think about it!
Not sure what rfindley does about hidden items on wkstats. I imagine he doesn’t include them to reduce confusion
They don’t At least not the two I mentioned. Can’t remember what other items there were.
It would be super nice if the hours minimap had its own separate color key that could be configured. Review counts in the hours minmap are usually lower than the daily counts, so it would be nice to be able to set up scales/colors to reflect this.
I think there is something wrong with error percentage with this script, I am sure to be making way more mistakes since lvl 22, I am at 24 now, but with this graph it shows otherwise
That’s the workload graph script. While it adds a button to the heat map it’s not one of my scripts. You’ll want to bring this up in its own thread
omg, for an instant, I lost all track of time when I noticed the row with 2022 Did not expect it to pop up. Was just the review forecast doing its work!
Thank you for this wonderful script! In additional to being one of my favorite scripts on its own, it’s fantastic for anyone like me that wants to learn more about how to write a user script!
I have a wild hair to write another script involving review stats, and everything I might want is already available in this script (and, of course, Wanikani Review Cache). I’m learning a ton just reading (and stealing) your code.
Silly example: I didn’t know how to avoid annoying lint warnings for globals like
wkof until I saw you explicitly pass
window.wkof in as a parameter to the outermost function called by the script manager. Obvious once I figured out what was going on, but I’d of had no idea without seeing your code.
There’s also the alternative of putting
/* global x */ at the start of a function to explicitly tell eslint that variable x is a global if you don’t want to use a parameter. Both prevent the warning from popping up though
OT, but @BIsTheAnswer totally wins the user profile wars. That I had to resort to Google translate was <chefs-kiss>
this script is essential for when we want to see the worst level we have been through.
That’s nice to hear considering that I learned to program by looking at other scripts. Full circle