The Name Read Wrong: Onimusha, Capcom's 2026 Slate, and the Fracture Inside the Esports Classification System

The Name Read Wrong

In Seoul, a cutting room at night has its own sound. Not the hum of machines, but the sound of a red label blinking, waiting for someone to nod. That night, the label read two words: esports. Beneath it was the name of a game — Onimusha: Way of the Sword — along with a long analysis file, full of tables, full of checkmarks, full of square cells reading N/A.

I sat still for a long while. Not because the data was difficult. Because I recognised an old feeling. The feeling of a twenty-four-year-old man, on the night of 22 July 2026, in the stands of Sang-am Stadium, reading a nineteen-year-old player's name wrong three times in front of more than thirty-one thousand people. Cho Young-wook became Cho Yong-ok. I called a person by the wrong name, and that mistake did not live in my mouth. It lived in the fact that I had not bothered to read carefully before opening the microphone.

The name I read wrong that year now rings like a song.

Tonight, the system also read a name wrong. It called Onimusha esports. It gathered a single-player action game — no teams, no tournaments, no competitive patch cycle, no players, no prize pools — into the very drawer I reserve for matches whose winners and losers are written in blood. And what kept me at my desk until nearly dawn was not the mistake itself, but its scale. A name read wrong on air affects one person. A name read wrong inside a data pipeline affects an entire analytical ecosystem downstream.

I opened my notebook again. The first line I ever wrote to myself, years ago, reads: Listen before you comment, that is how I correct my own mistakes. Tonight I turned back to that exact line, and I understood that the thing to do was not to erase the red label for the sake of cleanliness. The thing to do was to sit down, read the whole file through, and tell honestly what is actually happening inside it.

Because inside it is a real story. A story about a Japanese game company betting on premium single-player titles, about a revived legacy brand, about a content economy built around the question "how long does it take to finish", and about a classification error that looks small but could corrupt an entire body of esports analytics if we let it through.

Context: an old brand, a year of three titles, and a very ordinary question

Capcom entered 2026 with three major titles: Onimusha: Way of the Sword, Resident Evil Requiem, and Pragmata. Three names, three different bloodlines, all sitting in one catalogue. And in the document I was reading, one sentence sits near the centre, almost like the thesis of the whole original piece: Onimusha's campaign is said to be significantly longer, with more hours of content than the other two titles combined.

I stopped at that sentence for a long time. Not because it is compelling. Because it is incomplete. The writer makes a comparison but supplies no figures for the two titles being compared. How long is Requiem? How long is Pragmata? Nothing. There is only a claim standing alone, as beautiful as a slogan, and as hollow as a slogan.

This is the first thing I want readers to hold onto, because it will return many times in this piece: when a comparison omits the data for both sides, it is not measurement — it is market positioning.

Anyone in this industry knows the trade. You have three items on one shelf. You need buyers to tell them apart. You cannot say which is better, because that would be shooting yourself in the foot. So you say this one is longer, that one is more intense, the third is more novel. One adjective each. One position each. And the adjective Onimusha was handed this year is: long.

The Onimusha brand is no stranger. It is an action series set in old Japan, bound to the imagery of swordsmen, demons, and long nights under the moon. After years of silence, it has been raised again. And the way it has been raised is worth noting: not through a multiplayer title, not through a season, not through a tournament system. But through a long-form single-player campaign, sold at a package price, sustained by retail sales and catalogue longevity.

That is a business choice, and I think it is right for this moment in a very particular way. While most of the industry pours money into live titles — seasonal, with in-game stores, with endless loops — Capcom is betting on the opposite: a story with an ending. A product you pay for once, play to completion, then put away. No season pulls you back. No leaderboard measures you against others. Only you, a sword, and a long stretch of land.

And it is precisely here that the "esports" label becomes almost tragically misplaced.

Because the entire content economy around a single-player title runs on a completely different rhythm from that of a competitive title. Around an esports title, people write about patches, power shifts, rosters, transfers, tournaments, who rose and who fell. Around a single-player title, people write something else entirely: how long to beat it. How many bosses. Whether the side content is worth it. Whether you need two playthroughs for the platinum.

The document I was reading belongs to the second kind. And its very first line describing its audience states it plainly: for readers who just started the game, or who want to know its length before purchasing. That is a buying audience. Not a tournament audience.

