Paul Inouye, on 03 June 2020 - 12:09 PM, said:
[color=orange]Regarding Stomp Numbers: [/color]
But first, let's look at some numbers. We mentioned stomp stats that are matches that end with a score of 12-4 or worse for the losing side. While this metric isn't perfect, it does give us a good baseline for comparison purposes.
When we first implemented the queue merge, we mentioned that the current stomp rate increased by 5%. But as some of you mentioned, that 5% was not clear as to the number of actual stomps, just an increase in an unknown value.
How did we get the 5% increase? We took an average across a number of days prior to the merge and a number of days after the merge.
Prior to queue merge, our sample set gave us this:
1123 Stomps out of 3755 matches in an average 24hr period resulting in a 29.91% stomp rate.
Post queue merge, our sample set gave us this:
935 Stomps out of 2751 matches in an averages 24hr period resulting in a 33.99% stomp rate.
This was the 5% increase we saw.
When we first made some tuning changes to the match maker for Tier/PSR balance and tonnage balance, the sample set showed this:
1801 Stomps out of 5506 matches in an average 24hr period resulting in a 32.71% stomp rate. A 1.28% decrease in stomps.
When I did the stealth tweak to Tier/PSR and tonnage balance in the match maker, it resulted in this:
1057 Stomps out of 3453 matches in an average 24hr period resulting in a 30.61% stomp rate. A bigger reduction from peak of 33.99% down by 3.38%.
Essentially, overall stomp numbers increased by only 0.7% compared to pre-queue merge.
I very strongly disagree with how the stats were handled here. Percentages can't just be subtracted like that (although, even with subtraction, I'm not sure where the quoted 5% came from). 33.99/29.91 = ~ 1.136 or a ~13.6% increase.
Please just report the straight numbers in the future. I'm sure you are aware that a lot of people are looking for ways to call you guys dishonest, and handling things this way doesn't help that.
Quote
To change this, we will be implementing the following:
Current PSR values:
Player LOSES:
Match Score: 0-100 goes down in PSR by -2
Match Score: 101-250 goes down in PSR by -1
Match Score: 251-400 does not move.
Match Score: 401+ goes up in PSR by +1
Player WINS:
Match Score: 0-100 does not move.
Match Score: 101-250 goes up in PSR by +1
Match Score: 251-400 goes up in PSR by +3
Match Score: 401+ goes up in PSR by +5
New PSR values:
Player LOSES:
Match Score: 0-100 goes down in PSR by -5
Match Score: 101-250 goes down in PSR by -3
Match Score: 251-400 goes down in PSR by -1
Match Score: 401+ does not move.
Player WINS:
Match Score: 0-100 does not move.
Match Score: 101-250 goes up in PSR by +1
Match Score: 251-400 goes up in PSR by +3
Match Score: 401+ goes up in PSR by +5
To me, "zero-sum" would mean that for as much and as many as one team goes up, the other team goes down. Tying the magnitude of the increase or decrease to match score only accomplishes the goal of "zero-sum" if those match score bins are statistically equal on both teams, which is something I expect is unlikely.
Quote
We are making these changes to build the best matches with the tools and numbers we have.
We will continue to monitor the stomp rate, game win/loss scenarios and tier matching to make sure the new PSR system is working as intended.
I know I sound critical here, but I really do appreciate what you are doing. Perhaps I missed it, but when is the ETA for the PSR reset?