{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Majora:
10/21/2016 4:51:19 AM
8
Such a sad day that we STILL can't connect local! And, with no hope in sight!
How long has it been now? All we get is moderators and Q.A. Testers trying to convince people the issue is on our end. Funny how that works. But hey, would anyone really expect Bungie to own up to their mistakes?
All the people that bought multiple systems, multiple copies of the game, multiple network subscriptions. Only to find out that after a broken ass 2.3.0 update, it was all for nothing. And still, after all this time, we get the same bull crap for an answer. Bungie are "Actively investigating" the issue. That's it. No timeline. No details beyond the generic copy/paste.
I think what the are really "Actively Investigating" are plans for their 6wk vacations coming up and exactly what to cut and charge us extra for as so-called expansions in Destiny 2.
-
2 RepliesI understand the frustration, but we already know that Bungie is aware of the issue, so there is not much to do other than waiting and hoping. Also, to avoid misunderstandings: moderators are not Bungie employees, and if I remember correctly neither is that guy that has Q.A. Tester or something like that in his forum signature.
