{"id":37851,"date":"2025-01-28T16:09:21","date_gmt":"2025-01-28T16:09:21","guid":{"rendered":"https:\/\/dejan.au\/index.php\/2025\/01\/28\/csgo-pros-apex-and-s1mple-lock-horns-following-scrim-debacle-dexerto\/"},"modified":"2025-01-28T16:09:21","modified_gmt":"2025-01-28T16:09:21","slug":"csgo-pros-apex-and-s1mple-lock-horns-following-scrim-debacle-dexerto","status":"publish","type":"post","link":"https:\/\/dejan.au\/index.php\/2025\/01\/28\/csgo-pros-apex-and-s1mple-lock-horns-following-scrim-debacle-dexerto\/","title":{"rendered":"CS:GO pros apEX and s1mple lock horns following scrim debacle &#8211; Dexerto"},"content":{"rendered":"<p>CS:GO pros apEX and s1mple lock horns following scrim debacle StarLadder \/ apEX TwitterTensions between CS:GO stars Oleksandr \u2018s1mple\u2019 Kostyliev and Dan \u2018apEX\u2019 Madesclaire have flared up once again, this time after Natus Vincere apparently failed to show up to a scrimmage on time. Fans of the Global Offensive pro scene know that the space isn\u2019t without its dramas. While players tend to try to keep things within Valve\u2019s servers, disagreements can sometimes spill over onto social media. This time around, the two pros in question have had their history of Twitter jabs aimed at each other and neither one was backing down for the next installment in their publicized bout. In a June 27 post, apEX was clearly heated since his team\u2019s latest scrim partners had been late, and was not shy about shining the light on the org at fault. \u201cI wish a team could be on time at least once in a year,\u201d apEX said in a since deleted tweet. \u201cBut it feels like respecting the opposing team isn\u2019t normal. Natus Vincere.\u201d Not one to take a hit lying down, s1mple chimed in with a simple \u201cyes yes yes,\u201d which set apEX off. Fans think the Vitality pro\u2019s next reply was alluding to a comment made by s1mple in years past in a separate spat with apEX. \u201cBiggest r*tard on earth,\u201d apEX replied to s1mple. \u201cDon\u2019t tell (your) manager to come to me next event to shake hands.\u201d 600S1mple then pointed out that the comment seemed unwarranted: \u201cDo you understand what you just wrote? I respect you but don\u2019t disgrace yourself. Yes we were late but it\u2019s not a reason to start insulting me.\u201d The reply prompted two Vitality players in apEX and Alex \u2018ALEX\u2019 McMeekin to call out the CS:GO superstar for trying \u201cto be the victim,\u201d recalling a previous comment made by s1mple on private in-game servers. 600\u201cDidn\u2019t you say something else?\u201d apEX said, before repeating what s1mple had apparently typed in-game. \u201cSh*t player, sh*t person.\u201d \u201cDon\u2019t play this card on twitter man,\u201d ALEX said. \u201cSay what you said on the server and don\u2019t try to be the victim on Twitter.\u201d Don&#8217;t play this card on twitter man, say what you said on the server and don&#8217;t try to be the victim on twitter \u2014 Alex (@Vitality_ALEX) June 27, 2019 While the last comment by apEX sent fans in a flurry of confusion as to why he would burst out like that, the pro later clarified that he was simply reiterating what s1mple allegedly said prior. The entire spat didn\u2019t seem to end on a conclusive note of understanding or lament, but hopefully the pros settle their differences before their next matchup.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>CS:GO pros apEX and s1mple lock horns following scrim debacle StarLadder \/ apEX TwitterTensions between CS:GO stars Oleksandr \u2018s1mple\u2019 Kostyliev and Dan \u2018apEX\u2019 Madesclaire have flared up once again, this time after Natus Vincere apparently failed to show up to a scrimmage on time. Fans of the Global Offensive pro scene know that the space [&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-37851","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/37851","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=37851"}],"version-history":[{"count":0,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/37851\/revisions"}],"wp:attachment":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/media?parent=37851"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/categories?post=37851"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/tags?post=37851"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}