The Pit is my favorite map of all time and I want it in a good game. Halo 4 isn’t really the best game to put it in due to sprint and many other aspects of the game but I believe in that Halo 5 will be amazing thanks to your efforts in improving Halo 4.
What I am trying to say is that Halo 5 will have better mechanics (hopefully) and The Pit deserves to be played on good settings. I am sure alot of people feel the same way.
With all due respect, The Pit is one of the easiest maps to be made in Forge. Expect perfect Forge remakes in the first month after release. Adding it to Halo 4 was a mistake, in my opinion. After that, adding it to Halo 5 would be a colossal failure on 343i’s part.
> With all due respect, The Pit is one of the easiest maps to be made in Forge. Expect perfect Forge remakes in the first month after release. Adding it to Halo 4 was a mistake, in my opinion. After that, adding it to Halo 5 would be a colossal failure on 343i’s part.
Agreed. They should’ve remade a map that only they had the tools to remake. There were much better options.
Also, Halo 5 will probably have Sprint too. After making it default in Halo 4, there’s really no going back.
I don’t get the hate for sprint, I hardly use the ability and spent most of my time shooting and planning in games.
The sad truth about The Pit returning in H4 is that it’ll not flow as well as it’s predecessor.
This is in part due to it’s potential art style. We don’t need unnecessary aesthetic clutter.
This is also in part due to the game mechanics. IMO, the Forge remakes in H4 play out like crap, even if they are well designed.
This post has been edited by a moderator. Please refrain from making non-constructive posts.
*Original post. Click at your own discretion.
no
> I don’t get the hate for sprint, I hardly use the ability and spent most of my time shooting and planning in games.
Hehehe, it’s really fun when you’re pursuing someone and he tries to do a ninja on you but since you didn’t sprint, he leaves himself vulnerable. 
> > With all due respect, The Pit is one of the easiest maps to be made in Forge. Expect perfect Forge remakes in the first month after release. Adding it to Halo 4 was a mistake, in my opinion. After that, adding it to Halo 5 would be a colossal failure on 343i’s part.
>
> Agreed. They should’ve remade a map that only they had the tools to remake. There were much better options.
>
> Also, Halo 5 will probably have Sprint too. After making it default in Halo 4, there’s really no going back.
Don’t look a gift horse in the mouth.
> I believe in that Halo 5 will be amazing thanks to your efforts in improving Halo 4.
This makes no sense to me. 343 made Reach a much better game, but that obviously wasn’t an indicator of how Halo 4 would turn out. Why should their second go at fixing a broken game have any positive bearing on the future?
Anyways, there’s zero chance of The Pit being in the next Halo game since it’s going to be in the current one (as another ugly brown map - hooray!).
> > I believe in that Halo 5 will be amazing thanks to your efforts in improving Halo 4.
>
> This makes no sense to me. 343 made Reach a much better game, but that obviously wasn’t an indicator of how Halo 4 would turn out. Why should their second go at fixing a broken game have any positive bearing on the future?
>
> Anyways, there’s zero chance of The Pit being in the next Halo game since it’s going to be in the current one (as another ugly brown map - hooray!).
The outstanding grievances the community had with Reach were fixed in in the TU AND Halo 4, namely bloom, armor lock and OP grenades. So yes this is an indicator.
The Pit got made into an official map because it’s a fan favorite and thus deserves to be more than a bland-looking forge remake.
> as another ugly brown map - hooray!
You’re right.
Battlefields should always be sunshine and rainbows. There is absolutely no room for artistic, desolate looking maps in Halo.
We need green grass and blue skys, and ONLY green grass and blue skys. Forget that I can’t see my crosshair over all that light, Halo needs to look pretty.
> I believe in that Halo 5 will be amazing thanks to your efforts in improving Halo 4.
I’m skeptical as always.
Halo 4 was heading in the right direction, but somewhere along the line they just stopped and said “Ok we are halfway done fixing Reach, now we must stop and implement CoD”.
> > > I believe in that Halo 5 will be amazing thanks to your efforts in improving Halo 4.
> >
> > This makes no sense to me. 343 made Reach a much better game, but that obviously wasn’t an indicator of how Halo 4 would turn out. Why should their second go at fixing a broken game have any positive bearing on the future?
> >
> > Anyways, there’s zero chance of The Pit being in the next Halo game since it’s going to be in the current one (as another ugly brown map - hooray!).
>
> The outstanding grievances the community had with Reach were fixed in in the TU AND Halo 4, namely bloom, armor lock and OP grenades. So yes this is an indicator.
Uh huh, and what about:
Then there’s the transition from a sprint armor ability to built-in sprint that can’t even be disabled, the inability to allow players to drop the flag and a whole myriad of other problems.
Polishing a turd is not indicative of a better future product. People who don’t like the aforementioned items should not set themselves up for disappointment again.
> You’re right.
>
> Battlefields should always be sunshine and rainbows. There is absolutely no room for artistic, desolate looking maps in Halo.
>
> We need green grass and blue skys, and ONLY green grass and blue skys. Forget that I can’t see my crosshair over all that light, Halo needs to look pretty.
http://halowiki.net/images/0/09/Maps_Header.jpg
VS
https://www.halowaypoint.com/en-us/intel/maps
RIP maps that were functional and didn’t look like puke for the most part.
> > > > I believe in that Halo 5 will be amazing thanks to your efforts in improving Halo 4.
> > >
> > > This makes no sense to me. 343 made Reach a much better game, but that obviously wasn’t an indicator of how Halo 4 would turn out. Why should their second go at fixing a broken game have any positive bearing on the future?
> > >
> > > Anyways, there’s zero chance of The Pit being in the next Halo game since it’s going to be in the current one (as another ugly brown map - hooray!).
> >
> > The outstanding grievances the community had with Reach were fixed in in the TU AND Halo 4, namely bloom, armor lock and OP grenades. So yes this is an indicator.
>
> Uh huh, and what about:
>
> - Lack of in-game ranks - Halo 4 didn’t even one ONE ranked playlist at launch.
> - Complaints about loadouts - Halo 4 expanded on them instead of reducing them.
> - Lack of classic offering at launch - Again, there was nothing at launch.
> - Complaints about jetpack and active camo - Halo 4 kept them and then added even more crutches like promethean vision.
>
> Then there’s the transition from a sprint armor ability to built-in sprint that can’t even be disabled. the inability to allow players to drop the flag and a whole myriad of other problems.
>
> Polishing a turd is not indicative of a better future product. People who don’t like the aforementioned items should not set themselves up for disappointment again.
Armor abilities, loadouts and the like were integral to the overall design of the game. Not to say it wouldn’t work without them, but that Bungie’s vision included them and 343i wanted to respect that vision. Same with Halo 4. Bungie had a clear path that they wanted Halo to go, and 343i shares Bungie’s philosophy of evolving off of the previous game’s ideas.
The difference here is that 343i has openly acknowledged the mistakes they’ve made, that they’ve reevaluated what needs to be done in the future. They’ve learned more “about what the community wants” with Halo 4 than they ever did with Reach. This isn’t to say 343i are blameless, but it suggests a willingness to change things, something Bungie would never, and have never, admitted; they released Reach and never touched it again. To me that speaks more to 343i’s caring for this community’s opinion than Bungie’s. 343i did what they could with Reach and what they fixed persisted into Halo 4. Now Halo 4 has its own set of problems that 343i are acknowledging and working on from the ground-up in Halo 5.
It’s naïve to expect everything to be fixed in one go, nothing ever works that fast or smoothly. For what it’s worth, Reach post TU was a markedly improved game and all of those improvements spilled over into Halo 4. All that implies is that this line of work will continue into Halo 5. As I’ve said before, if Halo 5 still isn’t an improvement, then you can complain. But right now all signs suggest that it will be, so we can’t let our bitterness get in the way of facts.
>
Well that post is constructive…
> Armor abilities, loadouts and the like were integral to the overall design of the game. Not to say it wouldn’t work without them, but that Bungie’s vision included them and 343i wanted to respect that vision. Same with Halo 4. Bungie had a clear path that they wanted Halo to go, and 343i shares Bungie’s philosophy of evolving off of the previous game’s ideas.
Of course it would work without them. Bungie’s trilogy did it and guess what? They didn’t have crappy populations! Armor abilities and loadouts were a mistake and received a big outlash. Going crazy and putting the new gameplay elements and steroids is not evolving on an idea. It’s taking a problem and making it even worse. Not knowing what weapons and grenades your opponents are spawning with is terrible in a game like Halo, given the reputation that it made for itself in the earlier days.
> The difference here is that 343i has openly acknowledged the mistakes they’ve made, that they’ve reevaluated what needs to be done in the future. They’ve learned more “about what the community wants” with Halo 4 than they ever did with Reach. This isn’t to say 343i are blameless, but it suggests a willingness to change things, something Bungie would never, and have never, admitted; they released Reach and never touched it again. To me that speaks more to 343i’s caring for this community’s opinion than Bungie’s. 343i did what they could with Reach and what they fixed persisted into Halo 4. Now Halo 4 has its own set of problems that 343i are acknowledging and working on from the ground-up in Halo 5.
Bungie ditched Reach because they were pretty much out of control of the series and had to give Destiny more attention. Had they stuck around longer, they almost certainly would have made a TU and it almost certainly would have been less contained than the TU that we got.
How does 343 shown that they know what the community wants? They sure didn’t acknowledge the wants of the campaign and Spartan Ops filmers and speedrunners since they ruined theater mode. They sure didn’t acknowledge the wants of the competitive crowd since CSR didn’t exist until a few months ago. They sure didn’t acknowledge the wants of Firefight fans since they scrapped it.
How about red Xs? How about the file sharing/browing problem? How about the initial DLC fiasco?
All the positive reassurance from 343 (which is nothing more than a tool to try and string the skeptical along again) isn’t enough to pull the wool over the eyes of people who know better.
> As I’ve said before, if Halo 5 still isn’t an improvement, then you can complain. But right now all signs suggest that it will be, so we can’t let our bitterness get in the way of facts.
Please.
That’s just like what people were saying before release. They kept pumping out this nonsense about how you can’t judge a game before playing it. They said that if Halo 4 were bad, then people could complain. Eight months after launch and the game can barely crack 30K. Now you’re telling me that I, once again, must wait until the next game before being critical?
Broken record. Broken record everywhere.
> >
>
> Well that post is constructive…
I cannot explain why but I heavily lol’d at that…
The Pit should not return in Halo 5, but Construct should.
Please, no more Pit.
We had the Pit in the Halo 3 and Halo Reach circuits… and we’re probably going to have it for Halo 4. The Pit’s metagame is gone.
> > You’re right.
> >
> > Battlefields should always be sunshine and rainbows. There is absolutely no room for artistic, desolate looking maps in Halo.
> >
> > We need green grass and blue skys, and ONLY green grass and blue skys. Forget that I can’t see my crosshair over all that light, Halo needs to look pretty.
>
> http://halowiki.net/images/0/09/Maps_Header.jpg
>
> VS
>
> https://www.halowaypoint.com/en-us/intel/maps
>
> RIP maps that were functional and didn’t look like puke for the most part.
That makes me cry. I miss Halo 3 maps so much. All of the Halo 4 maps look too similar! 
> > > You’re right.
> > >
> > > Battlefields should always be sunshine and rainbows. There is absolutely no room for artistic, desolate looking maps in Halo.
> > >
> > > We need green grass and blue skys, and ONLY green grass and blue skys. Forget that I can’t see my crosshair over all that light, Halo needs to look pretty.
> >
> > http://halowiki.net/images/0/09/Maps_Header.jpg
> >
> > VS
> >
> > https://www.halowaypoint.com/en-us/intel/maps
> >
> > RIP maps that were functional and didn’t look like puke for the most part.
>
> That makes me cry. I miss Halo 3 maps so much. All of the Halo 4 maps look too similar!
I agree hopefully they go back to making good looking maps. Other Halo games had beautiful maps as well. Halo 2 had Sanctuary. Halo CE had Death Island, and Halo Reach had Highlands. Halo 4 maps aren’t good at all in my eyes. They look the same and the majority of the maps are forge maps.
