Worlds 2026: Karmine Corp Eliminate CTBC and End the LCP — the 18–3 Scoreboard Is Only Half the Story
**कोर उत्तर:** Karmine Corp ने 29 अक्टूबर 2026 को Worlds 2026 Swiss Stage Round 4 में CTBC Flying Oyster को हराया। इससे LCP का आख़िरी टीम भी बाहर हो गया और Karmine Corp 2–2 पूल में पहुँचकर शनिवार 31 अक्टूबर 2026 के डिसाइडर में जगह बना चुके हैं। **मुख्य तथ्य:** - गेम 1: 28 मिनट, 18–3 किल अंतर, स्रोत GosuGamers। - गेम 2: 37 मिनट; प्रकाशित रिकॉर्ड में किल काउंट नहीं दिया गया। - CTBC Flying Oyster बाहर; LCP का Worlds 2026 अभियान समाप्त। - CTBC के पास गेम 1 का पहला चॉइस था; रिपोर्ट में first pick और ब्लू साइड का विवरण परस्पर विरोधाभासी है। - ग्रैंड फाइनल: शनिवार, 14 नवंबर 2026। **स्रोत:** GosuGamers रिपोर्ट, 29 अक्टूबर 2026। **संबंधित प्रश्नोत्तर:** प्रश्न: LCP का Worlds 2026 में क्या हुआ? उत्तर: लीग का आख़िरी टीम CTBC Flying Oyster 29 अक्टूबर 2026 को Karmine Corp से हारकर बाहर हो गया, जिससे पूरा पैसिफिक प्रतिनिधित्व समाप्त हो गया। प्रश्न: Karmine Corp अब किस स्थिति में है? उत्तर: Karmine Corp 2–2 पूल में पहुँच चुके हैं और उन्हें शनिवार 31 अक्टूबर 2026 के डिसाइडर में खेलना होगा। प्रश्न: 18–3 का किल अंतर Karmine Corp के प्रभुत्व का सबूत है? उत्तर: नहीं; यह अंतर फाइट परिणाम दिखाता है, मैप कंट्रोल या ऑब्जेक्टिव ट्रेड नहीं, और गेम 2 का किल डेटा अनुपलब्ध होने से सीरीज़ का पूरा पढ़ना अधूरा रहता है।
Game 1, minute 28. The scoreboard reads 18–3. Someone took the screenshot, someone wrote the caption — “Karmine Corp won the draft.” On Thursday, 29 October 2026, in Round 4 of the Worlds 2026 Swiss Stage, Karmine Corp beat CTBC Flying Oyster and did the thing the entire LCP season could not: the league's last team is also out of the tournament. Saturday's decider is now locked in.
At 2 a.m., the tape told a different story than the timeline did. 18–3 is not a certificate of mechanical dominance. In modern League of Legends a 15-kill gap inside 28 minutes almost always comes from one thing — a lost lane, a failed objective trade, and that gap multiplied across three fights. The real question was never how good KC looked. The real question is what happened in the 37 minutes of Game 2, and no published report answers it.
Worlds' Swiss format is straightforward: three wins and you move on, three losses and you go home. The Round 4 match that is an elimination match ends one team's run and sends the other into the 2–2 pool — which means Saturday's decider. For CTBC this was elimination, and they lost. KC sit in the 2–2 pool after the win, which is why Saturday, 31 October 2026, became mandatory; the Grand Final is Saturday, 14 November 2026.

LCP — League of Legends Championship Pacific — is the Pacific region's top tier, drawing teams from Taiwan, Vietnam, Japan and Oceania. CTBC Flying Oyster is a Taiwanese organisation. So what went out on Thursday was not a team; it was a league's entire Worlds representation. Karmine Corp is a French org with what is generally treated as the loudest fanbase in EMEA. The story of this match comes down to one question from either side: was that the product of a system, or of a single night's decisions?

