Yeah, there was no way to detect resets via the original API, so it can only operate on the data Wanikani sends out. This will be fixed when I convert the site to APIv2.
In the meantime, I think it will start looking correct beginning with your next level, and you can click on the goofy one to exclude it from calculations.
Great, thx!
I reset my level down a couple yesterday and now the Stats site freezes on the opening page (the Loading API Data bar goes yellow, then nothing further happens). On the Console page it say
Uncaught TypeError: Cannot read property āpushā of undefined
at Object.
Could you help me get it working again, please? I use Chrome.
Select āForce Refreshā from the user menu on the site, then refresh.
If that doesnāt work, open the javascript consolev (press F12 and click on the Console tab), type the following command and press enter, then refresh the page and re-enter your api key.
localStorage.clear()That worked, thanks very much
I reset my level at the beginning of the year. But the website still says I started in August, and itās actually messing up my level duration, saying that I spent more time on the levels than I actually have. All I have to do is count the days to see that the level duration altogether ads up to much longer than a month. Plus it says the current level Iām on Iāve spent over 100 days on, and it keeps pushing back with each level I reach, I think even handing over some leftover ādaysā to the previous level if I had perhaps taken less time than what it āremembersā me on before reset.
The site uses Wanikaniās API version 1, which doesnāt support reset info.
I have plans to convert it to the new API version 2, but I have a long list of userscripts that also need updating. Iām currently finishing up a framework for APIv2 thatās going to take a lot of the work out of updating everything.
I donāt currently have a timeframe for when the changes will be done.
In the meantime, you can click on any incorrect levels (except the current level) to exclude them from the average calculations (the current level is automatically excluded from calculations). Theyāll still show up as long in the Level Duration graph, but the Progress and Projections section will be more accurate. Also, you can enter any hypothetical level-up speed in the Hypothetical box.
Thanks. I guess I found it weird because up until recently it seemed to conform to resets. I take it with the new method of resetting is the reason why it might not work anymore?
Iām not really sure if resets behave differently now under APIv1. I havenāt even looked at it, to be honest.
There was that change some months ago where they stopped deleting records when you reset so that synonyms and notes didnāt get deleted too. No idea if that could impact this though.
Yeah itās after that change that I noticed the website started acting different.
I came here researching the same thing!
I had it reset last week after making my account back in 2014.
Good luck with your new framework for APIv2 @rfindley!
Since you reset to level 2, it would have been better to just delete your account and recreate it.
That is an excellent idea which I did not have at the time. 
wellā¦ you can always just exclude level 2 from calculations.
hey @rfindley Iāve just got into the site from Google and Iām seeing @cooolcat stats. Donāt know if this has been reported already, but it seems like a bug to me? Googled āidigtech.com wanikaniā. This is the link on the Google search results wkstats
Geezā¦ First, Google refuses to retain the site in its index, and canāt tell me why. And now it has indexed a specific key!
Iāll see what I can do. Iāll re-check my parameter exclusions.
They have to be extracting that from peopleās bookmarks or something. Or maybe cooolcat has a link with their apikey posted somewhere, in which case this would be considered normal. Iāll see if the Google console can tell me where it found it.
Anyway, thanks for the heads-up!
Also, I apologize for any inconvenience, @cooolcat, assuming this isnāt from an intentionally-posted link somewhere.
Iāve re-applied the settings for Google to not crawl any URLs containing āapikeyā. Iām not sure how long it will take to remove existing ones from the index.
I have moved the stats site to its own domain.
Since Iāve started using LetsEncrypt for some of my domainsā SSL, itās a lot cheaper to own secure domains.
This also allows me to keep idigtech.comās site traffic separate from the stats. (idigtech is mostly dark-webā¦ i.e. non-indexed stuff that I use in my consulting business for individual clients and projects).
Mostly, though, it just makes it a lot easier to remember the stats siteās address 
