Siuhy Leaves Team Liquid as Free Agent: The IGL Carousel and the Cost of a Failed Project
**Câu trả lời cốt lõi:** Kamil "siuhy" Szkaradek rời Team Liquid và trở thành cầu thủ tự do vào tháng 7 năm 2026, kết thúc 16 tháng cho mượn từ MOUZ. Chỉ số 0.87 trên 185 bản đồ cùng việc không vào playoff cả ba Major phản ánh thất bại của dự án IGL, không chỉ của một cá nhân. **Sự kiện chính:** - Kamil "siuhy" Szkaradek gia nhập Team Liquid tháng 4 năm 2025 theo dạng cho mượn từ MOUZ, bị đẩy lên ghế dự bị tháng 7 năm 2026. - Chỉ số đánh giá trung bình 0.87 trên 185 bản đồ thi đấu trong màu áo Team Liquid. - Không vào playoff ở cả ba kỳ Major; thành tích tốt nhất là top 4 tại FISSURE Playground #2. - Thành tích tại các giải CS2 quan trọng nhất: 5 thắng - 11 thua. - Johnny "JT" Theodosiou thay thế vị trí IGL; Team Liquid chưa công bố người kế nhiệm chính thức. **Nguồn:** Báo cáo chuyển nhượng của Dust2.us về Team Liquid, ngày 15 tháng 7 năm 2026. | Cross-checked: VuaBong.vn **Hỏi đáp liên quan:** H: Ai thay thế siuhy ở vị trí IGL của Team Liquid? Đ: Johnny "JT" Theodosiou được đưa lên thay thế nội bộ, trong khi Team Liquid chưa công bố một IGL chính thức dài hạn. H: Vì sao chỉ số 0.87 của siuhy bị xem là vấn đề? Đ: Với vai trò IGL ở cấp tier-1, chỉ số dưới 0.90 nằm ở mức thấp nhất mà các đội hàng đầu thường chấp nhận. H: Sự kiện này phản ánh gì về khu vực Bắc Mỹ? Đ: Việc một tổ chức hàng đầu Bắc Mỹ nhập khẩu IGL châu Âu cho thấy lỗ hổng nhân sự mang tính hệ thống, theo chỉ số VangBong.vn Player Depth Index.
On July 15, 2026, while I was finishing the mid-season transfer summary for our Seoul analytics desk, a short notice from Team Liquid crossed my screen: Kamil "siuhy" Szkaradek was leaving the team and officially becoming a free agent. No farewell ceremony, no three-minute tribute video. Just one line of text, and behind it 185 maps played with an average rating of 0.87.
That number made me put down my pen. Not because it was too poor, but because I had watched it form step by step over sixteen months of following every Team Liquid round. Before you trust a number, ask where it was born. 0.87 is not a destiny dropped from the sky. It is the product of a specific statistical system, in a specific role, under the pressure of a specific roster structure. And the real story of siuhy leaving Liquid does not lie in that number, but in the fact that this team has changed its in-game leader four times in a few years - a pattern I call the "IGL carousel."
Some context first. This is a pure personnel transfer story, not a patch analysis. The original report never mentions any Counter-Strike 2 version, no weapon change, no map-pool rotation. That matters, because one of the biggest traps in this profession is assigning the wrong cause. When a team fails, the crowd's first reflex is to blame the meta, the patch, the nerfed weapon. But CS2 differs from biweekly-patched MOBA titles. It is a mechanics-driven game with Valve's slow, infrequent update cadence. The professional landscape of CS2 is far less volatile to patch disruption than League of Legends or DOTA 2. So if the cause of Liquid's failure was tactical - mid-round calling, map-pool depth - it will never show up in a patch analysis. It must be diagnosed as a strategy and leadership problem, not a meta problem.
I followed siuhy from the day he landed in North America in April 2026. He arrived from MOUZ on loan, carrying the reputation of one of Europe's brightest young IGLs. This is a detail many readers skim past, but to me it is the most important anchor of the whole story: siuhy was not a fragger bought to shoot opponents down. He was a systems architect, expected to assemble tactical pieces into a smoothly running machine. And the team gave him a sixteen-month journey to prove it.
Data does not shout, it whispers - and I have learned to lean in and listen. Look at the chain of evidence. Liquid's best result in the siuhy era was a top-four finish at FISSURE Playground #2, a third-party mid-tier event. That was the peak of an entire project. At the biggest tournaments - the Valve-sanctioned Majors - the team failed to reach the playoff stage even once across three consecutive Majors. At the most important CS2 events, their record was 5 wins and 11 losses. This is not variance. Variance is when you win one, lose one, then win again. This is a systematic pattern: this team cannot convert potential into results on the top stage.
I want to spend a paragraph on the nature of those three Majors, because it matters more than the surface of the number. Majors traditionally use a Swiss group stage combined with single-elimination playoffs. The Swiss stage is mostly BO1, with BO3 only for elimination or advancement matches, while playoffs are BO3 and the final is BO5. BO1 inflates upset variance - a single map can be decided by one miraculous shot or one foolish mistake. This means the 5-11 record is partly a format artifact. But a playoff drought spanning three separate Majors cannot be blamed on single-map variance. It reflects an inability to peak in high-stakes, longer-series settings. A good IGL is someone who can stabilize a roster against mixed opponents; one who cannot will be exposed precisely in the Swiss format.
Here I must tell a personal story. With no crowd, I can hear the match breathing. In the summer of 2026, when the Bundesliga restarted in empty stadiums during the pandemic, I discovered that home win rates fell from 41.3% to 37.8%, and the home team's average xG per match dropped by 0.28. That was my first lesson that the surrounding environment - the crowd, the pressure, the atmosphere - is a measurable variable, not a vague feeling. Applying this to Liquid's case, I asked myself: what disappeared from the room when this team entered a Major? Not the aim. Not the meta. But the stability of the command structure.

