We have something in common, your “Locked” panel doesn’t show anything. I’m guessing it’s because I reset from 60 to 1?
I don’t know. I assumed it’s because I greedily installed a bunch of scripts without the slightest idea about how much they’d clash with each other! I can’t fix it myself because I’m clueless (takes me about a decade to write 10 lines of code in R) but if you find a way/cause, please do share.
That’s what I have added:

I have never reset, I only just started WK.
Ah, I think I solved it. You have to install Kumi’s script “Locked count” for that panel to work.
It didn’t display immediately for me either. Try to play with the Dashboard Cockpit settings a little bit. Also reload the page several times. That did it for me.
Might I suggest
Burn Reviews by @Samuel-H and maintained by jonnydark: Adds a widget to the dashboard that quizzes you on random burned items.
It doesn’t really fit with its current UI, but if you modified it and added it in I would be so grateful.
This is the most beautiful UI work I’ve seen in a long time btw 
Might try re-starting… no amount of tweaking and refreshing had had any effect on that grey box.
Never bothered me after the initial

moment but now I feel I have to have it!
Looks like there was ample coding in the script to find those numbers for different cases already…
But as I said, this is just as mysterious as unlocked kanji to me!
Just had the problem. Switching the highlighted option to none and then back fixed it.


It’s the first thing I tried and yet, trying it again after seeing your message worked:

Must have done stuff in between… no idea!
So now I can get depressed by the massive number in there every single time I look at this page! I look at this page a lot…
Would it be possible to draw the leeches in circles instead of rectangles? Maybe using border-radius?
It didn’t display immediately for me either. Try to play with the Dashboard Cockpit settings a little bit. Also reload the page several times. That did it for me.
Switching the highlighted option to none and then back fixed it.
It’s the first thing I tried and yet, trying it again after seeing your message worked:
Interesting. There might be something off with the initial retrieval or possibly the default settings - I can probably reproduce if if I clear my local cache. Glad there’s a workaround, but something like this might cause errors for resetters as well, so I’ll see what I can do to fix. edit: fix available in v0.3 - was an issue with the treatment of the default setting
It doesn’t really fit with its current UI, but if you modified it and added it in I would be so grateful.
Not making any promises - I have no experiences with that script. But I can take a look to see if I can make the scripts work together or something. (or if I really like it…
)
Would it be possible to draw the leeches in circles instead of rectangles? Maybe using border-radius?
That’s a nice idea! I’d have to figure out how much space this would need in certain cases (at some point leech counts can go >100 and I don’t want it crowd out other info or pass outside its designated area). I’m adding this to the wish list for now - needs investigation. Also - I’m not particularly speedy with implementations
…
edit: available in v0.3
Finally found this! I kept seeing the screenshots and not finding the script. It’s a really nice look, thanks for all the work. I’m making sure to reply so that I remember to give it a go when I get back to my desk, haha.

Ah not another cool script!
It’s too pretty! Help! installs script anyway
Hi! I noticed this script isn’t on the master list of scripts, do you mind if I add it there?
Yeah, adding it is fine - somehow feels very official 
I love this script and I feel totally lost when I’m on a computer where I don’t have it installed. Thanks again for making it!
Just one small issue: I have the short progressbar below my “cockpit”. When I scroll up, the rest of the “cockpit” disappears under the top bar, but the progress par goes on top of it. Is there any way to fix this?
Is there any way to fix this?
Yes, I already have a fix for this locally, along with some others. I’ll try to publish an update this week.
edit: fix available in v0.3
Thank you! And thanks again for making this script, I love it!





