{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Brazello:
11/7/2015 7:37:39 PM
8
Coconut error during matchmaking ruined my trials passage
Had 8 wins and no losses. In matchmaking the screen went black like it was gonna start and then we got an instant coconut error. Two of us got losses on our card, one didn't. I've played alot of trials and this particular event never happened before The TTK update. Disconnects should not cause losses if you haven't actually even loaded in the game, it definitely shouldn't put a loss on the card when the problem is on your end bungie. It's extremely unfair to waste so much time on a good card just to have it ruined because of the game glitching. You should really consider figuring out a fix for this and implementing it ASAP
Edit: There is a lot of glitches in the game, in my opinion, this particular glitch is one of the worst ones in the game. It really should get immediate attention along with all the other glitches involved with the trials
-
Same here, i just had an 8-0 Card, My Mercy and another loss was accrued due to the Coconut error, kicked us all out of the match before it began, im thinking DDos, anyway it just cost me going to the lighthouse. and im very salty about. they need to do something about this shit,
-
Here here I agreed
-
1 ReplyDisconnects need to count as a loss
-
1 ReplyThere is a lot of final match ddosing
-
1 ReplyThis is a serious issue as most of the accounts of this happening is with the final match until flawless. Im in the same boat 8 and 0. Friend got kicked while in flight another after we had won 2 rounds and finally I was kicked after winning another round barely. This isnt a coincidence that after 8 matches of flawless connection from me and my friends that right when it mattered we all get kicked. This has got to stop! It is making trials a lot less fun then intended.
-
4 RepliesThis happened to us earlier. 8-0 and booted to a black screen. One player lagged out causing his passage to be lost. We were 3-1 and the went back to 0-1 when the game crashed. So frustrating to beat a team twice. A good team at that. Luckily we finished our passage but friend list his flawless.
-
My fireteam got errorcode baboon some how my 2 other teammates get a win and I get a loss wtf this game seems to be against me
-
5 RepliesIt can't be fixed... because all of Destiny is Peer to Peer
