Yep, but it’s easy to edit. In function function install_settings on line 87 edit these lines to add more values like I’ve done:
'totalNumberOfLeeches': {type:'dropdown',label:'Total number of leeches',hover_tip: 'The amount of leeches you want to display',default:defaults.totalNumberOfLeeches, content:{5:'5 (Min)', 10:'10', 15:'15', 20:'20', 25:'25', 30:'30 (default)', 35:'35', 40:'40', 45:'45', 50:'50', 55:'55', 60:'60'}},
'leechesPerTable': {type:'dropdown',label:'Number of leeches per table',hover_tip: 'Defines how many leeches will be included per table',default:defaults.leechesPerTable, content:{10:'10 (default)', 15:'15', 20:'20', 25:'25', 30:'30', 35:'35', 40:'40'}},
Does that mean you get more tables the more you add people?
I believe one paginated table would solve that in a much cleaner way, don’t you think? You never know how many people one might add, in return, they might end up with a lot of tables
The number of tables can be set in the menu. The maximum number of tables is three, since once you have three of them you basically occupy the entire width of the dashboard.
There are no doubt better ways of displaying the users but when I created this script I never planned on more than one table. Multiplying the tables was just a quick fix for people with really long leaderboards. I’ll look into paginating and the like later.
Actually I should amend what I said above. I am now seeing it when I had 22 users, I would get 7, 6, 7. So I actually would lose 2 people. When I added another user to get to 23, the three tables then showed the correct count of 8, 8, 7.
Also as a fix to the other issue I mentioned above with the wrapping, this seems to guarantee that all the tables are the same height of the parent div:
let leaderboardTableStyle = '<div id="leaderboard" class="row" style="display: flex">';
I’m quite concerned, how much information WK gives everybody about oneself… Even without API key. And with the API key you can absolutely analyse one’s soul
