{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/7/2015 11:54:44 AM
19
Can we all slow the hype train for a moment and address the fact that 343 are still up to their old tricks? Releasing a title with missing features and promising that they'll release them later.
What else isn't ready? They've yet to release a game that generally works well at launch with all of the features that we expect and they always promise to deliver certain features later on.
English
-
Edited by KingKrown: 10/8/2015 3:38:49 AMOh goodness,you've opened the flood gates. You're just supposed to throw money at it and not question it.
-
Just curious, would you rather the game launch mid-December?
-
No I'd rather 343 ensure that everything is ready before the release date that they set, it's not unreasonable.
-
If ambitious features had to be cut, say Forge in Halo 5 won't be as revolutionary in order to make the launch, would you be okay with that?
-
Why would I be Ok with that? The options aren't just a). release broken or b). delay features, they could also finish everything in time for release.
-
That's not what I'm saying. Cutting features =/= broken release. IE, Halo: Reach originally had a lot more wildlife in the game than just the Guta or Moa. In order to reach the launch date on time, they had to cut most of the Guta encounters and the rest of the wildlife in order to ship a complete and working game.
-
Would you prefer them to release a broken forge?
-
No I would prefer them to release a complete and working title on release but apparently I'm being unreasonable. Aside from their weekly update what assures me that I'm paying for Forge in a month and further more who is to say that it will work fully as you assume?
-
All h5 dlc is free so you won't need to pay for forge. With all the new content and tools with forge it'll take a little longer until the bugs are fixed
-
Halo 4 launched fine, even well especially for a first time developer bringing the next game in a very beloved franchise. The amount of stress those servers must've had in the first month makes it quite impressive to say the least.
-
Halo 4 launched with the promise of a file browser and a rank system later on, we waited almost a year and even then those features were not as good as past versions. As for server stress, the population dipped almost instantly so...
-
MCC is released, people complain it was rushed and wish it was delayed. Halo 5 is released, people complain some features were delayed and wish it was rushed. And regardless of what you believe, 343 has only released one game they themselves made, and it worked just fine at launch--Halo 4. Halo 5 had a beta and it worked pretty great for a game a year out.
-
MCC was a shambles, we need not argue about that release because it's been done to death. Halo 4 however released missing a rank system and a file browser, both of which were promised shortly after release and both of which got delayed considerably. I'm not a "hater" of 343, I'm just sick of the pattern of: 1. Say everything that everyone wants to hear. 2. Last minute delay the release of features. As for the bugs and other stuff I'm not cutting 343 any slack, we're not talking about some Indie dev here, we're talking about a Microsoft studio with a massive budget and years of experience at this point. I agree that the Halo 5 beta was good and pending good reviews I will pick up a copy of the game but it did have similar matchmaking issues to MCC upon release which also concerns me.
-
Halo 5's beta issues were no where near as bad, and they were fixed in relatively short order. 343i also didn't develop MCC, they only did the unified interface that connected the games. There were almost 10 studios actually working on that game. In any case we have no reason to believe that Halo 5 will have a shoddy launch. The beta worked great, and it is only one game, not 5 games running 7 engines with 3 incompatible architecture bases on a single console like MCC was. It's built from the ground up to work on Xbox One, and I'd rather Forge be working than for it to be released in shambles. The alternative is delaying the whole game, which makes no sense to do either.
-
Id rather Forge work and get it when it's done than gets broken game feature like MCC.
-
I can't argue with that logic but the Halo 4 file browser was promised shortly after release and that took a considerably long time, when it did release it left alot to be desired.
-
And again, Halo 4 had many issues that 343i addressed and admitted were big faults. But Halo 4 was built under the looming shadow of next gen and the 360 was beyond its limits. But Halo 5 is built entirely by 343, built in the current gen, and has already delivered on all of its promises. Forge is the next and they wouldn't just delay Forge for any bad reason. It's too huge of a Halo staple at this point for the delay to be because of a screw up. This is a good thing. Forge will be good and something tells me you are just mad that you have to wait.
-
I was with you until the last statement
-
I didn't mean it as an insult. Sorry if it came off that way.
