https://perchance.org/leaderboard-v1

Yes i literally just got it functional and have a trillion things to do before I make the plugin page look nice. BUT IT WORKS. try it there. incorporate it in to your games. make it so, after someone brings their kitty thru your long and arduous tasks, they get a score and let them enter their name and add it to your leaderboard which is on one of your tabs. stuff like that. I made it pretty easy to use I think. Uses node.js back end on Glitch and will adapt as we break it, lol. requires the barest tiniest javascript but so tiny that if you don’t know js just ask how to get it on your generator.

it is highly duplicatable. if you want to make it look nicer and be the master of it’s page, feel free.

literally just [leaderboard(leaderboardsettings)] to place the leaderboard and to add an entry, allo.leaderboard.add(score,name)

    • BluePower@sh.itjust.worksEnglish
      2·
      7 months ago

      Great plugin overall! I’ve just been working on the new update on the game with the new score system feature and suddenly stumbled upon this plugin when it was just released and decided to implement it into the update. 🙂

      I’ve used some more JS to make it super neat, prevent name duplicates, and also make each time user opens the game, new people/entries will appear highlighted.

      • allo@lemmy.worldOPEnglish
        2·
        7 months ago

        say anything i should do and i would!

        If you make a totally better frontend plugin for the backend I’ve made, I’m fine with mine being obsoleted.

        If you want to see or be part of the project for it on Glitch tell me your Glitch name so I can invite you

        • BluePower@sh.itjust.worksEnglish
          2·
          7 months ago

          Yeah, the leaderboard plugin definitely needs some more updates, although I could make some code to remove the extra colons and add a bunch of extra features onto it.

          Also an important tip for making plugins: Make sure that you add guarantee for backwards compatibilities when updating plugins. When someone already used your plugin with the old syntax (for example, passing options directly through parameters) and you decide to move on to using lists to pass the options in, make sure you keep both because generators using either syntax won’t most likely break even when you’ve moved to the new one. Same when you’re going to remove/replace certain features with a new one. Although if you really want to move it and wanted to remove the old one soon, you can mark them as “deprecated” first so users will get warned about their generators will break if they still use the old syntax for your plugin. (I also might create a separate post for this later)

          • allo@lemmy.worldOPEnglish
            2·
            7 months ago

            yep AND THUS IT IS FOREVER BACKYARDS COMPATIBLE

            now with a noDots = true option to remove the extra colons

            anything else i would do on my side???