Started by koeppy in Discord · Aug 25, 2026 · closed · Open in Discord ↗
Had a group in my clan run Chambers of Xeric 16-23 Mans.
Noticed the droptracker submission came back as 16 players but the one pulled from the clan chat pulled 16-23 players
joel via Discord · Aug 25, 2026
Ah this is because the plugin can tell how many players exactly there were in raid and the clan chat groups them into dif sizes
joel via Discord · Aug 25, 2026
Ill make it not dupe the cc messages but yeah we store individual team size pbs for cox iirc all the way up to whatever amt
koeppy via Discord · Aug 25, 2026
How would that work on the pb leaderboard?
koeppy via Discord · Aug 25, 2026
Like would we then have separate Leaderboards for submission from the clan chat vs the plugin?
joel via Discord · Aug 25, 2026
I suppose that it needs to be looked at because regardless the game is only storing pbs for those size increments anyways
joel via Discord · Aug 25, 2026
But yes in theory, unless I'm mistaken and that plugin submission is sending 16-23 but doesnt show it properly in embed
joel via Discord · Aug 25, 2026
Also the issue there is different too
joel via Discord · Aug 25, 2026
Its because one guy has exact timing on and one doesn't, so they read as two different times
joel via Discord · Aug 25, 2026
Another issue to fix 😛
koeppy via Discord · Aug 25, 2026
Yeah thats a separate issue I was noticing 😅
joel via Discord · Aug 25, 2026
Meh its unavoidable in most cases but for the cc integration its easy to fix
koeppy via Discord · Aug 25, 2026
I ended up building some logic around that for my discord bot. where is the time submitting isn't in .6 increments to automatically round it up to the next highest
joel via Discord · Aug 25, 2026
Player cant get 2 20 min pbs in under 20 mins
joel via Discord · Aug 25, 2026
Solved
koeppy via Discord · Aug 25, 2026
Good example is 40 second pb.
If they don't have precise timing on I default it to send 40.6 instead of 40.0
koeppy via Discord · Aug 25, 2026
Or like in their example above I am technically submitting 40:13.2 if they don't have precise timing on (cause on it's own its not certain their time is 40:12.6 or 40:13.2)
joel via Discord · Aug 25, 2026
I suppose I get your point but for the people who care about having the best times, they'll have precise timing on anyways
koeppy via Discord · Aug 25, 2026
For sure. I am making it a "disadvantage" to have it off essentially
joel via Discord · Aug 25, 2026
And its safer imo to not assume they took longer than the client sent, even if sometimes it ends with them slower
koeppy via Discord · Aug 25, 2026 (edited)
Cause for example if someone get 39.4 seconds without precise timing it comes through as 39 seconds
koeppy via Discord · Aug 25, 2026
(Jagex rounds up and down for non-precise timing when they display it)
joel via Discord · Aug 25, 2026
Yeah i mean it is what it is at that point haha I just think its best to be left how it is in that regard for us because nobody in the top listing is gonna be using non precise timing . Perhaps a config option for groups later idk
koeppy via Discord · Aug 25, 2026
Thats the thing though I guess I am saying. If someone has non-precise timing enabled it can be a benefit
koeppy via Discord · Aug 25, 2026
Cause it could display them with a faster time then they actually got (or is possible)
koeppy via Discord · Aug 25, 2026
Take Brutus for example.
1.2 seconds is the fastest time possible.
If someone has precise timing off it comes across as 1 second
koeppy via Discord · Aug 25, 2026 (edited)
I guess maybe thats a separate problem.
We probably want to solve the team size consolidation first so we dont have the following saved in our leaderboard. 16 - 23 16 17 18 19 20 21 22 23
koeppy via Discord · Aug 25, 2026
I'll write up a separate ticket for the precise timing
joel via Discord · Aug 25, 2026
I guess what I'm trying to say is that nobody speedrunning a boss is going to realistically have precise timing off, and if they do it just for their pb, turning it back on would update their stored pb with the right time in the db
joel via Discord · Aug 25, 2026
So idk doing it auto is an option I just dont know how much I see it happening
koeppy via Discord · Aug 25, 2026
Ah see what you are thinking. Guess was more just trying to flag it could be a case that unfolds (probably not high probability)
brondt_ via Discord · Aug 26, 2026
you think too highly of other people LOL
joel via Discord · Aug 27, 2026
i changed this btw
joel via Discord · Aug 27, 2026
like this
koeppy via Discord · Aug 27, 2026
Ah awesome. I think I saw you got some plugin update to send the full team size message as well
joel via Discord · Aug 27, 2026
Yeah it was normalizing on the plugin to make 16-23 or whatever into 16
joel via Discord · Aug 27, 2026
Just regex basically
joel via Discord · Aug 27, 2026
But I coded a fix on the backend regardless, so
joel via Discord · Aug 27, 2026
Not waiting on that
joel via Discord · Aug 27, 2026
Thinking, might make the logic for rounding PBs client side. Make it so the first time it does it before sending to the server, it sends the user a chat message telling them if they want more consistently accurate PB times reported, to enable precise timing in their settings
joel via Discord · Aug 27, 2026
Might get more people to enable it at least
koeppy via Discord · Aug 27, 2026
Yeah you could I'd just make sure it's something that can get turned off like the welcome message
joel via Discord · Aug 27, 2026
Well it would be a one time thing
joel via Discord · Aug 27, 2026
"The first time"
joel via Discord · Aug 27, 2026
😄
koeppy via Discord · Aug 27, 2026
Fair
joel via Discord · Aug 28, 2026
Is this good to close, you able to check when you have a free moment? I believe it should be all set, the plugin side changes arent public yet but the server handles it meanwhile
joel via Discord · Aug 28, 2026
@koeppy
koeppy via Discord · Aug 28, 2026
I can take a look when I get a chance:
You talking about consolidating the 16,17,18,19,20,21,22,23 team sizes for cox into 16-23
Or you referring to the if non precise time is enabled to automatically calculate it to milliseconds
joel via Discord · Aug 28, 2026
Both
koeppy via Discord · Aug 28, 2026
Ok I'll take a look when I get the chance
This thread is closed on Discord, so replies are disabled.