[Locked] #savemccfirst

Ya H5 is out of the question for me. Sad really. Maybe I'll get it used 6 months after launch.

SpiderMan616XD wrote:

Save mcc first dont ignore it and concentrate on halo 5 and the hunt the truth campaign

If I get H5, I'm getting it pre-owned, and not buying any DLC. 343 has seen the last of my money.

Mr Nogatco wrote:

ERUN BANE wrote:

Yes, reroute every employee that is currently working on Halo 5 to ensure that the MCC launch failure doesn't happen again--because why, because you won't buy Halo 5? In that case, you are one selfish little child.

Is this a serious comment? People are selfish for wanting the same developer of Halo 5 to deliver on promises that they made for their last title? So, because these people won't purchase a new product from "Company X", due to "Company X's" last title being riddled with bugs and issues (making the game non-playable for many), it's the consumer who is to blame and not the company? Are you smoking crack?

You clearly don't know how this MCC dev business works, do you?

There's a team in 343i working on Halo 5, presumably being most of their workforce, and another small team working on the MCC, the UI and networking to be exact. Other studios, such as Certain Affinity are working on other parts of the MCC, since 343 doesn't have enough of a qualified workforce--they aren't a Nike plant in Africa--remaining to work on the MCC. So, let's say the H5 team, which we'll call "Workforce A", are all rerouted to MCC, "Workforce B". In that case, the MCC would be fixed a lot faster (not that fast, considering there are quite a few pre-release roles in a dev team, but Halo 5 would be more broken due to less time programming and testing, which combined with the MCC's launch would probably be the downfall of Halo. If Workforce A continues to work on H5, however, then the MCC would be fixed more gradually while H5 would be released less broken.

Of course, quite a few people are screaming "yoink H5!", so I have no idea why you would be refuting the "selfish" thing. (Unless you understood my point wrong.)

CHRISPOCALYP5E wrote:

I'm buying Halo 5 for the campaign.

Multiplayer is a COD-Titanfall hybrid and I hate those games with a passion.

That is why I play Halo and now it has turned into a COD-Titanfall hybrid.

So do please, SAVE MCC FIRST!!!

Idk. I play cod and Titanfall. But halo 5 felt like halo to me. No load outs. Balanced gameplay. A weapon for every job. Fights for power weaponS. Map Control. Felt a lot like halo.

h1nt0n wrote:

AstroCyborg wrote:

mcc is fixed bdobbins fanboy

Aside from ranks, matchmaking, playlists, host issues, CE aiming and magnetism issues, and game chat its kinda fixed.

That and proximity voice and JIP for customs etc

GeT ThAt T4nG wrote:

I'm not going to tell anyone to do anything.

Ill get Halo 5.... A few days after it comes out, used.
I won't buy any DLC, 343 will not see another penny from me.

taking 4 months to make it to where I can play matchmaking with friends, still not have a working skill biased matchmaking system in place, coop campaign still doesn't work, you can't join custom games in progress, yeahhh all these problems pretty much sealed the deal for me.

But if people want to mindlessly pre order a game from a company that had one failed halo and one glitched to hell halo, then be my guest.

Yeah... I really don't see how people can think differently from this.
Oh well.

#thisthreadispointless There is no saving the population of MCC no matter what they do now. They sure as hell won't be delaying H5 either. There is no point advocating it, they are not going to do as the makers of Battlefield did. The Halo 5 ball is rolling and there is no stopping it. Not that there truly is a reason to anyways. MCC was meant to be there for the people who did not want to move on, and people who love Halo and wanted all the old games on the new console. Blunt truth. MCC is a stand in for the time between games. Even if it was just H2A that they released the results would have been the same population wise, there is an apathy in gamers nowadays, there is no sticking to one or two games, people move on to the next best thing. Because there are too many next best things in the gaming market as compared to back in the original trilogy days. Yes this even means at the expense of quality sometimes. But from what I am seeing of H5; 343i knows that if they fail that then there may be no saving their passion anyways.

PlusLizard5795 wrote:

ERUN BANE wrote:

Mr Nogatco wrote:

