{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Makima’s Little Woofy:
11/21/2018 7:42:32 AM
22
Primevil bug, must watch
Watch the video above guys, I haven't heard of this anywhere in the forums. Primevil spawned in, while the other team was well below us when we did . We were able to put him down before the other team could as they did not spawn their boss and had 73 motes on the board, but the win and the reward for the malfeasance went to them..... Yeah I know I have the malfeasance, but I was helping my dad and a clan mate with gambit so they can get their exotic weapon. If anybody can help report this to bungie , like any of the moderators , that would be awesome . Thank you for your time.
-
What the hell?
-
4 RepliesYou Banked No Motes. How did you expect to win?
-
That's total bollox, the invader waits until your Prime is nearly dead, then kills it and they win, WTF that's totally broken, they didn't even summon a damn prime. I suppose they've got their best team working on a super fast patch, and we'll see it implemented sometime in 2019. 😬
-
Its a known bug, sorry that happened to you
-
12 RepliesFunny thing... I opened the post and did not [u]have to watch[/u]. It's great being able to decide for myself. Muted because I can.
-
1 ReplyLol the catch-up is so strong they had to give the other team the win regardless.
-
-
Edited by Jazzle2K14: 11/21/2018 9:32:59 PMKnown bug, Bungo will never fix it is my guess. The intern potato they have to test the game fails at literally game mode 😂
-
6 Replieslol bungie you are so damn stupid
-
Haha get ur motes up!!!
-
1 ReplyThis has been going on & they are aware of it. Apparently they haven’t been able to figure out how to fix it yet. I believe even Cosmo posted about it. It was also brought up in one of the last couple TWAB.
-
2 RepliesI think the other team let you win to exploit this glitch... They are the true masters of gambit.
-
2 RepliesEdited by KEKSIS, THE BETRAYED: 11/21/2018 7:08:12 PM[quote] Destiny 2: Forsaken Known Issues In addition to the items listed above, Destiny Player Support is tracking the latest issues reported by players on the #Help forum. Provided below is a brief overview of the latest known issues in Destiny 2: Forsaken. Gambit Malfeasance Boss: We are investigating issues where a team will defeat the Ascendant Primeval Servitor, but the opposing team receives credit for the kill.[/quote] You know what would be a nice fix? Making a system that detects when that happens and just gives both teams the credit. That way the team that got it fairly still gets it, and the team that got it unfairly doesn’t get it revoked from their inventory.
-
Working as intended - Bungle #playOURway
-
Edited by PhEnOm: 11/21/2018 6:47:22 PMCongrats to the other team. They never gave up and were rewarded for their effort.
-
2 RepliesWorking as intended.
-
Edited by Ray: 11/21/2018 4:45:35 PMIts been a known issue for a while now and literally has been talked about a lot here. Don’t know how you could’ve missed that. This does suck tho. Idk what’s worse. This or having the opponents leave during the meatball and we get the win but not the drops
-
Whaaaaaaaaat?? That sucks
-
Bump.
-
1 ReplyIt's been a know issue since the meatball began to appear, and it apparently had multiple causes. They thought they had fixed it in a previous update, but this is from TWAB, in reference to the patch that's coming on the 27th: [quote]Ascendant Primeval We identified (another) issue that was causing the Ascendant Primeval to not always award credit to the correct team when killed, and we fixed it.[/quote]
-
2 RepliesHoly hell thats bad.
-
Terrible.
