StarCraft match rigging scandal is SERIOUS business - destructoid
Site layout weird? Try Ctrl-Shift-Refresh   |   Report a bug

StarCraft match rigging scandal is SERIOUS business

1:20 PM on 04.13.2010

Jim Sterling

Former Reviews Editor

You're familiar with that old trope, right? The one where a prize boxer agrees to "take a dive" in order for a mobster to win an illicit bet. Well, brace yourself for a real shocker ... not only does that clichéd plot device happen in real life, it's been going on in StarCraft. Yeah, that's right ... veteran players have been rigging matches in Blizzard's classic RTS. 

The most astounding thing about this affair isn't simply that players have been faking matches to benefit illegal gambling groups, but the fact this has rocked the South Korean gaming scene so thoroughly. They take their StarCraft seriously over there, and the busting of this racket has sent shockwaves through the pro gaming community. 

According to reports, "various pro gamers" were involved in the shady shenanigans, and a number of them have now been forced to shamefully retire in the wake of the scandal. Retired star players and coaches, as well as South Korea's e-sports organizers, have also been implicated. The organizers are alleged to have been aware of the cheating and tried to deal with it privately before suggesting that they actually work in conjunction with the illegal gambling rings. 

The huge controversy goes as high as "A-list" players like Ja Mae Yoon and has even been compared to the 1919 Chicago "Black Sox" affair. Only more geeky. Still, nerdy or not, this is a huge deal in South Korea right now and will likely have a considerable impact on its gaming scene. I'm just astounding a gambling racket for videogames ever existed.

StarCraft Cheating Scandal Rocks South Korea [Gamepron via 1UP]

Get comment replies by email.     settings



Unsavory comments? Please report harassment, spam, and hate speech to our comment moderators

Can't see comments? Anti-virus apps like Avast or some browser extensions can cause this. Easy fix: Add   [*].disqus.com   to your security software's whitelist.




Back to Top