I am not being dismissive. I make my living reading every kind of content closely, and I know that this buyer-facing kind is genuinely valuable, because it answers the question people actually have in their heads when they stand before a sixty or seventy-dollar price tag. But its real value lies in one place, and the label the system applied to it lies in another. That gap is what this piece is about.

Core One: length data and a small but real fracture

Let us begin with the numbers the document offers, because they are the spine of the entire original content.

On the difficulty setting called Action, players are said to take roughly thirty to forty hours to get through the main story. For players who want to complete everything, the figure exceeds fifty hours. For players not used to action games, it also exceeds fifty hours. The main story alone, stated elsewhere in the same document, is said to take about thirty hours.

Thirty. Thirty to forty. Fifty-plus.

I read that three times. Not to catch anyone out. Because in my trade, when two figures about the same thing appear in the same document and are never reconciled, that is a signal. A small signal, but a real one. It tells you the figure was written from feeling, from impression, from the memory of play sessions — not from a method that has been stated.

And this is where I want to linger a little longer, because it touches on how I work.

When I was still standing in the stands, I loved numbers. Scores, minutes, touches, distances covered. They gave me a sense of control. But later, sitting for four hours in Souq Waqif with fifteen North African fans, hearing them call their team's defence a hug, I understood something else. Numbers do not lie, but numbers do not tell everything either. And a number with no method behind it is worse than no number at all, because it creates an appearance of certainty that is really just a feeling.

The gap between thirty and forty hours is not small. That is a third of the playtime. A buyer who reads "thirty hours" and gets "forty hours" experiences a real difference. Thirty hours is a long-form series. Forty hours is a season. Ten hours of difference is several evenings, a book, a trip.

But wait. Before we convict the writer, let us look at the frame the writer is trapped inside.

Games-length content is not measurement reporting. It is content built to meet a search query head-on. The writer does not sit with a stopwatch. The writer reads a press build, hears a few accounts from early players, and assembles a range. That range is a communication tool, not an experimental result. And when such a range is consumed as though it were data, the fault is not with the person who produced the range, but with the person who consumed it.

That is why I call this fracture small but real. It is not a scandal. It is a reminder that there is a category of content that looks very much like data but is not data, and an automated analytics system is very likely to swallow it by mistake.

I say this as a man who has been fooled by himself. At twenty-four, I had every player statistic on the pitch memorised. I knew who ran how many kilometres. I knew whose pass accuracy was what. And I still read a nineteen-year-old boy's name wrong three times, simply because I had never sat down and asked who he was. Data gave me confidence. It did not give me understanding.

So when I read three figures about the length of Onimusha, I do not treat them as evidence. I treat them as a sign of how an industry tells stories about itself. And the story this industry is telling has a very clear name: value lies in the number of hours.

Core Two: thirty-six encounters and a division worth thinking about

In the document there is a fact that made me stop.

Thirty-six.

Thirty-six boss encounters in the main story. If we set that against the stated playtime, the division yields a notable density: roughly one boss per fifty minutes of play.

Let me be clear about why this number caught my attention more than the hour figures. It is not about length. It is about rhythm.

In football, I learned to read a team not through its goals but through the gaps between its attacks. A team that attacks every two minutes wants to impose itself. A team that attacks every five minutes wants to wait. Rhythm reveals intention. And when you read a match only by its scoreline, you miss all the intention behind it.

In the same way, boss density reveals the design's intention. One boss every fifty minutes means that after every hour of play, the player stands before a wall. That wall can be a challenge, or it can be fatigue. It depends on how differently each wall is built.

And I have to be honest: this is a design gamble, not a safe choice.

Imagine a player sitting down after work. They want to finish a chapter. But that chapter ends with a boss. They lose three times, then win. The next night, the next chapter also ends with a boss. They lose again, a few times. By the tenth chapter, the feeling of "again" starts to appear. That is what we call wear in this trade.

But look at the other side too. If every boss has its own movement, tells its own story, forces the player to learn something new, then that high density becomes a continuous chain of peaks. The player has no time to grow bored. The game becomes a piece of music rising in pitch across thirty hours.

