Worlds 2026 Swiss Round 4: Karmine Corp Eliminate CTBC Flying Oyster and End the LCP's Run — the Real Number Behind 18–3 Is Three

Game 1 finished 18–3 on the kill line and 28:00 on the clock.

I watched it twice. Once at night, in a room in Dubai where the Pacific feed arrives after midnight and the tea has gone cold. Once the next morning with the kill feed muted, watching only the minimap, ward timers and item spikes. Both times the scoreline was the same. Both times it was not saying the same thing.

Eighteen kills is the noise. Three deaths is the news.

Eighteen kills in twenty-eight minutes works out to roughly one every 93 seconds — twenty-one kills combined, about 0.75 per minute. That is not a massacre. That is arithmetic. A team that dies only three times in twenty-eight minutes did not spend risk; it collected interest on it.

And then Game 2 ran thirty-seven minutes. A nine-minute difference. A series we will call one-sided tomorrow contained a game that demanded nine extra minutes of somebody's patience.

There is one sentence in the report I had to read twice — that CTBC had first choice for Game 1 and "took first pick, which put Karmine Corp on the blue side." In the standard League of Legends draft, the blue-side team holds pick one. The sentence breaks inside itself. It is a small thing, and small things decide which story we tell tomorrow.

Context: the Swiss table, a closing league, a French noise

Worlds 2026, Swiss stage, Round 4, Thursday 29 October 2026. The Swiss rule is simple — three wins and you are through, three losses and you are out. Each round redraws teams against opponents on the same record, which means the 2–2 pool is the part of the bracket where everyone already knows the next loss is the last one. A bracket is a biography with the losing chapters torn out and taped back in.

CTBC Flying Oyster was the last LCP team standing in that round. The LCP — the League of Legends Championship Pacific — is the product of an attempt to bring the Pacific's separate leagues under one roof. "Last team standing" implies the others were already gone. The original report does not state how many teams the LCP sent to this Worlds, so I will not invent the number — and that missing number blocks the biggest conclusion anyone will want to draw.

Opposite them was Karmine Corp. A French org whose identity is its crowd; KC's noise rises above the home team in almost any venue, which is why a KC match is often better listened to than watched. The report's headline says the win forced a "Swiss decider" — meaning the result stopped the Swiss table from closing and created one more match, to be played Saturday. Which slot that decider decides — seeding or the last qualification place — the report does not say.

Let me name my vantage plainly: I am writing from Dubai, off VODs, broadcast feeds and WhatsApp threads. I was not in that room. What I could see was a screen; what I could not see was the room behind the stage. So wherever I infer below, I will say how firm the inference is — and where there is no number, I will stay quiet.

And it is worth counting what the report does not contain: no patch version, not a single champion pick or ban, no map attribution, no kill count for Game 2, no venue. Which means any "meta" narrative built on this match would be fiction. What survives is time and kills — and that is enough, if read properly.

Game 1: the team that did not die

Twenty-eight minutes, 18–3. I deliberately stopped looking at the kills and looked at the nexus instead. Eighteen kills gives a team an average KDA around six, and in League a KDA of six in a single game usually happens when the opposing team is somewhere accepting fights. Here the fight was never accepted.

Three deaths means all five KC players died fewer than once each on average across twenty-eight minutes. A team that dies that rarely is not preventing kills — it is removing the situations in which kills exist. That is not passive play. It is a three-way settlement between warding, tempo and back-timing: buy information on the map, buy time, then take risk only where the return is already guaranteed.

Which is why calling 18–3 a stomp is only half true. A stomp usually means blood — kills on both sides, one team simply faster. Here it was the reverse. One team stopped making mistakes and made the other team make them. Twenty-one kills in twenty-eight minutes is, by League's standards, a quiet game. Quiet games are the ones where one side executes what it prepared and the other side waits for a plan that never arrives.

There is a second thing the scoreline hides: eighteen kills is not the measure of a win, the timing of those kills is. If twelve of the eighteen landed inside the first fifteen minutes, the game was decided around minute twenty and the rest was paperwork. Eighteen kills arriving late produces the same scoreline and an entirely different story. The report gives us no timeline, so I will not claim one — but anyone who calls this game one-sided from first minute to last will be asserting something that is not even in the box score.

Game 2: nine minutes nobody will remember

Thirty-seven minutes. Nine more than Game 1. This is the most interesting number in the series and nobody will quote it.

In League, game length is an informal instrument. A game dragging on while a team is ahead is evidence that the team could not find a way to close. Twenty-seven to twenty-eight minutes is the normal speed of a clean conversion. Thirty-seven suggests that in Game 2 somebody delayed the fight, or somebody got a scaling draft and the time to use it, or both.

I will be honest here: I do not know which. The report does not give a kill count for Game 2. If it had been 12–9, I would say the game was a scrap; if 15–6, I would say KC held control again and simply closed late. Without that number, building a story from duration alone is the same error I try to stop in my own column every week — mistaking an outcome for a process.

The limited conclusion available is this: Karmine Corp won two differently-shaped games in one series. A fast, controlled twenty-eight-minute game, and a long thirty-seven-minute one. That is weak but real evidence of multi-speed adaptability — weak because it is a two-game sample, real because you cannot win both games with one trick. A team that knows only one speed falls apart the moment its draft is taken away. The report contains not one pick, so this too is an inference — but it is the kind of inference the next round can falsify.

The blue-side sentence

Back to the sentence I tripped over. "CTBC had first choice for Game 1 and took first pick, which put Karmine Corp on the blue side."

