surf dtoid with 
Rising (10+)
People you follow
Hamza, Halo CEA is only going to have 6 remakes...
@Dirasyaj X
Halo CEA has no armor abilities in it. The maps are for Reach, however, with the release of the title update, it will have settings identical to CE. The TU will be playable at Halofest during PAX Prime.
@Dirasyaj X
Halo CEA has no armor abilities in it. The maps are for Reach, however, with the release of the title update, it will have settings identical to CE. The TU will be playable at Halofest during PAX Prime.
Hamza made me log in to say that he's a fucking crazy person. Damnation was good, Hang 'Em High was the best.
as much as i LOVE halo 1, the ported halo reach mutliplayer im not a big fan of. if they are makign a big deal of keeping the halo 1 combat the same with just better graphics. then why not the same for the mutliplayer? im still getting this game. halo 1 was the first game that got me into fsps, the last fps was doom 1. ill get it just for the online coop so i can play online with my cousin like the good old days, :)
Damnation is a beautiful map. I'm so glad it's been remade. It's not the forerunner structure type I would have hoped for. But the Coviness of it doesn't look bad.
@Luna46
Frank O'conner of 343 (formally a Bungie Vet) said that classic Halo multiplayer was an original goal.
The problem was the engine. See for the single player they are running the classic Halo code with new graphics. So it literally plays the same exact way the old Halo did. Mainly because it IS the same old Halo. Only prettier. That's how they made you able to toggle the graphics update on or off at the touch of a button during gameplay.
The multiplayer code wasn't so simple. Halo's multiplayer was made in roughly 3 weeks. IT wasn't a huge deal for Halo until Halo 2 came out. As a result, the code for MP is far less suited to multiplayer and they couldn't get it to work with Xbox Live. Hence the Reach engine multiplayer.
TL;DR: Halo 1's code was just too archaic for it to ever work with Xbox Live on a 16 player scale. So the had to cut it in favor of Reach engine.
A fair trade in my opinion.
Frank O'conner of 343 (formally a Bungie Vet) said that classic Halo multiplayer was an original goal.
The problem was the engine. See for the single player they are running the classic Halo code with new graphics. So it literally plays the same exact way the old Halo did. Mainly because it IS the same old Halo. Only prettier. That's how they made you able to toggle the graphics update on or off at the touch of a button during gameplay.
The multiplayer code wasn't so simple. Halo's multiplayer was made in roughly 3 weeks. IT wasn't a huge deal for Halo until Halo 2 came out. As a result, the code for MP is far less suited to multiplayer and they couldn't get it to work with Xbox Live. Hence the Reach engine multiplayer.
TL;DR: Halo 1's code was just too archaic for it to ever work with Xbox Live on a 16 player scale. So the had to cut it in favor of Reach engine.
A fair trade in my opinion.
@Luna46
They couldn't do the Halo CE Multiplayer because there wasn't Live back then. They've said that it was the one thing that they thought the longest about, but came to the conclusion that it wouldn't be the same due to lag and other issues caused by internet connections. It's the same reason that Bloom is currently awful over Live, but during a LAN it works the way it was intended.
However, with the upcoming TU, 343 is looking to bring back was the "Classic" settings were in the past Halo games and offer them in their own separate playlist, along with the current Reach settings. The TU details will be revealed at Halofest during PAX Prime, where it will be playable.
They couldn't do the Halo CE Multiplayer because there wasn't Live back then. They've said that it was the one thing that they thought the longest about, but came to the conclusion that it wouldn't be the same due to lag and other issues caused by internet connections. It's the same reason that Bloom is currently awful over Live, but during a LAN it works the way it was intended.
However, with the upcoming TU, 343 is looking to bring back was the "Classic" settings were in the past Halo games and offer them in their own separate playlist, along with the current Reach settings. The TU details will be revealed at Halofest during PAX Prime, where it will be playable.
Damnation had too much grenade spam in my experience. Darn pubs -.- I'm biased towards Rat Race - as simple as it was - though, due to many 1v1-3v3's, friendly and competitive.
@Lycan XIII
Hahaha! I saw you posted right after I did and laughed. I had a feeling you'd post that I had just beaten you.
Sorry, brah!
Hahaha! I saw you posted right after I did and laughed. I had a feeling you'd post that I had just beaten you.
Sorry, brah!
I feel like the header alone would have sufficed as an article... you know... 'nuff said and all that
Derelict. Mostly because one of my friends would say "Derelict my balls" everytime it was chosen.
Sigh. Simpler times.
Sigh. Simpler times.
@Katherine and Lycan
That's the worst reason I've ever heard for anything in my life. They couldn't write new code that would make the multiplayer play like the original? And not all the maps are being redone? It sounds to me like they're just taking the easy route.
@SuperMonk4Ever
Agreed, plus Boarding Action.
That's the worst reason I've ever heard for anything in my life. They couldn't write new code that would make the multiplayer play like the original? And not all the maps are being redone? It sounds to me like they're just taking the easy route.
@SuperMonk4Ever
Agreed, plus Boarding Action.
@cockaroach
I imagine you wouldn't have gone for the sword as you couldn't wield it until Halo 2.
Also, Hang 'em High was always the standard.
I imagine you wouldn't have gone for the sword as you couldn't wield it until Halo 2.
Also, Hang 'em High was always the standard.
WTF They left the Multiplayer the same as Reach? Fuck Reach died in the ass cause it was terrible, now they take an original great game and wreck it....
Damn, people still think that it was a whole separate multiplayer? The first thing they announced was that it was a map pack for Reach...
@strangerdanger
If it's the worst reason ever, I'd like to see you take a ten year old code, that, like Katherine said, was created in the last weeks before shipping, and update it to work with today's internet connections. Make it play EXACTLY the same. No Host advantages or anything else. It has to play exactly like LAN play. I'd also like to see you create all of the Halo CE maps in less than a year while working an an entirely new game at the same time.
And once again, I'll say, that the reason for the Reach TU is so that it plays as close to "Classic" Halo as they can make it, so that people that like to bitch about change will shut up.
@strangerdanger
If it's the worst reason ever, I'd like to see you take a ten year old code, that, like Katherine said, was created in the last weeks before shipping, and update it to work with today's internet connections. Make it play EXACTLY the same. No Host advantages or anything else. It has to play exactly like LAN play. I'd also like to see you create all of the Halo CE maps in less than a year while working an an entirely new game at the same time.
And once again, I'll say, that the reason for the Reach TU is so that it plays as close to "Classic" Halo as they can make it, so that people that like to bitch about change will shut up.
I really wish they'd consider making a PC port. The Halo 1 community is still going strong on the PC and a remastered Halo 1 isn't exactly a system seller, so I think it doesn't really NEED to stay exclusive.
we always played sidewinder and hang 'em high at my house. from the looks of the comments those are big time favorites.
I don't get the hate for Reach's multiplayer. I mean, I never got to play online, but it's still fun to play with friends. Meh.
@Katherine Leigh McHugh
That's a bullshit excuse, and I'll tell you why.
A game with LAN multiplayer, from a network engineering perspective, is the same as a game with Internet multiplayer. The only difference is having code that compensates for latency with things like prediction, interpolation, extrapolation and dead reckoning. This is why you were able to play Halo CE on Xbox through GameSpy Tunnel and Xbox Connect, but with terrible, terrible lag.
You mention: "See for the single player they are running the classic Halo code with new graphics. So it literally plays the same exact way the old Halo did. Mainly because it IS the same old Halo." That's true... except you fail to mention they ADDED NETCODE for ONLINE CO-OP with latency compensation. The amount of work it would take to move that same code over to versus would at worst be less than the three weeks they spent building the original LAN multiplayer.
This was a business decision, pure and simple. They didn't want to create a schism in the Halo multiplayer community and compete with themselves, while Halo Reach is still played by a lot of people.
That's a bullshit excuse, and I'll tell you why.
A game with LAN multiplayer, from a network engineering perspective, is the same as a game with Internet multiplayer. The only difference is having code that compensates for latency with things like prediction, interpolation, extrapolation and dead reckoning. This is why you were able to play Halo CE on Xbox through GameSpy Tunnel and Xbox Connect, but with terrible, terrible lag.
You mention: "See for the single player they are running the classic Halo code with new graphics. So it literally plays the same exact way the old Halo did. Mainly because it IS the same old Halo." That's true... except you fail to mention they ADDED NETCODE for ONLINE CO-OP with latency compensation. The amount of work it would take to move that same code over to versus would at worst be less than the three weeks they spent building the original LAN multiplayer.
This was a business decision, pure and simple. They didn't want to create a schism in the Halo multiplayer community and compete with themselves, while Halo Reach is still played by a lot of people.
LAWLZ at the hate from PwnTang, strangerdanger and others about "WAAAAAAAHH!! IT'S NOT RECREATING MY LAN NOSTALGIA FROM 10 YEARS AGO!"
Times change, and the crew didn't feel like RE-WRITING all the netcode to work with a new version of Live. Who can blame them? Why pay for all those work-hours when they have a perfectly good MP engine in Halo 3, ODST, or Reach already?
You love playing Halo on a LAN so much, call your friends over and hook up your old black cinder blocks and play Halo LAN. Otherwise, STFU.
Times change, and the crew didn't feel like RE-WRITING all the netcode to work with a new version of Live. Who can blame them? Why pay for all those work-hours when they have a perfectly good MP engine in Halo 3, ODST, or Reach already?
You love playing Halo on a LAN so much, call your friends over and hook up your old black cinder blocks and play Halo LAN. Otherwise, STFU.
@DasPooch
Oh, so its okay to recreate the nostalgia of the single player campaign with updated graphics and online netcode is okay, but asking for the multiplayer component (which was the most popular feature) isn't? Nice derp logic.
Anyway, the only reason I posted was to point out that it has nothing to do with rewriting any code, because as I said, THEY ALREADY WROTE THE NETCODE for the new online co-op component. It was simply a business decision.
Frank O'Connor has actually confirmed this in interviews, it's not up for debate: http://www.g4tv.com/thefeed/blog/post/715011/halo-combat-evolved-anniversary-edition-details-343s-frank-oconnor-talks/
"The multiplayer component [in Anniversary] all runs in the Reach engine. We didn't want to cannibalize the existing player base for Reach in the middle of its lifespan, so what we did was we picked a group of multiplayer maps that would work well with that Reach stuff."
Oh, so its okay to recreate the nostalgia of the single player campaign with updated graphics and online netcode is okay, but asking for the multiplayer component (which was the most popular feature) isn't? Nice derp logic.
Anyway, the only reason I posted was to point out that it has nothing to do with rewriting any code, because as I said, THEY ALREADY WROTE THE NETCODE for the new online co-op component. It was simply a business decision.
Frank O'Connor has actually confirmed this in interviews, it's not up for debate: http://www.g4tv.com/thefeed/blog/post/715011/halo-combat-evolved-anniversary-edition-details-343s-frank-oconnor-talks/
"The multiplayer component [in Anniversary] all runs in the Reach engine. We didn't want to cannibalize the existing player base for Reach in the middle of its lifespan, so what we did was we picked a group of multiplayer maps that would work well with that Reach stuff."
I was disapointed when I heard this game was using the Reach engine. The vehicle physics in CE were so much fun to drive.
Blood gulch is all I ask for. That, and Gephyrphobia and Timberlands.
Blood gulch is all I ask for. That, and Gephyrphobia and Timberlands.
I can't play halo now without sprint. Armor lock, jet packs, and invisibility pretty much cancel out any joy I get from sprint though.
@PwnTang
I'm glad that you left out the part in that same interview where he said that it wouldn't be able to play the same...
I'm glad that you left out the part in that same interview where he said that it wouldn't be able to play the same...
@PwnTang - ...and what exactly is wrong with that decision? Assuming for a moment that this is the ONLY reason for taking this action (which it's not), not wanting to split a playerbase is a valid concern.
Herpy-derp is as herpy-derp does, kid.
Herpy-derp is as herpy-derp does, kid.
Gephyrophobia. Only existed on the PC version but is definitely one of the funnier maps. Falling deaths guaranteed. You could launch a warthog to the enemy side by driving it into the turrets but I doubt this would be in due to it not being Halo 1 style gameplay.
@Lycan - Care to point out that part? Because I'm pretty sure it doesn't exist.
@DasPooch - Because die-hard Halo CE multiplayer fans are not playing Reach.
@DasPooch - Because die-hard Halo CE multiplayer fans are not playing Reach.
@DasPooch
No hate, I simply said it was a weak reason. And, as PwnTang pointed out, not the real reason. I'm still looking forward to the game. It'll be fun to play old maps with new gameplay.
@Lycan
Wut? Because it's the worst reason ever, I'd like to see you do it while baking a cake and doing cartwheels. That way we'd not only get a straight update of an old game, but also have cake and be entertained by your cartwheels.
No hate, I simply said it was a weak reason. And, as PwnTang pointed out, not the real reason. I'm still looking forward to the game. It'll be fun to play old maps with new gameplay.
@Lycan
Wut? Because it's the worst reason ever, I'd like to see you do it while baking a cake and doing cartwheels. That way we'd not only get a straight update of an old game, but also have cake and be entertained by your cartwheels.
DERELICT, people! That's the best H1 map.
I'm not too thrilled about how the Dammy remake looks, but I'll take it because it's a good map. Battle Creek looks lovely, though.
I'm not too thrilled about how the Dammy remake looks, but I'll take it because it's a good map. Battle Creek looks lovely, though.
follow
