{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/5/2024 5:52:42 AM
2
Unable to Change Name Back from August 13 Erroneous Name Change
I saw the [url=https://x.com/Destiny2Team/status/1829549654905671965]Twitter post from the Destiny2Team account[/url] saying we received a new name token to fix our names if we were impacted by the erroneous mass name changes that happened on August 13th.
I've tried several times to use my new token, but the website keeps acting like it's saving my name, even asking for confirmation, but then not actually saving the new name once I close the tab (I hit both save buttons multiple times). Not sure if it's related, but when I bring up the JavaScript console in Chrome, I see a POST 500 error code, alone with another error that says:
[quote]Field "displayName" has an invalid value in it. Please provide a valid value for the field and try again[/quote]
I'm fairly certain there's nothing wrong with my name as it's not offensive and has only letters in it (i.e. no special symbols that could break the site). Can someone please help me figure out why I can't change my name?
[url=https://imgur.com/a/Ux8SAKf]Here's a screenshot of what I'm seeing when I try changing my name[/url]
-
3 답변Hello there[url=https://cdn.discordapp.com/attachments/902560216871239752/989591085506515074/Hellothere.gif],[/url] Bungie issued the tokens last week. To change one's name the new name must be in alignment with the Code of Conduct and Bungie name policy. It is worth noting that while they did fix the issue, some names that were impacted are still not able to be selected as they were before. Bungie is investigating that. You can either wait for Bungie to implement a fix for previously moderated names or change your name to a variant of your previous name.
-
1 답변Maybe it flagged the first part as Gaym? Maybe the [b]MMA[/b] part in the middle? No one is really sure. But something definitely tripped the (currently) overtuned filter.