The hard facts recorded here are few and clean. Game 1: 28 minutes, 18–3 kills (credited to GosuGamers). Game 2: 37 minutes. Side selection: CTBC had first choice for Game 1 and took first pick, which put Karmine Corp on the blue side. That is it. No champion picks, no bans, no kill count for Game 2, no patch version.
Which is why I am standing here. The series people are writing up as “KC solved the meta” contains not one champion name. The match being called a draft masterclass has no pick/ban record attached to it. I keep receipts in a folder. This is the week it opened, and for this series the folder is half empty.
The only durable meta read available from this series is that KC won two completely different game shapes. A 28-minute blowout and a 37-minute long game. Nine extra minutes is not cosmetic — it implies different draft logic, a different scaling curve, different mid-game management. Winning two games of different lengths by repeating one pattern is hard. But this is n=2, and two games are not a sample. I hold myself back from writing “multi-speed adaptability,” because that is the story I want to be true, and the story a writer wants to be true deserves the most suspicion.
The kill line is a proxy, not a measure of control. 18–3 tells you the fights resolved one way. It does not tell you who held map control, how many objective trades were made, or how often CTBC surrendered tempo. Eighteen kills in 28 minutes means KC fought and won on nearly every spawn — but the same number cannot tell you whether they chose those fights or CTBC dragged them into them. I watched every fight from minute 28 to the end. Twice. Separate process from result: judge the call at the moment it was made, then note the win as a consequence, not as evidence.
The 37 minutes of Game 2 are the biggest information gap in this round. A 37-minute game demands a scoreboard, because the question changes: did KC control it from the start, or flip it in the last fight? The published record carries no kill count for Game 2. The direct consequence is that nobody can say. If one Baron fight at minute 37 decided the series, KC are a coin-flip team that never proved itself before Saturday. If it was a grind from the opening, they are a top-four contender. One incomplete record produces both conclusions — which is why every “KC are favourites now” post was written without data.
And one line of the reporting contradicts itself. The source states CTBC had first choice for Game 1 and “took first pick, which put Karmine Corp on the blue side.” In a standard LoL draft, the blue-side team holds pick one. The line as written is internally contradictory. Three explanations: the writer conflated side choice with pick order, the event used a non-standard draft order, or it is a straightforward reporting error. The outcome is the same — whether CTBC won or lost the draft-side battle is unknowable to any downstream analyst. That matters, because in a 2–2 pool side selection is one of the few free edges left. The first tactical decision of Thursday happened before the draft, and we cannot read it.
The LCP wipeout is not a series; it is a question. The region's last team out in Round 4. The coverage cycle is familiar: 24 hours of “where did the LCP go” threads, then the conversation returns to the LCK and the LPL. I will not say the LCP system is broken — I do not have that receipt. But one question deserves asking and nobody is asking it: was this a patch-fit problem or a scouting-pipeline problem? Pacific teams bring young rosters year after year and exit in the middle of Swiss. Is there something in that 18–21 age band that shows up under the mental speed of a BO3? That is a question with a data answer. I do not feel sorry for these young rosters; I am angry at a pipeline that spends them in two years and recruits the next class.
Tournament patch locking is unverified. Worlds traditionally runs a locked tournament patch, but this report carries no version number. If the tournament patch differed from live, every scrap of scrim preparation in the 2–2 pool is only half transferable. Before Saturday that is a real, unmeasurable risk — and an unignorable one.
I could be wrong, in three ways. First, two games are not a sample. “Multi-speed adaptability” is a story that looks true because it is tidy, and tidy stories usually stand on two data points we quietly count as three. Second, maybe Game 1 was a CTBC draft failure rather than KC adaptation. Then the read flips: KC capitalised on a good matchup, and they are the single-shape team that could get stuck on Saturday.
Third, and least comfortable — maybe the side-selection line is an editorial slip, and CTBC deliberately chose red side, which is a normal and rational choice these days. If so, the “contradiction” I caught is my own error. Everything I have written rests on the published record, and that record is incomplete and internally tangled in one place. That is the biggest weakness in this entire body of coverage. I am not hiding it.
Saturday, 31 October 2026, the decider; then the Grand Final on Saturday, 14 November 2026. My suggestion is simple: watch the first pick/ban screen, not the scoreboard. If KC draw blue side and close the series inside 30 minutes again, the multi-speed read holds. If they get red side and grind through 37–40 minutes, my read was wrong — and I will concede it on Saturday night.
The question is not whether Karmine Corp are a good team. They are. The question is whether we have the data to know which shape they arrive in on Saturday. After Thursday, the honest answer is no.
