Seven Years Reading Hidden Signals: From the Dragon Pit to Minute 42 in Reykjavik

Minute Fifteen, and a Question With No Ready Answer

"In the first fifteen minutes, EDG controlled 62.4% of their time inside the enemy jungle. But along the river, RNG's vision score was 1.7 times higher."

I read that sentence aloud, my voice steady, my hands still holding the tablet. The man standing in front of me went quiet for about four seconds. Four seconds in a crowded interview area is a long time. He nodded, turned away, and I knew I had just survived a test I had never signed up to take.

That was the summer of 2026, in Guangzhou. I was sixteen. The match was EDG versus RNG, in the LPL Summer regular season. The final score was 2-1 in EDG's favor. The first two kills of the second game — and of the entire series — both went to RNG, both taken from bushes EDG had walked past without looking into.

Years later, writing these lines, I still think about those four seconds of silence more than I think about the match itself. Because in those four seconds, something was established: I no longer argued with feeling. I argued with what could be measured.

Vision score never lies, but it also does not know how to tell a story. People look at the stats sheet and see a row of numbers. I look at it and see a map of wrong decisions arranged in chronological order.

---

Context: A Summer When the Map Was Read Backwards

To understand why my answer silenced the room, you need to understand how the summer of 2026 unfolded in the LPL.

That was the period when leading Chinese teams began shifting away from the model of "controlling the jungle by volume" toward "controlling the jungle by position." In other words, jungling was no longer judged primarily by how many monsters you consumed, but by whether you were in the right place, and whether your opponent knew where you were.

The technical change was small. The philosophical change was enormous. If you judge a jungler by the monsters they farm, you are measuring input. If you judge them by kill participation and their presence at hot spots, you are measuring output. These two metrics frequently contradict each other, and that contradiction is where I work.

In the EDG versus RNG series, the 62.4% figure is an input metric. EDG spent more than sixty percent of the first fifteen minutes inside the enemy jungle. Standing alone, that number would lead any analyst to conclude that EDG had won the early game.

But if EDG spent more than sixty percent of the time in the enemy jungle, why did the first two kills belong to RNG?

The answer lies in a different, far less noticed metric: vision score along the river.

What is the river in a match? It is dead land. No monsters, no towers, nothing to farm. New players cross the river because it is convenient. Good players cross the river because they have already calculated that they need to be on the other bank at exactly second X.

And precisely because there is nothing to farm there, the river is where the most important early-game information concentrates: the position of the enemy jungler, the cooldown timing of Flash, the rotation direction of the mid laner.

RNG's river vision score was 1.7 times higher than EDG's in the first fifteen minutes. The consequence? RNG was present in the brush twice before EDG ever saw them.

This is what summary stats never tell you. A high jungle control rate does not mean you control information. Those are two different systems, operating on two different layers of the map.

---

The Core: Vision Score as an Immune System

When I was a young athlete, my coach had a line I never forgot: "Don't fight the darkness. Bring a lamp."

He said it about warding. But it took me years to understand he was not talking about the warding mechanic at all. He was talking about risk governance.

Imagine a team's vision score as an immune system. A healthy immune system does not stop you from encountering a virus. It only ensures that when you encounter it, your body is already prepared to respond.

A team with a high vision score is not a team that never gets caught. It is a team that, when caught, knew it would be caught thirty seconds earlier, and had arranged someone behind.

The opposite — a team with a high jungle control rate but a low vision score — is a team with big muscles and a weak immune system.

In the first fifteen minutes of a game, the gap between these two categories of metrics usually decides who wins the mid game, not the number of monsters anyone farmed.

The Fifteen-Minute Window

There is a technical reason the first fifteen minutes are considered the most important window in a professional match.

Before the fourth minute, lanes can hardly generate meaningful leads because respawn timers are too short. From minute four to minute fifteen, the jungler is the only factor capable of generating structurally meaningful advantage. After minute fifteen, outer towers start falling, and the focus shifts from "who controls the map" to "who pushes towers faster."

So every early-game analysis is really an analysis of an eleven-minute stretch, from minute four to minute fifteen.

In those eleven minutes, a professional jungler can execute roughly three to four meaningful ganks. If their success rate on four attempts is two out of four, they generated an advantage. If it is zero out of four, they lost their rhythm.

But there is a variable that is often overlooked: the opportunity cost of ganking the wrong place.

