Early on in Code Vein 2, you are introduced to Noah, but at the end of his missions, he gets into a fight that you know from the present that he will lose. Lavinia even tells you to leave it and not change the past. However, should you still save Noah in Code Vein 2?

Code Vein 2 Saving Noah

Despite what Lavinia says, you do actually have to save Noah in order to get all of the endings in Code Vein 2. You can wait on this as long as you want, but one of the endings requires you to save all the characters that suffer a fate similar to Noah.

Saving Noah changes the MagMell of the present, and the bridge from the Builder’s Request lasts through history to be available in the present, giving you a path to the present era Sunken City.

The issue here is that saving Noah isn’t exactly possible from when the opportunity unlocks due to your character being absolutely underleveled for the situation. This seems to be some sort of check by the game to subtly tell you to return later.

Frantz Boss Fight

Frantz Boss
Image Source: Bandai Namco Studios via Phrasemaker

Following Noah down into the fight that awaits him shows you a cutscene in which he finds out that Frantz, an old friend, has been transformed into a monster. In the present, you already found out that the two end up seemingly encased in stone.

This is a nearly impossible fight that you are locked into undertaking if you stay in the MagMell past. As you can’t venture out and gain XP or upgrade anything, you are too underprepared for the fight, and your only choice is to leave this area through the Bond back to the present.

I was level 27 when I was able to actually beat Frantz, with a Rank-C Blood Code backing me up and the Deluxe edition sword sitting at 390 damage. I think this is a reasonable point to return, and the story point I came back from was after defeating the Darkborn Leader in Josee’s story.

So, while it is pretty much required to save Noah, it is something you won’t be able to do until a little further down the line.

Subscribe

Notify of

guest


0 Comments


Inline Feedbacks
View all comments