PUBG: Scoring rule change for season 6

Moving away from XPUBG has given us the opportunity to access a large amount of data, which has enabled the introduction of a new leveled scoring system. The Kanastats.com\ service is integrated directly into the PUBG API, from which we have been able to collect data ranging from hours of play to the accuracy of shots. The data has been collected from all the matches played by the players, so it also includes e.g. Team Deathmatch games, Ranked games and tournament games for competitive players. Almost a hundred million lines of data were collected from the entire project. From this we developed a reasonably complex calculation formula for player-specific handicaps and combined the player-specific handicaps into team-specific handicaps.

Despite the level series, the skill levels of the teams differ from each other even within the level series. So we wanted to make the series as even as possible for everyone, and that’s why we developed this leveling system. We ran the results of the game days of previous seasons through the system and to our delight we got a very even league table situation throughout the season, thus allowing each team an equal chance to win the series.

We will be implementing the scoring system starting today, and tonight’s Challengers games will be played using the system.

Leveling system operation

In the system, each team is given two numbers: handicap factor and handicap number. The leveling system is dynamically based on the composition of the teams participating in the maps and their PUBG history, so the figure is not actually publishable. The teams do not have to separately report the players playing in the matches, as the player-specific values ​​are constantly calculated while the players are playing the game, and when calculating the points, the points are calculated using numbers. Teams can therefore still freely change players between maps, as long as the player has been announced to the team in advance.

Equalization number

The handicap figure is added to the SUPER score earned by the team. The purpose of the number is to equalize the number of points accumulated by the teams from the matches. The chapter uses the presupposition that teams playing with certain formations will place better than others in matches. For example, the pre-assumed score of a team that constantly finishes at the tail ends is lower than a team that constantly takes ten-kill wins, so the team accumulates points even for positions that SUPER scoring would not reward with points. The number can be negative, in which case teams with a lot of points earn less points from matches than SUPER scoring would give the team.

For example, Team A’s handicap number is 4 and Team B’s handicap number is -4. Team A finishes ninth and gets one kill in the game, earning the team five (5) points from the game. Team B, on the other hand, wins the match and gets six (6) kills, team B earns 12 points.

Smoothing factor

The handicap coefficient is a coefficient based on the performances of the team’s players on the playing fields. The number is a coefficient number between 0.3-3.0. The handicap coefficient is used to multiply the team’s score after calculating the handicap number and is rounded to a whole number according to the rounding rules.

According to the team examples in the handicap figure, Team A’s handicap coefficient is 1.7 and Team B’s coefficient is 0.8. In this case, Team A’s final score from the match is nine (9) points, and Team B’s score is ten (10) points, respectively.

Below are the standings after five (four for the Challengers) game days. The standings will be updated on Kanastats.com during the day.

Masters

Challengers

2nd Division

For the sake of transparency, we open the code used to calculate the leveling to everyone. Attempts have also been made to open intermediate gears to the code in plain language, so that it should also be understandable to players who do not know the python language. You can get to the code page from here. We recommend that everyone at least glance at the code so that you can better understand how the system works!