{"id":38114,"date":"2025-01-28T16:11:08","date_gmt":"2025-01-28T16:11:08","guid":{"rendered":"https:\/\/dejan.au\/index.php\/2025\/01\/28\/esic-says-it-would-not-have-banned-hunden-under-different-circumstances-dexerto\/"},"modified":"2025-01-28T16:11:08","modified_gmt":"2025-01-28T16:11:08","slug":"esic-says-it-would-not-have-banned-hunden-under-different-circumstances-dexerto","status":"publish","type":"post","link":"https:\/\/dejan.au\/index.php\/2025\/01\/28\/esic-says-it-would-not-have-banned-hunden-under-different-circumstances-dexerto\/","title":{"rendered":"ESIC says it would not have banned HUNDEN under different circumstances &#8211; Dexerto"},"content":{"rendered":"<p>ESIC says it would not have banned HUNDEN under different circumstances Valve \/ ESICThe Esports Integrity Commission (ESIC) has shed more light on the two-year ban handed to Counter-Strike coach Nicolai \u2018HUNDEN\u2019 Petersen for a breach of its integrity program. The esports watchdog group revealed on August 27 that HUNDEN had been slapped with a two-year ban after sharing documents from his then team, Heroic, with a competitor ahead of IEM Cologne. In the report of its findings, ESIC said that HUNDEN was locked in talks with the opposing side \u2014 whose name was not disclosed \u2014 about a career move when he shared the documents, with both teams set to attend IEM Cologne, the first international Counter-Strike LAN event during the global health crisis. This, according to the esports watchdog, threatened \u201cthe integrity of an ESIC member event\u201d, the \u201creputation of an ESIC member\u201d, and \u201cthe reputation and competitive integrity of esports, and ESIC\u2019s member ESL.\u201d And it was because of these special circumstances that ESIC saw the case as more than a labor dispute between a company and an employee, and decided to intervene. \u201cIn any circumstance other than those surrounding Mr. Petersen\u2019s conduct (see our release for the specific dot points that set these out \u2013 but specifically the timing and context of his action), ESIC would not have acted to impose a sanction,\u201d ESIC explained when contacted by Dexerto. Ban details The length of HUNDEN\u2019s suspension has been criticized in some quarters given the lack of precedence and the fact that he was previously banned for half that period for abusing the spectator bug \u2014 an offense that many would say is more serious than the sharing of information with a rival team. However, ESIC insisted that the two cases are very different and, as such, should be looked at separately from one another. \u201cESIC takes any threat to the integrity of a member event very seriously,\u201d the esports watchdog said. \u201cMr. Petersen\u2019s conduct posed a significant threat to a member\u2019s major tournament, which had the effect of potentially undermining the competitive integrity of the match in question but secondly and consequently the whole event. \u201cESIC\u2019s sanction is a precedential statement of the severity of misconduct around and leading up to an ESIC member event. \u201cThis is not in any way comparable to a historical examination of coaching bug abuse, which was conducted with a comparative sanctioning model involving many other offenders.\u201d With HUNDEN being a second-time offender, many have wondered whether his past transgression was taken into account when the length of his new ban was determined. But according to ESIC, HUNDEN\u2019s previous offense \u201cwas considered but not applied in the sanctioning process as a result of a plea bargain offer.\u201d This explains why the esports watchdog said in its report that, if HUNDEN rejected a plea deal and decided to appeal against the ban, he risked \u201ca more onerous sanction at the discretion of the Independent Appeal Panel.\u201d Reopening the bug case On August 26, HUNDEN made a shocking claim that \u201csome of the players\u201d on Heroic were aware that he was using the spectator bug. In his first version of the story, HUNDEN had claimed to have acted \u201con my own, without the knowledge of my teammates.\u201d CS:GO analyst Jacob \u2018Pimp\u2019 Winneche has said that it is \u201chighly probable\u201d that HUNDEN is now telling the truth after seeing evidence obtained by TV2.dk that seems to support the coach\u2019s new claims. Coach bug scandal \ud83d\udea8 Hunden claims that the heroic players also was involved and aware of his cheating in the coach bug scandal. I\u2019ve been presented the material the article is based on. My judgment is that it\u2019s highly probable he\u2019s telling the truth.https:\/\/t.co\/8SaJGgqrl1 \u2014 Jacob \u201cPimp\u201d Winneche (@PimpCS2) August 26, 2021 ESIC did not rule out reopening the spectator bug case if new information comes to light, but it stressed that it had not yet been presented with the evidence mentioned by Pimp and TV2.dk. Read more: Guild CEO considering entering CS:GO &#8211; \u201cNo information has been received to date,\u201d ESIC said. \u201cIn the case that information is received, ESIC will investigate. ESIC is awaiting any evidence from any source that would enable ESIC to proceed.\u201d<\/p>\n","protected":false},"excerpt":{"rendered":"<p>ESIC says it would not have banned HUNDEN under different circumstances Valve \/ ESICThe Esports Integrity Commission (ESIC) has shed more light on the two-year ban handed to Counter-Strike coach Nicolai \u2018HUNDEN\u2019 Petersen for a breach of its integrity program. The esports watchdog group revealed on August 27 that HUNDEN had been slapped with a [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-38114","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/38114","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/comments?post=38114"}],"version-history":[{"count":0,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/38114\/revisions"}],"wp:attachment":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/media?parent=38114"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/categories?post=38114"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/tags?post=38114"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}