There was a thread a while ago concerning a Halo 5 beta and of course some people were with it and other against it.
I’m somewhat against a beta because it could take up too many resources but I wouldn’t mind helping with stress tests and trying to find glitches or just testing which weapons should be nerfed and what gametypes have flaws in them.
So if possible by 343i would it be nice to get some sort of what you will be doing this week for Halo 5. Like saying which features from this forum you are considering and giving us a week or a longer period of time check up on Halo 5 progress such as things that might be cut out and if fans like the sound of that certain thing in the game than trying to find a possible way to put it in and at the same times listing what would have to go if that item is implemented into Halo 5.
Of course if something like this takes up too much time by all means disregard it but people like me or i’d assume anyone who comes to this side of the forum want to try and help build Halo up as much as possible and this seems like the biggest way we could help while not being left in the dark and actually having something more to do with the game than what we have been doing over the past decade.
OP, I absolutely love your idea and I truly believe that is exactly what they should be doing. However, 343i has shown they didn’t learn their lesson from Halo 4 so sadly, while they should be updating us, its not gonna happen. We’ll just have to wait until E3 next year to find out what they’re adding…
While I feel like this is a terrible idea, let me propose a hypothetical. Let’s say 343 says, “This week, we decided against Elites in MM again because they aren’t canon with regards to matchmaking.”
Because then instead of actually working on the game, people would have to do damage control and try to justify decisions that wouldn’t necessarily have context. Because all we on the internet see is the surface. For each decision made, there are tons of underlying issues/reasons behind that but instead of realizing that, everyone grabs on and focuses on ONE thing and it causes a huge commotion.
> While I feel like this is a terrible idea, let me propose a hypothetical. Let’s say 343 says, “This week, we decided against Elites in MM again because they aren’t canon with regards to matchmaking.”
>
> Because then instead of actually working on the game, people would have to do damage control and try to justify decisions that wouldn’t necessarily have context. Because all we on the internet see is the surface. For each decision made, there are tons of underlying issues/reasons behind that but instead of realizing that, everyone grabs on and focuses on ONE thing and it causes a huge commotion.
Thats the thing, its not just going to be a this is what we are doing update but what we are doing and why. They system wouldn’t work well if their wasn’t a why to the things being taken out right before our eyes.
> While I feel like this is a terrible idea, let me propose a hypothetical. Let’s say 343 says, “This week, we decided against Elites in MM again because they aren’t canon with regards to matchmaking.”
>
> Because then instead of actually working on the game, people would have to do damage control and try to justify decisions that wouldn’t necessarily have context. Because all we on the internet see is the surface. For each decision made, there are tons of underlying issues/reasons behind that but instead of realizing that, everyone grabs on and focuses on ONE thing and it causes a huge commotion.
To bounce back from a different point of view, what 343 could do is post an update saying (Hypothetically), “This week, teams have been testing including playable Brutes in War Games as a new element. While it’s not decided whether or not this makes it to the final game, What do you think of the idea?”
Not only would it allow for instant feedback from the Community instead of the amount of negative response that came directly after launch because of new elements that the players did not want, but it would also send a subtle message to people who gave up with Halo 4 that 343 is trying to get Community support on this.
> some people were with it and other against it.
Why would there be anybody against a beta? Betas help improve the game based on player feedback. If Halo 4 had a beta, it certainly might not be in the position it is today.
> I’m somewhat against a beta because it could take up too many resources but I wouldn’t mind helping with stress tests and trying to find glitches or just testing which weapons should be nerfed and what gametypes have flaws in them.
I figure this is a somewhat good and probably the only valid reason for not having a beta. However, the gain of a beta could not only be significantly useful feedback, but also the promotion of your game or another game. For example, the purchasing of Halo 3: ODST guaranteed you access to the Halo: Reach beta, which most likely had an effect on Halo 3: ODST sales. Bungie is also doing this with their newest game Destiny, allowing those who preorder the game to gain access to the pre-release beta. Let us also not forget Crackdown and Halo 3’s beta.
As for my main reply to this thread, it’s simply too early for 343 to be giving us anything. People, as well as myself, are forgetting that this game is most likely due in a little more than an entire year from now. We don’t even have a proper name for the game besides the broad “Halo Xbox One”, which I would be quite surprised if they kept. Development is probably in such an early stage right now that there’s no telling what the future could hold for it.
> > some people were with it and other against it.
>
> Why would there be anybody against a beta? Betas help improve the game based on player feedback. If Halo 4 had a beta, it certainly might not be in the position it is today.
Gee, maybe you should read some of the posts in this thread
I’d give you an insight on why people are against a beta, which btw, doesn’t always improve the game, and not every single player gives feedback other than “I -Yoinking!- HATE THIS GAME!”, “YOU FAIL AT MAKING HALO GAMES!”, and “I WANT BUNGIE TO MAKE HALO NOT YOU!”, plus like OP said, Beta’s take resources, time, and money, to do. They have to take their current build, make a copy of it, but without everything but the main menu, sound, armor models and textures, and a handful of MP maps they want to use. They then needs to test the beta to make sure no issues pope up with removing most of the game from the build, they then have to button it up, send it off to Xbox LIVE to be certified which takes 6 or so weeks before it’s put onto Xbox LIVE, then they need to set up a server to run the beta, and then have employees sort through the feedback.
BTW by the time the beta is released, the build the beta was made from is at least 3 months old.
I would love to see 343i aiming at something like this. If not a weekly update maybe every two weeks or Fortnight Update.
Twice a month getting an update about what 343i is currently doing and how Halo 5 is going. If you ask me it wouldn’t hurt as much if they were to bump the date back if the public would know the reasons why.
Like if one update takes out alot of things but 343i wants to put them back in but it would push the game back a few months. IF it is for reasons that we know of i think it wouldn’t leave as big of a wound. Not to mention that many believe making Halo 5 in 2014 is already a small amount of time to make a game. At least a Halo game.
> While I feel like this is a terrible idea, let me propose a hypothetical. Let’s say 343 says, “This week, we decided against Elites in MM again because they aren’t canon with regards to matchmaking.”
>
> Because then instead of actually working on the game, people would have to do damage control and try to justify decisions that wouldn’t necessarily have context. Because all we on the internet see is the surface. For each decision made, there are tons of underlying issues/reasons behind that but instead of realizing that, everyone grabs on and focuses on ONE thing and it causes a huge commotion.
-
343 Don’t have to (and most likely wouldn’t) tell us everything.
-
It will produce a better game with a more sustained population and a more satisfied community.
-
If they did say “This week, we decided against Elites in MM again because they aren’t canon with regards to matchmaking.”, then the community could reply: “Screw MM being Canon we want elites!.” And (I Know this is just an example) but why should MM be canon? Its questions/responses like these in which the community can respond.
I like your idea OP.
> 2. It will produce a better game with a more sustained population and a more satisfied community.
This is a 50/50 truth.
On one hand, yes it would be a better game, with a more sustained population and a satisfied community to back it up. But on the other hand, like Snicker said, it could drive a wedge into the community and drive farther apart, and break up the community.
Hell, we saw some of this when 343i took over, and a few features that Bungie had offered didn’t transfer over to 343i, like Saved Film Rendering, and Nameplates. Every now and again, new members show up and question why there’s no more rendering, no more nameplates, why we can’t change nameplates, asking how to convert Saved Film Files into Video files.
Most of those people have no idea why those features wasn’t included in the transfer, and others have no idea that Saved Film Files are not video files, and yet they still get pissed, and have issues understanding the truth behind something.
Granted I would love to see them have VidDocs and weekly updates explaining how and why some things are, for me it’d explain why do somethings, but then again, I understand more of what goes on behind the scenes when it comes to game development. I’d love to see them do a weekly update that gives us a up-to-date look on a patch that’s coming out, explaining each set as they make it. That’d most likely help explain why it takes so long for a TU to be released, and hopefully either clam the nerves of some nay sayers, or get them to go after the true reason why it takes months to release TUs.
> > 2. It will produce a better game with a more sustained population and a more satisfied community.
>
> This is a 50/50 truth.
> On one hand, yes it would be a better game, with a more sustained population and a satisfied community to back it up. But on the other hand, like Snicker said, i<mark>t could drive a wedge into the community and drive farther apart</mark>, and break up the community.
>
> Hell, we saw some of this when 343i took over, and a few features that Bungie had offered didn’t transfer over to 343i, like Saved Film Rendering, and Nameplates. Every now and again, new members show up and question why there’s no more rendering, no more nameplates, why we can’t change nameplates, asking how to convert Saved Film Files into Video files.
> Most of those people have no idea why those features wasn’t included in the transfer, and others have no idea that Saved Film Files are not video files, and yet they still get pissed, and have issues understanding the truth behind something.
>
>
> Granted I would love to see them have VidDocs and weekly updates explaining how and why some things are, for me it’d explain why do somethings, but then again, I understand more of what goes on behind the scenes when it comes to game development. I’d love to see them do a weekly update that gives us a up-to-date look on a patch that’s coming out, explaining each set as they make it. That’d most likely help explain why it takes so long for a TU to be released, and hopefully either clam the nerves of some nay sayers, or get them to go after the true reason why it takes months to release TUs.
Like sprint :p. I see your point, but whether we know what’s gonna happen or not isn’t gonna affect the community as much as the content itself. I’d rather discuss something with my fellow community members and not got the result i personally desire than get a result which noone in the community asks for.