Himass and TanVuu Move to Delta Force: Does One Publisher's Sanction Follow the Players?

Opening

A sanction is issued inside one publisher's competitive circuit. A career is rebuilt inside a second publisher's circuit. And the loudest demand to enforce that sanction comes from the community of a country where the new title barely registers in the competitive scene.

Those three pieces do not sit inside the same regulatory frame. In football, a ban issued by FIFA automatically applies across every member federation, no explanation required. In esports, that structure does not exist. Each publisher is its own sovereign, with its own rulebook, its own circuit, and no obligation to recognize a neighbouring sovereign's ruling.

When two Vietnamese players, Himass and TanVuu, were sanctioned by PUBG and decided to compete in Delta Force, they were not moving between two tournaments. They were moving between two legal systems. The story spreads as community news — the Korean community keeps hounding them, demanding Tencent block the pair from Delta Force events. But the data lives somewhere else, and it is emptier than most assume.

The original sanction has never been disclosed in detail: offence type, duration, scope. Nothing. Tencent, according to the report, has made no decision. The most notable thing in this story is not that two players changed games. It is that no publisher has published a ruling written in a language that can travel across titles. Results are the lie that time memorizes; the match log is the testimony. Here, neither has been opened.

Context: a restart on the calendar

Himass and TanVuu are names tied to Vietnam's PUBG community. After a PUBG penalty, both decided to switch to competing in Delta Force. The report's framing is telling: it calls the move almost a new beginning, where both must rebuild their image, achievements and professional path from scratch.

One point must be stated up front. Delta Force operates under Tencent; PUBG belongs to Krafton. Two ecosystems, two rulebooks, two operations teams. A penalty issued by the PUBG system does not automatically bind Delta Force unless the relevant organiser chooses to honour it. No information suggests such a recognition mechanism exists here.

On the community side, the picture is less uniform than headlines imply. Vietnam's PUBG community retains interest in the pair. A related petition recorded more than 4.1 million signatures of support. That figure says one thing: this is not a story of two isolated individuals, but of a story with an audience large enough to carry commercial weight.

In South Korea, a streamer warned of negative reactions if the players join events or appear at Delta Force tournaments. A segment of Korean viewers keeps pressing the publisher to act. Yet inside Korean forums, many push back, arguing this is one streamer's personal opinion rather than a collective stance. Another argument appears as well: Delta Force's popularity in South Korea is not enough to create real pressure on the publisher.

Two load-bearing facts are missing. The nature and scope of the original PUBG penalty is never described. A Tencent or Delta Force decision does not exist on the record. Every debate is happening on unsurveyed ground.

Cross-title skills: what transfers and what does not

PUBG is a battle royale: a hundred players, a shrinking circle, the final prize going to the last one standing. Delta Force is an expanded tactical FPS, spanning large-scale warfare and extraction-style modes. On the surface both are shooters, so many assume the skills carry over almost intact. The reality is messier.

What carries over is relatively clear: long-range gunplay, positioning discipline, composure under rotation pressure. Anyone who watched Himass and TanVuu in PUBG can recognize those. But the transferable part is only the outer layer. The inner layer — decision logic — changes almost completely.

This is what I always check before judging a player switching titles: the rate of objective-driven engagement. In PUBG, a fight that serves no direct objective can still be correct if it secures your position for the next circle. In Delta Force, a fight that serves no objective usually just burns time, exposes position and pushes teammates into a worse spot. Same action, two opposite readings.

Based on my experience tracking matches in both titles, the most common analytical error is using the old metric set to measure new ability. Damage per match, survival time, final placement — the battle-royale measures — say nothing about objective completion, trade efficiency in small duels, or point-control time. The metric set changes, the thresholds change, and fan expectations must change with them.

For Himass and TanVuu, no Delta Force competitive data has been published. No metrics, no results, no defined role in a roster. That means any judgment about the viability of the switch is currently an informed guess, not a conclusion. Data does not judge anyone; it merely exposes what the scoreboard hides. Right now, that scoreboard is blank.

Does a sanction have borders?

This is the central question, and it has no answer yet.

In esports, jurisdiction attaches to the publisher. Krafton governs PUBG and its circuit. Tencent governs Delta Force and its circuit. The baseline principle: a Krafton sanction does not bind Tencent unless a cooperation or mutual-recognition agreement exists. Nothing indicates such an agreement applies to this case.

One consequence matters. The demand for publisher intervention is framed as a consumer preference, not a rule violation. No Delta Force rule has been broken. No rule has been cited. Community pressure here is a reputational-cost mechanism, not a rule-based one.

Two different questions are being blended. First: should these players be allowed to compete in Delta Force — an ethics and community-sentiment question. Second: does the current rule system permit excluding them — a jurisdictional question. The answer to the second, on available evidence, is unclear. And that lack of clarity is the actual problem.