The document has one small detail worth noting here: it concedes that some bosses are considered harder than others. A small detail, but it gives me a signal. If difficulty is tiered, then very likely the bosses' movements are tiered as well. The designers did not build thirty-six identical walls. They built thirty-six walls at thirty-six different heights.

Every player's name is a short poem, if we bother to read it closely.

I wrote that line in my notebook years ago, and tonight it returned when I looked at thirty-six boss names. Because this is exactly where my reading differs from a spreadsheet's reading. A spreadsheet sees thirty-six as many. I see thirty-six as thirty-six chances for a designer to tell me thirty-six different things about fear.

And I wonder: will people remember their names? A player walks through a game, defeats thirty-six things, and three months later remembers how many? If they remember three, then the thirty-six were just a number. If they remember thirty, then this document has missed the most important thing, because it only counted and never named.

This is where I return to the story of the name read wrong. A player remembered only by shirt number will be forgotten. A player remembered by name will stay. A boss is the same. Thirty-six nameless bosses drift away like thirty-six respawns. Thirty-six named bosses become thirty-six memories.

BUT I do not want to romanticise this too far. If thirty-six bosses are merely thirty-six reskins of the same mechanic, then that number is not richness but repetition in makeup. And players, in my experience, always notice that faster than anyone. They do not need a data table. They only need to reach the fifteenth and feel the familiarity.

Core Three: upgrades locked behind optional content

This is perhaps the most important part of the whole document, and also the easiest to overlook.

In Onimusha, the protagonist is Musashi. The character's progression runs through two things: the sword and the clothing. Both are upgraded with crafting materials, and the two main materials named are iron and leather.

So where do iron and leather come from? From side quests and from archery challenges.

I want to stress this, because it completely changes how one reads the "ten to fifteen hours of optional content" figure in the document. Optional content here is not decoration. It is part of the power system. If you skip it, you are not skipping a few extra hours of play. You are skipping the upgrade path of your sword.

Let me put it in the language of my trade. In football, there are tournaments where you must play qualifiers to earn a ticket to the main round. You can say "I only want to play the final". But you have no ticket. The qualifiers are not an extra. They are a condition.

Iron and leather function here as qualifiers. You must pass through them to be strong enough for what comes later.

And that is a design I find very clever in one sense, and very risky in another.

The clever sense: it turns optional content into unskippable content. Players no longer choose between "playing more for fun" and "not playing". They have to play. That raises average playtime, raises the sense of investment, and gives the in-game world weight.

The risky sense: it creates a trap for the rushed player. Someone who wants to go straight through the main story will arrive at the final bosses with a weaker sword than the design intended. They will find the game unreasonably hard. They will think the game is unfair. When in truth, the game told them what to do from the start, and they simply did not listen.

I have seen exactly this pattern in sport. A team skips the small matches, saves energy for the big one, then enters the big one exhausted and loses. Nobody stole their victory. They took it from themselves weeks earlier.

So when I read the document and see it list optional content as side quests, investigations, treasure hunts, chance encounters, and Lion Dogs, I ask myself: did the writer realise that part of that list is a lifeline and part is only a border?

Because in that list, one thing is called Curious Cases. These are quests described as exploring the myths and legends surrounding Eastern Kyoto in the Edo period. And that, to me, is the most interesting part of the entire optional structure. Not because it gives materials. Because it gives context.

This is where I want to say something I believe firmly.

A game set in old Japan, made by a Japanese company, can sell to the whole world by two routes. The first is the sword. The second is the culture. The first sells faster. The second stays longer.

Core Four: two playthroughs and a trophy

There is one detail in the document I read again and again, because it says a great deal about the game's philosophy of time.

To earn the platinum trophy, players must finish the game at least twice.

Twice. Which means that for a player chasing maximum completion, the playtime doubles. The fifty-hour figure becomes a hundred. And the thirty-to-forty-hour figure becomes sixty to eighty.

This is a very familiar design structure, and it always splits the player community.

For the first group, this is an invitation. They like the idea that the second run differs from the first. They carry all their existing progression and walk the same road with different eyes. The first time they walked to understand. The second time they walk to master.

For the second group, this is a wall. They have spent fifty hours on a story, and now someone tells them the story is not finished, that they must walk it again to be fully credited. For someone with little time, that is not a challenge. It is an impossible condition.

