an asynchronus solo/co-op release is a mistake

Games Halo Infinite
1

This massively shortchanges co-op focused players. I myself am a solo player for a first playthrough, so I’m not affected, but you are basically alienating a large portion of halo fans with this move, the same way solo players were alienated with halo 5’s co-op focused campaign.

I understand that 343 is probably out of options here, with microsoft fixated on a holiday release window and not having enough time before release to both polish the game properly and thoroughly as well as finish work on co-op without heavy crunching, but it really shows a lack of correct priorities at both 343 and microsoft, as well as the negative impact remote work has on game development.

I’m sure Infinite will still do alright, but it’s a bit more uncertain now if the game will be a runaway success. Up until now I thought this game was going to knock it out of the park in terms of sales, popularity, and both mainstream and old-school appeal.

2

Your thread title is an odd choice. I came here expecting to defend asynchronous PvE netcode (the superior model), but you are referring to the delayed campaign co-op experience.

3

> 2717573882290912;2:
> Your thread title is an odd choice. I came here expecting to defend asynchronous PvE netcode (the superior model), but you are referring to the delayed campaign co-op experience.

By asynchronous I just mean not being released at the same time, but I understand what you mean, since the new asynchronous netcode is in mcc right? Sorry for the confusion.

4

It is unfortunate what they’re locked into doing, especially since I was planning on doing my first play through with a friend. Although saying this will hurt the game dramatically is most likely not true. Most of Infinite’s player base will be new players coming to try the F2P multiplayer.