After FF7 Remake Part 3: Square Enix Strike Team’s Next Move

With Final Fantasy 7 Remake Part 3 moving through development, Square Enix’s “strike team” is already talking about what comes next. The director hinted the group could either build a completely new IP or spin up something new within the Final Fantasy series. That’s a big fork in the road, and it speaks to how confident the studio is in the production pipeline refined across Remake and Rebirth. Whether they carry forward the hybrid combat DNA or pivot to a different flavor, the key takeaway is this crew wants to stay together and apply its hard‑won tools and workflows to a fresh challenge.

Reading between the lines, two paths form. A new IP lets the team define tone, world rules, and mechanics without legacy constraints—high risk, high reward. A new Final Fantasy entry or subseries offers a strong brand and clearer expectations, but it must justify coexistence with mainline titles. Either way, the Remake team’s strengths—tight character action layered with ATB strategy, cinematic set‑pieces, and dense side content—are likely to inform the next design. Expect pre‑production to incubate prototypes while Part 3 locks down content and QA gates.

Tech and platforms matter. The team has deep Unreal expertise, so continuing on Unreal Engine 5 would speed iteration with Nanite and Lumen, while keeping cross‑platform options open. Square Enix’s recent messaging favors broader launches beyond a single console, so PS5 and PC are a given, with Xbox potential depending on deals and scheduling. On the systems side, anticipate learnings from Rebirth: more readable skill trees, smarter companion AI, and traversal that balances open‑zone freedom with authored pacing so story beats land without bloating runtime.

How to tell which way they’re leaning? Watch hiring. Listings for worldbuilding from zero, IP incubation, or narrative bible creation scream new IP. Roles referencing established FF lore pipelines, job specs for crystal mythology touchpoints, or franchise‑specific tools hint at a new FF branch. Trademarks, composer partnerships, and combat designer briefs are also telling—if they call out stance systems, party synergies, or aerial juggling, you can infer a more action‑forward loop versus a tactical slant.

Conclusion

Temper expectations on timing: meaningful reveals likely land after Part 3 ships and the team exhales from post‑launch support. The good news is that, whichever path they pick, the strike team has a clear identity and a mature toolchain. If you’re tracking signals, follow job boards, engine notes in dev diaries, and platform language in investor calls. New IP would showcase range; a fresh Final Fantasy would channel that craft into familiar mythology. Either outcome is promising if the focus stays on sharp combat readability, strong narrative arcs, and smooth performance from day one.