A failed gank does not only cost time. It costs two more things. The first is vision in the enemy's territory, because while you are wandering in the bottom lane, you cannot be warding the top lane. The second is map pressure, because your opponent, who is farming monsters on the other side, gains extra time to generate pressure on the remaining two lanes.

This is why the jungle control metric — which only measures presence — can mislead. It measures presence. It does not measure the value of that presence.

Three Types of Signals

When analyzing a team's early game, I always separate three signal types and never let them blend.

The first is structural signal. This is highly stable data that changes little between games, such as the timing of the first outer tower falling. If a team routinely destroys the first outer tower before minute twelve, that indicates a very specific early-game plan.

The second is behavioral signal. This is data reflecting habits, such as a jungler's preferred rotation after clearing their third camp. This type requires many games to establish, and it can be broken by the team itself if they realize they are being read.

The third is intrinsic signal. This is data reflecting a moment's state, such as Flash coming off cooldown at second sixty in a lane. This type is highly accurate but extremely short-lived.

Only when these three signal types agree do I draw a conclusion. With only one type, I treat it as information, not a conclusion.

This is a discipline I learned not from books, but from a mistake.

---

From the Dragon Pit to the Mud: The Origin of This Style

I started my career in a position few people think about: a young athlete removed from the race by a wrist.

In 2026, I was fifteen, with an injury to my left wrist. It was a quiet injury — just a small pain after each training session, then more pain, then a point where I could not hold a mouse for more than twenty straight minutes. The doctor said rest. I rested. Then the scouting window arrived, and my name was not on the list.

During recovery, I watched the World Cup in Russia. I did not understand football the way people usually understand it. I looked at the pitch the way I looked at a map with vision.

In the Portugal versus Spain match, three-all, Cristiano Ronaldo took a free kick in the eighty-eighth minute. The ball went over the wall, past the keeper, into the net.

I wrote an analysis on a community forum. In it, I called that free kick a "Flash plus ability, executed perfectly." I argued that the Spanish goal at that moment resembled a stationary practice dummy, and their defense resembled brush with no vision.

The result: four thousand two hundred shares. Football fans messaged me asking what the metaphor "brush with no vision" meant.

From that night, I understood something. The language of video games and the language of traditional sports are not far apart at all. They are just using two different sign systems to describe the same thing: space, time, and decisions.

From the mud of injury, I learned to read matches with the heart of a survivor. But for that heart to say anything valuable, I needed data as a spine.

A Working Principle Born There

There is one principle I set for myself after that first piece and have kept for seven years: every emotional judgment must be anchored to at least one verifiable fact.

If I want to write that a player performed poorly, I must point to exactly what they lost. If I want to write that a tactic has been decoded, I must point to a chain of metric changes across at least three games.

This discipline does not make writing drier. It makes it more trustworthy. And in an information environment where everyone has an opinion, trustworthiness is the only asset with long-term value.

---

The Saigon Stray Cat: When Data Lies Outside the Scoreboard

In 2026, world sports paused. Esports events moved online. I, seventeen, sat in Guangzhou and followed a small tournament between amateur teams in southern Vietnam.

I found a name.

His handle was Pun. He played support, picking a champion with stealth and close-range assassination. His streak was twelve straight wins. His kill participation was eighty-seven percent.

What does eighty-seven percent mean?

Across those twelve games, in nearly nine out of every ten kills his team secured, Pun was present. For a support player, this number is close to absurd. Support is the role that usually sacrifices time to ward, to rotate, to hold position. Warding while also being present in almost every fight requires a rare level of map-reading ability.

But there was one detail the stats sheet did not tell.

Pun had no sponsor. No coach. No training facility. He played from an internet cafe in Saigon, during a time when the city was empty.

I wrote about Pun in a memoir style, calling him "a lone hunter in a city with no people." The piece spread far enough that professional teams began inquiring about buying Pun in the next transfer window.

What I learned from this story matters more than the story itself: there are signals that do not live on the scoreboard, and they only appear when you are willing to read the context surrounding the number.

The eighty-seven percent figure is a technical signal. Playing from an internet cafe is a contextual signal. Only the two together become a story worth reading.

With only the metric, I would have written a dry analysis of a support player with a high number. With only the context, I would have written something moving but hollow. Both are needed.

---

Minute Forty-Two in Iceland

In 2026, I was eighteen, invited by a major platform to commentate at the World Championship held in Iceland.

In the semifinal, at minute forty-two, a legendary player was caught in the enemy jungle while trying to secure vision. His team lost the series two-three.

