Siuhy Becomes Free Agent After Team Liquid Exit: 185 Maps and the Lesson of an Unstable IGL Seat

In July 2026, a short notice appeared on Team Liquid's internal communication channel. Kamil "siuhy" Szkaradek was leaving the Counter-Strike 2 roster, moving to free agency. No transfer fee was announced. No lengthy farewell statement was issued. The in-game leader seat was left empty, and Johnny "JT" Theodosiou was promoted to fill it. For most Counter-Strike viewers, this is an ordinary roster move in a season where teams constantly shuffle their lineups. But one figure made me pause when I read the report: a 0.87 rating across 185 professional maps in a Liquid jersey. That is a low individual output for any player at the top level of world competition, let alone an in-game leader once considered one of Europe's most promising tactical callers. I do not trust intuition; I trust numbers that speak after being asked the right questions. And 185 maps is a sample large enough that it cannot be explained by luck or a handful of poor matches. The question is not whether siuhy played badly. The question is: what happened over 16 months that turned a loan deal from MOUZ into a one-line notice of free agency, with no fee recovered. To understand this story, it must be placed in the broader context of Team Liquid in the Counter-Strike 2 era. Before siuhy arrived, the roster had gone through two different leadership phases. Casper "cadiaN" Møller once held the in-game leader role. Russel "Twistzz" Van Dulken later took over. Both were respected names, but neither created lasting stability across multiple seasons. In April 2026, siuhy joined Liquid on loan from MOUZ. This was a notable move because MOUZ is one of Europe's top organizations, where siuhy built his reputation as a young tactical caller capable of organizing play and exploiting opponent weaknesses. The Pole, then in his mid-twenties, was expected to bring the tactical structure Liquid had lacked for years. An NA organization borrowing a European in-game leader is a sign of a trend that has existed for years. Liquid, alongside other North American teams, has grown increasingly dependent on imported talent from Europe to fill strategic positions. This is a point I will return to later, because it speaks not just about one player but about the structure of an entire region. When siuhy arrived, Liquid was still seen as one of the financially strongest organizations in Counter-Strike. Facilities, coaching staff, and talent acquisition capability were all at a high level. The expectations placed on siuhy were significant: to return the team to Major playoffs, where the organization had once been a familiar presence. But expectation and outcome are two parallel lines. Over the next 16 months, Liquid went through three Majors without a single playoff appearance. At the most important events, the team's record was five wins and eleven losses. The best result achieved was a top-four finish at FISSURE Playground #2, a mid-tier third-party event. In July 2026, Liquid's coaching staff benched siuhy. JT, an internal name, was brought in to replace him as in-game leader. This was the third leadership change in the team's CS2 era, and the fourth counting JT. Let us start with the central figure. A 0.87 rating across 185 maps. In Counter-Strike 2, rating is a composite metric measuring a player's individual contribution through kills, assists, and survival in each round. A level of 1.00 is considered average. 0.87 sits significantly below average, and this is a low mark even compared to other in-game leaders. Fairness is required when reading this figure. The in-game leader role usually carries a cost in individual statistics. The tactical caller must focus on coordinating the lineup, reading situations, and making decisions within short time windows. They often play support positions, using smoke and flash grenades more than seeking kills. A caller with a 0.95 or 0.97 rating is therefore considered acceptable if the team wins. But 0.87 is low even after accounting for the role discount. Across 185 maps, this is not a poor form stretch. This is a sustained pattern. The issue is not that siuhy played badly in a few matches, but that his individual contribution was systematically low throughout his time in a Liquid jersey. This is a signal analysts cannot ignore. This leads to a question about role valuation. In modern Counter-Strike, the in-game leader role has gradually shifted toward a model of fragging-capable leadership. Top teams increasingly expect the tactical caller not only to make correct decisions but also to win individual duels. The list of today's top in-game leaders shows a clear trend: they typically sustain ratings around 1.00 or higher. An in-game leader with a sub-0.90 rating, even accounting for the role factor, sits at the lower edge of what top teams can tolerate. This is an inference about role valuation, not an absolute conclusion. But it provides a framework for reading the rest of the story, and for understanding why Liquid chose a different path. Now place that figure beside the collective results. Three Majors, no playoff appearance. At the most important events, a record of five wins and eleven losses. The best result was a top-four at FISSURE Playground #2. The structure of the Majors must be understood to read these numbers accurately. Valve-organized Majors typically use a Swiss group stage combined with single-elimination playoffs. The Swiss stage is mainly played in best-of-one format, while elimination or advancement matches shift to best-of-three. The playoffs are best-of-three, and the final is best-of-five. The best-of-one format in the Swiss stage increases variance. A team can lose because of a few unfavorable situations in a single map. This is why Majors often produce upsets. But variance explains only part of it. Failure to reach playoffs across three consecutive Majors cannot be attributed to the luck of a best-of-one format. It reflects a systematic failure to convert at the highest-tier events. This is a sample wide enough to exclude randomness, and long enough to show a trend rather than a single event. Compare this with the top-four finish at FISSURE Playground #2. This is a mid-tier third-party event, with competition significantly below Major level. A team achieving its best result at such an event while failing to reach Major playoffs reveals a performance ceiling far below the organization's expectations. Both the floor and ceiling of Liquid underperformed the brand. Notably, these three Majors likely span 2026 to 2026, consistent with siuhy's April 2026 arrival. If so, Liquid missed playoffs in essentially every Major of the siuhy era. This is a sample wide enough to exclude randomness, and to raise questions about the nature of the problem. Now examine the contract structure. siuhy arrived at Liquid on loan from MOUZ, not on a permanent buyout. This is a financially important detail. Loan deals typically mean the receiving team does not own the player's economic rights. If the team wants to keep the player long term, it must negotiate a buyout fee with the parent club. When siuhy moved to free agency, Liquid recouped no transfer fee. This is a key point. In the professional esports business model, players are assets. A team can buy a player for X, develop him, and sell for Y. The difference, Y minus X, is the value the team created. With a loan deal, this model changes. The receiving team does not own the asset. It pays a loan fee and salary but holds no right to sell. Between the transfer numbers lies a story that never makes the report. The story here is: Liquid invested 16 months of salary and loan fees into an in-game leader and ended with a free-agency notice and no recovered fee. On the books, this is a recognized loss. On cash flow, releasing a highly salaried player is a positive move. Liquid cut wage costs without paying a buyout fee. The problem lies elsewhere. Releasing siuhy does not resolve the vacant in-game leader seat. This is an opportunity cost. The team needs a new tactical caller, and finding a suitable candidate takes time. In that window, the team may enter the next event with an improvised lineup. This is a time-bound competitive risk, and it does not disappear simply because a notice was posted. Look at the roster structure. JT, promoted as the replacement, is an internal candidate. This is not the product of a planned in-game leader search. It is a reactive move, following siuhy's benching. This sequence, from benching to internal promotion, suggests a team managing a situation rather than executing a long-term strategy. This is an important distinction in roster governance. This leads to an observation about the leadership model. siuhy is the third leadership figure referenced in Liquid's CS2 era, after cadiaN and Twistzz. JT is the fourth. This is an in-game leader carousel problem, not a single-player problem. A team changing leaders four times in one era is a team that has not solved the question of system identity. The tactical caller is not merely the in-match decision-maker. They are the architect of how the team plays. They set tempo, allocate resources, and establish engagement principles. When the leader changes, the entire system must be rebuilt. Four rebuilds in one era mean the team never had enough time for one leader's system to mature. Each change resets the clock to zero. This is a self-reinforcing loop: the team changes leaders because results are poor, but constant change prevents better results. This is a pattern I have observed many times in team sports. It appears not only in Counter-Strike. It appears in football, in basketball, and in any sport where the leadership role requires time to build relationships and systems. Now consider the regional context. Liquid is one of North America's flagship Counter-Strike organizations. But borrowing a Polish in-game leader from MOUZ reveals a structural reality: North America cannot self-supply enough top-tier in-game leaders. This is a reversal of historical patterns. For years, North America was a talent-import market, but mainly in fragging positions. A flagship organization borrowing a tactical caller from Europe signals that the talent gap has widened into strategic positions as well. This is reinforced by the broader context. In the same period, 100 Thieves, another NA organization, was also rebuilding its Counter-Strike roster. Two flagship organizations in one region shuffling rosters simultaneously indicates a wave rather than an isolated event. One detail in this story is often overlooked. A Dust2.us report described Liquid as having several strong pieces around siuhy. This is an important data point, and it raises a question about causation. If Liquid truly had several strong pieces, why could the team not reach Major playoffs? There are two readings. The first: siuhy lacked the ability to turn strong pieces into a winning system. The second: those strong pieces were not as strong as believed, and siuhy was blamed for a collective failure. A mistake years ago taught me that data never lies, only the reading is wrong. The 0.87 rating is real data. But it does not automatically prove siuhy was the sole cause of failure. This is a question of correlation and causation. In sports data analysis, we often commit a basic error: when two events occur together, we assume one causes the other. A low rating and poor team results occur together. But this does not prove the low rating caused the poor results. Both may be symptoms of a deeper problem. What is that deeper problem? It could be roster instability. It could be a competitive culture gap between a European in-game leader and an NA lineup. It could be pressure from coaching staff or management. There is insufficient data to identify the root cause. This is why I always annotate a confidence level for each claim in my writing. The claim that siuhy had low individual output carries high confidence, based on 185 maps. The claim that siuhy was the primary cause of failure carries medium confidence, due to missing data on other factors. This distinction matters. It prevents us from turning a correlation into an absolute conclusion, and it forces us to acknowledge the limits of the data model. Consider another possibility. In a tactical system, the in-game leader makes the decisions. But decisions only have value if the other members execute correctly. If a team has problems with individual discipline, duel-winning ability, or position-holding, even the best in-game leader cannot save it. In Liquid's case, there is a notable signal. The team changed in-game leaders four times in one era. If the problem lay in the in-game leader position, constant change should have led to improvement. It did not. This suggests the problem lies elsewhere, or in several places at once. Another possibility to consider is the role of the coach. In Counter-Strike, the coach is responsible for building the tactical system, preparing for opponents, and managing team psychology. If the system does not work, responsibility does not rest solely with the in-game leader. However, information about Liquid's coaching staff is not referenced in the report. This is a data gap I cannot fill with speculation. One more point deserves consideration. In Counter-Strike 2, there is no meta-reset mechanism as in MOBA titles. Valve's updates occur at a much lower frequency than games like League of Legends or DOTA 2. This means professional teams are less affected by major meta shifts. The consequence: if Liquid's failure was tactical, it will not appear in a patch analysis. It must be diagnosed as a strategy and leadership problem. There is no patch to blame. This also means roster changes in Counter-Strike are less influenced by external factors. When a team changes players, it is usually a decision based on internal assessment of synergy, not a reaction to a game change. In Liquid's case, releasing siuhy is a decision purely about people and systems, unrelated to any factor from the publisher. Looking ahead, several signals deserve monitoring. The first is who will sit in Liquid's in-game leader seat. If the team signs a big name, the story will be reframed as an upgrade. If JT is retained, it will be a temporary solution. Time will reveal whether Liquid has a clear plan or is merely reacting. This is a question whose answer will appear within months. The second is siuhy's next destination. As a Polish player with a MOUZ past, he will likely return to Europe. A mid-tier European team needing a system-builder could be a suitable destination. This will be a test of whether the problem lay with the player or the environment. If siuhy succeeds at a European team, the story will be reread differently. If he continues to fail, the evidence will lean toward individual capability. The third is the broader North American trend. Liquid and 100 Thieves restructuring simultaneously indicates a wave. If NA organizations continue importing and recycling European talent without addressing structural problems, the gap with Europe will keep widening. This is a trend I have tracked for years, and it shows no sign of reversal. Esports does not need luck; it needs people who read the meta faster than the servers. But reading the meta is not just reading patch notes. It is reading an organization's structure, the history of its decisions, and the data patterns people often overlook. siuhy's story at Liquid is a lesson about how individual talent cannot compensate for an unsolved system. 185 maps and three Majors without playoffs is a sample wide enough to say something. The remaining question is: how will Liquid read that sample, and will it read it correctly? Every season is a ritual, and the analyst is merely the one who records the omens. In this case, the omens were recorded long ago: a team changing leaders four times in one era is a team searching for something it has not yet named. siuhy's departure does not end the story. It merely moves the story into a new chapter, where the central question remains unanswered.