{"id":27664,"date":"2023-01-20T13:38:17","date_gmt":"2023-01-20T18:38:17","guid":{"rendered":"https:\/\/esportbet.com\/?p=27664"},"modified":"2023-01-20T13:38:17","modified_gmt":"2023-01-20T18:38:17","slug":"blast-gives-reason-for-faze-clan-replacement-issues","status":"publish","type":"post","link":"https:\/\/esportbet.com\/blast-gives-reason-for-faze-clan-replacement-issues\/","title":{"rendered":"BLAST gives reason for FaZe Clan replacement issues"},"content":{"rendered":"

Tournament organizers, BLAST has admitted to miscommunication and lack of clarity in the recent replacement issues with FaZe Clan’s Counter-Strike: Global Offensive<\/a> stand-in position.<\/p>\n

The North American esports franchise had recently announced their decision to recruit the services of Kristian “k0nfig” Wienecke as a stand-in for H\u00e5vard “rain” Nygaard at the ongoing BLAST Premier Spring Groups tournament. The decision was birthed owing to rain’s earlier announcement of skipping the event as he anticipates the birth of his child.<\/p>\n

However, the franchise’s procurement of the Danish rifler was struck down by other teams, as they claimed that the 25-year old was listed on Heroic’s roster as a substitute and was not officially a member of FaZe Clan CS:GO roster. As a result, the tournament organizer denied the team’s emergency replacement with k0nfig, but the franchise insist they were given the go-ahead by BLAST.<\/p>\n

BLAST took to its Twitter<\/a> page to address the misunderstanding that trailed the CS:GO community with the BLAST Premier Spring Groups at hand. It explained the reason for the issue and took the blame, tagging it as a lack of clarity on its end.<\/p>\n

“We want to acknowledge the confusion that has transpired around the roster lock for the kick-off of the 2023 season,” the statement read.<\/p>\n

“At the beginning of the year FaZe Clan submitted a roster change for this week’s Spring Groups due personal reasons. FaZe requested the use of k0nfig, this request was denied as the player was registered on another team’s roster for the event. In that process there has been confusion around whether this subsequent emergency substitution request was formally accepted and validated by BLAST.”<\/p>\n

“After looking into the incident internally, we identified miscommunication and a lack in clarity from BLAST on roster lock timings and k0nfig’s eligibility to play in Spring Groups. This of course is not how we typically operate and we will be looking into strengthening processes and communication with teams, specifically around roster locks.”<\/p>\n

\n
\n

Update: BLAST Premier Spring Groups. pic.twitter.com\/BY30K32N1f<\/a><\/p>\n

— BLAST Premier \ud83d\udca5 (@BLASTPremier) January 19, 2023<\/a><\/p><\/blockquote>\n