In that moment, live on air, I said a line: "He is like a beam of light, but even a beam of light must go out for the night to take the throne."

That line was translated into fifteen languages.

But what I want to talk about here is not the line. What I want to talk about is the analysis behind it.

Why Would a Top Player Go Secure Vision at Minute Forty-Two?

At minute forty-two of a professional game, the match has entered its late phase. Towers have mostly fallen. Teams are preparing for decisive fights around major objectives.

In this phase, vision becomes the scarcest resource. Without vision, you cannot decide whether to fight or retreat. Without vision, you do not know where the enemy is on the map during a stretch of time where a single mistake ends the game.

So a key player going alone to secure vision in a dangerous area is not a tactical error. It is a calculated decision.

The problem lies elsewhere.

When a team forces its key player to secure vision alone at minute forty-two, that team failed to build a vision structure twenty minutes earlier.

This is the kind of analysis I pursue: not blaming the individual, but tracing back to structure. A wrong decision at minute forty-two is usually the consequence of a wrong choice at minute twenty.

After that tournament, I wrote an analysis of how teams use junglers capable of creating mid-game disruptions to shift the course of an entire season.

That piece was widely read, but what I remember most is what I cut.

I cut a long passage about the audience's emotions. I cut a passage about head-to-head history. I cut beautiful sentences. I kept the only part with lasting value: the mechanism.

---

The Contrarian Angle: When Vision Score Becomes a Religion

At this point, I must argue against myself.

For years, I was a strong advocate for using vision data as the central metric. I used vision score to defend my positions in debates where the other side would not even listen to the argument, only to the gender of the speaker.

But I realized that way of using it carries a trap.

When a single metric becomes the center of every debate, it starts being used as a moral shield. People stop asking "what does this metric mean in the context of this match?" and only ask "who has the higher number?"

That is when analysis becomes propaganda.

Three Common Errors in Reading Vision Score

The first error is comparing vision score between two teams without accounting for match duration.

A match lasting forty minutes will have a significantly higher total number of wards placed than one lasting twenty-five minutes, because after minute twenty-five, teams are forced to place more wards to move safely. Comparing totals is comparing two things of different natures.

The correct metric is vision score per minute, or better, vision score by specific phase.

The second error is ignoring ward location.

A team that places twenty wards in its own safe zone will have a higher vision score than a team that places fifteen but puts all of them in the river and enemy jungle. Yet it is precisely the wards in dangerous areas that generate valuable information.

The third error, and the most serious, is turning vision score into the sole explanation.

I have fallen into this trap. I once wrote an analysis attributing an entire game's outcome to the vision gap in the first fifteen minutes. A reader sent me a long message pointing out that in that game, the winning team also had another advantage: they rotated their mid laner two minutes earlier, which freed their jungler from escort duty.

She was right. I had overlooked a variable of equal value.

Since then, I have applied one rule: I only assert that a hidden signal is a cause when at least three independent signals point the same direction. With only one, I write "there are signs," not "precisely because."

Some stars do not choose the spotlight; they simply wait for the right rain. But a writer is not allowed to declare themselves the rain. A writer is only allowed to record that it rained, when, where, and based on what data.

---

Cross-Reference With Traditional Sports: Lessons From the Pressing Problem

Many people are surprised to learn that I spend more time reading about European football than about my own discipline.

The reason is simple. Football has a longer data history, and therefore it has already passed through the traps esports is now entering.

The Story of High Pressing

For about a decade, high pressing was treated as the ultimate answer to the problem of controlling a match. Teams that adopted it gained an edge, and analysts praised it as a revolution.

Then, at some point, mid-table teams began responding in a very pragmatic way: they increased their physical volume, extended their passing sequences in their own half, and turned the match into a running contest.

The result? High pressing ceased to be an absolute advantage, because opponents had prepared their fitness to endure it. Good pressing teams still won, but they no longer won because of pressing. They won because they had better players.

Does this mean high pressing failed? No. It means every tactical advantage has a life cycle.

I see exactly the same cycle in esports.

There was a phase when jungle control was the answer. Then teams responded by increasing their early-game defensive capacity, accepting jungle concession in exchange for lane safety. Then the jungle control metric gradually lost its weight.

Every metric in esports has a life cycle. Whatever metric is praised today will be neutralized by the best teams within eighteen months.

This is why I never write a piece simply to praise a metric. I write to show what question that metric is answering, and how long that question will remain valuable.

On Transfers and Late-Career Stars

Another topic I follow closely is the transfer market.

