Hey people, this updates the script at [Unsupported] Userscript: Dashboard Level Progress Detail (srs stages on progress bars) to use WK Open Framework instead of hitechbunny’s backend server. Long story short, hitechbunny had a server to make API calls to instead of the WK API directly, and that returned a JSON object, so my addition rebuilds the JSON object from the WKOF library and the WK API.
It also includes some misc updates I made a while ago:
Marker at 90% is better looking exists at all (wow I forgot that the original didn’t actually have a 90% marker in the pictures) - 90% marker will show the number and have the line lined up to the right spot
Adjustment to deciding which bars are shown above current level’s - a bar will be shown if the 90% guru mark hasn’t been hit or 100% of the items haven’t been at least learned
In this picture, my mouse is hovering over the bar to make the “Apprentice II (5/31)” popup.
Most of hitechbunny’s main frontend work is intact, since I don’t know how to make that stuff.
If there’s any other parts of the script I should change, or stuff I should add to this post or the greasyfork page, let me know. I don’t know too much, I just figured it out by googling.
Thank you so much. I wanted this script to be fixed so badly so I’m glad to see it being done well. I updated it and it seemed to work for me because of seeing the 90% marker, but it still shows the old information from when the servers stopped, being a level behind me. I don’t know if it’s broken or just not updated the displayed information but either way there’s a problem there. Hopefully you can fix it because as it is it’s basically not working for me.
None of the userscripts seem to work for me… instead I get an error log:
TypeError: global.wkof is undefined
I guess somehow the Framework is not working for me…
Is there something I can do about it?
Firefox & Greasemonkey is up to date.
Hey there. I don’t know for sure how to fix this because it worked instantly to overwrite the old cached data for me, but maybe it’s something with your Wanikani Open Framework installation? Installing Wanikani Open Framework Make sure WKOF is at the top of your userscripts list.
So uh, I don’t know if it’s working for me now but since my WaniKani has become a bit of a mess now that I’m in Uni I’ve noticed a small problem with how it’s laid out.
Not sure if it’s an easy fix or not to make the levels go in proper order or if it even should show 8 at all but I’m doubting it’s a big deal since most people won’t see it.
I’ve also realized it’s still not working because it still shows the app store, so I’m pretty sure that means it’s not updated the cache. I’d really appreciate some help because the only help I can find is just saying to have the open framework on top.
All of those should be showing because you haven’t Guru’d them to 90% yet, so that part is working right. The 8 being out of order is mysterious, and I thought I had tested the sorting across more than 2 levels but I can take another look. Edit: just realized level 9 is backwards too, should be radical, kanji, vocab but it’s backwards. I’ll definitely have to look into it somehow.
As for the app store, I didn’t touch that part yet even though I know I can/should remove it.
Oh, ok. Also thankfully comparing that screenshot to my current state I think the scripts working for me. Thanks for getting this script up and running again (especially with that nice 90% bar), I’ve needed this back. Let’s just hope you don’t have a hard time sorting out the order or the app store showing.
Oh well. Shame but not important. If I were to guess it’s that the whole thing is purple and the pinks are put on top of it, so slithers can appear when the pink boxes don’t line up right from something like rounding. But hey, what do I know. At least with the levels in order again it’s made a surprising difference in readability, which is good.
Hi thanks for this script it’s really nice to see which levels you have trouble with and what your progress is.
I’ve just reached level 60 and the script has stopped working, it throws an Empty string passed to getElementById() error. I think it’s just because there’s nothing to display anymore… I’ll deactivate it but wanted to tell you about this marginal bug.
At least with the levels in order again it’s made a surprising difference in readability, which is good.