This is a third-party script/app and is not created by the WaniKani team. By using this, you understand that it can stop working at any time or be discontinued indefinitely.
Hi everyone,
Lore
After dealing with a big pile of reviews, and trying to also do lessons in the meantime I’ve encountered a problem - How to properly estimate how many lessons and reviews I can handle given a set amount of reviews per day. At first I was winging it, latter I’ve created an app to track down reviews (first by adding review data by hand, later, by OCRing screenshots from webpage and mobile app). I’ve been doing reports on this forum for almost a year now The struggle
It was good at first until I realized that I’m doing to much lessons so the review pile stagnated and even grew. I stopped doing lessons, did less and less reviews - plie grew once more.
Then I updated my app to make some prediction on how many reviews should I be doing to keep up with the lessons without straining myself (let’s say to I want to do 200 reviews per day and don’t want my pile to grow even a bit)
This is what this script is for. It’s derived from my app to be an independent WaniKani script.
This script adds a forecast timeline panel to the WaniKani dashboard. features:
- A multi-day forecast of your future review queue based on your current assignments;
- Simulated daily review outcomes using configurable accuracy, lesson pace, and review limits;
- A chart showing due-before-review, due-after-review, leech, and threshold queue trends over time;
- Optional bar displays for incoming reviews by SRS stage, remaining queue by SRS stage, or reviews completed;
- Day-by-day detail popups with queue breakdowns, review counts, level progress, and overdue stage information;
- Level-up tracking based on current-level kanji progress, with forecast markers when a simulated level-up occurs;
- Summary information above the chart showing projected queue size, level, active leeches, and the assumptions currently in use.
Most parts of the display are user-configurable. The settings interface is accessible through the user menu.
The script relies on @rfindley’s Open Framework.
Couple of screenshots
