JavaScript is required to use Bungie.net

#feedback

Modificato da Tgane: 3/2/2015 11:13:28 PM
3

Question to bungie about 1.1.1

edit at bottom Now before this gets started. I don't even have a vex. So I'm not a kid that has one and is butt hurt by it being affected in the most recent patch. My question is, why would you ( bungie ) release this patch knowing that you were for lack of better terms breaking a gun? I was shocked to see you guys included that part in your patch notes, Like telling us would make it blow over any better. Did any dev stop and think " hey guys, maybe we should hold the patch ( yes miss your end of February deadline ) until we figured out a way to introduce the patch without any unwanted repercussions? I thought patches fixed things not cause more issues." I'm just curious on how some thought processes go on over there. Were you that worried about making that end of February deadline that you rushed it out? Was there a way to hold back what broke the vex and implement the rest of the patch without it? There seems like a lot of possible alternatives that could of been brought about. P.s. I'm 99% sure bungie won't ever reply to this but still, this is the feedback forum and stopping little things like that (accidentally breaking the vex ) from happening will go an extremely long way with your community. EDIT: Thanks to TDK, he was kind enough to point out that the info about the vex was later added to the notes after the patch was released. So good on bungie for that part. But shame on you for not catching that. Products need to be tested before being sold to the general population. I'm not going to sell you a boat I've made without seeing if it will at first float.
English
#feedback

Lingua:

 

Fate i bravi. Prima di postare date un'occhiata al nostro codice di condotta. Annulla Modifica Crea squadra Invia

Non ti è permesso visualizzare questo contenuto.
;
preload icon
preload icon
preload icon