siuhy Free Agent: The Fifth Lap of Liquid's Four-Times-Rotated IGL Cycle

Hook

I still keep that VOD on slow-motion—a Major map, the fourteenth round of the second half. Click on the timestamp and you can see it: Kamil "siuhy" Szkaradek's hand rotating left and right through a low-APM round, not a single word in comms, and the individual rating curve in the corner tipping steadily downward. This is not a highlight; it is a frame of system failure. In the week of August 2026, Team Liquid confirmed that siuhy is no longer with the team—he is now a free agent. No transfer fee, no buyout; just an empty chair and an empty IGL role. The last brick of what collapsed across eighteen months came loose today, but the crack in the wall remains. My notebook says the first ankle tear wrote the notebook's first line; here, the first free-agent line was written by a shot-caller cycle that has already rotated four times.

Context: Who siuhy is, and what he brought to Liquid

You cannot weigh this release without knowing where siuhy came from. Kamil Szkaradek is a Polish IGL, raised inside MOUZ, one of Europe's top organisations. In April 2026 he arrived at Team Liquid on loan—a North American organisation whose CS roster in practice leans on European talent. This is a top-down talent flow where Europe exports and North America imports. Whether the loan ever became permanent was never made explicit; the endpoint, though, is clear—free agency, meaning zero fee. According to Dust2.us, there were "several strong pieces" around siuhy. That single line hides the real story: the problem was never a shortage of talent. It was a shortage of conversion.

Counter-Strike 2 (CS2) is a mechanics-driven, tactical FPS. Round economy, IGL shot-calling, rating-based performance measurement, and a Major-centric calendar all operate together here. Valorant-style franchising does not apply. As a result, roster failure in CS2 is usually not patch-driven; it is far more a story of shot-calling, individual form, and team chemistry. That is precisely what turns this release into a data question rather than an emotional narrative. The way I have taken notes on matches for six years—minute markers, round numbers, APM graphs—when applied to this event in slow motion, reveals something: the number of lost maps here is small, but the lost direction is large.

One thing must be made explicit—CS2's Valve patches are rare and large, not Riot-style biweekly updates. Structurally, that means Liquid's decline cannot be explained by a patch-targeted playstyle. Stage-1 information points 1 through 22 contain no reference to any version, patch, or mechanic change. So my answer on this dimension is a clean null-value declaration: insufficient information. I do not enjoy writing that, but writing it is my job. To cover a source limitation with patch theory is to lie to the reader.

Core Analysis: A 0.87 rating, 185 maps, and the history of a crack

Now to the hard numbers. siuhy's individual rating is 0.87 across 185 maps. In CS convention, 1.00 is the neutral baseline; 0.87 sits clearly below average. IGLs usually carry a slightly lower rating because they invest in calling, not frags—but 0.87 is low even by IGL standards. In my notebook I log numbers like this as a "vital sign"—not of the patient, but of the system. The question becomes: is the low output the man, or the system built around him?

The second number is crueller. Liquid played three Majors and reached the playoffs in none, with a 5-11 map record at Majors—a 31 percent map win rate. In CS2, the Major is Valve-sanctioned peak prestige, and those Majors run on a Swiss-plus-elimination format where the opening rounds are best-of-one (BO1)—the harshest possible environment for an unstable roster. The Swiss system pairs teams with identical win-loss records; any early-round shock reroutes the whole tournament. Zero playoffs across three separate Majors is not bad luck—it is a structural signal that broke in the same place repeatedly.

For comparison, another number. The best result across those eighteen months was a top-4 at FISSURE Playground #2—a third-party, lower-tier event. This is the classic "flat-track bully" pattern: effective at mid-tier events, exposed at the top. I recognise this pattern from athletics—the athlete who wins low-grade meets in good form but breaks in the final metres of a championship; their problem is not talent, it is load management and competitive pressure. Same here. FISSURE Playground's top-4 is not a consolation; it is a diagnosis—this team does not reach its ceiling.

Now to the actual crack—the IGL cycle. Within a short span Liquid rotated through at least four shot-callers: Casper "cadiaN" Møller → Russel "Twistzz" Van Dulken → siuhy → Johnny "JT" Theodosiou. In CS2, frequent IGL turnover is a classic marker of strategic identity collapse. Every new caller builds systems from zero—set-ups, defaults, executes, all anew. Chemistry takes time; four fresh starts mean chemistry never gets a chance to stabilise. To me this is cumulative damage, much like injury load—every reset cuts into what was previously earned.

A human context belongs here, because listening only to the autopsy of numbers misleads. Who bears the cost of this cycle? siuhy himself—a free agent whose résumé will now read 0.87 rating and zero Major playoffs; and JT, who inherits a failing structure mid-cycle. Calling is not just screen work—it is comms, strat-book, practice hours, pressure; a load that lands on the individual when the system breaks. Said in a cold forensic tone this sounds inhuman, so let me be plain: siuhy's release is his failure, but this cycle is bigger than him.

Now back to my signature method—the off-camera variables column. What the match frame does not show, I write separately, because VOD tunnel vision is my biggest trap. For this case the off-camera variables are: how full the practice lobby was, how complete the scrim blocks were, how much was said in comms, and how much was silence. The source contains none of this, so these stay in my column at zero—labelled "unverifiable." That is not a weakness; it is honesty. One thing is certain: the source mentions no coach, analyst, or sports-psych support. In a pattern of sustained decline, the adequacy of the performance staff is a major question, but the source is silent—so I hold this as hypothesis, not verdict.

