SUBPLOT The story under the story. Breakdowns, theories, reactions, opinions, reviews and lore from the people who actually watch it.
Tue, 20 October 2026 35 creators writing here Become a SubPlotter →
← Back to the front page
TheoryGaming

Resident Evil Code Veronica Remake May Have Slipped to Fall 2027, and That Might Be Good News

A credible rumor points to a later launch window, and the reasons behind it could mean a much bigger remake

C Chaos (AI-assisted)26 September 2026 · Editor: Digital Fox Talent Editorial Team 1,180 words · 5 min read

Resident Evil Code Veronica may have been delayed, and that delay might actually be the best thing that has happened to this remake. According to a new report, Capcom may have pushed the game all the way into fall 2027, not because the project is falling apart, but because it may have grown into something a lot bigger than originally planned.

First, I want to make something clear: Capcom has not officially delayed Resident Evil Code Veronica. The company revealed the remake at Summer Game Fest and only gave a broad 2027 release window, which was smart, since there was never an official date for Capcom to move off of. Earlier insider reports had the game targeting the first half of 2027, possibly as early as the first quarter.

Resident Evil insider Dusk Golem says there is a very high chance the game has internally slipped into fall of next year. He says he has heard this from three separate people he trusts, but he is not independently locking it down. So treat it like a credible rumor, not a press release. We are not doing the internet thing where one insider makes a post and suddenly everybody pretends Capcom held a press conference. Dusk Golem has been ahead of several Resident Evil announcements before, including this remake existing in the first place, which is why people listen.

The important takeaway is not that we have to wait a few extra months. We have waited more than 25 years for Code Veronica to get special treatment, and I think we can survive another summer. What matters is why the internal timeline may have shifted, because apparently Capcom has been making some significant late changes, and the scope of those changes is a lot larger than expected.

Code Veronica skipped Tokyo Game Show entirely, and that absence feels strange

That could explain why Resident Evil Code Veronica completely skipped Tokyo Game Show. Capcom officially revealed the game, confirmed it for 2027, and then showed nothing at one of the biggest gaming events in Japan. No gameplay, no trailer, no character showcase, not even a few seconds of Claire opening a door slowly.

That absence felt strange once you consider that Capcom normally keeps feeding people new information after revealing a major Resident Evil game. But if the team recently decided to expand or restructure large portions of the remake, showing unfinished gameplay would accomplish nothing. They would either be showing material that could change, or locking themselves into expectations they are not prepared to meet.

I like that reasoning. If Capcom looked at the project and decided it was not ambitious enough, I am okay with the delay. Code Veronica is not some disposable side story that only hardcore fans remember. This is one of the most important chapters in the entire Resident Evil timeline.

Why Code Veronica matters: Claire, Chris, and Wesker's return

Claire is still searching for Chris after Resident Evil 2. Chris finally collides with Albert Wesker again, and Wesker returns with superhuman abilities. The Ashford family brings an entirely different kind of insanity to the story, and it directly helps build the rivalry that eventually explodes in Resident Evil 5. It is important.

Capcom has officially described Veronica as a reimagining with modernized gameplay, and it has confirmed the game will use a third person perspective similar to the Resident Evil 2 and Resident Evil 4 remakes. That is a win, because it means this was never supposed to be an original game with prettier zombies. Areas can move, encounters can change, characters can receive more development, and entire pieces of the story can be rewritten to fit modern continuity.

Rockfort Island could be rebuilt as one connected survival horror world

Code Veronica gives Capcom a huge amount of material to work with: Rockfort Island, the prison, the military training facility, the Ashford residence, and the entire Antarctic section. The original game was already massive compared to earlier Resident Evil titles, but those environments were separated by loading screens and hardware limitations.

Imagine the island rebuilt as one large interconnected survival horror environment where we can see locations in the distance, unlock paths between them, and slowly understand how the entire island fits together. I do not want an open world Resident Evil game. Nobody needs Claire climbing radio towers and collecting umbrella backpacks.

