And multiplayer! Well that was the challenge. We ached over this one. Do we build peer-to-peer netcode for Halo 1 and simply update the graphics? Do we disrupt the Halo: Reach player base and community ecology? Or do we invest in the loyalty of those players, and the amazing new features Reach has brought to the table? It was a super hard decision, but ultimately the thing that tipped the balance in Reach’s favor was this simple fact: If we added netcode to Halo CE’s console gameplay, it would change it irrevocably. It would NOT be the same game you remembered – it would be a compromised vision of it, with the pros and cons that lag, latency and more can bring. Oh, and everyone would whore the pistol 24/7.
So Reach it is. And that helped us define which maps to choose. Obviously Blood Gulch would be a bit redundant. And obviously Beaver Creek was a no-brainer. You’ll also see a new Covenant-themed version of Damnation, a glimpse of another old fan favorite from Halo CE, and one map that while famous and awesome, has never been seen on console before. I’m sure you’ve figured it out by now.
Czyli w skrócie, dlatego, że Reach ma lepszy kod sieciowy i każdy wykorzystywałby podczas gry tylko Pistol'a.
Ostatnia nadzija w tym że naprawią reach...
OdpowiedzUsuńOstatnia nadzieja w tym, że zrobią porządne halo4...
OdpowiedzUsuń