Repository navigation
Conversation
The Analytics card lists the five longest kills over the range, of any cause, and nothing else could ask for more. A page that wants a weapon's record, a class of weapons' records, or every shot but the mines had no route: on a busy server the five are AT mines at six kilometres (a mine's distance is from whoever laid it), and the kills route pages newest first, so the longest M4 kill meant walking the whole history. The new route answers with the card's rows over the card's ranges, narrowed by `cause` (keep these tags) and/or `exclude` (leave these out). Both match whole and in any case, as the kills route's filter does, take repeated or comma-separated values and are capped at 64 tags; `limit` is 1-25. The card's query now goes through the same function, so the two cannot drift. Tested against Postgres: order, range bounds, cause and exclude in any case, and the cap on limit. The route has its line in the API matrix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The feed carries the odd distance no shot can have. Over the last 30 days on a busy server: a Deagle at 4,042 m, a Bushmaster M17S at 2,290 m, an SVD at 1,807 m and an M500 shotgun at 1,455 m, while the real sniper records sit just under a kilometre (AMR 50 998 m, SV98 993 m). Asked for a class or a weapon, the route put those glitches on top of every list, and a client cannot filter them out of a top five it never sees past. `maxM` drops kills beyond it, as `minM` bounds the kills route from below; missing, malformed or not positive, it is no bound. A client after plausible long shots can now ask for firearms within 1,200 m and get the real records. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A page linking each record to the shooter's profile had only the name to go on, and names are neither unique nor stable. Looking them up meant walking the player directory, which on a cold cache took a site 35 s for one panel. Each longest kill now carries `killerSteamId` from the kills row, on the new route and on the Analytics card alike. Both already sit behind server.view, which reads SteamIDs on the kills route, so nothing new is exposed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Feat/longest kills by cause
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.