JavaScript is required to use Bungie.net

Destiny 2

Discuss all things Destiny 2.
Edited by A_dmg04: 11/7/2019 8:03:14 PM
146

Bungie Doesn't Respond To CRITICISM.

Some of you probably have seen my most recent post. Almost 1200 upvotes. Thanks to everyone who took part in that. In one of the Bungie vidocs, they said Shadowkeep will be a two way conversation between them and the community. They told the truth. But twisted the words. If you ever just casually stroll around here in the forums, you'd know Bungie replies to certain feedback. But take a look at how much of it is "oh this is awesome!" or "Bungie you're the best." They only respond to things they like. Blind praise for 95% of the time. Last night was a perfect chance for Bungie to respond to a thread like mine. Was trending. Top of the board. 900+ upvotes in less than a day. What does bungie do? They respond to the thread directly underneath mine. Less upvotes by more tha. 75%. Less comments by I dont remember how much but A LOT. They didnt just miss it. They're hypocrites. They're liars. They can not handle criticism. That's why posts like mine do not get replied to. Side note...this is not an entitlement thread. I'm not entitled to anything, but it's hard to NOT reply to a trending topic with 1200 upvotes.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • Edited by TheShadow-cali: 11/9/2019 1:51:11 AM
    The straight-out truth is, Bungie talks the talk but doesn't walk the walk. Edit: You know it's BS when a company can't back up their own words. This going back on their word is actually just being totally disrespectful to the player base. The higher-ups pulled this with Dawning and later had one of the community managers come on this forum and (straight out lie saying) "Eververse wasn't intended to be end-game content". https://www.youtube.com/watch?v=m3qnr35_sZw&t=474s So Barrette comes out with this, you know, to show good faith in the changes they will make for future events, etc, right? But the one thing they do to cover their... is to use this "subject to change". That's all fine and dandy, but this company in the last 5 years has literally abused that phrase. They are constantly changing things that that phrase is just BS now so they can use that as an excuse to go back on their word. https://www.bungie.net/en/Explore/Detail/News/46567 So here comes this event, gee I wonder what happened. It's like you might as well flip a coin and ask, which event is worse? what happened to what Barret said? Does Bungie's word mean anything anymore? because this is what DMG said, more so on what the higher-ups told him to say. https://www.bungie.net/en/Forums/Post/254251970?sort=0&page=0 [quote][b]We're currently bringing feedback to the development team over the Season 8 Eververse changes, and they're looking into it. Once we have more info, we'll let you know.[/b][/quote] So, Bungie is going to wait until they grab as much as cash as they can before they change anything, you know, as they did with Dawning and made the changes later after the fact when no one gave a flying hoot about the hundreds of stupid ghost shells, sparrows, etc... So here they are again, saying we're going to make changes. Who wants to make a gentlemen's bet this next Dawning will go right back to this BS with Eververse and Bungie will use the excuse "things are subject to change" again so they can keep playing their childish games? What this all comes down to, constructive feedback whether it be negative or not means absolutely Nothing to this company and it shows how disrespectful they actually are. There is no way in hell knowing they have had 5 freaking years of way over the amount of feedback that they don't know what they are doing. Just the Dawning vid alone that I posted proves that.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

    48 Replies
    You are not allowed to view this content.
    ;
    preload icon
    preload icon
    preload icon