There is a recurring phenomenon across many disciplines: when a newly emerging league arrives with large money, it buys stars who are past their peak and turns them into media icons.

From a financial standpoint, this is a rational decision. A star past their peak still brings viewers, still sells shirts, still attracts sponsors. From a development standpoint, it is a decision to postpone.

Why? Because money is spent on names instead of on the development system. A mature league is measured by the number of twenty-year-old players it produces, not by the number of thirty-five-year-old players it buys.

I have tested this against data many times. In leagues that spend heavily on late-career stars but do not build academies, the share of domestic players appearing in starting lineups after five seasons usually does not rise. In leagues that spend less but persistently build academies, that share rises steadily.

This is not a moral judgment. It is an observation about how resources are allocated.

---

The Problem of Empty Data

Now I have to address the hardest thing in this piece.

When I sat down to write it, the material I received contained no analytical content at all. The data fields were empty. No tournament name, no team, no patch, no player, no metric.

There is a very easy professional reflex in this situation: fill the gap with what you already know. I know enough about this discipline to write something that sounds entirely plausible. I could pick a familiar tournament, assign it a patch, add a few convincing-looking metrics, and the piece would flow.

But if I did that, I would betray the very discipline that gave me this career.

Vision score does not lie. But a writer who lies can manufacture any stats sheet they want.

The Trap of Writing Without Signal

In this profession, there is a category of writing I call "the piece from nowhere." These are articles with full structure: a compelling opening, clear context, three-part analysis, a forward-looking conclusion. But if you peel away each layer, the bottom layer contains nothing. No verifiable fact, no traceable source, no one accountable if the information is wrong.

This type is more dangerous than writing that is obviously wrong. Obviously wrong writing gets caught. Writing from nowhere survives in aggregators, gets cited, gets translated into many languages, and eventually becomes part of collective memory.

Five years later, someone will cite it as historical fact.

That is why I choose a different approach: when there is no signal, write about the absence of signal. That is still an honest act, and honesty in this profession is the only thing that remains after every media fever has settled.

What I Have, and What I Do Not Have

I have seven years of observing this industry. I have notes on specific matches I watched live. I have a drawer full of slips recording numbers I once verified, and another drawer full of numbers I once doubted but could not verify.

I do not have analytical material for this piece.

And I think saying so is worth far more than pretending otherwise.

---

Standing Between Two Cultures: What Insiders Cannot See

There is one aspect of this work I rarely discuss, but it affects every line I write.

I was born in Vietnam and work in China, reporting on esports for the Chinese market. This position gives me a vantage point that neither insiders nor outsiders possess.

Differences in How a Match Is Read

Fans on either side of the border often love and hate players in different ways, and those differences reflect different underlying assumptions about what counts as playing well.

On one side, people tend to value stability. A player who makes few mistakes is seen as the foundation of a strong team. On the other side, people tend to value moments. A player who can produce a decisive play at a critical time is seen as the one who won the match.

Both views are partly right, and both miss something.

When I write for Chinese readers about a Vietnamese player, I must translate in both directions. I must explain why a stability metric can be undervalued on one side. I must explain why a flash of brilliance can be overvalued on the other.

A writer at an intersection carries a specific responsibility: not to let the familiarity of the culture they grew up in decide what they see.

What This Means in Practice

Before every piece involving a comparison between two esports cultures, I ask myself three questions.

First, if a neutral fan belonging to neither culture reads this, will they understand why I chose to compare these two things?

Second, am I comparing two things of the same kind, or am I comparing a thing to an idealized version of it?

Third, if the data contradicts my feeling, am I willing to write according to the data?

The third question is the hardest. It forces me to admit that my feeling may be wrong.

I have been wrong. Many times. And each time, I rewrote the piece — not to make it prettier, but to make it truer.

---

The Numbers I Did Not Write

In my drawer there is a file I call "numbers unused."

These are data points I collected but that did not qualify for publication. Some because the sample was too small. Some because the source could not be verified. Some because I doubted the measurement itself.

A typical example is a team's win rate in games where they placed more river wards than their opponent in the first fifteen minutes. Sounds reasonable, doesn't it?

The problem is that the causal relationship may be reversed. A team that is already winning tends to ward the river more, because they are safer doing so. So is the high win rate the result of warding, or is warding the result of winning?

This is the reverse causality problem, and it appears in nearly every esports analysis based on summary data.

How I Handle Reverse Causality

There are three approaches I commonly use.

