Without an API, the only way to do this is with self reporting. So essentially people would need to use a discord command to log the kill, along with picture proof. If we do this with a database, we can ditch discord and integrate the API with the database as soon as the API arrives. There's no way around it, sadly. My argument is that whoever leads the leaderboards would be under big scrutiny from the community. If little Timmy who's been around for a week suddenly shoots through the ranks, people will be suspicious. Suspicions can be confirmed by devs (alt killing, etc) if they deem the situation worthy. But the main point is: I don't think many people will try to cheat this because there's no physical benefit from doing it. The benefit of a leaderboard as it is atm is bragging rights. Are people going to risk bans to cheat the leaderboard? Yes, confirming suspicions is, technically, more dev work. But I think the need to do this will proabably be extremely rare because cheating the leaderboard isn't worth the risk. So the added workload for the devs would be minimal if any. While the benefits to boost PvP could be major. Whether it's worth it or not is up to the devs, I suppose.

Simple Solution, do what was done before with zero drama. release the API already...

I really wish we had this e.e

But idk how "simple" of a solution that is xP

Either solution needs a bit of technical hammering. You know what doesn't, though? Events 😄 How are we on those?

im tired, and grumpy. so i choose not to answer that at this time.

> "Cannot log kill for someone not in Discord" > If what you mean by this is: "User A kills user B and wants to log it, user A must be in discord" then sure. > If what you mean by this is: "User A kills user B and wants to log it, user B must be in discord" then this is a problem. > The idea of using a database is you don't need to have the data stored on discord. any and all - values are stored per discord user id's in a collection in the database for the bot on the bot platform (not discord) "You cannot log a kill of someone not in Discord or not in this server." https://discord.com/channels/610868764338290728/1339275064994173118/1339334917183635631 So it would only be possible to be used by and hold data of discord users so ok for a simply leaderboard ranking feature but not for a fullfleshed featured thing like what, I now know, you meant...

> "It uses discord user system to store data per user..." > My point is you don't necessarily need this. Yes and no. Yes for how this work. No - not for what and how you want to do it. > Discord bot would merely function as a way to send data and read data from the database through the use of discord commands. I got it, I am fully onboard and aware what you meant and want - several comment back actually 🙂

Please take this as the perfect example of how we have (and others) and potentially will misunderstand each other in the future. > "I did not build it to be able to ping ppl." > You were the one who brought pings into the convo, I assumed it was something you wanted. In a reply to your question 🙂 You brought up the need or not to ping. I did not make any of this with being able to ping in mind. As said it have another function now than for what it was made for (users setting a goal, getting a strike if they do not reach it). That function is here changed to simply ping ppl if they did not post/log a win during the week - a way to keep ppl 'feeding' the leaderboard. Each week they did not post anything for the leaderboard they would get a strike. Upon the third strike (third week with out posting) their user id would be removed from the user list (not leaderboard ranking or user data removal as you took it as). As said https://discord.com/channels/610868764338290728/1339275064994173118/1339337170485248123 purely a maintenance thing - as to not keeping ping loads of ppl who left long ago Which I said like this > "The user is removed from a list on 3. strike ie the system stop pinging. Makes no sense to ping someone who have not logged anything for months."

> "yes, as established - another platform is needed." > Yeah. A simple database with the bot acting as a way to interact with it will probably do the trick. so we need a free, 24/7 up, API access providing service which do not have various ratelimits which restricts what is needed (f.ex limited tables, limited size, time) Google Cloud Platform offers mysql - but comes wiht a cost. Google Appsheet does offer a database for free - but it is somewhat feature limited. No idea yet whether API for it is an option.

back looking at this - found a free place, no card requireed but size was only 5mb and setting up tables as Lyon suggested took 1,2% of the space with no data added) Had to adjust the tables SQL a bit to get it to accept it: ||CREATE TABLE characters ( id INTEGER PRIMARY KEY AUTO_INCREMENT, name varchar(255) UNIQUE NOT NULL, nation TEXT NOT NULL, class TEXT NOT NULL, score INTEGER DEFAULT 0, owner_discord_id INTEGER ); CREATE TABLE score_logs ( id INTEGER PRIMARY KEY AUTO_INCREMENT, character_id INTEGER, score INTEGER, timestamp TIMESTAMP DEFAULT CURRENT_TIMESTAMP(), FOREIGN KEY(character_id) REFERENCES characters(id) );|| - not finding anything other than restricted by size of database, credit card required and no way(or I do not know) to interact with the database... - so I am going my own way - ! lots of bits and pieces missing yet but there is a sheet based database, site and a very basic board with a 'design' no way to add anything yet - via discord will be required for screenshots, access to site would require having a google account logged in - due to rate-limiting: one idiot could be spam loading the site and blocking it for everyone else - by having the requirement of having a google account logged in - the idiot would only spam loading on their own rate-limit and not affect anyone else (that is how google offer this service) - or it could just be a couple of users doing nothing put using it as intended and they could hit the limit (60 requests per minute per user per project) https://cdn.discordapp.com/attachments/1339275064994173118/1342243567304835102/image.png?ex=67b8ed3c&is=67b79bbc&hm=51ef7801a06d15c508a064eef078b8331a892cf645348640c35f4b1643fbd2b9&