I belong to the second group by nature, but I understand the first by profession. And what I want to say here is this: the two-playthrough requirement is not a decision about difficulty. It is a decision about how much the game trusts the density of its own memory.

A game that asks you to walk again is a game confident that its first run did not say everything. The designer believes that when you return, you will see what you overlooked. A scene, a line, a face, a door.

If that belief is right, the second run is a gift.

If that belief is wrong, the second run is a punishment packaged as a reward.

And I think this is the biggest question anyone writing about this game must answer. Not "how many hours is it". But "is the second playthrough worth it". Because the answer to the second question determines the answer to the first.

Unfortunately, the document does not answer it. It only notes "requires at least two playthroughs", then moves on. And that is its largest omission.

Core Five: a three-title catalogue and the risk of eating itself

Now I want to lift my gaze off the game and look at the shelf.

Capcom's three titles in 2026 are Onimusha, Resident Evil Requiem, and Pragmata. All three are premium, story-driven, single-player games with endings. That is a very thought-provoking coincidence, because it reveals a belief.

The belief is this: the market still has room for stories with endings.

For more than a decade, the games industry saw a great migration. Money flowed into live titles — seasonal, with in-game stores, able to earn forever. And alongside it ran a quiet belief that the story with an ending was a dying model. You sell once. You have no returning players. You have no wallet left open.

But three titles in one year is a different answer. It says the pay-once model is still alive, still has buyers, and still matters enough for a major company to place three bets at once.

I read this as someone who works in sports business, and I see a familiar pattern in it.

Think of a tournament with three consecutive competition days, one big match each. Fans want to watch all three. But fans' wallets are finite. Tickets, shirts, food, time. And when three big matches sit too close together, they do not reinforce each other. They eat into each other.

That is the risk I call eating itself. It is not the risk of making a bad game. It is the risk of making three good games at the same time and letting them compete for the same wallet.

And this is where the line "longer than the other two combined" starts to carry a second meaning.

Read the first time, I saw it as a boast.

Read the third time, I saw it as a defence.

Because if you have three items on a shelf and a buyer can afford only one, you need to give them a very clear reason to choose yours. And the clearest, simplest, most measurable reason in a crowded year is: this one gives you the most hours.

Value lies in the number of hours.

I want to talk about this pattern seriously, because I think it is shaping an entire consumer culture. We are teaching players that quality can be counted. That a good game is a long game. That time is the most honest measure. And when you teach people that, they will start asking: is this game worth every hour of mine?

That is a fair question. And it is sad that the answer to it is usually not written in hours.

Contrarian angle: a classification error is not a small error

It is time to return to the red label from the start.

I have read the whole document. Across its twenty-four information points, there is not one team, not one player, not one tournament, not one patch, not one prize pool, not one competitive map. Everything is single-player content. Everything is the buyer's question: how long, how many bosses, is the side content worth it, how does the trophy work.

Yet it bears the esports label.

And I want to be clear about why this is not a small thing to shrug off.

In my trade, data is a current. It flows from sources, through pipelines, into datasets, then out into dashboards, models, predictions. Every pipeline has an assumption at its intake. And that assumption is usually very simple: if it is in this pipeline, it belongs to this category.

A wrong label at the intake does not stay at the intake. It travels with the current. It adds a non-competitive item to a competitive dataset. It forces a performance model to handle something with no performance. It forces a comparison table of esports titles to seat a single-player game beside seasonal ones.

And the worst part: the error does not announce itself. It sits quietly in the data, looking exactly like every other entry, until someone pulls it out to use.

I have seen this in sport. A statistic attributed to the wrong source, and three years later it appears in an article as though it were fact. Nobody re-checks. Nobody asks. It has been in the data too long to be doubted.

That is why I say this classification error is more dangerous than it appears. It is not one writer's mistake. It is the mistake of a system that stopped asking.

And I think the deeper cause lies in how we have stretched the definition of esports so wide that it lost its edges.

Let us try to redefine it.

Esports needs three things. First, a contest with a clear winner and loser. Second, an organised competitive structure — tournaments, qualifiers, schedules. Third, a competitive community that can practise, compare, and improve.

Onimusha, by every piece of information in the document, lacks all three.

