Anatomy of the Gacha Revenue Engine: Pity, 50/50 and the Scarcity Policy

Two weeks before phase two of version 7.0 closed, a banner schedule spread quickly through the Genshin Impact community. It listed the names expected to appear in phase one and phase two of version 7.1, along with the familiar advice: start saving Primogems now. Within days came thousands of shares, hundreds of analysis videos, and a wave of debate over which banner deserved the money.

From the standpoint of someone who tracks deal structures, the notable event is not the character list. It is the fact that an unconfirmed schedule can shape the spending behavior of an entire community for weeks. When the contract ink has not yet dried, the real story already began with a two a.m. phone call. Here, that call is the publisher's internal meeting, where the schedule was designed before players had a chance to ask.

I do not write about player value; I write about what makes that number move. And in this case, what makes the number move is the monetization architecture, not the character names.

A Product Outside the Esports Ecosystem

One thing must be said plainly before going deeper. Genshin Impact is an open-world role-playing game run on a gacha model, where players spend premium currency for a chance to obtain characters or weapons. It has no professional tournament circuit, no franchised league, no clubs, and no transfer market in the esports sense. Its versions are single-player content drops, not competitive balance patches.

That means labeling this content as esports is a misclassification. The industry's analytical framework, roster form, tournament systems, regional landscapes, transfers, does not apply. There are no teams, no competitors, no coaches, no matches in this picture.

Yet there is one transferable analytical value, and it sits at the business layer. Gacha is a revenue engine that runs on logic anyone doing industry analysis should understand: recurring cash flow, supply control, and concentrated information governance.

In Vietnam, the mobile and online role-playing game market has become inseparable from the digital content economy. Revenue from randomized-item models is a subject regulators watch closely in many markets. Reading a banner schedule as a business event, rather than as entertainment news, is the more useful approach.

Where the Engine Lives: The Pity Architecture and the Cash-Flow Problem

The banner schedule is only the surface. Beneath it lies the guarantee system, which determines the real cost of each time a player spends.

The core mechanism has three layers. First, a guarantee threshold: a player is certain to receive a five-star character within at most 90 pulls. Second, a split mechanism: the first five-star on an event banner has a 50 percent chance of being the featured character and a 50 percent chance of a standard one; if it lands on the standard side, the next five-star is guaranteed to be the featured one. Third, shared accumulated pulls across banners of the same type.

Together these three layers form a price sheet with a wide range of variance. A player might get the desired character after a few dozen pulls, or might need to exhaust the guarantee threshold twice in a row. It is that variance, not the listed price, that generates revenue.

This is the point where I want to linger, because it is a lesson transferable to every digital-content business model. A fixed price sheet lets buyers know in advance what they will pay. A variable price sheet lets buyers know only an upper limit, and that upper limit is designed high enough that most buyers accept the attempt. The 90-pull guarantee acts as a minimum commitment, lowering the psychological barrier to entry. The split mechanism acts as a control valve: it turns a purchase into a game that can be lost halfway, and the very possibility of losing halfway makes players spend more than they originally planned.

The entire pity and 50/50 architecture is not designed to sell a character, but to turn a single spending decision into a repeating chain of decisions.

Scarcity as Policy, Not Accident

If you read only the news, it is easy to assume a character's long absence is an operational matter. Seen from the cash-flow angle, it is a deliberate choice.

According to the data the source article compiled, the rerun schedule is not fixed: some characters are absent for more than a year, while others return within a few versions. This asymmetry destroys predictability. When you do not know when the next chance comes, the opportunity cost of waiting becomes more expensive than the cost of spending now. That is the fear-of-missing-out mechanism in its purest form, operated through scheduling rather than through advertising copy.

Alongside it sits a secondary monetization lane few notice. The Chronicled Wish mechanism allows older characters to be re-monetized under a separate rule set, detached from the main banner rhythm. Structurally, this is how a publisher earns from characters past their hype peak without diluting the new release calendar. It resembles a club staging a friendly with a legends squad: it creates no new competitive value, but it creates new cash flow from fans' memory.

The sharing of accumulated pulls across banners of the same type also deserves a close read. It reduces friction when players move from a new banner to a rerun. On the surface, it is a concession to the community. In substance, it is a revenue-smoothing mechanism, ensuring cash flow does not break between release waves.

