Posts on Current Forum | Archived Posts
|
|
|
||
|
||||
|
||||
|
||||
| Frequently Asked Forum Questions | |
|||
|
||||
|
|
|||
| ||||
| ||||
| ||||
| Search Older Posts on This Forum: Posts on Current Forum | Archived Posts | ||||
| ||||
| ||||
| ||||
| Re: If you were in charge of creating a Reach Patc | |
| Posted By: FyreWulff <mkidder@gmail.com> | Date: 3/9/11 4:36 a.m. |
In Response To: If you were in charge of creating a Reach Patch... (UnrealCh13f) : The Bungie.net forums are going rampant about how 343 Industries will : "save" Reach by possibly deploying a title update to fix : "Reach's obvious flaws" (i.e Armor Lock, Bloom, etc.) : Is it needed? If yes, what would you change? They're expecting too much out of a TU. AL is a matter of opinion. Bungie already nerfed it massively from the beta, so the only thing you can really tweak it to do is remove it from a gametype or include it. Simple as that. Bloom is client side on the console, meaning that even if there was a patch that removed it for the host, clients would still see the bloom effect. The only way to fix this would break compatibility with older versions of Reach, and that is something not worth breaking compatibility over. And even if they removed bloom, all they would do is force you to fire at the pace you can already fire at to have perfect precision. Learn to shoot, scrubs. I have literally yet to see anything that requires something as time intensive and costly as a TU. It's obvious that after the fiasco that was Halo 2 online, Bungie wanted to avoid patching as much as possible. Reach can apparently add new achievements without patching, etc. If anyone is willing to try and convince me that Reach needs a TU other than just because we should have a patch for the sake of a patch, go ahead.
| |
|
| Replies: |
The HBO Forum Archive is maintained with WebBBS 4.33. |