Last Friday, the news of RNG replay suddenly occupied the first place in the hot search of microblog, Zhihu, station B and other major platforms. Whether you play lol or not, you probably see this news. This matter can receive so much attention, I think it is two words: outrageous **
Microblog sent by RNG players after learning the news ▼
Until the night before yesterday, I had an 8000 word technical note explaining the beginning and end of the RNG replay. After reading it, I felt it necessary to nag with you.
First of all, let's give you a brief introduction.
Well, every year, the fist company (lol official) will hold an MSI mid-season competition, which can only be participated by the champions of each division.
But this year, due to the epidemic, the champion of our division can't go to the scene.
After consideration, the official decided to let the team in our competition area play remotely and other teams play at the scene of the competition in Busan, South Korea**
This is actually an uncommon transnational game. After all, the game delay will be different due to the different distance from the server.
For the sake of fairness, fist decided to use a delay tool, to unify the delay of all players to 35ms**
Three days after the game, RNG won all three wars, and everything seemed to win.
However, at 1 p.m. on the fourth day, the official suddenly issued a notice saying:
RNG competition does not count. It needs to be replayed
Because the actual delay of the on-site team fighting with RNG is more than 35ms, which is even more stuck.
Although everyone was puzzled by this decision, RNG, as a professional team, could only agree to the official decision and played three games again.
Here, it's not over yet.
After the RNG replay, some players found that the Ping value displayed on the player's screen was about 22ms when the other two teams were playing
Huh? Didn't you agree to unify 35ms?
How come the game played by RNG is 35ms, and when you are offline, the game delay of other teams becomes 22ms?
After the hot search on this topic, it was soon found that perfectly answered this question "early" in the English announcement of RNG replay:**
Oh, after the delay tool is enabled, the Ping value seen by the on-site players will be 13ms lower than the actual value.
Therefore, RNG players will see that the Ping value is about 37ms, while the scene sees about 24ms, but the actual delay of is the same**
Emmm, the answer is self consistent.
But you may not believe it. This explanation was added to the announcement after everyone found the 22ms problem.
One of the most powerful evidence is that when the official first issued the announcement, the senior brother of the former professional player doublelift read it live, and there would be no such message at all.
In the end, the fist added the updated logo to the announcement, and the concurrent microblog indirectly admitted it.
Last night, it finally issued a technical report on the delay problem.
Shichao gives you a brief summary.
In order to ensure the same delay, there are two methods
Either put the game server between China and South Korea, or use the delay tool..
Because the Yellow Sea is between China and South Korea, it is too difficult to put the server there..
So I decided to use the delay tool
Its principle is to continuously measure the delay of each player, add the delay in real time, and keep the delays on both sides equal.
You can think of it as a scale. For balance, it will keep both sides with a 35 ms delay
For servers from Shanghai to South Korea, the original delay is about 35ms, so RNG does not need this delay tool.
The delay of the on-site team is only 15ms. In order to ensure that their delay is the same as that of the RNG, the fist will add a delay of 20ms to them through the delay tool, so that both sides will be 35ms.
Here comes the problem..
There is a bug in this delay tool. It seems that 20ms is added, but it's more than that
In other words, the real delay of the on-site players is greater than 35ms**
Because only RNG family participated in the competition overseas, there was delay in the competition participated by RNG only, which is why only RNG wanted to replay..
Someone may ask, haven't you found such a big bug before? Can't you see it in the log?
The explanation given by fist is that because the code calculation is wrong, it is also wrong in the log. If you only analyze according to the original log, you really can't find the problem.
Green is the old monitoring data,
Red indicates new monitoring data ▼
Later, with a new monitoring method, it was found that the tool would delay about 13 MS, and finally fixed the problem..
However, their repair only adds an offset to the result
In other words, there is still a problem with the delay tool. It will still delay for 13ms.
Therefore, the fist just gives an instruction to keep the delay tool at 22ms. In this way, the delay of 13ms is exactly 35ms..
This is why you can see that the Ping of the on-site player is about 22ms, while the fist is actually 35ms.
About technology, about so much. Judging from logic alone, it can be established.
But Shichao wants to say that it doesn't matter what the truth is and whether 22ms is really equal to 35ms
I would like to ask, it is the most basic responsibility of the organizer to conduct a lot of debugging before the competition to ensure that there is no problem with all settings.
The bug of a tool is not found. It's not just for you to explain..
In addition, on May 11 (the second day of the competition), some players questioned the delay. Can we suspend the competition process first? In case there is a problem, we will stop the loss in time..
When the problem is really found out, take a pat on the thigh and decide to replay, isn't it a little taken for granted.
Most importantly, it can be seen from the microblog of RNG head coach that they still didn't know to replay in advance.
Obviously, the game will be played in 2 hours. As a result, I was told that the previous game did not count.
Will it hurt anyone?
Finally, the secret change announcement.
After 22ms, many netizens said they didn't know it in advance. If they didn't know it after 22ms, why didn't they change it to 35..
Shichao also thinks it's strange to do it.
In short, the various operations of the fist these days have lost credibility. The truth is not convincing enough.
Therefore, no matter how the logic of this technical description is established, there may not be many people who believe and care
RNG remote competition has been controversial.
Since the fist has made this decision, it should do its best to make the game as fair as possible.
We can see that it has made some efforts in this regard, such as trying to make the delay the same, and the whole process video monitoring makes RNG vacate the training room in advance and debug the equipment..
Just fair, but also based on respect.
RNG has always abided by the rules and cooperated with the official, but unexpectedly, it was asked to replay because of "fairness" in the end..
Although the RNG record after the replay did not change, even gala's five kills were staged again.
From the data, it seems that nothing has happened.
But everything has happened again.
As a company that has held many large-scale events, as a popular production team, and as the winner of the best game event in 2021.
The fist in the technical control, as well as the way to deal with the problem.
We should do better.