I reset to lvl 2 yesterday morning - the stats page was still accessible, showing I’d been on lvl 2 for 300 days, which I expected, but by evening the page wouldn’t load properly (“loading API data” with the bar showing as full without progressing). Any ideas? I have also looked at the new page, but there’s not as much info there yet.
Edit: I’ve just seen that the progress section of the new page is split into 3 instead of all the scrolling, so most of the info is there, cheers!
Not sure what’s up with the current version. Definitely not working on your API key.
I even generated a new key to see if there was a problem with the ‘old’ key after the reset (I really have NO IDEA how these things all work! 
) but to no avail…
Hi @ rfindley,
I am wiling to lend my APIv2 keys. Just let me know! Thanks
P.S. Just noticed that there is an “error 404” msg on the page after I changed my API key (it was the first time since I changed the key that I’d tried to access the page from this device).
I poked around on my unloading WaniKani Statistics page and came up with this:
Can you tell what has gone wrong and how I / you / the WaniKani team can fix it, please?
I just noticed the ‘Open Config’ at the top of the Wanikani Items page on your new site - what a thing of beauty! Cheers!
Hi
When looking at the JLPT chart section of the Stats webite, The kanji for 喋 apears to be missing?
Why is this?
Thanks
喋 isn’t one of Wanikani’s kanji, and there are no official JLPT lists.
The JLPT list I’m using is one of the newest, even though it’s still about 6 or 7 years old. The other most common JLPT list has more kanji on it, but it was derived from the pre-2010 JLPT tests, before N5 was added.
Thanks 
I just came here to report the same issue. I debugged it very briefly and I think it is because we reset our level. The “item.level” at this point is most likely a level that you had reached before your reset (it was in my case at least).
Manually clearing the local storage will fix this. I called user.clear_data() in the browser console and it worked. You just have to re-enter your API key again afterwards.
Interestingly, I fired up my new tablet last night and was able to open it on that, but still can’t on my old tablet nor my PC (both tablets are Android).
My understanding of this is sadly limited, but I’ll give it a go, cheers!
Sorry about that. It is a cache issue, and normally something I’d try to fix on my side… but since the current version of the site will be going away soon, I’m staying focused on getting the new version done.
I tried typing this in and it didn’t work, but then I noticed there was a ‘Clear Cache’ button nearby, clicked on it, and Hey Presto! I have access to the old stats site again - thank you so much. 
@rfindley - I really appreciate the work you are doing on the new site (especially the personalisation with that funky configurations bit!), so no worries at all about not spending time on the old one. 
I was just missing the projections aspect of the old one is all.
I love the site! I have two quick questions regarding leveling up stats:
‘Estimated’ uses your average level length… i.e. the average of all levels that aren’t excluded by clicking on them in the Level Duration graph.
‘Hypothetical’ uses the level length that you enter into the “Enter a hypothetical level-up speed” box.
So, each forecasted levelup adds the average or hypothetical level length to the prior level date. But, obviously, it won’t allow the resulting date to be sooner than the fastest you can possibly level up… like if you’ve been on your current level longer than average already.
Thanks for the quick reply!
Hi Rfindley, I’m an academic (economics) and I’m interested in finding a better estimate than the average for the progress. If you are also interested in this please feel free to reach me (my username here at email.unc.edu).
Best!
What did you have in mind?
The basic idea is that not all levels were created equal: higher levels might be harder; levels with more kanji might be harder; etc… If one has access to aggregate data then it would be possible to estimate the level completion time (level “difficulty”) and so the individual completion estimate would depend on the individual past performance (as it is now) but also on the level estimated “difficulty”.
