Spectator Glitch That Got CS:GO Coaches Banned Is Back
Counter-Strike: Global Offensive (CS:GO) is never a title to stray away from controversy, as much as it would like to, despite having one of the more professional leagues, developers, and tournament organisers assisting in its upkeep.
Recent events have placed CS:GO back under the microscope, with Ninjas in Pyjamas' loss versus Anonymo being replayed due to NiP's outrage at the connectivity issues. The organisation called out Flashpoint for not finding a solution to their packet-loss server issue, which the TO's ruled a rematch, much to the dismay of Anonymo and the wider community.
However, just as the community allows the ruling to fade from memory, another of their controversies has resurfaced.
The ESIC investigations that banned 37 coaches from CS:GO tournaments has now hit the headlines again, as it appears the game-breaking glitch the landed the coaches in hot water seemingly still exists in the game.
CS:GO Spectating Glitch
Former Virtus.pro, mousesports, and HellRaisers coach Sergey "lmbt" Bezhanov found that the spectating mode still exists, calling on Valve and ESIC to intervene.
Imbt was originally caught up in the wave of bans, sanctioned to a 7.5 month-long spell on the sidelines, before lodging a successful appeal. The coach was cleared of wrongdoing three weeks after the bans were enforced, allowing him to return to duties.
Seemingly hoping that the glitch doesn't put his career in any more jeopardy, the coach has highlighted that other coaches and players can still access these game-breaking glitches.
Will Valve fix the spectators glitch?
The spectator bug was originally removed from the game back in September, upon the conclusion of ESIC's investigations.
However, Veteran CS:GO referee, Michael Slowinski, previously cast speculation that more bugs of a similar nature may be prevalent. Speaking on a podcast following the bans, Slowinski said: "Unfortunately I think there might be more. I think there might be two more different instances that we are looking into right now."
With the bug being highlighted again, and a $1,000,000 event coming up in two months time, Valve will now be forced to take another dive into the backend and rectify the bug.
Image via Valve