The first is to find an independent mediating variable. If I want to prove that warding generates advantage, I need a case where a team warded heavily while in a disadvantaged position. If that team still turns the game around, that is powerful evidence.

The second is to compare the same team over time. If a team increases its river ward rate while all other factors remain constant, and its win rate rises accordingly, the causal relationship becomes more credible.

The third, and my favorite, is to re-read the match notes chronologically. Instead of asking "which team had the higher metric," I ask "what happened at the first second, the second second, the third second."

This approach is slow. A piece written this way can take three days. But it gives me something the stats sheet cannot: a verifiable story.

---

On Women Who Write About Sports

I must address something I avoided for many years.

When I started writing, people often asked whether I understood what I was talking about. That question was never asked of male writers of the same age.

At sixteen, when I held up a tablet and read out metrics, I was not just answering a question about tactics. I was answering a question about the right to speak.

And the only way I knew to answer that question was to make my answer impossible to dispute on the data.

What I Do Not Want This Piece to Become

I do not want this piece to become a story about overcoming prejudice. That is a story someone else has already told better than I could.

I want to talk about something more specific: the pressure to always be right.

When you occupy a minority position in a field, every mistake you make is not just your own mistake. It is read as evidence for a prejudice about an entire group of people.

That pressure has two effects. It makes you more careful, and it makes you more afraid.

I learned to convert that fear into process. Every piece I write goes through the same check: which fact, which source, which date, who confirmed it.

This process does not make me fearless. But it turns fear into part of a professional standard, rather than an obstacle.

---

On Commercialization and Things Used as Props

There is a topic I follow but rarely write about, because it easily becomes a moral sermon.

That is how organizations use underfunded competitions as a communications tool.

This phenomenon appears not only in esports. It appears in every discipline. A competition is founded, a press release is issued, a few images are shared, and then silence.

What interests me is not the silence. What interests me is the financial structure behind it.

If a competition has a budget for communications but no budget for prize money, the order of priorities has been stated clearly. If a competition has a budget for an opening ceremony but no budget for training facilities, the order of priorities has been stated clearly.

The way to read a sports organization is not in what it declares, but in the budget line it allocates.

I apply this reading to every sports entity I follow, including the ones I love.

And I apply it to myself. Each year, I look back at what I spent my time on. If I claim that data analysis matters most to me but spend most of my time on pieces that travel easily, my claim is meaningless.

---

What I Believe After Seven Years

After seven years, I believe some things, and I doubt others.

I believe data is the foundation. Without data, every judgment is a personal preference dressed up in language.

I believe context is the condition. Without context, data becomes a tool for conviction rather than understanding.

I believe story is the vehicle. Without story, no one remembers your conclusion, however correct it may be.

And I doubt conclusions that arrive too easily.

Whenever I read an analysis and find myself nodding from the first paragraph, I stop and ask: is this piece telling me what I already wanted to believe?

On Minute Eighty-Eight

There is a line I wrote years ago and still keep in my notebook: minute eighty-eight is the boundary between a legend and a forgotten story.

In that minute, a single moment can shape an entire person's career. But what few notice is this: to be present at minute eighty-eight with that opportunity, one had to do a great deal of work in the minutes no one records.

The twelfth minute of the first half. The thirty-seventh. The fifty-fourth. The minutes where nothing special happens.

That is where the real work happens.

And that is also where the writer must stand. Not at minute eighty-eight, where everyone is watching. But in the minutes before, where few bother to look.

---

Conclusion: A Question Left Behind

I received empty material for this piece. I chose not to fill it with what I already knew.

But I also chose not to stop at saying it was empty. Because an absence, properly articulated, is still information. It tells you that there is a break somewhere in the flow from event to reader.

Every sports piece travels such a flow: from the field, to the data sheet, to the analyst, to the writer, to the reader. At each junction, information can be distorted, trimmed, or replaced with something that sounds more plausible.

I do this work because I believe the flow can be made a little more transparent.

As I write these lines, I do not know which playstyle the current patch favors. I do not know which tournament is entering its decisive stage. I do not know who is preparing a performance that will be discussed years from now.

But I know one thing. When the material arrives, I will read it the way I always read: find the number first, find the context second, and only tell the story once both have agreed.

Vision score never lies, but it also does not know how to tell a story. Telling stories is a human task. And a good storyteller must know when they do not yet have enough material to begin.

The question I leave for myself, and for everyone in this profession: when you are handed a blank page, do you have the courage to say that it is blank?