Quote from: Sprungli on August 02, 2015, 04:15:43 PM

Quote from: Jono on August 02, 2015, 04:30:27 AM

Quote from: BaconShelf on August 02, 2015, 04:23:55 AM

I love seeing all the competitive types who try and make up excuses for why Halo 4 is the most popular game specific playlist in MCC, why it has more backwards compatibility votes than any other and why H4 comes up a lot more in multi game playlists than 2 or 3. Just admit that the damn thing is more popular by the majority of the playerbase.

That's because the Halo player base left on the MCC is nothing but Reachtards and anyone who joined Halo after.

Halo veterans that have been there since CE weren't gonna wait 6 months for them to fix the MCC.

That makes sense, people that have played Halo for 14 years and stuck with the franchise through the totally problem-free Halo 2 are unwilling to wait six (which is overly dramatic) months. Not as if there are people that actually like Halo 4; it's also strange to assume that those that liked Reach automatically like 4, you've got living proof against that right here.

At least Halo 2 worked day one unlike the MCC which like you said took 6, supposedly, dramatic months to fix. Fuck me for expecting a game that I paid $60 for to work day one right? Yep, totally couldn't work around what Halo 2 had vs what MCC had. It's only 6 months, I should get over myself, because fuck the satisfaction of wanting my games to work and function properly. MCC was a disaster for 6 months, unplayable, literally unplayable. I think you can look past Halo 2's problems vs what MCC had. 6 months is a long time, it makes sense as to why people are so turned off to it now. At least I was able to play Halo 2 whereas the MCC I had to wait 6 months for them to fix, and even now it's still not perfect.

Nobody has said any other Halo was more dysfunctional. Saying Halo 2 wasn't and isn't broken is a flat out lie.

Halo 2 was undeniably the most bug-ridden of them all. Super Bouncing, Button Combos, and Sword cancelling, were all ways to gain an advantage over unsuspecting opponents. The Vista version was even worse, the net coding was so bad, there was lead in LAN games. That Ghost of lockout video also shows how the Host is sometimes unable to see any animation on some bipeds online, and that hit detection can be seriously bad, on top of the death announcements will just sometimes take a holiday.

Quote from: Zonda on August 04, 2015, 01:29:30 AM

Reach had that glitch where sometimes vehicles would inexplicably launch themselves at extraordinary speeds, killing all occupants, due to a similar issue to the Super Bounce glitch.

Holy shit I forgot about that glitch. I never ran into it myself, but just about every Fails of the Weak had some poor sap suddenly end up flying to his doom at Mach 12 in a wraith.

Quote from: Majestic Star Dragon on August 04, 2015, 01:50:42 AM

Quote from: Zonda on August 04, 2015, 01:29:30 AM

Reach had that glitch where sometimes vehicles would inexplicably launch themselves at extraordinary speeds, killing all occupants, due to a similar issue to the Super Bounce glitch.

Holy shit I forgot about that glitch. I never ran into it myself, but just about every Fails of the Weak had some poor sap suddenly end up flying to his doom at Mach 12 in a wraith.

If you played Big Team Battle in Reach and had a match on that shitty Forge map called Asphalt, the Wraith would do that every game.

Quote from: Majestic Star Dragon on August 04, 2015, 01:50:42 AM

Quote from: Zonda on August 04, 2015, 01:29:30 AM

Reach had that glitch where sometimes vehicles would inexplicably launch themselves at extraordinary speeds, killing all occupants, due to a similar issue to the Super Bounce glitch.

Holy shit I forgot about that glitch. I never ran into it myself, but just about every Fails of the Weak had some poor sap suddenly end up flying to his doom at Mach 12 in a wraith.

If you played Big Team Battle in Reach and had a match on that shitty Forge map called Asphalt, the Wraith would do that every game.

Quote from: Corrupt Setter on August 03, 2015, 08:38:26 PM

Quote from: Sprungli on August 02, 2015, 04:15:43 PM

Quote from: Jono on August 02, 2015, 04:30:27 AM

Quote from: BaconShelf on August 02, 2015, 04:23:55 AM

I love seeing all the competitive types who try and make up excuses for why Halo 4 is the most popular game specific playlist in MCC, why it has more backwards compatibility votes than any other and why H4 comes up a lot more in multi game playlists than 2 or 3. Just admit that the damn thing is more popular by the majority of the playerbase.