that is not static info btw

This is looking pretty cool

Good job

So what's the goal of this?

the return of the leaderboards, aka chestthump table for pvpers

> chestthump table he, had precisly that frasing in mind too

added leaderboard to the channel name - to help make it more clear what this is about

Have been fiddling with various needed bits and pieces here, check logic of name content - similar to what is experienced in-game when entering name for a character yes, including the no no word list https://cdn.discordapp.com/attachments/1339275064994173118/1348762852726538364/leaderboard-checkname_content.gif?ex=67d0a4ca&is=67cf534a&hm=a8ba5a5b11d3ac35e58aedbb18227a95841148ebba237e6a68851755ba6c8c14& https://cdn.discordapp.com/attachments/1339275064994173118/1348762853099962458/leaderboard-check_name_content_2.gif?ex=67d0a4ca&is=67cf534a&hm=10f5897b7dd784026990ed6a8d5dc80328003ea28ea0b82d9dfe8aba4894692d&

here, lookup of a captain (when logging a battle) - that is live pulling data from the sheet database and populating the dropdown content on the spot https://cdn.discordapp.com/attachments/1339275064994173118/1348763202586017862/leaderboard-namelookup.gif?ex=67d0a51e&is=67cf539e&hm=5fa1954e5e7f9366fcf0c206979aad2c7b83bbb51622e883c56733c82f8b58b0&

and create character: various dropdown selections for the needed info and dumping it to the sheet db (the short darkening of the screen after the class dropdown is a popup of a name field-form) https://cdn.discordapp.com/attachments/1339275064994173118/1348765857173602405/leaderboard-createcharacter.gif?ex=67d0a797&is=67cf5617&hm=ffaca5b09b625085bb96902253d727b8165faf6892246e6db336682bf53ca93e&

so, found some time for this leaderboard project again. Here 👆 it took ~8 seconds to get and handle 59 records (getting the double would take almost double that) - that is a long waiting time. got it to do it a much cleaner way. Here it pulls and handles 126 records in ~2 seconds also, added nation/faction icons to the dropdowns https://cdn.discordapp.com/attachments/1339275064994173118/1350752604883386388/leaderboard-findcharacter-improved.gif?ex=67d7e1e4&is=67d69064&hm=6c435e84c351744d9d2d0aac4e77758028b1ff112ebe2ab7a45ac05b51b35206&

It's looking smooth 😎

tiggy unplayable continual discon / across all toons

totally a wrong channel...

thank you 😃

Note / B4 : compared to what have already been shown there is nothing new content wise (apart from access/possiblity to view it yourself now) so while, setting up various things, sheet, script, API - in short the place the leaderboard will live, on the account I use for potbs - I thought I would create a page for it, so you could get a feel of the board Some styling may be blocked via this 👆 so you might have different experience on a mobile device, try the direct link: (this link will change everytime I make changes to the board page, so it is not an error if/when it stops working) ❗ Clicking Legacy / Roberts will 'break' the page (not responding to clicks) untill reloaded - this is not an error - there it simply nothing connected (the structure will be replicated once I am done, so there will be content per server) ℹ️ showing f.ex 4 characters with rank 5 is not an error. Same score gives same rank. A feature seen on the original board, I remade that here. Short info on the other parts needed for this: during the week I did a bit for the 'create character' part - added a check whether the name entered(to be created) is already present (no need to create). Setting up the living place for the board is part of tying up pieces trying to get ready for a first open test (__**maybe **__ next weekend depending on time avilable during the week) https://cdn.discordapp.com/attachments/1339275064994173118/1355979422359879811/image.png?ex=67eae5bf&is=67e9943f&hm=cec105a27d9e49d7acef7aa742fc0f7ffc982c6b65ecb48eee90eab3877f3ca2&

oh yes, there is a short delay before the board is shown (load data, build table) - cannot do much about that (for now at least)