From 'Here We Go' to Resident Evil Code Veronica Remake: When Leaks Become an Emotion Industry

At two in the morning in Seoul, I sat in front of a screen reading a thread more than four hundred replies long, all of it about a game that had never been officially announced. One user laid it out neatly: Claire Redfield would follow a semi-linear route with more freedom to explore; a crafting bench would appear in the item system; Steve Burnside would get an image rebuild; Leon S. Kennedy would appear in a short segment; the confrontation between Chris Redfield and Albert Wesker would be expanded; weather and injury systems would affect character outfits; and an old enemy, Bandersnatch, would return.

I read it through, then read it again, slower. The feeling was so familiar that I had to put the phone down and look out the window. It was exactly the feeling I get during every transfer window, when an anonymous account declares that a striker will join a club, complete with shirt number, announcement timing and fee. Nothing about it can be verified. Yet everyone believes it, because the more specific the detail, the thicker the belief. The problem with a leak is not whether it is true or false, but that it is told too smoothly to be doubted.

That night I understood something my years in the trade had taught me but I keep forgetting: we do not consume news, we consume the feeling of waiting. And in that emotion industry, the person who writes a leak is not merely a reporter. They are a producer of a feeling cheaper than a match ticket, but faster-spreading than any contract.

To read this story properly, two layers of information must be separated. The first layer is what Capcom has confirmed: a remake of Resident Evil: Code Veronica, built on RE Engine, third-person, drawing on the original released on 3 February 2026 for the Dreamcast, developed by the core team behind RE2 Remake (released 25 January 2026) and RE4 Remake (released 24 March 2026), with adjustments to parts of the story and additions suited to a modern experience. The second layer is everything else, from the semi-linear design and crafting bench to the Steve Burnside image and the Leon appearance and the expanded Chris versus Wesker fight, all of which remain unconfirmed leaks.

The ratio between those two layers is the real story. The verified part is narrow and dry. The unverified part is wide, vivid and easy to remember. A leak is structured more like a poem than a report: rich in proper nouns, rich in sensory detail, leaving just enough space for the reader to fill in the rest with their own imagination.

I used to think this was a story belonging only to the games world. The closer I look, the more it is the story of my own trade. In football and in esports we have a complete leak ecosystem: aggregator accounts, transfer journalists, communities that translate, and a layer of fans doing verification work for free. The phrase 'here we go' that Fabrizio Romano uses has become a ritual. When it appears, fans treat the deal as done, even though no document has been signed.

The mechanism behind the power of that ritual is not complicated. The more specific a detail, the harder it is to fabricate, and the stronger the sense of authenticity. But the sense of authenticity and the level of authenticity are two different things. Psychologists call this the vividness effect: the brain processes concrete images faster and believes them more easily than an abstract sentence. A crafting bench, a ten-second Leon appearance, a three-minute extended Chris versus Wesker fight, all are grains of sand small enough to slip through the net of suspicion.

What caught my attention was not the content of the leak but how the community reacted. Almost immediately, people drew diagrams, translated it into Korean, made ten-minute analysis videos from three lines of text. The transformation from information to product took hours. An unconfirmed rumour had become content, a broadcast schedule, a debate with winners and losers.

Based on my experience following matches, I have learned that the speed at which information spreads is inversely proportional to how well it is verified. The easier it spreads, the less evidence it has. That is a harsh rule, because it means most of the content we read each day sits on the wrong side of the curve.

Behind that mechanism lies a business logic that is far from invisible. A remake of a long-established brand is a lower-risk bet than a new brand: the fan base exists, the graphics engine exists, the design assets exist. The publisher needs only one new thing, a sense of anticipation. And anticipation can be fed with leaks at no advertising cost at all.

This is where I want to pause longest. In many industries, a leak is treated as an accident. In gaming and in sport, a leak is often treated as a semi-official marketing channel. It lets the publisher or the club keep a safe distance: if the public likes it, they can move closer at the official reveal; if the public reacts badly, they can say it was only a rumour. The risk is pushed onto the fans, who have already invested emotion in something that does not yet exist.