That's because the Halo player base left on the MCC is nothing but Reachtards and anyone who joined Halo after.

Halo veterans that have been there since CE weren't gonna wait 6 months for them to fix the MCC.

That makes sense, people that have played Halo for 14 years and stuck with the franchise through the totally problem-free Halo 2 are unwilling to wait six (which is overly dramatic) months. Not as if there are people that actually like Halo 4; it's also strange to assume that those that liked Reach automatically like 4, you've got living proof against that right here.

At least Halo 2 worked day one unlike the MCC which like you said took 6, supposedly, dramatic months to fix. Fuck me for expecting a game that I paid $60 for to work day one right? Yep, totally couldn't work around what Halo 2 had vs what MCC had. It's only 6 months, I should get over myself, because fuck the satisfaction of wanting my games to work and function properly. MCC was a disaster for 6 months, unplayable, literally unplayable. I think you can look past Halo 2's problems vs what MCC had. 6 months is a long time, it makes sense as to why people are so turned off to it now. At least I was able to play Halo 2 whereas the MCC I had to wait 6 months for them to fix, and even now it's still not perfect.

It really wasn't six months though (like I said before you jumped to your preferred interpretation, six is dramatic, 3 is closer to the truth), and the MCC was perfectly playable-lets be specific here in that it was only the online multiplayer that was broke, campaign, playlists and customs were all fine (bar split-screen H2A customs, that still performs poorly).

Quote from: Sprungli on August 04, 2015, 03:25:25 AM

Quote from: Corrupt Setter on August 03, 2015, 08:38:26 PM

Quote from: Sprungli on August 02, 2015, 04:15:43 PM

Quote from: Jono on August 02, 2015, 04:30:27 AM

Quote from: BaconShelf on August 02, 2015, 04:23:55 AM

I love seeing all the competitive types who try and make up excuses for why Halo 4 is the most popular game specific playlist in MCC, why it has more backwards compatibility votes than any other and why H4 comes up a lot more in multi game playlists than 2 or 3. Just admit that the damn thing is more popular by the majority of the playerbase.

That's because the Halo player base left on the MCC is nothing but Reachtards and anyone who joined Halo after.

Halo veterans that have been there since CE weren't gonna wait 6 months for them to fix the MCC.

That makes sense, people that have played Halo for 14 years and stuck with the franchise through the totally problem-free Halo 2 are unwilling to wait six (which is overly dramatic) months. Not as if there are people that actually like Halo 4; it's also strange to assume that those that liked Reach automatically like 4, you've got living proof against that right here.

At least Halo 2 worked day one unlike the MCC which like you said took 6, supposedly, dramatic months to fix. Fuck me for expecting a game that I paid $60 for to work day one right? Yep, totally couldn't work around what Halo 2 had vs what MCC had. It's only 6 months, I should get over myself, because fuck the satisfaction of wanting my games to work and function properly. MCC was a disaster for 6 months, unplayable, literally unplayable. I think you can look past Halo 2's problems vs what MCC had. 6 months is a long time, it makes sense as to why people are so turned off to it now. At least I was able to play Halo 2 whereas the MCC I had to wait 6 months for them to fix, and even now it's still not perfect.

It really wasn't six months though (like I said before you jumped to your preferred interpretation, six is dramatic, 3 is closer to the truth), and the MCC was perfectly playable-lets be specific here in that it was only the online multiplayer that was broke, campaign, playlists and customs were all fine (bar split-screen H2A customs, that still performs poorly).

I'm pretty sure the campaigns didn't work at launch either.

Quote from: McLemon on August 03, 2015, 10:59:20 PM

Nobody has said any other Halo was more dysfunctional. Saying Halo 2 wasn't and isn't broken is a flat out lie.

I'd rather deal with button combos and be actually able to play a fucking game than have to waste hours trying to connect to friends, stay together long enough to find a lobby, and then hope the game doesn't crash or the host leaves.

Quote from: BaconShelf on August 04, 2015, 06:37:42 AM

Quote from: Sprungli on August 04, 2015, 03:25:25 AM

Quote from: Corrupt Setter on August 03, 2015, 08:38:26 PM

Quote from: Sprungli on August 02, 2015, 04:15:43 PM