Three scenarios exist. Worst case for the players: Tencent or Delta Force quietly aligns with the PUBG ecosystem and discreetly keeps the pair out of marquee events, extending the sanction across titles without a formal statement. Middle case: no formal exclusion, but reputational drag reduces invitational access, forcing them through open qualifiers. Optimistic case: the publisher treats it as a closed PUBG matter with no cross-title reach.

No evidence shows the worst case is unfolding. None rules it out either. This suspended state, rather than any decision, is what unsettles all sides.

Community pressure: measured how?

One rule I keep when reading esports stories pushed into cross-border news: always ask how loud the original voice was before amplification.

Here, the source indicates the originating voice came from a streamer with relatively low live viewership. From one clip, the story became news in another country, then returned as pressure on a publisher headquartered in a third. This is a textbook amplification pattern in the livestream ecosystem: short-form content, high emotion, spreading faster than verification.

Notably, Korean forums themselves raised this counterpoint. Many argue the exclusion demand is a personal opinion, not a representation of the entire Korean gaming community. Another argument appears: Delta Force is not popular enough in South Korea to create meaningful pressure. Both weaken the simple reading that an entire nation is hounding two players.

On the support side, the petition with more than 4.1 million signatures is a weighty signal. It indicates an audience large enough to carry commercial value. For a publisher looking at Southeast Asia as a growth market, that audience is a serious consideration.

The overall picture is a polarized sentiment field: one side strongly supportive, one strongly opposed, and in between a publisher that has not spoken. In such cases I always separate two kinds of value: media value and competitive value. These two players currently have proven media value, and unproven competitive value in the new title. Blending the two is the root of most of the argument.

Market asymmetry: who actually holds leverage?

Pressure only carries weight when the pressuring side holds something the pressured side needs. Here, the opposition comes from a community with deep PUBG heritage but not a major Delta Force market. The support comes from a large, rising community directly attached to the two players.

The publisher's calculus in this situation is likely commercial, not moral. The cost of keeping the players is reputational risk in a small market. The benefit is presence in a large audience market. Transfer data is like a tide: watching the surface tells you nothing; you must measure the seabed. Here the seabed tilts toward support.

This is structural analysis of incentives, not a prediction. The publisher may choose any direction for its own reasons. But on a pure cost-benefit reading, staying neutral and letting the pair compete normally is the cheapest option.

Risk matrix and industry transmission

First risk cluster, for the players: an extended adjustment period in the new title, combined with reputational pressure and possible online harassment. Medium probability, medium impact. Mitigation lies in a structured practice and qualifier path, plus PR support to control social exposure.

Second risk cluster, systemic: the possibility of a sanction being informally extended across titles. Low-to-medium probability, high impact if it happens. The fix is clarifying the sanction's scope with the relevant publishers instead of leaving it suspended.

Third cluster, and the most important long-term in my view: precedent risk. If community pressure becomes a criterion for competitive eligibility, that standard replaces rule-based criteria. Such a system runs on emotion, and emotion changes weekly. Today it targets one person; tomorrow another.

Along the transmission axis, this story touches three layers. Publisher layer: one has issued a sanction, one has not decided. Community and player layer: two people switch titles, one side supports, one opposes. Ecosystem layer: the norm on whether sanctions travel with players across publishers is being shaped right now, and it will affect similar cases later.

Contrarian angle

The common reading is a confrontation between two communities, one hounding, one defending. I think that reading is on the wrong axis.

The real axis is a governance vacuum. There is no mechanism for a sanction in one title to be enforced in another. No mechanism to separate one streamer's personal opinion from a collective community will. No mechanism for a publisher to decide on publicly explainable criteria rather than volume of noise.

Second contrarian point: if publishers begin honouring each other's sanctions on community request, the long-term damage belongs to players generally, not to these two specifically. Such a precedent turns every local sanction into an industry-wide sanction, and every publisher into an enforcement agency for every other.

Third contrarian point: the petition with more than 4.1 million signatures can be read two ways. It is evidence of support strength, and simultaneously a commercial argument for keeping the pair in the competitive system. Here, strong support and publisher interest likely align. That is why I consider a systemic-exclusion scenario less likely than most commentary assumes.

What to track next

I have never quit data; I only changed suppliers. In this story, the supply to watch sits in three places: an official Tencent or Delta Force statement on eligibility; the original PUBG sanction record, specifically offence type and scope; and the entry lists for upcoming Delta Force qualifiers.

When one of those opens, the story shifts from emotional debate to verifiable fact. That is the moment to reread the whole affair, not the moment to conclude before the data sheet is filled in.