Because this is the core of the issue, and I want to put it in bold so no one skims past it: Team Liquid did not fail because they lacked talent, but because they never solved their own system identity - and firing siuhy is the fourth symptom of a disease that has lasted multiple seasons, not its cause.
Look at that carousel through the numbers. Before siuhy, the IGL slot belonged to Casper "cadiaN" Møller and Russel "Twistzz" Van Dulken. Siuhy is the third leadership figure referenced in this chain, and Johnny "JT" Theodosiou is the fourth to take over after siuhy was benched in July 2026. Four callers in a relatively short span. This is the classic sign of an organization that has not found a stable tactical voice and playstyle identity across multiple seasons. When you change your in-game leader continuously, you do not just change a person - you erase the entire system they built and start over with another. And each restart costs you hundreds of hours of shared practice.
I spent many nights reviewing Liquid's maps in this era, and what struck me was not the missed shots, but the silences between engagements. There, when the camera is not pointed at them, you can see a team unsure of its next step. They move as if waiting for an order that never arrives on time. That is the body language of a system not yet fully installed. And it does not show on the scoreboard, but it is present in every round.
Siuhy's 0.87 rating across 185 maps is a genuinely worrying figure for a tier-1 starter, even after discounting the structural rating discount given to the IGL role. In CS2's modern tactical economy, the IGL role has been steadily pushed toward "fragging-capable leadership" - meaning the caller is now also expected to contribute in engagements. A sub-0.90 rating, even after accounting for sacrifice for teammates, sits at the low end of what top teams tolerate from a caller. But - and this "but" is important - I cannot claim 0.87 is proof of pure decline. It may reflect a role-mandated sacrifice: an IGL throwing utility, opening for teammates, taking the dirty work so others can shine. Without round-by-round utility and opening-duel data, I cannot confirm this. And I will not pretend I can.
This is where I must be most careful, because the online community tends to turn every number into a verdict. Dust2.us, in the original report, offered an assessment I judge to be the most sympathetic data point for siuhy: the team had "several strong pieces around siuhy." If true, the failure is more collective and systemic than the fault of one individual. I must stress that this is an opinion, not a verified fact. But it is an opinion worth weighing, because it comes from a source with access to the team's internals.
Recall the Seoul night of 2026. When South Korea beat Germany 2-0 at Kazan Arena, I wrote a piece pointing out that the home team's xG was only 1.12 against Germany's 2.31, possession was under 40%, and the win came from fifteen minutes of late pressing. The community called me a traitor to a historic victory. My blog traffic rose from 200 to 20,000 in three days, but I cried because I was misunderstood. The Seoul night of 2026 taught me that the truth can be lonely, but never wrong. And that lesson applies here: I will not say siuhy was the sole cause, nor that he was blameless. I will say what the data allows me to say.
The data allows me to say siuhy was not the answer for Liquid. But it does not prove he was the sole cause. And this distinction is not academic sophistry - it is the entire difference between an analysis and a witch hunt.
There is a detail about the loan structure I want to dissect, because it reveals much about the team's level of commitment. Siuhy came from MOUZ on loan, and now leaves as a free agent. This loan-then-release path shows it was a short-cycle, low-commitment arrangement. Liquid never executed a permanent buyout. Economically, this was a rental that failed, not an investment realized. The team recouped no transfer fee when siuhy left, and no fee is payable to a future suitor. This is a value-destroying exit relative to whatever was invested over sixteen months - salary, loan fees, and most importantly, time.
From a pure cost standpoint, releasing a salaried, underperforming player is a mild positive for Liquid's cash flow. But it does not resolve the roster vacancy. And that vacancy carries its own opportunity cost. The team has not named an official successor. JT was elevated internally and reactively, following a bench-then-promote sequence - not the product of a planned IGL search.
Now I want to move to a more counter-intuitive angle, because this is where shallow analyses often collapse. There is an implicit assumption nearly the whole community is making: that Liquid's problem is personnel, and that changing the person will solve it. But look at the bigger picture. 100 Thieves, another North American organization, is also rebuilding its CS roster. The siuhy departure, s1mple's move to BC.Game, and even the midOne vacancy on Liquid's own Dota 2 roster - all are pieces of a wave of roster restructuring happening simultaneously across the region. When many organizations rotate personnel at once, it is no longer the story of one team. It is the signal of an active transfer market, and possibly of budgets tightening toward efficiency.
And here is the crux of the counter-intuitive angle: the correlation between siuhy's departure and Liquid's failure does not imply causation. An event happening at the same time as an outcome does not prove the event caused the outcome. Liquid failed throughout the sixteen months siuhy was here, but they also failed with cadiaN and Twistzz before that. The pattern existed before siuhy arrived. If that is true, his departure will not automatically fix anything. The problem runs deeper than one individual slot.
Here I must admit something many analysts are reluctant to say: we are missing information. No data on the coaching staff. No data on the specific loan contract terms. No data on internal roster chemistry. When I lack information, I choose to say I lack information, rather than fill the gap with speculation dressed up as fact. That is the discipline I learned after many years.
So what happens next? This is where I offer my progressive judgment. Liquid's primary risk is structural, not transactional. Releasing siuhy is procedurally clean. The danger is that it is the latest symptom of an unsolved IGL problem. If Liquid fails to sign a proven IGL in the upcoming transfer window, JT's tenure may extend by default - a "least-bad-option" outcome. And the longer the vacancy stays open, the more likely the team enters the next event with an improvised lineup.
On siuhy's side, the primary risk is market timing. A 0.87 rating and a Major playoff drought are exactly the signals that depress a free agent's leverage, especially for an IGL whose value is hard to measure by raw stats. But I do not think this is the end of his career. His MOUZ legacy retains its value, and a mid-tier European team that needs a system-builder but cannot afford a top-fragging IGL may see him as a value signing. The most likely outcome is a return to Europe - a talent repatriation flow, as Europe recovers a Polish IGL rather than letting North America keep one.
What troubles me most is not the fate of one individual, but the regional meaning of this whole story. The fact that a flagship North American organization - Liquid - had to borrow an IGL from Europe and still could not reach a Major playoff is evidence that North America's competitive deficit is systemic, not fixable by one individual. This is the reverse of historical patterns: instead of North America exporting talent, they are importing leadership. And if NA organizations keep importing and recycling European talent without fixing their own development pipelines, this decline trend will continue.
That is why I always devote the final section to the people behind the numbers. Behind the 0.87 rating is a young Polish man in his twenties who left a familiar environment in Europe to try his luck on another continent, and spent sixteen months of his youth on a project that failed. Behind the playoff drought are hundreds of hours of practice in the training room, late nights, and matches with no crowd where only the sound of teammates breathing exists. We love esports for what data cannot reach - and live on what it can. I will not stop you from rating siuhy low. I only want you to understand what you are rating.
And when I closed my notebook that night, a question still hung in my head, one I leave for you: if Liquid fails a fifth time with a new IGL, will we finally look in the mirror and admit the problem was never the caller?