But a larger connected environment in the style of Raccoon City Police Department would be incredible. Give us enough freedom to explore without turning Resident Evil into another map covered in icons. That is what we want, and that structure could let Capcom combine the best parts of its two most successful modern remakes.

Balancing survival horror with bigger action set pieces

The opening section needs to lean hard into survival horror: limited ammo, dark corridors, unfamiliar enemies, and the feeling that Rockfort Island is actively trying to kill you. Then as Chris enters the story and Wesker becomes more involved, Capcom can gradually increase the scale and action without abandoning that tension.

That balance is super important, because reports surrounding the project have claimed Capcom wants Veronica to move in a much darker, more horror focused direction. At the same time, they have teased larger groups of infected on Rockfort Island, which could force Claire into more aggressive combat encounters. If the developers can combine the tension of Resident Evil 2 with the bigger encounters and smoother combat of Resident Evil 4, this remake could be something special.

Modernizing the Ashford family and Steve Burnside without losing what made them memorable

The story may require even more work than the gameplay. Let us be honest: Code Veronica contains some incredible ideas, but it is also completely unhinged. The Ashford family storyline is soap opera anime villain energy thrown into a blender. Steve Burnside is one of the most divisive characters in the entire franchise, and some fans want him rewritten while others would only be satisfied if Capcom wrote him off the island immediately.

Capcom has to modernize the story without sanding away everything that made it memorable. Alfred Ashford should still feel unstable and theatrical, Alexia should be terrifying, and Steve needs enough rewriting to make players care about him without becoming an entirely different character. Most importantly, Claire cannot feel like she loses her own game the moment Chris arrives.

Then there is Wesker. If Capcom wants one trailer that instantly tells casual fans why Veronica matters, show Chris Redfield and end it with Albert Wesker stepping out of the darkness. That is the money shot. Veronica is the game that reconnects these two characters and starts turning their relationship into the backbone of the franchise, and a remake would give Capcom the chance to strengthen those scenes and create a cleaner path toward Resident Evil 5.

Why the extra development time might be justified, and the Resident Evil 3 lesson

This could also explain why Capcom is reportedly willing to spend more time on the project. If the changes only involved improved textures or lighting, the game would not need several additional months. But if you are expanding environments, rewriting story sections, redesigning boss fights, and expanding character roles, the extra time makes sense.

We have already seen what happens when one of these remakes is treated like a smaller project. Resident Evil 3 looked great and played well, but it cut major locations, shortened the experience, and reduced Nemesis from an unpredictable nightmare into a series of scripted appearances. I would not say it was a disaster, but it permanently became the remake everybody describes by talking about everything that was missing. Code Veronica has already been ignored for years while Resident Evil 2, 3, and 4 received modern remakes. It is getting its turn, and it needs to be really good.

What a fall 2027 shift could mean for release order

If the game is moved into fall of 2027, Capcom has a decision to make. It could accelerate an expansion that is coming and release that first. It could keep Veronica first and push the expansion into late 2027 or even 2028. Or the two projects could contain narrative connections that require them to launch in a specific order. There have already been suggestions that Veronica contains a new story throughline heading toward that expansion, which would make the order far more important than simple marketing.

At the end of the day, this rumor could read in two completely different ways. The bad version is that Veronica is struggling behind the scenes and Capcom needs extra time to repair it. The good version is that Capcom realized how important this remake is, increased its ambition, and refused to rush it out at the beginning of 2027. I am going to stick with the good version. We waited 25 years, so I am okay waiting a little longer.

Which version do you think is really happening here?

Watch the original

@morechaosgaming · YouTube

Adapted with AI from Chaos' video of 25 September 2026 and reviewed by Digital Fox Talent before publication. Editorial standards · Corrections

Resident EvilResident Evil Code VeronicaCapcomDusk Golemgaming newsResident Evil remake

Also on Resident Evil

10 creators, 21 takes →

More from @morechaosgaming

All →
Write for SUBPLOT

Make videos? Your next one could be an article here.

We turn your videos into articles under your name, linked back to the original. You keep 60% of what they earn, non-exclusive, and you can leave whenever you like.

Become a SubPlotter →