[Userscript] Burn Manager (Review / Resurrect / Retire)


#21
riskyshift said...So, this script kind of catastrophically screwed my progress.
[...]
Wow, that's terrible!  And that's definitely not something that should be possible.  When I developed this script, I tested it extensively, and tested it again just a few minutes ago.  I can't reproduce what you described.  I even manually sent the request to the WK server to resurrect and retire several items that I hadn't burned (on my test account), and WK ignored it.

Can you tell me exactly what steps you took when you used the Burn Manager?  e.g. what you entered into the Levels box, which item types were checked, whether you used the Preview button or just the Execute button, etc.
Also, if you'd like me to take a look at your data, go to the stats site (https://www.idigtech.com/wanikani) and enter your API key.

I see your start date was May 2014.  Did you have your account reset at some point?
The reason I ask:  The script uses two criteria to determine if each item is currently burned or was in the past:
If the API says the item's srs level is 'burned', it is currently burned.
If the API says the item's srs level is NOT 'burned', but the burned_date is non-zero, then is was burned sometime in the past.
Any other combination shouldn't even be touched by this script.

#22

Not seeing this pop up ? Firefox, mac, wondering what I’m doing wrong. Thanks!


#23
Yabba said... Not seeing this pop up ? Firefox, mac, wondering what I'm doing wrong. Thanks!
 Do you have TamperMonkey or GreaseMonkey installed?   If not, install that, then reinstall the script.

Once it's set up properly, you can open it from WaniKani's user menu (as shown in the top post)

#24
rfindley said...
Yabba said... Not seeing this pop up ? Firefox, mac, wondering what I'm doing wrong. Thanks!
 Do you have TamperMonkey or GreaseMonkey installed?   If not, install that, then reinstall the script.

Once it's set up properly, you can open it from WaniKani's user menu (as shown in the top post)
 Woops. guess I should learn how to read. Yes it's in the user menu. Thank you.

#25

I don’t use the mnemonics, so the radicals are just wasting space in my brain. Is this the best way to get rid of them? What are the other options?


#26
brandonhartfiel said... I don't use the mnemonics, so the radicals are just wasting space in my brain. Is this the best way to get rid of them? What are the other options?
 This won't get rid of them.  There's really no option for that, though you could add a dummy synonym to all the radicals.

#27

Thank you rfindley! I needed to refresh a lot of levels as I’m back after a long time… This is just what I needed!


#28

Neat. This way you can re-do WK without resetting your level.


#29

I love the idea of this userscript. I am wondering, however, if there is a way to reset burned items just back to Enlightened, rather than all the way to Apprentice. I want to see the burned items again in my reviews, but if I still remember them easily, I don’t really want them clogging up my reviews again - I’d just like them to be burned once more. Can I edit the Userscript to do this, and if so, how?


#30

The script just uses WK’s resurrect/retire links, which can only set it to Apprentice.

You could use the [Quiz script] to quiz your burn items without resurrecting them, then keep track of which ones need resurrecting and use Burn Manager to resurrect in bulk.


#31

Ah, I gotcha. Thanks, the quiz script looks pretty great; just had a go with it and it looks like it’ll work just fine. Thanks!


#32

I’ve been wishing for something like that for a while, thank you! :+1:

At what frequency are the resurrected burnt items reviewed though?


#33

They drop down to Apprentice 1, and follow the normal SRS schedule. So, 4hrs for the first interval, 8hrs for the next, etc.


#34

Here’s a bug report (or a false alarm)

1

This is before. I had resurrected the few apprentice items a few days ago. At this point I was about to unburn all the other Kanji from level 6.

2

Here’s bug #1 (still before unburning the rest). the Kanji count as shown on the dashboard mismatches the those from the stats site. (I have six apprentice items on that screenshot alone)

3
Now after unburning the rest, the items that were previously apprentice 4 jumped to guru 1. (I had expected them to go down to appr 1, because it happened to me and another user before)

However: If the “previously apprentive 4 items” were actually already guru’d, just not yet updated on the stats site, this is a false alarm. I’m reporting anyway because I’ve experianced these issues before: Items that werent burned going down to apprentice and apprentice counts on the dashboard being wrong even after force refreshing. I will continue to try these bugs and report them if I get results.


#35

These are both most likely a cache issue on the stats site, which will be fixed when I migrate the stats site to APIv2. But if this is something that persists after a Force Refresh, it would have to be a WK issue.

Were they previously burned at some point? Even if there’s a bug in the Burn Manager that makes it try to unburn the wrong things, the WK server rejects unburn requests for non-burned items… unless Wanikani AND the script are broken. I’m not doubting what you saw, but I’m at a loss to explain it unless those items were previously burned at some point, in which case I can try to replicate it on my test account.

If you mean that the dashboard counts don’t match the stats site, and the Force Refresh was done on the stats site, then WK would have to be reporting the wrong data. Or do you mean ‘force refresh’ == ‘clear cache on WK’?


#36

In my case yes.
I think it was level 4 or 5. I first unburned about half of the Kanji, and then 1 or 2 days later all the other Kanji from that level. I didn’t bother unchecking the Kanji that I had already unburned, which caused those to become immediately available for review as well.

I did the CTRL + F5 - refresh on the WaniKani dashboard (and I think that’s called a force refresh)


#37

^^^ Okay, I’ll run a test on unburning already-unburned stuff.


#38

Has the script stopped working on firefox 55/56? I was able to unburn some things about a week ago. But when I tried to today, it gets stuck on executing.


#39

Nothing has changed on the script recently, but GreaseMonkey has been having problems with recent Firefox versions… though I thought the problems started on FF57. I’m not a FF user, so I’m not certain where the version cutoff was.


#40

The big change happened with v57. I don’t know why it was working one day and not the next when I haven’t changed anything. And I’m not using v57. Guess I’ll try another browser.