Not because it is lesser. Because it is different. And that difference needs to be named correctly, not swallowed into a label broader than its reality.

Because when we call every video game esports, we do not make esports bigger. We make esports lose the thing that makes it what it is.

Calling one person by the wrong name is one thing. Calling a whole category of person by the wrong name is another. And the second always begins with the first.

Contrarian angle, part two: what the label concealed

But I do not want to stop at criticism. I want to speak to what the wrong label concealed.

Because while we argue over whether Onimusha is esports, we overlooked the genuinely important story inside it.

That story is about an industry in the middle of an internal dispute over how to measure value.

One side measures by time. How many hours. How much content. How many things to do.

The other side measures by impression. What do you remember afterwards. What do you retell. Do you have to retell it.

In sport, this dispute exists too. People can measure a player by goals, or by the moments that made the stands rise. These two measures do not always agree. And for years I have chosen to stand with the second, not because it is prettier, but because it is more honest about how humans actually remember.

We do not remember what we went through. We remember what we could not forget.

That is why I read thirty-six boss encounters in the document and ask: how many will people remember? That is why I read "fifty hours" and ask: what do those fifty hours leave behind? That is why I read "two playthroughs" and ask: does the second run give us a moment the first did not?

The esports label turned these questions into N/A cells. It made people stop asking about memory and start asking about hours. It turned a conversation about experience into a conversation about product.

That night, sitting in the cutting room, I remembered Mrs. Kim Soon-ja, seventy-four years old, who had not missed a single home match in six hundred and seventy-four games, and who cried the first time someone asked her about her memories. She does not count matches by pleasure. She counts them by longing. And across the twenty-four information points of that document, there is not one line about longing.

Mrs. Kim Soon-ja's voice on the empty stand — a goalless match still has a heartbeat.

I wrote that line in my notebook, and tonight I understand it better than ever. A document about a game carries no note about its heartbeat. And that is the real loss, not the wrong label.

The story of the name, third time

There is something I have not told.

After the night of 22 July 2026, when I read Cho Young-wook's name wrong three times on air in front of more than thirty-one thousand people, I did not apologise right away. I went home, re-watched the footage, listened to my own voice, and wrote a letter. In that letter, I did not say "forgive me for my mistake". I said: "let me ask permission to say your name correctly".

It is a small difference in wording, but a large difference in posture. I was not asking forgiveness for my error. I was asking for permission to do it right.

And I bring that posture into tonight, looking at a red label reading esports.

I am not trying to apologise on behalf of a system that mislabelled. I am not trying to erase the label and go quiet. I am trying to ask for permission to name things correctly. Onimusha is a single-player action game by Capcom. That is its name. And when we name it correctly, we only then begin to see what it truly is.

I once thought I understood a match when I knew the score. I was wrong. I only understand a match when I know the names of the people in it.

I once thought I understood a game when I knew how many hours it takes. And perhaps I am wrong in exactly the same way.

What I want to leave behind

There is something I learned from Kazan, in 2026, when Korea beat Germany two-nil and I cried on radio for three seconds before I could hold it back. My editor told me something I have carried ever since: that emotion belongs to a million people.

My voice cracked in Kazan, but it was there I learned which sounds are real.

Tonight, reading a long document about a single-player game mislabelled as esports, I have no cracking moment. I only have a long silence. And in that silence, I realise something about myself.

I have spent years learning to say people's names correctly. I still have not finished learning to say my own trade's name correctly.

Because if I call a single-player game esports, I am not merely mislabelling it. I am taking from it the most precious thing it has: the right to be a story with an ending, in a world that has forgotten that a story with an ending can still make people remember.

And if I take that from it, I take it from myself.

Perhaps what I must do is not to fix the label. What I must do is sit down, every time, before every name, and ask again the question I forgot to ask at twenty-four.

Who is this person?

Not: what label was this person given.

But: who is this person.

Because every name, however many times it is read wrong, still stands there waiting to be said correctly. And the job of the person behind the microphone, from twenty-four years old to the end of life, is simply that.

Listen before you comment.

Read the name before you read the score.

See the person before you see the number.

And sometimes, just sit still long enough for a game to tell you what it is, rather than pinning on it the name you need it to carry.