Tha Robbertster
Member
Stop it. Reach was the $60 beta.
Reach barely had any glitches at launch. 4 has lots of 'm.
Stop it. Reach was the $60 beta.
Never been a big nintendo fan so i complete see where he is coming from.
Bar HD mario I don't know whats appealing to me on the system.
Pokemon Games? Under developed franchise
Zelda? No Interest
Metroid? Never played them.. maybe
Reach barely had any glitches at launch. 4 has lots of 'm.
But Reach had a beta. Just saying.Reach barely had any glitches at launch. 4 has lots of 'm.
I was talking about the title update in which they fixed no bugs and introduced new ones.
That was 343's doing.
But Reach had a beta. Just saying.
Bahha true, still it did go through a beta so not really that comparable?The Halo Reach beta had less glitches than Halo 4.
What's this about a new FFA Playlist? I can't see the details since I'm at work.
Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
8 Players FFA only oddbal and KOTH games.
No bullshit overshield or damage boost when somebody is good.
Camo should not be an Armor Ability. Shame on 343 for furthering Bungie's mistake.
It's incredibly frustrating. It's so hard to see and sometimes it doesn't show up on the radar. Why is that?
Camo should not be an Armor Ability. Shame on 343 for furthering Bungie's mistake.
How about this, if i absolutely has to be an AA:
-When moving, you gain better camo, but you show up on radar; similar to previous Halo games.
-When still, your camo fades to poor camo. This helps eliminate the invisible long range sniper and you remain invisible on the radar.
Reach barely had any glitches at launch. 4 has lots of 'm.
Stop it. Reach was the $60 beta.
GAME CHANGER!Just played FFA King Abandon. Same rules for Team King applied to FFA. Didn't give you any + white text for kills, your hill points count up in white text as you're in the hill.
These player count charts from Halocharts.com are super depressing. Every single playlist took a nosedive with Black Ops II launch and hasn't recovered at all.
Even the overall population peak was hitting 400k players at a time before COD released... Now it's dropping below 200k...
http://www.halocharts.com/2012/chart/dailypeakpopulation/all
Someone should tell 343i that you can't out-CoD CoD before they start working on Halo 5.
jk
I'm getting runtime errors when going to Waypoint.
Code:Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>
It's incredibly frustrating. It's so hard to see and sometimes it doesn't show up on the radar. Why is that?
Yup, I wish 343 could have been bolder to give jetpack and camo the ax. these things need to die asapCamo should not be an Armor Ability. Shame on 343 for furthering Bungie's mistake.
I believe you don't show up on radar as long as you're not moving. While invisible. Yeah.
Nope. They can fuck around with it all they want, but being invisible is incredibly powerful for an online experience where the netcode is, ahem, "buttery smooth". When you start adding the stealth specialization like what's just starting to happen, it will be even worse. I hate watching clips of people hiding around a doorway just waiting for someone to do something as stupid as walk through it. :-\Everyone else but 343 gets it.
There can never be any justification for camo on spawn.
This is one of the reasons I think I'm inadvertently holding Spartan Ops to a high standard. We lost a LOT with Firefight, and Spartan Ops needs to really differentiate itself and bring a lot to the table to make those loses feel worth it, and it's not there yet.Hell, even Personal Ordnance in SpOps would have been a great feature. Then again, so would medals, scoring, skulls, theater... :-(
and ammo.
Can you use camo in the hill? My beloved auto turret blows up if I enter the hill and I can't set one up inside. I figured, if they did that they'd make it so camo doesn't work in the hill. For balance. Right?Also, what the hell happened to adjusting loadouts based on gametype? Camo users in KOTH are the worst type of person.
Wheress my team snipers...
Forgot to add my Halo 4 hate today: NERF THE AR. NERF THE AR. NERF THE AR. KEVIN, NERF THE AR.
Nope. They can fuck around with it all they want, but being invisible is incredibly powerful for an online experience where the netcode is, ahem, "buttery smooth". When you start adding the stealth specialization like what's just starting to happen, it will be even worse. I hate watching clips of people hiding around a doorway just waiting for someone to do something as stupid as walk through it. :-\
Make the AA something to be earned in Personal Ordnance (along with PV, no more teams of with these AA's); it would make a more than suitable replacement for the extra grenades that nobody wants.
Also, what the hell happened to adjusting loadouts based on gametype? Camo users in KOTH are the worst type of person.
It acts like a mini-Saw and is effective even from large distances.The AR? I thought it was fine. It's actually a viable weapon to use now (in CQ)
That's a great point, what if personal ordnance granted you only a selection of AA's? These would only last for one life.
Everything else would be like the older Halo's, weapons and power ups on the map.