>See you in the sequel
Love this genre of failed sequel hints
>>748280696>343 didn't get to rape 2 and 3 silver linings and all that
I wonder if 343 remade 2, they'd misunderstand the playable Arbiter segments and remove them or drastically alter them.
>>748280909The only thing they changed was insanely low hanging fruit or anything they perceived as a technical limitation so i doubt it.They'd definitely mutilate random level design but i don't think it'd be related to the pushback to playing as Arbiter; especially as that would imply they remember ancient Halo discourse.
>>748280981I dunno. "I vaguely remember people didn't like the Arbiter, let's fix that" would be typical 343 thinking.In 1, there's not really much you can remove without breaking the entire game. Like several levels are repeated but backwards, so they obviously could never be removed.
>>748280792And then they gave it to Activision.It's like saying,>Alright, you didn't like the diarrhea we tried to serve you>but how about this nice hot bowl of sour milk and pickles vomitJust let it die already
>>748280771Why was he replaced
>didn't we just remake halo 5 or 6 years ago??>that's long enough, remake it again!bravo
>>748281162Cannot be any worse than leaving the IP with 343 for another 15 years.
>>748281162I don't care about the new shit just don't rape the old shit
>>748281174He wanted as much pay as RDJ and threw a hissy fitThey just tossed him away
>>748281162who else are they going give it to?everything else under ms was so hilariously mismanaged for the past 10 years they either gutted the studios or closed them.
>>748281162It doesn't matter. You could give Halo to anyone and it would still fail.They story ended with 3. There's no point to Halos, Forerunners, the Flood, and so forth other than to retread the same plotline that ended with 3.
>>748281342If Halo was unironically so reliant on its forerunner reveal and nothing else to function as a franchise it'd look insanely different; it was obviously fucking possible to do that.You are getting too caught up on 343 shitting on your plate. Obviously the collapsing empire would splinter, and you can get this; just introduce new threats. The idea of an ancient enemy to the ancient humans would entirely work under different pretenses(namely ones that aren't five layers deep retcons).
>>748281162343 and its so called devs should have been shitcanned 12 years ago after the whole mcc scam debacle, phil the fag should have made a public apology too for not shitcanning them sooner
>>748281174hard to work with...
>>748281162I trust Activision more than another Halo Studios outsource job or Id, because Acti still makes games LIKE Halo without the arena shooter elements, to the point that Halo tried to be like what CoD provides repeatedly. It's probably not going to have any spirit or be anything world turning whatsoever, but some serious carnage would have to occur for things to go horribly wrong. Worst I expect is shit like awful story, but that's just par for the course now. And Id is not only already gutted and too small to handle full projects right now, they'd go extra retarded too. Unsurprisingly studios that worked with Halo in the past are also cooperative with Activision's CoD development processes; if anything, this is partially a reunion tour, almost inevitable even.If turns out shit yet again, it's no skin off my bones, just more entertainment trainwrecks to observe as Microsoft yet again flounders about uncertain as to why no one can make this shit anymore.Christ, give Treyarch some legs and breathing room, let them get some air in their lungs after the 1-2 rape punch of Black Ops 7 having to be made right after 6, and you'd have the recipe for at least an AMUSING Halo on our hands. That's more than I can say after what we've been through since 2012.
>>748281745after halo 5 they kinda weremicrosoft shifted heavy on contractor policies with 18 month rotations, you had some mainstays and management as well as some fans getting hired in the background but a majority of 343 was largely expunged of standard employees because the big wigs wanted to avoid having to pay health insurance and liabilities for consistent rosters after all these years. by the time you hit halo infinite, the rotations were so fucky that it resulted in brain drains every year and a half, and virtually no one knowing how to use the blam-turned-slipstream engine anymore, which is why the live service element completely fucking stalled in on itself like an unfixable car breaks failure. one can even argue this was happening sooner; the contractor policy started in 2014, right around the same time the master chief collection was caught between, what, six fucking outsourced studios while 343 was "hard at work" on 5?by the time they rebranded as halo studios, it still was a problem of a few mainstays now surrounded by virtually nothing but new faces, and it wasn't even enough of a dev team to actually make campaign evolved even; it's why that project largely outsourced for almost everything until the emergency fuckery in the last six months where they had to rush to finalize what other people put together because the main outsource things got fired too. staffs credited but not proper studios. and now even the mainstays are gone in the mass layoffs, leaving a skeleton management crew to "support" whoever is actually developing shit now.people cried for 343/halo studios to die, but the reality is it was dead since 2016-2017. they outlived their usefulness a decade ago and just pretended it still mattered by using a couple names or trying to bring folks back every once in a while. this is why infinite was a hodgepodge mess, joe straten came in to find they had a far cry clone with zero direction. death criers already won, they just didn't know it.
>>748282790why do these companies keep outsourcing everything instead of just hiring smaller dedicated teams? Surely in the long run it's cheaper to shill out for benefits to keep talented guys making games rather then dumping practically billions of dollars into games that take half a decade or more, thousands of absolutely incompetent people, and then the finished products shit the bed. ESG money can't be THAT good, can it? Pretty much all these companies have sacrificed any reputation they had on the altar of DEI and Blackrock cuck bucks.
>>748280696No you won't
>Halo on the CoD engine>which is a modified version of the Quake enginePeople were saying Halo should've used idTech after they acquired id they just never specified which version
>>748281162>how about this nice hot bowl of sour milk and pickles vomitI thought Hershey chocolate was popular.
>>748283302halo has it own engine that they threw away to use ue5 lol
>>748283458A lot of developers trashed their in-house engines in favor of Unity/UE to make the on-boarding process easier for their outsourced developers.Kingdom Hearts was another big one.
>>748281034They would split it into two games, half Chief missions, half Arbiter missions (selling both full price ofc).
>>748283458>halo has it own engine that they threw away to use ue5 lolnot quite. campaign evolved was basically halo's blam engine, reach iteration, with a UE5 scripting and graphics layer on top. so it was functionally a remake coded on reach logic from 2010, hence why the AI was so fucky. they kept their engine, but good luck to whatever's happening from here on.
>>748282416>I trust Activision more than another Halo StudiosHow? Why? When was the last good cowadoody?
>>748283908Same story with Oblivion Remastarded. Just layers of shit no one understands on top of AI genned textures. That's why the characters don't grimace when they get hit. It's like asking Indians to build the Pyramids and instead of an engineering marvel you get a giant conical pile of garbage and they say it looks better.
>>748280696He sure wasn't addressing the Halo Studios employees, lmao.
