Closed frozenpandaman closed 1 year ago
I guess the result says afterGradePoint is 995 and s3s assumes that 1005 -> 995 as a W2 loss, isn't it?
Uh-oh... This behavior seems different from in 2.
I know point loss is halved when 1 or more players DC, but it's also true when players have a large diff in EVP I think. So tracing the previous result via previousHistoryDetail or passing EVP as next function args seems better.
tracing the previous result via previousHistoryDetail or passing EVP as next function args seems better
@k-ashiya I think you're right. It's slower (an extra request for every job) but it definitely is the most accurate.
This should be fixed in 10dd403!
Bug report from Minaraii on Twitter:
This error came from a W2 loss EVP 999 -> 994, which only happens when a match has 1 or more player DC. I believe this is due to the data registering an EVP 999 final result as a 979 -> 999, regardless of the starting EVP (e.g. 980 / 985 / 990)?
export.zip