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

Match stats longest shot seems inaccurate #892

Closed
brendanfuller opened this issue Jun 23, 2021 · 8 comments
Closed

Match stats longest shot seems inaccurate #892

brendanfuller opened this issue Jun 23, 2021 · 8 comments
Labels
bug Something isn't working

Comments

@brendanfuller
Copy link

I've recently noticed that end game match stats only care about about the longest shots/sniped shots on land rather than shots that have death by void, or death by falling. All I'm wondering is should all bow shots count and not just land shots, assuming this is not intended.

Originally I thought it was due to the 60 block sniped vs shot but that doesn't seem to be the issue.

Though anyways here some evidence:

  1. I kill someone with a great shot (these images are all from the same match)
    Screenshot_20210622_133124
  2. The match ends, but its only the attacker who had the land shot (which is rounded up for some reason?)
    Screenshot_20210622_133113
  3. Find said attacker, who got that "longest shot" in the chat, which was on land
    Screenshot_20210622_133140

Further more I wanted to see if this was common with every match I've played/spectated via the Minecraft logs.
So I create a simple python script to see said information:

Out of 432 games which have the Match Stats shown, only 112 of them were actually accurate, and 106 of them were all land shots only.

For anyone interested here's the the outputted data from said python script here ya go matches.txt

@KingOfSquares
Copy link
Contributor

Oh yeah thats not intended but its something i never found the reason for when i initially made it.

@Pugzy
Copy link
Contributor

Pugzy commented Jun 23, 2021

I though the falling/void deaths included the distance the person fell too? This would make them inaccurate as the arrow doesn't actually hit at that range.

@Pablete1234
Copy link
Member

Pablete1234 commented Jun 23, 2021

Match stats is what is accurate, it's the distance the arrow traveled, kill message however, is distance from killer to victim at their time of death, so if you knock them out of the world all the height they fall is added up

@Electroid Electroid added the bug Something isn't working label Jul 4, 2021
@CoWinkKeyDinkInc
Copy link
Contributor

Fixed

@Pablete1234
Copy link
Member

Fixed

Could you reference the commit/pr that fixed it? If you mean #897 it only fixed one (small) issue, but not the big difference

@Pugzy
Copy link
Contributor

Pugzy commented Sep 5, 2021

Could you reference the commit/pr that fixed it? If you mean #897 it only fixed one (small) issue, but not the big difference

Unless scenarios like 'sniped out of the world' are updated to only be the distance the arrow flew I don't think they should be considered longest shots.

@Pablete1234
Copy link
Member

Unless scenarios like 'sniped out of the world' are updated to only be the distance the arrow flew I don't think they should be considered longest shots.

Yeah, the fix is to modify the sniped out of the world message to only include how long your snipe was, not how far they fell after you sniped them. Should be distance between shooting point and impact on the attacker, like match stats are properly reporting

@Pugzy
Copy link
Contributor

Pugzy commented Jun 19, 2024

The changes made in #897 and #1272 should both resolve this discrepency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

6 participants