內容大致如下:
Dear Community,
First of all, we would like to apologize for the delay of our investigation. We sincerely thank you for your patience. We understand that a large part of our userbase is disappointed because of the lack of transparency and status updates. However, we can ensure you that it was the right decision when it comes to playing in the hands of Riot Games. Therefore, we cannot divulge too much information, because it may be used against us by Riot.
Over the past weeks, all previous League of Legends binaries have been re-checked for anything out of the ordinary. We have thoroughly checked the entire way LeagueSharp interacts with the League of Legends game servers. This is why the investigation took as long as it did. We are really sorry for any banned users that were affected, but please keep in mind that it is a penguin and fish game -- there is always a chance to get banned. We can't stress enough to refrain from cheating on accounts that you cannot afford to lose.
We noticed that a few things were not working as they should and we re-worked a large amount of code of LeagueSharp to make sure that everything fits our safety standards again. Note here that these flaws still exist in any other tools interacting with League of Legends. As far as we know, the actual injection is safe (where LeagueSharp connects to your game). We must emphasize that safety cannot be 100% guaranteed, but we will continue trying our best to reach the highest level possible. In the previous patches, several measures were taken to make the usage of LeagueSharp more safe. For example, by implementing a global humanizer in the core and randomizing everything around LeagueSharp itself, along with some other things that affect the way LeagueSharp interacts with the game servers. There is evidence to suggest that Riot Games started analyzing the network traffic and gave up fighting in the memory.
As you may have noticed, we have been pushing many core updates more frequently than ever before. These are all to modify LeagueSharp, such as "anti- anti-cheat" measures (this is just as a precaution), and other security features. Riot has worked to make it unclear when the bans will stop, which is typical in this penguin and fish game. We are still working on a more final and permanent solution to the server-sided detection issue. We believe that the bans will reduce in the next few weeks and that the only bans left would be ones that are delayed or flagged. Therefore, we hope that we have already found and fixed the issue. We recommend that you only script on smurfs, or accounts that you do not care about as much. Currently, it is just a matter of time until we know the future of LeagueSharp in relation to Riot. Please also keep in mind that every other cheat tool provider is being affected by bans because of the server-sided detection. However, it is not simply the tools, but the entire act of scripting. Overall, scripting in general is detected, not the tool. We do not know for certain what exactly is "detected" by Riot on the server-side. The majority of scripters and cheaters are still continuing to play without any bans. Only time will tell.
未來及展望
正如你們可能已經注意到,我們比以前比起來更新CORE的頻率是更高, 例如反編釋LOL的內核程划,以及其他L#的安全性問題,我們已有比以前更多的頻率去更新這些東西,我們仍然去努力解決雙向回傳數據和防止被偵測的問題. 我們建議大家暫時在未解決真正問題的幾個星期內,使用小號去使用LS,或者是不用那麼多明顯的腳本, 這也是我們早已會預料到的問題,這些事情也跟其他第三防軟件有密切的關係,不是只針對LS來做的,我們到現在也不太清楚RIOT的真正檢測方法, 而他們檢測到的是腳本而不是LS本身這個工具, 我相信各個用戶和腳本作者也非常努力去解決問題, 最後, 時間會給出答案的.
By 翻譯:clavin3ivan
