The Line Is Never Straight: When Esports Analysts Draw Conclusions on Empty Data

Inside my office in Marseille, I keep a habit my colleagues call the rule robot: before reading any report, I open the match record first. Not because I love numbers. Because the record is the one thing that does not lie. That night, a young editor sent me a six-page esports analysis. Full of tables. Full of metrics. A conclusion nailed down about a team I had never heard of. I turned to the source-data section. Empty. No game title. No patch version. No team name. Not a single player. Those six pages were built on nothing, and what chilled me was how persuasive they still read. That is why I sat down to write this piece. The industry is outgrowing its ability to check itself Over the past five years, esports analysis in Vietnam has exploded. League of Legends with the VCS, Arena of Valor with its domestic arenas, CrossFire, Valorant — every discipline now has its own analysis desk. Broadcasters invite experts. Online platforms pay writers for deep dives. Readership of tactical breakdowns rises every season, and wherever there is demand, there are people writing fast. But there is a difference between writing fast and writing right. That difference usually hides in the part readers rarely look at: the source data. An analysis only deserves trust when every claim is anchored to a timestamp, a verifiable figure, a citation that can be traced back. When that source is empty, the writer faces two choices. One: stop and say there is not enough data. Two: fill the gap with conjecture, then present that conjecture in the tone of fact. The second choice is not necessarily deliberate deception. It is more dangerous than that, because it happens silently. I call it silent subject substitution. Silent subject substitution — the most dangerous error Picture an analyst asked to write about a match. The input is empty. Instead of stopping, he wonders: it is probably about the strongest team in the group. Then he answers himself. Then he writes. The patch version is inferred from memory. The roster is taken from the most recent match. Player names are filled in by habit. By the end, the reader receives a fluent analysis of a subject the author himself never verified. This is the difference between an individual mistake that can be fixed and a structural defect that cannot. A disallowed penalty can be fixed, a gap in the rulebook cannot. In football, a referee errs on one incident, VAR intervenes, the match continues. But if the rules leave the VAR protocol vague, every referee can err in the same way, and no one is held accountable. Esports analysis works the same way. A wrong article is the writer's fault. But a process that permits writing on empty data — that is the system's fault. The patch is an invisible referee In esports there is a figure traditional analysis rarely names: the patch. It does not appear on stage, it is not listed in the lineup, yet it has the power to change the outcome of an entire season. When a publisher weakens a dominant champion, they are not just adjusting a number. They are rewriting the rules of the game for every team at once. I often joke that there are two kinds of referees in esports: one wears a jersey, one ships an update. Both hold the power to judge, and both are questioned far too rarely. Teams that adapt quickly to a patch are praised as elite. But meta adaptability is often mistaken for raw strength. A team that wins on a patch that suits its style is not necessarily stronger than the runner-up — it simply hit the right moment. In one analysis I once edited, the author merged two different patch versions into one, throwing the conclusion about team strength completely off. When I asked why, the answer was: I thought they were the same. That is not mere carelessness. It is a process gap: nobody was required to state the version number before writing. And if the input contains neither the game title nor the version number, any meta analysis is nothing but a decorated empty table. A gap is not neutrality There is a misconception I held in my early years in this trade: that missing data is neutral data. No injury news means the player is healthy. No wage-arrears news means the club pays on time. No integrity-violation news means the league is clean. Wrong. In analysis there is a principle called screening asymmetry. The most serious risks — wage arrears, match-fixing, injuries to key players, sanctions from organisers — are silent risks. They surface only when someone actively looks for them. If you do not screen, they will not appear on their own. And their absence from the data is not evidence of safety. It is only evidence that you never looked. VAR is not wrong. The person operating VAR is, after all, only human. The same goes for a gap in the data. It is not wrong. It is simply waiting for someone to fill it — with fact, or with conjecture. Distance covered and the trap of pretty metrics I once followed a tournament where a young player was judged to be in poor form based on a single metric: reduced distance covered. Nobody asked why. It turned out he was playing a different position, in a different role, under a different tactical instruction. Running less does not mean playing badly. Running more does not mean running effectively either. Distance covered was once packaged as a measure of effort. But ineffective running also produces pretty numbers. When you do not check where a metric comes from, you are not analysing — you are rereading a prejudice. For small teams in Vietnam, this pressure is heavier. Big teams have their own media, open data, fans ready to cross-check. Small teams do not. Nobody verifies. Nobody responds. And precisely because nobody verifies, assumptions about them often slip through. The transfer market is the same: loan deals with mandatory purchase clauses are quietly wrecking the financial plans of small clubs, turning them into farms for big clubs. But because small teams are rarely analysed, that structural injustice just drifts past. What separates the analyst from the guesser I once wrote about a major transfer and was attacked by many fans. I did not rely on rumour. I built a legal framework from the contract, cross-checked it against financial fair play rules, attached timelines and a compliance scenario. A month later, the governing body updated its rules and confirmed part of my analysis. I do not tell this to boast. I tell it to mark the boundary. The guesser starts from a conclusion and then hunts for evidence. The analyst starts from evidence and lets the conclusion form itself. But both can read the same way if the writer is skilled enough with language. And that is precisely the trap: a complete analytical framework, with nine sections and thirty tables, can be mistaken for a substantive analysis — when in fact it is just an empty skeleton dressed up. I call that the illusion of framework completeness. It is dangerous because it deceives through form. Readers see tables and believe. Readers see jargon and are impressed. Nobody asks: is the data underneath real? Fan emotion is valid data Before I am mistaken for someone who only knows numbers, let me be clear: fan emotion is a form of data. When a stand erupts over a decision, that is not madness. It is a signal that an expectation has been broken. In Vietnam and in France, fans react differently, but they react for the same reason: they see the line is not straight, and the system tells them it is. The problem is not emotion. The problem is using emotion in place of verification. Fans have the right to be angry. Analysts do not have the right to fabricate. Those are two different things, and unfortunately they are often conflated. My own test Whenever I face a document with empty input, I ask myself four questions. What is the subject of this piece, and is it named? Where does the primary source data come from, and when was it published? What would change if that subject were actually a different team, a different patch version? And finally: am I writing about fact, or about an assumption dressed as fact? If the last question cannot be answered, I stop my pen. The proposed clause If I could write one clause for esports analysis processes, it would be short: no analysis shall be published before source data is verified; if publication is unavoidable with incomplete data, the degree of certainty and the unresolved parts must be stated. It sounds simple, but most major failures in this industry trace back to skipping exactly one such clause. I remember once building a thirty-eight-point checklist for referees during the empty-stadium season. That checklist could not save the season, but it saved the reputation of the people holding the whistle. After applying it to more than twenty friendly matches, disputes dropped by nearly one fifth. That number did not come from referees being better. It came from a process forcing them to write down what they saw — before they could forget. Analysis is the same. It is not about writing more. It is about writing with records, with cross-checks, with traces that can be traced back. The offside line has never been straight, it is only that today I saw it bend. And if I fail to see it, then what is crooked is not the line. It is me.