I learned to read a balance sheet before I learned to read a center-back. It is the same here: reading a banner schedule without reading the guarantee structure shows only a character list, while reading the guarantee structure shows an engine running to its own rhythm.

Why This Model Differs Fundamentally from Esports Revenue

A useful comparison is a structural one. A typical esports ecosystem earns through multiple layers: sponsorship, broadcast rights, in-game item revenue sharing, and tournament distributions. These layers depend on third parties, sponsors, streaming platforms, television audiences, and external events. They also depend on match schedules and results, things not fully within the publisher's control.

The gacha engine is different. It is a closed loop between publisher and player. The publisher is simultaneously the game's operator, the rule-setter of the gacha system, and the announcement authority for that system. There is no independent arbiter, no third-party verification, no season that can be canceled for external reasons. The value chain here is so short and concentrated that it has almost no external bottleneck.

That concentration creates a clear resilience advantage. An esports season can collapse from losing a sponsor or from a global event. A gacha engine only needs the publisher to keep releasing new versions. But the same concentration creates a corresponding weakness: there is no buffer layer between the publisher and external regulation.

The Risk Sits at the Regulatory Layer, Not the Competitive Layer

Apply an esports risk framework here and you will find nothing. No injuries, no form, no roster upheaval. But there is another kind of risk, and it deserves serious attention.

It is regulatory risk around probability transparency and consumer protection, especially for underage players. The pity mechanism, the 50/50 odds, and the guarantee threshold are information the publisher publishes and defines itself. In many markets, probability disclosure is mandatory, and limiting spending by minors is a continuously tightened area. When the publisher is both rule-maker and beneficiary, the gap in independent verification becomes the thinnest point of the whole system.

This is what industry analysts call systemic risk, because it stems not from a specific error but from the structure of power itself. And with randomized-item rules shifting across regions, a small change in disclosure requirements can affect the entire margin structure of the model.

The Contrarian Angle: The Schedule Is Not the Story, It Is a Noise Filter

This is where I must say what most content around this event avoids. In the dataset the source article compiled, most information points carry no source. Only one rests on an official publisher announcement; several others are the writer's opinion. Many character names and version numbers appearing in the material cannot be cross-checked against known game state.

That does not mean everything is false. It means the article's reliability is low, and anyone acting on it is betting on an unconfirmed schedule. The source itself admits the exact banner schedule is still to be confirmed. Such an admission is an honest signal, but it also confirms that the whole content is forward-looking.

Fans see a scheduling shock, while I see a content piece engineered to filter traffic, where promotional tone comes first and verifiable data comes later.

This leads to a hard but necessary conclusion. The audience best served by this type of content is not the player weighing a purchase, but the platform needing views. When sourcing is thin and tone is thick, informational value is lower than viral value. A clear-headed reader must separate the two.

This is where three-layer verification discipline earns its keep. Layer one, verify the origin of the information: does it come from an official announcement, from searchable historical data, or from an anonymous account. Layer two, cross-check against the operator's track record: does this publisher have a history of early announcements, and does that history match the spreading information. Layer three, state the confidence level within the content itself, rather than leaving readers to guess. Never use the word certain unless there is an official statement from the publisher.

There is a human detail that data tables often skip. Behind every press of the pull button is a real player, perhaps a student weighing whether to top up or set the money aside for something else. A banner schedule tells them nothing about their own financial capacity. Reading the engine is not about being smarter than others, but about not being swept along by a rhythm someone else designed.

What to Track Next

During a transfer window, I always lay out three scenarios with attached probabilities, because the market does not move in a straight line. It is the same here.

Scenario one, high probability: the publisher announces official banners exactly on the regular cadence, with two new characters in phase one and reruns in phase two. The schedule story then closes and the real story, players' currency allocation, begins.

Scenario two, medium probability: the announcement deviates from the leak, partly because the information was unverified, partly because the publisher adjusts to avoid being predicted. This is the scenario that makes those who acted early on rumor pay the price.

Scenario three, low probability but worth watching: a regulatory change on probability transparency or minor protection in a major market, forcing the publisher to adjust its disclosure or operation. The engine still runs, but the rules of the engine itself change.

The transfer market has no secrets, only sources priced correctly. And in every revenue engine, the person who understands the structure always has an edge over the person who only reads the list. The question is not which character appears in the next version. The question is who is designing the rhythm that makes you feel you must decide right now, and why that rhythm is calibrated never to give you enough time to think.