{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Double Dip:
3/6/2022 7:08:12 PM
1
Aye, and the maddening part is the lack of info from Bungie. The ONE thing I've read from them about the bug is from a patch note which incorrectly states they already fixed the issue, which is either a flat out lie, or they messed it up even more and don't know how to fix it so they're being quiet about it. It may be weeks before this is "fixed." I have yet to see any information from a single mod, mentor, or tech that addresses the issue or answers any questions regarding the bug. 80 or so posts I've read through in the last two days and not a ONE with an actual reply from the help desk.
English
-
My sentiments exactly. You know, at this point, having played since 2017, I wouldn't even mind if they said, "Yeah, it's broken. We won't fix it but when we release the other two subclasses, you'll be squared away"...because then I would at least have something to look forward to. It's such a shame because this season is great in almost every other way (style, story, weapons, VOID 3.0).
