ALGO Disband, FACEIT Bans 12K Smurfs in CS2 Week 30 News
Ukrainian org ALGO has stepped away from Counter-Strike 2, while FACEIT dropped a massive smurf ban wave and patched a spawn bug flagged by STYKO.
ALGO Call It Quits
The Counter-Strike 2 scene lost another organization this week. Ukrainian outfit ALGO announced they are disbanding their roster and, as reported by HLTV, stepping away from the discipline entirely. It is a quiet end for a team that had notable names pass through its ranks over the years, including Tomáš “oskar” Šťastný, Simon “KWERTZZ” Horák, and Hubert “szejn” Światły.
The roster that was active at the time of the announcement consisted of Žygimantas “nukkye” Chmieliauskas, Andreas “aNdu” Maasing, Kacper “Bambosh” Szlachta, Adelin “adeX” Nica, and coach Oleksandr “Shara” Hordieyev. All five are now without a team. ALGO ranked 133rd in the world at the time of disbandment, according to HLTV’s data, so the competitive ceiling was always going to be a hard conversation for ownership to have. Still, any time a team of five people loses their professional home, it stings.
FACEIT Drops the Hammer on Smurfs
For anyone who has ever ground out a FACEIT match only to get stomped by someone with a suspiciously fresh account, this one is for you. FACEIT announced a major wave of smurf bans, and the numbers are genuinely striking. According to the platform, 12,478 accounts have been banned for smurfing and multi-account abuse, through what FACEIT described as “new detection methods that now run automatically,” as reported by HLTV.
The more meaningful figure might actually be this: 20 million Elo has been restored to 544,098 players. That is a lot of people who were quietly dragged down the rankings by accounts that had no business being in their lobbies. Automated detection running continuously rather than in periodic manual sweeps is the kind of structural fix that, if it holds, could change the daily experience of casual competitive play more than any map update.
STYKO Finds a Spawn Bug, FACEIT Fixes It Fast
FAEIT also had a different kind of fire to put out this week. Martin “STYKO” Styk posted a video on X demonstrating a spawn bug with real competitive implications. As HLTV reported, spawn locations were not being randomized after the knife round, which opened up a specific exploit: if your team won the knife round while playing on T-side and then switched to CT, you would know exactly where your opponents could spawn on the pistol round and position accordingly.
Anyone who has played enough Counter-Strike knows how much a single spawn location can dictate the first fifteen seconds of a round. FACEIT moved quickly, and the bug has been fixed. Credit where it is due on the turnaround time, and credit to STYKO for surfacing it publicly rather than quietly exploiting it.
Liquid Navigate a Scheduling Crunch
Team Liquid find themselves in a scheduling puzzle heading into the end of the month. Coach Viktor “flashie” Tamás Bea laid out the situation in a post on X, as covered by HLTV. Liquid are scheduled to play their BLAST Bounty series match on July 30. The outcome of that match determines their next move entirely.
A win in the Bounty series means they exit Stake Pulse Beat. A loss in Malta sends the team on a flight to Stockholm by July 31, where they will have one full day to recover and prepare before their first Stake Pulse Beat match on August 1. It is the kind of logistical scenario that coaching staffs quietly dread, and flashie putting it out publicly at least sets expectations with fans before anything goes sideways.
Why did ALGO disband their Counter-Strike 2 roster?
According to HLTV, Ukrainian organization ALGO announced they were disbanding their roster and stepping away from the discipline. No specific reason was given beyond that statement.
How many accounts did FACEIT ban for smurfing?
As reported by HLTV, FACEIT banned 12,478 accounts for smurfing and multi-account abuse, and restored 20 million Elo to 544,098 players in the process.
What was the FACEIT spawn bug that STYKO discovered?
According to HLTV, Martin 'STYKO' Styk shared a video on X showing that spawn locations were not being randomized after the knife round. The bug was especially exploitable when a team won the knife round on T-side and switched to CT, allowing them to predict enemy spawns. FACEIT has since fixed the issue.
How is Team Liquid handling the scheduling conflict between BLAST Bounty and Stake Pulse Beat?
As explained by Liquid coach Viktor 'flashie' Tamás Bea in a post on X, if Liquid win their Bounty series match on July 30 they will exit Stake Pulse Beat. If they lose in Malta, they travel to Stockholm on the 31st and get a full day to prepare before their first Stake Pulse Beat game on August 1.