I’ve always disliked how items get burned – previously I’d just resurrect them instantly, but that eventually created a lot of churn. There are some existing userscripts that try to solve this problem, but they’re either unmaintained or don’t work very well (IMO).
Ideally, items would just stay in ‘enlightened’ forever and never get burned. I implemented this for Kaniwani (see Feature request: Add a setting to disable burning items · Issue #450 · Kaniwani/kw-backend · GitHub ) and looked into how close I could get to this with Wanikani’s API.
Long story short, I created a userscript for myself that keeps track of an item’s progression assuming that there was no burn level, and lets you resurrect and re-burn items that are due for a review.
For example, here’s a screenshot of the data for an individual card, which shows that this particular card would still be enlightened if it weren’t burned:
When it’s due for a review (around December 15), it’d be marked for resurrection, and when it’s reviewed, it’d be marked for re-burning.
The main view in the dashboard is this:
where you can see that a bunch of levels have items to resurrect. I’ve kept levels 15 and 16 untouched since I’m still working out the kinks in the code.
I’ve found that this keeps me refreshed on all my burned items, while not having such a huge load as when I resurrected every burned item instantly. It’s also much simpler to maintain than some other burned item review scripts I’ve seen, since I don’t have to build my own review UI.
Anyway, would anyone else be interested in using such a userscript? If so, I can polish it up a bit more and then release it publically.