JavaScript is required to use Bungie.net

Destiny 2

Discuss all things Destiny 2.
4/24/2019 10:36:09 PM
11

To all the core defenders

Answer these 2 questions: How would removing cores from infusion affect you in a negative way? How would removing cores from infusion affect the game in a negative way?

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
  • #1 It won't effect me negatively at all. #2 If Bungie gives into the vocal minority, they will have to every time. And eventually, it could lead to changing all of our answers to your first question. Let's use other forum topics as examples. "I hate having to play crucible, for certain gun quests. Bungie should just get rid of pvp, all together." Or "Without raid matchmaking, I can't run the raid, so they should dumb the raids down and add matchmaking or just stop wasting time and energy building raids." Or "I only have time to play 1 guardian, so everyone should only have 1. People with more than 1, have an unfair advantage in grinding weekly activities." Or "I only play a Titan, so nerf the Hunters and Warlocks into the ground, because it won't bother me." Over the years, I've actually read posts that have suggested these things to Bungie. And Bungie refused to change their game, even though people on this forum made request posts, and even had people agree with them. It is Bungie's game, for better or worse, they get to make the choice to keep or remove cores. And they have made their choice, and given their reason. It is time for people to accept it, and keep playing. Or move on. And yes if the majority of the player base quits, it will suck for those of us who don't. But why would anyone who quits, care about those who stick with Bungie and the Destiny Universe.

    Posting in language:

     

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

    1 Reply
    You are not allowed to view this content.
    ;
    preload icon
    preload icon
    preload icon