> > Servers going up & down?? How long has 343 had to get the servers ready for the release of Halo 4? Bad start to a less then stellar game.
> You sir have no idea how game deployment works. Even if they had preparation for a million years they would never be able to gauge how much their full customer base will be. And overshooting it is bad business. Adjusting to demands is better, sure its a rough start but it’s better than losses.
This would be true had Waypoint not already have been a battle-tested system for the past 3 years on Halo: Reach.
There are also a myriad of ways of supporting far more users than a server is naturally capable of by providing database queues and forcing latency / loading times while hardware is expanded to compensate for the large influx of players.
People who often say “You have no idea how game development works” often if ever actually work within the games industry itself and don’t know themselves.
While some bugs should be expected, especially with new system implimentations; when you are building upon already established systems, then the issues at play come down to poor planning, implimentation or stress testing.
In-fact the complete lack of Halo 4 Beta Testing on Xbox Live, to me is absolutely inexcuseable with the modern console designs. Even one that lasted only a matter of a week or two would’ve provided invaluable stress test feedback, along with a large amount of community feedback to fine tune systems in time for release.
As far as I’m concerned while this is a Premium Franchise, how things have been handled so far frankly just shows 343s’ development inexperience; particularly concerning game development.
While you can easily point to a large number of other developers who suffer from similar issues, that is not an excuse… just means there are plenty of other developers who frankly haven’t grown up and evolved as technology has or to accomidate the growing needs of communities that SHOULD be more involved rather than seperated from the development pipeline.
Anywho as for the Challenge itself… one of them is actually impossible to get, because it is for completing Chapter 2 Episode 2; but the Challenge itself is for Chapter 5 Episode 1, so it is looking for the wrong chapter in Episode 2.
The same issue happened last week with “Episode of Legend” or whatever, where it wouldn’t complete until you completed the entire Episode on Legendary then completed the one it wanted on Legendary Solo.
It is annoying as many of the mistakes that seem to be at the root of Waypoint, to me appear to be quite simple programming errors… which is most puzzling given Visual Studio (even Web Edition) has some incredibly robust debug and intellisence tools that simple mistakes like this should instantly show up to the developer - almost makes me think the entire system was rushed through development.