ERUN BANE wrote:

Yes, reroute every employee that is currently working on Halo 5 to ensure that the MCC launch failure doesn't happen again--because why, because you won't buy Halo 5? In that case, you are one selfish little child.

Is this a serious comment? People are selfish for wanting the same developer of Halo 5 to deliver on promises that they made for their last title? So, because these people won't purchase a new product from "Company X", due to "Company X's" last title being riddled with bugs and issues (making the game non-playable for many), it's the consumer who is to blame and not the company? Are you smoking crack?

You clearly don't know how this MCC dev business works, do you?

There's a team in 343i working on Halo 5, presumably being most of their workforce, and another small team working on the MCC, the UI and networking to be exact. Other studios, such as Certain Affinity are working on other parts of the MCC, since 343 doesn't have enough of a qualified workforce--they aren't a Nike plant in Africa--remaining to work on the MCC. So, let's say the H5 team, which we'll call "Workforce A", are all rerouted to MCC, "Workforce B". In that case, the MCC would be fixed a lot faster (not that fast, considering there are quite a few pre-release roles in a dev team, but Halo 5 would be more broken due to less time programming and testing, which combined with the MCC's launch would probably be the downfall of Halo. If Workforce A continues to work on H5, however, then the MCC would be fixed more gradually while H5 would be released less broken.

Of course, quite a few people are screaming "yoink H5!", so I have no idea why you would be refuting the "selfish" thing. (Unless you understood my point wrong.)

Hey uhh, just wondering where anyone in this entire thread said that all the people working on halo 5 should be re-reouted to fix mcc? (Nobody said that) But I agree they shouldn't take the workers away from halo 5, or at least not all of them. But still, they could definitely hire some more people for at least a little while until the game is fixed.

"savemccfirst"

They want 343 to fix MCC before making H5, implying that they want, literally, to stop H5's development and fix MCC first.

Yeah, I think I've said enough.

ERUN BANE wrote:

PlusLizard5795 wrote:

ERUN BANE wrote:

Mr Nogatco wrote:

ERUN BANE wrote:

Yes, reroute every employee that is currently working on Halo 5 to ensure that the MCC launch failure doesn't happen again--because why, because you won't buy Halo 5? In that case, you are one selfish little child.

Is this a serious comment? People are selfish for wanting the same developer of Halo 5 to deliver on promises that they made for their last title? So, because these people won't purchase a new product from "Company X", due to "Company X's" last title being riddled with bugs and issues (making the game non-playable for many), it's the consumer who is to blame and not the company? Are you smoking crack?

You clearly don't know how this MCC dev business works, do you?

There's a team in 343i working on Halo 5, presumably being most of their workforce, and another small team working on the MCC, the UI and networking to be exact. Other studios, such as Certain Affinity are working on other parts of the MCC, since 343 doesn't have enough of a qualified workforce--they aren't a Nike plant in Africa--remaining to work on the MCC. So, let's say the H5 team, which we'll call "Workforce A", are all rerouted to MCC, "Workforce B". In that case, the MCC would be fixed a lot faster (not that fast, considering there are quite a few pre-release roles in a dev team, but Halo 5 would be more broken due to less time programming and testing, which combined with the MCC's launch would probably be the downfall of Halo. If Workforce A continues to work on H5, however, then the MCC would be fixed more gradually while H5 would be released less broken.

Of course, quite a few people are screaming "yoink H5!", so I have no idea why you would be refuting the "selfish" thing. (Unless you understood my point wrong.)

Hey uhh, just wondering where anyone in this entire thread said that all the people working on halo 5 should be re-reouted to fix mcc? (Nobody said that) But I agree they shouldn't take the workers away from halo 5, or at least not all of them. But still, they could definitely hire some more people for at least a little while until the game is fixed.

"savemccfirst"

They want 343 to fix MCC before making H5, implying that they want, literally, to stop H5's development and fix MCC first.

Yeah, I think I've said enough.

Even if someone actually said that it'd be a pretty reasonable request for someone who owns a broken 5 month old game that's going to be kicked to the curb by the dev when the next one comes out