The Empty Analysis and the Subject-Substitution Trap: The Discipline of an Esports Reporter

Sitting in a small studio in Shenzhen, I opened a nine-section report. Every section had a heading, a table, a notes field. And every field said the same thing: insufficient data. The analysis was about a match with no tournament name, no patch number, no team, no player. It had only a skeleton.

I read it three times. The first time I saw emptiness. The second time I felt irritation. The third time I realised my hand was already on the keyboard, ready to type a team name I had never verified. Nobody asked me to. The skeleton itself invited me to, because a table with nine rows looks a great deal like a table waiting to be filled.

That was the moment I understood the biggest danger of this trade: saying something formally correct about something that does not exist.

I have followed esports since I was seventeen, when I secretly wrote a blog about a match in Hanoi while hiding it from my parents, and ten years on I still keep one odd habit: I save my abandoned drafts. That draft belonged to the most frightening category. It was clean. It was orderly. It was complete. Legends are not born on stage; they are sewn from details nobody notices. So are disasters in the news trade.

A post-match verdict usually has twenty minutes to live before breaking news buries it. The writer receives a summary, not the original text. The process is split into two layers: the first reads the source and extracts raw facts such as tournament name, patch number, teams, players, figures; the second interprets them. When the first layer returns blank paper, the person on the second layer does not know they are holding blank paper. They only know they are holding a frame.

That frame is beautiful. It has a slot for the game patch, a slot for tournament format, a slot for club finances, a slot for competitive-integrity risk. It resembles a scorecard waiting to be marked. And because it resembles one, people mark it. Not with data, but with memory of similar matches. Memory is more generous than truth.

I saw this once at a tournament I was hosting. One evening after a semi-final, an editor asked me whether the tournament server version matched the practice server version. I said I did not know. He nodded and wrote in the piece that the teams had adapted well to the update. It sounded perfectly reasonable. It was also entirely invented. It passed through three editing layers, because nobody in those three layers had ever read the raw data line.

Subject substitution is the most visible path. When the source is empty, the analyst picks a plausible subject: a team on a hot streak, a controversial patch, a freshly completed transfer. From there every conclusion looks certain, because they are built on a foundation the writer himself poured. In esports, getting the patch wrong means getting the whole story wrong: the same team, on two different patches, is two entirely different teams. Getting the roster wrong means analysing a group that has never stepped onto the server together.

Subtler still is screening asymmetry. The heaviest risks in this industry, including unpaid wages, match-fixing suspicions, injuries to star players and publisher sanctions, are silent by default. They surface only if someone actively goes looking. A dataset that does not mention unpaid wages does not prove wages were paid. It proves only that nobody opened that drawer. Based on my experience following matches and transfer windows, this is the costliest kind of error: it does not produce false news, it produces false reassurance.

And the last trap, the most dangerous of all, is the illusion of completeness. A document with nine sections, tables and risk classifications will be read very differently from a single line saying there is no data. Non-specialist readers judge credibility by structure rather than content. Professional writers do the opposite: the more perfect the structure, the harder they must ask where the data is.

In 2026, at eighteen, I wrote a ballad for Croatia after the final on 15 July at Luzhniki. Croatia held 61 percent possession, took 22 shots, and lost 2-4 to France. I called it a mis-executed gank. Thirty thousand reads, forty thousand shares, and I was emotionally exhausted. I had idealised a team whose fitness for a third consecutive extra-time match I never checked. The snow had melted and the song was still on the pitch, like a position nobody occupied. That lesson taught me something highly technical: without data on the fundamentals, every word of praise is a loan.

Four years later, on 22 November 2026, Saudi Arabia beat Argentina 2-1. I got a call at two in the morning to commentate live. In the forty minutes of preparation, I chased exactly one thing: how many times Argentina had been caught offside in the first half. That number decided the entire story. My emotions decided nothing. Ninety days watching a static server taught me that the biggest fight begins on a quiet evening. That night, quiet meant searching for data before opening my mouth.

There is a romantic reading of honesty: the brave writer is the one who dares to say I do not know. I do not entirely believe it. Saying there is insufficient data without saying what comes next is just a polite shrug, and a polite shrug still leaves the reader empty-handed.

That empty report did more than that. It identified which field was missing and why, which could be filled with one email, which had to wait until the tournament began, and which belonged to the risk group of wages, competitive integrity and injuries that cannot be declared clean merely because nobody mentioned them. A decent empty analysis is a diagnosis with a to-do list. That is labour, not humility.

But watch the other side of the coin. Insufficient data can become a very convenient shield for the lazy. If every match is answered with that phrase, the writer never has to be accountable for a single judgement. This trade lives on bounded judgement: stating what you are basing it on, how strong the claim is, and where you would be wrong. Silence has never been a virtue in itself. Silence becomes a virtue only when it was paid for with an evening spent hunting for numbers.

The first gank never comes from the jungle; it comes from the dark corner of the keyboard. The nine-section skeleton invented nothing. It simply stood still and waited for me to invent. I think everyone in esports reporting should ask themselves one thing: how long did I spend last night trying to know, before deciding that I could not know.