PUBG's Shadow War: The Permanent Bans on Himass and TanVuu, the Glass Reflection Aimed at Soopi, and the Ledger of KRAFTON's Silence

A glass reflection. The smear of light hanging across a monitor, the detail that has split Asia's PUBG community in two. In a clip from his own broadcast, the Korean player-streamer Soopi stated that he uses only one monitor. A segment of that same clip was cut and circulated by Chinese and Vietnamese fans, who argue that the reflection reveals the presence of a second screen. Years of pausing VODs frame by frame have taught me this much: a screen reflection cannot convict anyone of cheating. But the screen is not the centre of this dispute. The centre holds two decisions — the weight of one, and the silence of the other. The incident happened at an Asian exchange tournament, described in the source material as a friendly match. Soopi's allegation was that two Vietnamese players, Himass and TanVuu, watched opponents' live streams during the match to learn positions, movement and tactics. KRAFTON locked their accounts and then banned both permanently from competition. Himass's team, AG.AL, is described as having won a world esports championship in Paris — a claim that has not been independently verified, and one that sits awkwardly beside PUBG's actual flagship, the PUBG Global Championship, which KRAFTON itself operates. Three regions are now tangled inside one dispute: Korea, Vietnam and China. And the structural problem sits right there — the rule-maker, the event organiser and the commercial stakeholder are the same institution. I read patch notes the way I read an elegy with timestamps: which team lost what, which engagement stopped working, all of it filed by date. This dispute has no such ledger. No patch number, no win rate, no pick rate, no match report. What exists is the outcome of a rules enforcement — and questions about whether that outcome is internally consistent. The first question is proportionality. An incident in a friendly match, where no league points, no seeding and no prize money were at stake, produced a permanent ban. This is the fans' heaviest complaint, and argumentatively the hardest to deflect. Nobody is objecting to strict rules; the objection is to the ratio of strictness. The declared purpose of an exhibition event is goodwill and regional exchange. If that same event can end a career, the event's stated character and the sanction's actual effect contradict each other. The second question is consistency, and it is far more dangerous for KRAFTON than for Vietnam. Fans allege that Gyumin of DNS stream-sniped throughout the official domestic season, with no publicly disclosed punishment. Place those two facts side by side and a simple conclusion emerges: either the rule is not applied evenly, or the rule is itself unclear. The first is called favouritism, the second neglect. Neither is good news for competitive integrity. I remember waiting two weeks before writing about EDward Gaming's fifth game against DAMWON KIA in 2026, holding the piece until patch 11.19 data was in hand. I waited so the claim would hold. Right now KRAFTON has replaced that patience with silence, and every day of silence hardens the community's assumptions. The third question is transparency. There is no public rule text, no evidence schedule, no account of the investigation's stages. Where evidence is hidden, people fill the gap with imagination — the ordinary chemistry of every governance controversy. From a Chinese gaming forum to Vietnamese social media, one theory travels: the Korean publisher decides as it pleases. There is anger in that sentence and no proof in it. Yet the allegation survives, because nobody has published anything to refute it. There is a layer most people skip. PUBG is a battle royale. Matches are long, maps are open, player counts are large, and almost every elite competitor is also a streamer. Compared with any round-based title, the opportunity surface for information leakage here is enormous. That is not a patch-created problem; it is a birth defect of the format. Every stream-sniping ruling therefore carries weight, and every ruling should carry evidence of matching weight. And the accuser is himself a streamer — at a moment when some fans argue that streamer followings have overtaken professional players. That branding tension is not new, but this time it has arrived on the enforcement stage, where one streamer's accusation determines another streamer's career. I have a habit I notice in every controversy of this kind: sit down to write an elegy and every small incident becomes a funeral. Not this time. Where patch 7.18 changed identities, a nerf merely tunes numbers; nobody here lost an ability. Someone lost a licence, through a process that remains unverified. Writing about empty rifts and empty stadiums in 2026 taught me to make absence a character. Now I understand that the most important absence is disclosure — the absence inside the absence. And the largest problem is the decision that never came. If Himass is genuinely part of a championship-winning roster, then this ban is not one player removed. It is a team's rebuild plan, its sponsorship commitments and its transfer-market arithmetic collapsing at once. Meanwhile there is no public ruling on the Gyumin matter. If that asymmetry holds, regional teams will decide next season whether to invest in competition or shift everything toward streaming. The result of that calculation could erode PUBG's competitive depth far more than any single ban. The full picture still isn't mine to hold. I have no interest in closing on a guess, so I'll close on a watch-list instead. If KRAFTON publishes its rule text and a summary of the evidence, the decision stands as law. If silence continues, it remains an allegation. A formal ruling on Gyumin would show how hollow or how solid the double-standard claim really is. And the appeal outcome for Himass and TanVuu, alongside neutral observers' statements on Soopi's setup, could still rewrite the story. Until then, what exists is this: an empty screen, a crowded comment section, and a timestamp nobody has managed to verify.