In the standard draft, blue side holds pick one. So if CTBC took first pick, CTBC was on blue, not KC. Three possibilities. One, the reporter conflated side choice with pick order — the most common error, because choosing a side and taking first pick are two separate rights and easy to collapse into one clause. Two, the event used a non-standard draft order, unusual for Worlds but not impossible. Three, it is a straight reporting error.

The result does not change. But the cost of that sentence is that any analysis of the Game 1 draft battle is now unreliable. If you do not know who was on blue, you do not know who had pick one, who gave up the counter, who opened their prepared plan and who responded. The entire draft-battle discourse of the next four days will stand on a foundation that has already cracked.

I flag it because nothing I file ships without a number behind it. Two years ago I held back nine charts from an essay because one column in my spreadsheet could not be rebuilt. Since then the rule is: a claim I cannot count is a claim I do not write. The blue-side sentence sits in that category.

The Swiss bracket: who actually authored this

Now the part nobody writes — the format.

KC's win eliminated CTBC and forced a decider. We will tell that as a story about KC, because we like stories about winners. But KC did not author the decider; the Swiss system did. The 2–2 pool is not geometry; it is pressure learning your name. The Swiss redraws every round, which means your next opponent is a function of other people's results, not of your own performance. A team arriving at 2–2 can meet a team that was 0–2 yesterday and is 2–2 today — the single largest source of uncertainty in the tournament, and one we usually wave away with the word "form."

So "KC forced a decider" is technically true and analytically incomplete. KC did its job; it won. The bracket did the rest. When that match is played on Saturday, at least one team's season can end inside 72 hours — not because of how it played, but because of who it drew.

The LCP question: what is n?

Now the part that will be written worst: "the LCP is finished."

CTBC lost and the LCP's last team went out. That is a fact. The conclusions that will follow — the Pacific cannot compete, the merger failed, the league does not deserve a slot — all rest on a sample whose size we do not know. The report does not say how many LCP teams were here. If two, an entire region is being judged on two best-of-threes. If three, on three. Any regional-strength claim built on two or three teams is the equivalent of judging a batter's career on two innings.

I say this plainly because I come from a scene where this number game is played daily. For years in India we read the "so many hundred million gamers" headline while the audience actually watching competitive play was a fraction of it — and when sponsorship collapsed, it turned out that money had never belonged to esports at all. The Pacific deserves the same caution. The LCP's decline will not be decided by one team losing; it will be decided by its slots, its finances and its next generation — none of which is in this report.

For me the real LCP story is the merger: putting leagues with different rules, different audiences and different languages at one table, then watching that table negotiate for an international slot. One team going out is not the death of that project. It is its first real exam.

The café mic and this draft

The café mic taught me that a room listens before it speaks. In 2026 I hosted nine unpaid hours in a café in Karama — thirty-two teams, a 1,200-dirham prize pool, sixty people in the room. I still remember that when my voice cracked on the third stanza of my opening, nobody left. The room decides whether it will listen to you, and it decides before your first sentence.

That is why the moment I care about most in this series never appears on the scoreboard — the last five minutes of the thirty-seven-minute game. When the clock passes thirty and the game is still open, both teams have the same question: who bends first. The broadcast fills that moment with replays, but the real thing happens where one team loses its patience and takes a fight it did not need. Thirty-seven minutes is the ledger of that patience.

The transfer window: the price of sixty-five minutes

Here the story turns to the place I return to every November.

CTBC's Worlds is over, which means their off-season has begun, which means five players are now on the market — contract dates, buyout clauses, agents' phones, all of it starting the same week they lost. And that is the part that worries me.

The transfer models currently in circulation will look at the scoreline I opened with — 18–3, twenty-eight minutes — and discount all five players. Those models overrate youth potential and underrate dressing-room chemistry. A team that played a year together, qualified out of its region and played two games at Worlds is being priced on sixty-five minutes of footage. It is the same arithmetic that has sold a lot of good players cheap and made a lot of cheap players expensive in this scene.

My rule has been the same for years: no transfer goes out before the family knows. In January 2026, when a seventeen-year-old IGL's move closed, I sat on it forty minutes before the announcement graphic and called his mother first. That was the best decision I made that window. The same applies to CTBC's five — this week they are a line in a model, and at home they are a decade.

The contrarian read: what this series does not say

First: "the LCP is finished" is a sentence that passes judgement on an entire league off a sample of two or three teams. Regional strength requires slots, draws, pool depth and years of data. We have one series.

Second: "KC forced a decider" gives the winner credit for the format's work. The Swiss forced that match. KC won half the fight.

Third, and most important: treating 18–3 as a class gap. If the gap were really that wide, why did Game 2 take thirty-seven minutes? The nine extra minutes weaken the class-gap theory rather than strengthen it. One-sided series do not run to thirty-seven. More likely this was a good team against an average team, and 18–3 was the one game where the average team picked the wrong draft. That is also an inference — but a cheaper one than burying a whole region.

Fourth: the market. The most expensive mistake of this series will be made next month by somebody's analytics desk, pricing five careers off sixty-five minutes.

What to watch

Saturday brings the decider; the Grand Final is Saturday 14 November 2026.

On Saturday I will not watch the kill column. I will watch the death column. The team that dies fewer than ten times wins that match, whether it registers seventeen kills or nine. And I will watch to see whether Game 2's kill count gets recorded anywhere — because if it does, somebody should point out that it was the most ignored number of this entire Swiss stage.

The question is not whether the LCP is finished. The question is whether, the next time a region sends two teams and comes home with two losses, we will call it two losses or a region.