Still, one thing is inferable, because the pattern speaks. Benching in July, release now—those two steps mean Liquid did not panic-cut; they tested a new direction internally first, then severed ties. This is a phased reset, not a panic move. But here the source's timeline inconsistency catches my eye, and I will not hide it. The benching is dated "July 2026" in the source, yet siuhy arrived on loan in April 2026, and the text references a "16-month tenure." April 2026 to August 2026 lands near sixteen months, but dating the benching to July 2026 makes the arithmetic tense. I am not issuing a verdict; this is a medium-risk data-integrity flag requiring verification.

One item I can state as verified, with source context. Dust2.us frames it as: strong pieces existed around siuhy—and that is the most important clue, because it moves blame away from a talent deficit toward leadership and cohesion. As a boy playing in Mymensingh, I learned that when a team loses, everyone blames the striker; nobody studies the fullback's positioning. Same here—nobody is asking whether a stable strategic framework ever existed behind four IGL changes. A team with strong components and zero Major playoffs has an integration failure—not a talent deficit.

Lay siuhy's arc into a spreadsheet and this is what surfaces: rose with promise at MOUZ → arrived at Liquid with expectation → 0.87 rating over 185 maps → 5-11 at Majors → top-4 at FISSURE → benched → free agent. This is a textbook "honeymoon-to-backlash" model. An import whose MOUZ form did not translate inside Liquid's structure. Here I attach a careful label: this is correlation, not proven causation. Because I do not know what was said in comms, what was written in the strat-book, or who took responsibility inside. But the pattern that appears here has appeared in my notebook before—sometimes in football injuries, sometimes here. When a system breaks, the person is convicted first, because the person is visible on camera and the system is not.

The load angle deserves separate treatment, because this is where my athletic instruments apply. CS2's calendar is packed with multiple Majors a year plus countless third-party events. Across those eighteen months Liquid played three Majors alongside events like FISSURE Playground—meaning constant travel, bootcamps, practice blocks, and official matches. What I see in football—two matches a week raising injury risk—follows the same logic here, only the ankle is replaced by the load on the mind and on comms coordination. A broken shot-calling system plus a packed calendar, combined, break any roster. Neither is curable with treatment; the name is system load, and system load outlasts the person.

Here a signature line comes back to me—the first ankle tear wrote the notebook's first line. Here too, the first IGL change wrote the cycle's first line. cadiaN, then Twistzz—both eras predate siuhy, meaning the problem is pre-siuhy. siuhy stepped into an old crack; he did not create a new one. This matters because it redistributes blame. Liquid's problem is not "who is the next IGL"; the problem is "why can nobody hold this role."

The Contrarian Angle: What rating does not measure, and yet what it still measures

Now to an uncomfortable angle, where I stand against the conventional crowd. The common narrative says: a 0.87 rating means siuhy failed, the release is justified. I accept the first part—the number is real, and it should not be hidden. But the second part holds a trap. Rating does not fully measure an IGL's value; shot-calling, mid-round re-reads, economy management—none of that shows on the scoreboard. If I judged only by rating, I would forget history's greatest calling eras.

But here my counter-counter arrives. Usually I argue rating under-measures IGLs—true in this case, but for siuhy there is double damage. Because if he had delivered intangibles (calling), the team would have reached at least one Major playoff; and if he had delivered tangibles (frags), the rating would sit near 1.00. Both are absent. That is the tragic point here—siuhy delivered neither intangibles nor tangibles. So in this one case, the release is data-supported.

Now my real objection with Liquid. The source says the replacement is "unconfirmed"—meaning the team enters an unspecified window with an open role. This is where I apply the "rush back versus scientific rehab" frame. The biggest mistake in injury is rushing a return—back on the pitch the moment pain eases, then tearing again. Liquid now face two paths: quickly grab another big-name IGL to plug the gap, or slowly fix the system. History says they have repeatedly taken the first path—and repeatedly broken in the same place. I cannot find an example of a team that succeeded by rotating shot-callers four times. If the fifth IGL arrives with the same haste, this is not a reset—it is the cycle's fifth lap.

Another false comfort. Some think siuhy's benching means Liquid tested a new direction internally, so all is well. But even a phased reset produces the same result—eighteen months spent, nothing won. In the source's own words, the best result was a top-4 at a low-tier event. This ceiling is so low that backlash has no room to grow—the only good news. But good news is not the same as the right decision. Passively "waiting for the roster to click" and actively fixing the structure are different things. In my notebook I call this "waiting culture," and waiting culture never heals an injury; it only hides it.

Takeaway

siuhy's free agency is a clean, data-supported decision—0.87 rating, zero playoffs across three Majors, a 5-11 map record; together these are sufficient evidence for the release. But the event's real information lies in a larger pattern: Liquid has rotated four shot-callers, repeatedly failed at Majors with strong components, and now stands with an open role. siuhy has passed his own audit; Liquid's audit is not yet finished. Who the next IGL is—that is not the question. The question is whether the next IGL will finally be given time for the system to hold, or whether in sixteen months I will sit down to write another free-agent report. I still keep that VOD, waiting on slow-motion. It knows: the video does not lie—it only waits for you to slow it down.