An 'Esports' Label on a Gacha Calendar: Notes from the Rules Desk

Marseille, a Monday morning. Two tabs are open on my desk. The left one is an analysis file tagged 'Esports'. The right one is a version schedule for a role-playing game. I read the left file first, following a habit I have kept for ten years: read the label, read the source, then read the content.

There is no team in that file. No bracket, no fixture list, no transfer market, no contracts, no competitive balance patch. There are only phases of roughly 21 days, a guarantee threshold at 90 pulls, and a 50/50 split for the featured character. My pencil stops on the first line.

In 2026, at 24, working as a data sub-editor in Marseille, I went back through the footage of Olympique Marseille against AS Monaco, minute 73, when Dimitri Payet's goal was disallowed for offside. I wrote 1,200 words with three situation diagrams; the piece drew 40,000 reads in 24 hours. What I kept from that day sits in the craft rules: cross-check two sources before publishing, and cite the correct article number. I read the match report before I read the news, because a match report does not lie.

Strip the label away and the file is fairly clear. Version 7.0 phase two brings reruns of Flins and Ineffa. Version 7.1 phase one introduces two new characters, Vesna and Vodyanitsa, and phase two is a set of reruns. A new region called Snezhnya is mentioned. The names Odette, Skirk, Escoffier, Aino, Iansan and Lan Yan appear in the schedule forecast section. On mechanics: 90 pulls guarantee a five-star; the first five-star has a 50% chance of being the featured character, and a loss guarantees the next one; pity is shared between banners of the same type; a separate system called Chronicled Wish serves older characters; and there is no fixed rerun schedule, with some characters absent for more than a year.

More notable is the sourcing. Of 28 information points, 20 carry no source, exactly one cites an official publisher announcement, and three are the author's own opinion. The article itself admits the exact banner schedule is still to be confirmed.

Here I have to state one thing clearly about the analytical frame. This title has no professional tournament circuit, no team system, no scrims, no qualifiers, no competitive balance patch in the sporting sense. The nine-dimension esports frame does not fit it. I refuse to force it: I will not turn characters into players, banner phases into tournaments, or a guarantee threshold into transfer rules. A wrong label is not fixed by filling in empty boxes.

What does transfer is not small. The pity architecture here is a pricing rulebook, and it deserves to be read like one.

The publisher is simultaneously the rule-maker, the operator and the sole announcement authority. In esports, the publisher also writes the rules, but there is always a third layer: organisers, teams, player associations, referees, the VAR team. Here the loop closes on itself, with no independent arbitration and no verification of disclosures.

The 90-pull threshold is a soft floor: it creates a sense of accessibility and caps the worst-case spend, but it commits to nothing about real cost. The 50/50 plus guarantee is what creates variance, and variance is the revenue engine. Shared pity between banners of the same type lowers the marginal cost of switching, which smooths cash flow between launch windows and rerun windows. The absence of a fixed rerun schedule is a deliberate scarcity mechanism. Chronicled Wish is a separate revenue lane for older characters, allowing dormant names to be monetised again without disturbing the main banner cadence.

Read as a rhythm, version 7.1 places two new characters in the same first phase, with reruns in the second. That is a spending-rhythm design, not a competition rhythm. The currency-allocation pressure falls exactly on phase one, an observation about monetisation structure rather than character strength. The original piece contains not a single line about kits or power. It answers 'when', not 'should I'.

Set beside esports, the difference becomes plain. Esports revenue depends on sponsorship, broadcast rights, skin revenue sharing and prize pools, which means dependence on the competitive calendar and on outside events. The gacha model is self-contained, less exposed to calendar shocks, but exposed to regulatory change.

I owe the player side a paragraph, because community emotion is valid data. The phrase 'save for 7.1' is real decision language, and it works the same way football fans talk about a transfer window. I do not take that lightly.

But a promotional tone paired with thin sourcing is a familiar combination: traffic-filter content. The central problem sits with the label. When a purchase decision is read as a competitive decision, the reader is handed the illusion that data sits behind it. In esports, 'should I invest in this roster' is answered with metrics. Here, 'is it worth pulling' has no metric at all, only a schedule.

VAR is not wrong. The people running VAR are only people. And here the operator is a single party. Gacha is not classified as gambling under most current legal frameworks, but it sits close to the loot-box debate. Probability disclosure is mandatory in several markets, while the original piece reproduces the mechanics without citing any regulator.

Based on what has been verified, a provisional conclusion: this file belongs to Game Content / Gacha Monetisation; claims about 7.0 and 7.1 and the names Odette, Vesna and Vodyanitsa need cross-checking against official channels before use. What remains open is every conclusion about the value of a pull.

Three proposals, written in the clause format I still use when submitting rule-change suggestions. First, re-tag it: Game Content / Gacha Monetisation, separated from the esports label. Second, apply a source-disclosure standard: every schedule claim must carry an official channel and an absolute date. Third, treat all forward-looking claims as provisional until confirmed.

A 38-point checklist will not save a season, but it saves the reputation of the person holding the whistle. Here, what needs saving is the reputation of a label, and of whoever applied it. Anyone who writes the rules needs someone outside the line to check their signature. If a mislabelled file passes through three editing layers without anyone stopping it, which layer is holding the whistle?