JavaScript is required to use Bungie.net

#xur

Edited by AngryGoblin57: 8/16/2015 4:18:24 PM
123

Bungie's Transparency is Offensive (Xur, Cozmo weighed in)

So Xur is selling Gjallarhorn. To all the guardians who sought this gem but were eluded by RNG's grace, CONGRATULATIONS and I am seriously happy the pain can stop for you. However, to me, this move on Bungie's part is offensively and obviously twisted and pervasive. On the surface, they would have you believe they are opening a previously sealed door for all the people who once could not join raid groups due to the "must have Gally" demands on LFG posts. Nope. If Bungie cared or wanted you to have a raid group, THEY WOULD IMPLEMENT OPTIONAL MATCHMAKING. Nice cover Bungie. The real reasons Xur just happened to lift his trade embargo on Gjallarhorn this weekend? 1. To deflect / distract all the negative press from TTK announcements 2. To pad their activity numbers in this ridiculous lull as people wait for TTK since the year 1 legendary announcement all but destroyed grinders' reason to play. 3. To troll us. Like Bungie always does. "Here, have a Gally." ***nerfs the crap out of Gally three weeks later*** 4. To gain our favor. The relationship with Bungie gets more and more unhealthy the longer it goes. Watch out.

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
  • Yes. ...and you seem to be the unhealthy component to that relationship. Because your post is nothing but a string of cynical logical fallacies, conspiracy theory tripe, and data cherry-picking. Bungie doesn't have optional matchmaking for a very simple reason....illustrated by an experience I had this weekend. Got an invite from a player on my friend's list. I saw they were running the level 34 PoE...and I still needed it for my Titan for the week....so I decided to go join them. I arrived in the middle of the Second round of the arena. To find the two guys fighting...and not hearing a PEEP on the team chat channel. Only because I had run this arena a dozen times since the HoWs dropped was I able to fall right in, and know exactly what needed to be done in spite of the lack of communication. Only because I was running my Titan (as a Defender with Helm of St.-14) was I able to keep that lack of communication from turning into a team wipe at several key points. By dropping my Ward and blinding everythinig on the platform, I kept us from being overrun several times over the rest of the arena. I finally realized that what had probably happened is that they tried to complete the arena with one or more people without headsets...and were either struggling to do it, or someone had bailed out seeing that had handicapped itself so badly. In the final boss fight we wiped the first time, because I was reduced to SHOOTING at the airlock door's right door frame to try to communicate that I wanted the team to fight from the back right platform. They didn't understand the first time.....they did the second. We cleared the boss that second time. But all this just made for an interesting story, since I was dealing with a fight I knew VERY well...and two pretty good players who (for some reason) chose to handicap themselves by trying to clear this arena without headsets. Well with random matchmaking...I GUARENTEE you that occurences like this will be COMMON...and regularly set you up for failure. The only reason I even attempted to complete this arena under those conditions was because it was a fight that I knew extremely well...I had the right character for trying to complete it this way...and I knew that I could carry the team if it came to that. But had I arrived and found people trying to complete the level 35 arena like that.....I'd have set a land speed record on my way back to orbit and off that fireteam.

    Posting in language:

     

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

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