In other words, a leak is an emotional options contract. Fans pay upfront with expectation. The publisher keeps the right to decide whether to deliver.

In this specific case, I believe another possibility deserves consideration: details that fit too well and look too good may come from a partial source, real in part but extrapolated to be more attractive. An internal build that leaks out can be embellished by a community with details that insiders never decided. Then the leak is both true and false, and the true part is always easier to remember than the false.

This is where I want to speak plainly, even though I am used to standing behind the screen rather than in front of it. An unconfirmed leak presented as if it were almost certain is a professional error, not a clever move. A reporter may not invent details, but if they omit the words 'unconfirmed' at the start of the sentence, they have created something more powerful than fake news: a truth misread because it was never labelled.

I once made exactly that mistake, only in another form. On 22 July 2026, at the age of 24, I commentated the Seoul derby at Sang-am, FC Seoul drawing 2-2 with Suwon Bluewings. In the 90th plus third minute, a 19-year-old named Cho Young-wook equalised, and I mispronounced his name three times in a row. In front of 31,248 spectators and who knows how many radio listeners, I turned a person into a wrong syllable. What frightened me was not that I erred, but that I had said his name all match without ever checking.

I went back to the footage, wrote him a letter of apology, and asked permission to say his name correctly. When I published the moment he struck the ball into the net, with his eyes lifting to the stand, the eight-hundred-word piece was shared more than one thousand two hundred times. Many said I had seen what they had missed. But I knew the truth was different: I had only done the one thing I should have done from the beginning, which was to listen before commenting.

Since then, I stopped reading the scoreline first and started reading the person inside the scoreline. For every match I keep a private note about one player's name, background and dream, not to go on air immediately, but to understand them before telling their story. The name I mispronounced that year now rings out like a song, and it reminds me daily that a mispronounced name is also a kind of leak: it spreads fast, it sounds true, and it hurts the person who carries it.

On 27 June 2026, at Kazan Arena, South Korea beat Germany 2-0 with a goal by Kim Young-gwon in the 90th minute and a second by Son Heung-min in the 90th plus sixth. I was a 25-year-old radio commentator, and I cried on air for three seconds. I feared being judged unprofessional and thought of apologising, but my editor told me that emotion belonged to millions. When I wrote the story at three in the morning, I let the words tremble like the stands. The scoreline appeared once. The rest was the breath of a generation.

I tell these two stories not to talk about myself, but to point at one thing: emotion is the best raw material in reporting, and also its most dangerous poison. A good writer is not one without emotion, but one who knows where to place emotion and how to name it correctly.

Applied to the Code Veronica Remake story, I see a clean split. The confirmed part belongs to Capcom and has value only as an anchor point. The unconfirmed part belongs to the community and has value only as a signal of what fans long for. Read it as a technical specification and you will be disappointed. Read it as an emotional map and you will learn a great deal.

Looking at the leaked list, three desires stand out. One is the feeling of freedom in a game famous for cramped spaces. Two is justice for a character mocked by the community for more than twenty years. Three is iconic confrontations extended. All three are emotional needs, not technical ones. The leak therefore reflects the fans more accurately than it reflects the product.

This is when I think of Mrs Kim Soon-ja. In 2026, when the pandemic silenced every pitch, I ran a twelve-night livestream series called Echoes from Empty Seats, inviting forgotten fans to speak. On the third night, Mrs Kim Soon-ja, 74, a FC Seoul supporter since 2026, said she had not missed a home match in 674 games, and she wept because it was the first time anyone had asked about her memories. I let her talk for eighteen minutes without interrupting.

What I learned that night is a principle I think games media is missing. When you let others speak first, you hear what they actually want, not what you want them to want. The empty seat that day said more than any crowd. And an unconfirmed leak, if forced to answer before it has finished speaking, becomes an empty seat stuffed with our own echoes.

Here I want to return to a view I have always held in this trade: pre-season friendly tours and the marketing attached to them often turn clubs into circuses, where players' fitness is exploited in exchange for revenue. Leaks in gaming operate on a similar logic, except that what is exploited is not muscle but waiting. Fans are put on stage, made to perform their own eagerness, and pay with their own trust.

