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.