{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by templar1:
9/12/2014 12:31:26 PM
5
Something to note fellow Guardians:
There could be a patch in the works. The reason patches aren't coming out quickly however can be summed up by one word: Microsoft.
A content creator needs to pay Microsoft $50,000 for every patch they make for a game on their platform. That means even if it is the smallest of changes, like changing a few letters of text, Bungie will need to pay $50,000 to have the game re-certified and that's AFTER going through all the red tape. So it stands to reason that content creators would bundle as many changes/fixes as possible within each patch to conserve costs, and I know how ludicrous that must sound considering Destiny's commercial success, but $50,000 a pop can add up quick. As to why this should effect Playstation users; multiplat developers won't release patches for one platform and not the other, that is a fast track to alienating a large portion of your audience.
So I guess just be patient. Sure, its frustrating seeing almost no feedback from Bungie on this, but Deej has commented that they are aware of the negative response to no proximity/team chat (I cannot remember the link though). So there is a good chance it will be included in the next hotfix/patch.
English
-
Here's the sauce for Deej's response: [url]http://www.bungie.net/en/Forum/Post/66612180/0/0/1[/url] "Our concern was that people who are not your friends won't respect the quality of your experience. UPDATE: Sharing all of this feedback with the people who should read it. We'll see what they have to say."
-
Edited by templar1: 9/12/2014 2:28:41 PMThere was actually a more recent response, on Twitter, in which someone linked to this post (or one regarding the same issue) and Deej replied saying they are aware and are always watching but nothing else.
-
Thanks for this information. I was not aware of the costs that Microsoft Certification brought to a developer. Do you have a link or something from Microsoft demonstrating their prices for this asinine behavior?
-
Actually, I'm afraid I was mistaken. Apparently this policy was dropped in June of last year for 360 titles/arcade. I had heard from someone recently that his practice was still going on, but researching the issue confirmed this to be false. Though something to note: getting information about this change was like pulling teeth apparently, so who knows what sort of bureaucracy is going on behind the scenes regarding console patches.
-
Even if there were costs for Microsoft certification per patch, Destiny has the ability to do in-game patches, as seen on all consoles during the beta. There's no need for re-certification in this case, when it can all be done through in-game patching(which, I assume, was why the tested, and successfully completed those tests, in the beta). That also doesn't address Bungie's lack of response to one of the biggest problems people bringing up in the feedback. A post from before the game was even in beta, and another slightly afterwards adding basically nothing to the discussion, is not communicating well with their players. I think that's first and foremost what we want right now - communication. I don't think we expect it to just happen overnight, but to know that it's being worked on, or that it's definitely being considered, would be satisfactory.