There is another, counter-intuitive reading that I consider more important. We tend to think leaks harm the publisher. Look closely and leaks harm fans more. The publisher loses a little surprise at the reveal. Fans lose more. They lose the ability to be fully surprised. When every detail has been told in advance, the official reveal is no longer a door opening, but a checklist comparing what percentage of the leak was right.

In sports culture, we are used to waiting for a deal to be officially announced even when we have known about it for months. And we still watch the unveiling. So I do not think leaks will disappear. But how we treat them can change. We can treat them as a draft, not a final manuscript.

One detail in this story caught my attention more than any other. It is that a fictional character, Steve Burnside, is said to be undergoing an image rebuild. In sports language, that phrase belongs to a player in crisis, needing to be repositioned in the squad. But here the subject is a character created by a writer. Using sports language for a writing decision shows how fully we now read every story through the lens of performance.

I think this is the biggest blind spot of collective memory. We remember names because they once disappointed us, then assume their existence needs fixing. But a character is not a metric. Steve Burnside may be clumsy, may irritate players, and that very irritation is part of the work. If the remake erases that clumsiness to please the majority, it may be smoother, but it also loses a scar that fans once owned.

This also brings me to the larger story of esports, where I began my career in 2026 as a player and tournament organiser before moving into media. I hold a view that is rarely stated: a women's competition run as a closed ecosystem, self-sufficient and detached from the open competitive current, will never produce a genuine star. It only produces famous people inside a small room. The same holds for leaks. A community that confirms itself, that praises itself for guessing right, will never build a trustworthy information platform.

And here is the point where I want to name what I consider the heart of the matter. The power of a leak comes not from how true it is, but from the gap it leaves behind. Anyone who fills that gap with certainty is selling you something that does not belong to them.

This leads to a professional question. If I am the one reporting, what should I do with a leak like this? I think the answer lies in three very concrete moves. First, always place the words 'unconfirmed' where the reader's eye will land, not at the end. Second, separate verified and unverified material into two distinct blocks, never mixed. Third, and most importantly, never use a small detail as evidence for a large conclusion.

Those three moves sound dry, but they are precisely what keeps this trade standing. I learned that at 24, when I mispronounced a player's name three times in a row and realised that the fear of being criticised is less frightening than erring without knowing it.

Every player's name is a short poem, if we bother to read it closely. With a game, the same. Every leaked detail is a line that can be read in rhyme or out of it. But a poem without a source note is not a poem, it is a rumour broken into lines.

Back to Code Veronica Remake. I think we should hold a simple reading posture. The remake is confirmed to exist. It runs on RE Engine, in third person, developed by the team behind RE2 Remake and RE4 Remake. Capcom says it will adjust parts of the story and add improvements suited to a modern experience. That is the entire hard part of the story. The rest is software, and software can be rewritten many times before release.

I do not say that to belittle those who spent nights translating and analysing the leak. They are the ones keeping the community alive between two announcements. But there is a thin line between keeping the fire and burning the house. The firekeeper says this is what we are hearing. The arsonist says this is what will certainly happen.

In sport we call the period between two events by a beautiful word: the season. A season is a stretch of time in which nothing is settled, and precisely because it is unsettled it is worth living. A leak, read properly, is the season of a game not yet released.

So what is the ending of this story? If the remake arrives and matches most of the leak, the community will cheer that they knew in advance. If it differs, the community will say the publisher changed the plan. In both cases the leak gets the credit, because it is never held responsible. That is the most powerful gift we accidentally give it.

I want to close with a thought I believe is progressive rather than a summary. If over the next few years the games industry and the sports industry learn one thing from each other, I hope it is this: let fans keep the right to be surprised. It is the last asset they still own, and the only thing an official reveal can give away without needing any leaked detail at all.

In a match without a goal, we still hear the heartbeat of a whole community. In a game not yet released, we hear that heartbeat too. The reporter's job is not to lie about that heartbeat, and not to rush to count its beats on behalf of the people living inside it.