Final Fantasy VII Rebirth Ending Was Intentionally Confusing, Story Won’t Betray Fans Of The Original

by Muhammad Ali Bari

The ending to Square Enix’s action role-playing game, Final Fantasy VII Rebirth, was intentionally kept confusing.

During an interview, Final Fantasy VII Rebirth creators Naoki Hamaguchi and Yoshinori Kitase were asked about the sentiment of confusion arising from the game’s ending, how fans should interpret the new developments, what kind of reaction the team is hoping to garner from them, and what message they wanted to convey regarding the possible confusion and dissatisfaction surrounding the new version of events.

Final fantasy vii rebirth ending

Kitase added that the creators were also talking about how the original shows Cloud’s perspective, his feeling of immense loss, of losing someone that he loved, and having this hole in his heart. When considering how to depict this in the Remake series, the development team also thought about not only expressing this loss of someone who means so much to you but also this sense of a person experiencing loss, being unable to force yourself to forget this person and almost like, an inability to accept it, while struggling with the possibility of losing someone.

On the subject of wildest fan theories, Kitase mentioned that he’s head a lot of players’ different conjectures, saying, “Oh, how much will this story change from the original?” According to him, this isn’t how it will be. He mentioned that the development has always kept the original in mind, and he doesn’t believe the Remake trilogy will end up being a storyline that will betray the fans of the original. At the same time, he said that it’s been 27 years since the release of the 1998 game. There are these things that the creators feel they can only do now in the remake project that can bring a new happiness, a new sort of feeling of satisfaction to those playing now, 27 years later. What this will entail exactly is something Kitase hopes players will get to experience soon.

You may also like