{"id":20016,"date":"2022-05-05T21:54:42","date_gmt":"2022-05-06T01:54:42","guid":{"rendered":"https:\/\/esportbet.com\/?p=20016"},"modified":"2022-05-06T12:54:27","modified_gmt":"2022-05-06T16:54:27","slug":"esic-ready-to-issue-charges-over-csgo-spectator-bug","status":"publish","type":"post","link":"https:\/\/esportbet.com\/esic-ready-to-issue-charges-over-csgo-spectator-bug\/","title":{"rendered":"ESIC ready to issue charges over CS:GO spectator bug"},"content":{"rendered":"

The Esports Integrity Commission (ESIC) has almost reached the end of a two-year investigation regarding the exploitation of spectator bugs in Counter-Strike<\/a>: Global Offensive (CS: GO) esports.<\/p>\n

The commission first caught wind of it in 2020, as coaches were using it to give their teams an unfair advantage in the game. Some 37 coaches were sanctioned for their role in using the bug, with bans ranging from a few months to three years.<\/p>\n

However, recent reports have revealed that a lot more CS:GO coaches could be in the firing line. When 37 coaches were sanctioned in 2020, only about 20% of the data had been analyzed.<\/p>\n

Although the commission is yet to reveal names, it said in a press statement that another 47 offending coaches had been uncovered, bringing the total number of culprits to 84.<\/p>\n

The ESIC has acknowledged that the investigations have taken a while, which prompted this release before sanctions are handed out:<\/p>\n

“While ESIC is aware that the Spectator Bug matter has been active for an extended period of time, it has been deemed necessary that ESIC make an interim release ahead of ESIC\u2019s upcoming enforcement activity in the public interest.”<\/p>\n

\n
\n

ESIC to Imminently Issue Charges Resulting From Historical Spectator Bug Investigation<\/p>\n

In the statement, ESIC identifies its intended treatment for three forms of Spectator Bug discovered which collectively impact 134 participants.<\/p>\n

Read on our website: https:\/\/t.co\/7VAkWjpKVd<\/a> pic.twitter.com\/aUMF39qOLH<\/a><\/p>\n

— ESIC (@ESIC_Official) May 5, 2022<\/a><\/p><\/blockquote>\n