Quote from: Jono on August 02, 2015, 04:30:27 AM

Quote from: BaconShelf on August 02, 2015, 04:23:55 AM

I love seeing all the competitive types who try and make up excuses for why Halo 4 is the most popular game specific playlist in MCC, why it has more backwards compatibility votes than any other and why H4 comes up a lot more in multi game playlists than 2 or 3. Just admit that the damn thing is more popular by the majority of the playerbase.

That's because the Halo player base left on the MCC is nothing but Reachtards and anyone who joined Halo after.

Halo veterans that have been there since CE weren't gonna wait 6 months for them to fix the MCC.

That makes sense, people that have played Halo for 14 years and stuck with the franchise through the totally problem-free Halo 2 are unwilling to wait six (which is overly dramatic) months. Not as if there are people that actually like Halo 4; it's also strange to assume that those that liked Reach automatically like 4, you've got living proof against that right here.

At least Halo 2 worked day one unlike the MCC which like you said took 6, supposedly, dramatic months to fix. Fuck me for expecting a game that I paid $60 for to work day one right? Yep, totally couldn't work around what Halo 2 had vs what MCC had. It's only 6 months, I should get over myself, because fuck the satisfaction of wanting my games to work and function properly. MCC was a disaster for 6 months, unplayable, literally unplayable. I think you can look past Halo 2's problems vs what MCC had. 6 months is a long time, it makes sense as to why people are so turned off to it now. At least I was able to play Halo 2 whereas the MCC I had to wait 6 months for them to fix, and even now it's still not perfect.

It really wasn't six months though (like I said before you jumped to your preferred interpretation, six is dramatic, 3 is closer to the truth), and the MCC was perfectly playable-lets be specific here in that it was only the online multiplayer that was broke, campaign, playlists and customs were all fine (bar split-screen H2A customs, that still performs poorly).

I'm pretty sure the campaigns didn't work at launch either.

there was a few bugs like data erasing IIRC, but it was uncommon.
They've been playable since launch though

Quote from: Sprungli on August 04, 2015, 03:25:25 AM

Quote from: Corrupt Setter on August 03, 2015, 08:38:26 PM

Quote from: Sprungli on August 02, 2015, 04:15:43 PM

Quote from: Jono on August 02, 2015, 04:30:27 AM

Quote from: BaconShelf on August 02, 2015, 04:23:55 AM

I love seeing all the competitive types who try and make up excuses for why Halo 4 is the most popular game specific playlist in MCC, why it has more backwards compatibility votes than any other and why H4 comes up a lot more in multi game playlists than 2 or 3. Just admit that the damn thing is more popular by the majority of the playerbase.

That's because the Halo player base left on the MCC is nothing but Reachtards and anyone who joined Halo after.

Halo veterans that have been there since CE weren't gonna wait 6 months for them to fix the MCC.

That makes sense, people that have played Halo for 14 years and stuck with the franchise through the totally problem-free Halo 2 are unwilling to wait six (which is overly dramatic) months. Not as if there are people that actually like Halo 4; it's also strange to assume that those that liked Reach automatically like 4, you've got living proof against that right here.

At least Halo 2 worked day one unlike the MCC which like you said took 6, supposedly, dramatic months to fix. Fuck me for expecting a game that I paid $60 for to work day one right? Yep, totally couldn't work around what Halo 2 had vs what MCC had. It's only 6 months, I should get over myself, because fuck the satisfaction of wanting my games to work and function properly. MCC was a disaster for 6 months, unplayable, literally unplayable. I think you can look past Halo 2's problems vs what MCC had. 6 months is a long time, it makes sense as to why people are so turned off to it now. At least I was able to play Halo 2 whereas the MCC I had to wait 6 months for them to fix, and even now it's still not perfect.

It really wasn't six months though (like I said before you jumped to your preferred interpretation, six is dramatic, 3 is closer to the truth), and the MCC was perfectly playable-lets be specific here in that it was only the online multiplayer that was broke, campaign, playlists and customs were all fine (bar split-screen H2A customs, that still performs poorly).

I'm pretty sure the campaigns didn't work at launch either.

Quote from: PSU on August 04, 2015, 10:50:37 AM

This thread is a fuckin embarrassment.

You guys seem like butthurt little kids who have been spawnkilled one too many times.

>PSU