Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Enhanced scores #154

Open
therealpanse opened this issue May 16, 2016 · 1 comment
Open

Feature Request: Enhanced scores #154

therealpanse opened this issue May 16, 2016 · 1 comment

Comments

@therealpanse
Copy link

It would be nice to see your 1k 2k etc rounds of a match without crawling through the kill log and count them yourself. Another column with your ADR would be nice too to plot your ADR over time, just for giggles. I don't know if thats really something useful, but nice to have just to calculate the HLTVrating yourself.

I know you could filter the rounds in the search, but it's a hassle to pick the stats from a specific match if you play more than one a day. Usually I play about 7 matches per day, so the list gets longer.

@therealpanse therealpanse changed the title enhanced scores Feature Request: Enhanced scores May 16, 2016
@bugdone
Copy link
Owner

bugdone commented May 16, 2016

The match scoreboard features a HLTV rating column. In the next version will have the ADR column as well.

As for the multikills, adding them to the scoreboard would make the scoreboard too cluttered I feel. I guess a round breakdown like the in-game "Your matches" -> "Round performance" would be nice to quickly see which rounds had multikills.
Related to this is also issue #90. The idea is that you could configure certain conditions that if fulfilled would make a round interesting (ie. 3k, jumping headshot kill, etc). If a match contains such rounds, this match would be marked as such in the match list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants