Feature requests

The last selected game type is now saved in a cookie and used across pages.
Appending "#duel" to the player profile link will show the duel stats (overriding the cookie).

Showing the opponent is something I already had on my todo list, but it requires some work on the database to work efficiently

I have had to recreate a STEAM account because my account crashed so I would like to link my previous QLSTATS to my new player. Can this be done through the !alias command?

I see what I can do. It's a bit tricky because that data isn't available from the stats data feed and I'd have to get it separately from a server browser request.

The stats data does not support such fine grained level of detail.
The best thing that could be derived from the data is the time span you were alive in a round. The game server only emits events for match start, death, kill, round over, match over, player connect / disconnect and team switch.
What you want can only be done by analyzing a demo file.

Forgot to login, it was me. Do you have information whether player was kicked? Because stats of the match looks like I played full time, although I was kicked after about two minutes.

Changed to minimum of 4 for GL, RL and RG. All other weapons still require 10 shots minimum.

When you start adding damage_taken or any sort of net_damage or net_kill, it will reward defensive play, like hiding in save spots while your mates do the dirty work and die.
The current system seems to work quite well for CA matchmaking, which is the main purpose for the ratings, so I am not making any changes to the formulas without statistic "proof" that it will produce better team-ups.
Personally I think it doesn't matter for the match results whether you survive with 1hp or with 200hp. But the damage you deal has an impact on the match result.

It shows your last 20/50/100 matches.
There is no option to show them all.

To what purpose? 5 rated game types, 6 regions, A and B ratings and now you want that for 200 maps?
Next step would be a ranking per steam-id, so everyone is #1 :)

that is a good idea

Rating is the process of assigning a skill estimate. For that I use the Glicko system. But you need to understand how such systems work.
You can't throw in a random set of numbers and except something good coming out of it. The system "learns" each players skills by observing many matches.
For that, all the matches you feed into the system need to be comparable, otherwise you are confusing the system instead of teaching it.

If you have several sub-communites who never mix with eachother, their ratings are not comparable either. They both form their independant rating distribution in the 0-3000 point range. That's not because the system is broken, that's because of the worong expectations about the system. It simply can't tell if A is better than B when they and their friends never play against eachother.

Now when you use these already shady ratings to sort all players and see who comes out top 100, you get rankings that are even more shady.

And if you then start to mix team sizes, pql/vql, vampiric/normal, ... for the system's input, you'll get nothing but garbage as output.

quit, forfeit, crash, loss ... all the same - at least for duel.
In other modes a player with less than 50% match participation gets ignored, 50% and more are counted.
Ratings are there to have an idea about a player's skill for the purpose of shuffling teams and not for ranking (as in: you are #78 in the world). Arbitrary changes of the rating values to punish someone will do more harm than good. You'd award the quitter with better team mates.

sorry, won't happen. i'm not going to add any more rankings.

I'm pretty sure you get 1 point for a kill. So if same damage but other guy has 10 more kills then he has 10 more points. 1 point is 100 damage, so you would need 1000 additional damage to match that. That is at least how I know it, I could be wrong.

Not really. Not because I don't want to, but because that doesn't work for several reasons.
When a server owner choses to track his server on qlstats, you'll have to accept it when you want to play on his server. His house, his rules.
The main purpose of qlstats is providing rating data to servers so teams can be balanced. This requires that all players have ratings. Another use of qlstats is to provide data for restricting access to the server, like min/max rating or keeping out cheaters/offenders. And that ofc requires that offenders are tracked and can't opt-out of it (I'm not saying here you are an offender).

None of those pages you linked were ranked for Domi. - - - for all glicko results.

I can't lower that percentage. Scaling up 25% of game time to 100% causes a massive extrapolation error. One could get 2 quads early in the game, then quit and his score would scale up as if he had 8 quads.

The rating is meant to measure a person's skill and a match that's only played for 2 minutes doesn't provide any accurate information to change the rating either up or down.
Unfortunately people don't understand that, look at the rating numbers and try anything possible to inflate them - or punish other people by deflating them. Both things reduce the quality of the ratings.

In team games, if a player is "punished" by lowering his rating, it is actually a "reward" because he will get better team mates the next game.
And then there are some technical issues about the data that's available about a match. I can't distinguish whether a player quit, got kicked, connection interrupted, ...

The only way to avoid this Heisenberg problem (people changing their behavior because you are observing them) is to not make the ratings public.