{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by TeWrecks:
9/30/2018 3:48:22 AM
307
So after finally spawning the servitor this happened.
Long story short, we spawned our servitor. The other team knew so they backed out and sent me the message above.
Played many many games after that one and no luck.
Edit:- I hope this doesn't happen to anyone else.
Update:- We just killed the boss and the quest dropped. I've almost stopped playing Gambit after what happened to me with these guys. Bungie really should look into this so it doesn't happen to anyone else.
Edit:- Alot of people are angry because I shared this. Believe me you wouldn't be so angry if this situation happened to you. If you ignore this, soon enough it will become a problem and people will talk about it in the forums. Also it might've happened to people who don't have access to b.net and in all seriousness ingame reporting does nothing.
-
Oh, Just another reason the quest needs a change.
-
Edited by zNapSack: 9/30/2018 4:34:05 AMTo those below who are complaining about SS in Gambit: Where in the ToS does it say Sleeper Simulant is not allowed in Gambit? Where does it say any named weapon is not allowed in a given activity? The answer is, to my knowledge, there's no such thing. Therefore, any weapon in the game can be used in any activity in the game, which everyone already knows. Bungie is aware of the Sleeper Simulant issue in Gamibit and took measures to help address it. And they may do more if they deem it necessary. I understand the frustration. We've all 'been there' at one time or another. Be patient and give it time. Such issues seldom last forever.
-
6 hours of Gambit and it's only spawned once for me, when the enemy team was seconds away from winning. FML
-
7 RepliesIf that happens, Bungie should add a mechanic that if idiots do some shit like that, that the quest is restricted for them for an entire month, or if they already have the Malfeasance, auto dismantle it. No -blam!-ing mercy.
-
Edited by xXDeViouS v2: 9/29/2018 11:59:51 PMReport them to Bungie and Sony. That's BS
-
Ouch man. Good roast, though.
-
2 RepliesWow dude... that's a dick move for real
-
4 RepliesBump for Bungie to see. You should have received an automatic win.
-
7 RepliesReport them. You have enough support now
-
Such a wonderful community
-
Can you pm me his screen name pls
-
Mind pming me those names of theirs?
-
Report for sabotage in mission results screen.
-
So you didn't get to kill it? That's -blam!-ed up man.
-
Thats messed up. So many douchebags in this community.
-
Bungie promotes cancer people, they create issues that enables worms like that to troll a shet ton of other innocent guardians. I can't for the life of me understand why Bungie decided to put this exotic quest behind a RNG boss in a PVP game mode.
-
I’ll never get that gun. So sick of rewards coming from PvP game modes. I’m burnt out already.
-
1 ReplyShouldve named and shamed this asshole. This is the kinda person i wouldnt mind getting swatted.
-
1 ReplyThis could be the poster for what most of this community is like.
-
Wtf is wrong with people :(
-
2 RepliesYou blurred the names? I wouldn't have had that mercy
-
You got screwed over and yet despite that bad experience, you got over it and completed the task at hand. Thats a life lesson right there. GG
-
Ohhh the whole team backed out i didn't know it'll end the match. At least you got the quest now you gotta play hella more gambit matches since bungie went way overboard on the gambit quest steps.
-
That’s -blam!-ing epic
-
22 RepliesIf you use Sleeper in Gambit you deserve to have that happen to you tbh.
-
1 Replyum maybe I just got really lucky but when it spawned for us it also spawned for the other team so either it spawns for both teams and they missed out on the chance to get the quest or they are a bunch of masochists who enjoy suffering through matches of gambit lol
